Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No map displayed #1

Open
davilima6 opened this issue Aug 17, 2016 · 5 comments
Open

No map displayed #1

davilima6 opened this issue Aug 17, 2016 · 5 comments

Comments

@davilima6
Copy link

davilima6 commented Aug 17, 2016

I tried the thet-cleanup branch in a coredev buildout, also getting plone.formwidget.geolocation and plone.patternslib from their respective latest branches, respectively thet-plone5 and master.

I stopped seeing the map after leaftlet was implemented. Is there any direction I'm missing? /cc @thet

image

The TinyMCE errors seem unrelated. In default view, they do not appear (i.e. possibly breaking the pattern).

@davilima6 davilima6 reopened this Aug 18, 2016
@woolyseal
Copy link
Member

I encounterd the same Problem without any evidence of failure in my Firebug. Any suggestions?
Versions:
Plone = 5.0.6rc1
Plone Patternslib = 1.0
collective.geolocationbehavior = 1.5.1

@thet
Copy link
Member

thet commented Jun 8, 2017

Not sure about that ... Maybe the leaflet bundle from plone.patternslib - installed via plone.formwidget.geolocationbehavior - is missing or not compiled?

@woolyseal
Copy link
Member

I installed "collective.venue [geolocation]" and tried it out, afterwards the behavior worked to. Don't exactly know why, because everything was on board and compiled before, too.

@woolyseal
Copy link
Member

So. I deinstalled "collective.venue [geolocation]" and made a set back of in my versions.cfg from
plone.registry >= 1.0.4 to
plone.registry = 1.0.4

Now the map won't show. Are there depencies with the registry, which are not mentioned in the setup.py?

@thet
Copy link
Member

thet commented Jun 8, 2017

I could imagine, that this change makes a difference. Although collective.venue already worked for me in different contexts and Plone 4.x.

https://github.com/plone/plone.registry/blob/master/CHANGES.rst#110-2016-07-05

I recommend to use the latest available Plone 5.1 release as a basis, though. It's much better.
http://dist.plone.org/release/5.1-latest/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants