You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be the same or related to #22 but I can't be sure from its description. I apologise that my problem description may also be vague and difficult to reproduce. It has been tricky to pin it down to a pattern. I'll try to describe my environment comprehensively, please let me know if more info is required.
The behaviour I see is that when I enable caching on a page with maps, the map (and library) load the first time, but not on subsequent refreshes - obviously I see a blank div where the map should be. The javascript code is not included in the source. This is easy to work around for individual pages (using cache_enable in frontmatter but it would be better to find the cause :)
I have the same experience so I decide to add the google-maps JS-lib by twig {% do assets.addJs ... %} within the page.
This shows the same behavour like discribed in the issue.
Everything works finde with chache_enable = flasefor this page.
The problem seems to be that Google doesn't want you to host the Maps javascript. I resolved this issue once and for all by replacing the addAssets() with a hardcoded script tag in the template.
This may be the same or related to #22 but I can't be sure from its description. I apologise that my problem description may also be vague and difficult to reproduce. It has been tricky to pin it down to a pattern. I'll try to describe my environment comprehensively, please let me know if more info is required.
The behaviour I see is that when I enable caching on a page with maps, the map (and library) load the first time, but not on subsequent refreshes - obviously I see a blank div where the map should be. The javascript code is not included in the source. This is easy to work around for individual pages (using
cache_enable
in frontmatter but it would be better to find the cause :)I have extended your plugin to add support for map Places shortcodes but I don't think my extensions modify any original plugin code. (When I have time to make the code more generic, I will submit my fork with new features as a pull request.)
Asset pipeline settings seem to make no difference, as I originally thought that was the problem.
I'm running Grav on nginx with the following plugins, all up to date:
I also have three custom plugins but none of them use Javascript at the moment. I'm extending the Antimatter theme.
Hope that helps. Please let me know if you require more details.
The text was updated successfully, but these errors were encountered: