- Issue created by @fonant
- Status changed to Closed: cannot reproduce
5 months ago 7:56am 25 June 2024 - 🇮🇹Italy itamair
Thanks for reporting this @fonant
BUT I cannot reproduce the this Bug you report.This Leaflet Demo View Page:
https://www.geodemocracy.com/drupal_geofield_stack_demo/web/geoplaces-ma...is indeed using:
Drupal Core: 10.2.2
Drupal Leaflet Version: 10.2.18and < node entity via ajax > as Leaflet View Popup settings (screenshot attached),
and it doesn't report any Leaflet Popup functional issue (even in its inspector).The issue you report doesn't look like a general Leaflet module bug, but might depend by/from you specific Drupal app instance configuration ...
Closing this as "Cannot Reproduce".
Please reopen ONLY if you find (and can prove) evidence of a general Leaflet module Bug on this functionality.Regards.
- 🇬🇧United Kingdom fonant
More information, although I haven't narrowed down the symptoms enough yet:
I have a map that has working popups in the node view page (it's a View Reference field), that fails in exactly the same way when I edit the View (without making any changes) and try to get the popups in the View Preview.
Working:
- Leaflet map view, added to Node display as a View Reference.
- Map displays entity references from four different Node reference fields from the current node.
- Four contextual filters using "Content ID from URL" defaults for "When the filter value is NOT available".
- Popups loading content using "< node entity via ajax >".
Fails:
- Edit the above View.
- Enter the NID four times in the Preview arguments (e.g. 1234/1234/1234/1234).
- Click on a marker in the Preview: popup appears for an instant then disappears. Same error as in summary.
- 🇬🇧United Kingdom fonant
Could it be that the AJAX mechanism needs the page to be for a node?
The other maps that break with "< node entity via ajax >" are those for a View that's not embedded in a node display.
These views used to work in previous versions of Leaflet and Drupal. Only broke in the last few days.
- 🇬🇧United Kingdom fonant
Hmm... another difference I've found:
The maps that fail to open popups contain an additional command in the AJAX returned:
{ "command": "add_css", "data": [ { "rel": "stylesheet", "media": "all", "href": "\/core\/themes\/claro\/css\/classy\/components\/node.css?sfkw3v" } ] },
whereas the maps the work only contain the popup HTML insert command:
{ "command": "insert", "method": "replaceWith", "selector": "[data-leaflet-popup-ajax-entity=\u0022node-2294-map_popup_balloon-en\u0022]", "data": "<pop-up-html-here>", "settings": null }