Help with MapsExtended (possible bug?)

Hi Macklin!

I am Nekky-chan, the German Wiki Representative, and I am using the MapsExtended script for a community project. Despite all the efforts I made trying to set up the script, it seems like, the search functionality is not working properly. It is similar to the known issue "Clicking entries in the search box does not display marker popups for markers that are hidden outside of the viewport.", with the only difference that all markers appear in the viewport. Clustering is disabled as described on the script's page.

I am no JS expert, but clicking on the marker in the search result does not trigger any event to show the position of the marker.

This is the map and this is the configuration.

I appreciate any help and advice from you!

Best – Nekky-chan (Message Wall | User contributions | Social Activity) 16:24, 7 August 2023 (UTC)

Heya Nekky-chan, thanks for reaching out!

I've identified and have resolved the issue, thankfully it was just a simple oversight on my part. The script uses a series of checks to match marker elements in the DOM to marker definitions in the JSON, one of which is to compare the image name that is used in the JSON with the name of the image on the marker element itself. It normalizes the file names, including the namespace prefix "File", but I've neglected to do the same for non-canonical namespace names (i.e. like "Datei" in German). As such, the markers weren't being matched correctly, which had a cascading effect across functionality that required this.

Very much appreciate the info you've provided, it helps immensely with diagnosing these sorts of issues. The fix should be live as soon as it is reviewed.

Thanks again, and feel free to message if you encounter any other problems. - Macklin (talk) 17:17, 7 August 2023 (UTC)

Thanks for the quick fix, I really appreciate it! :) – Nekky-chan (Message Wall | User contributions | Social Activity) 17:37, 8 August 2023 (UTC)

Thank you for InfoboxTabberLinks!

Hi Macklin, I'm Jane! I just wanted to reach out to express my thanks for the InfoboxTabberLinks script - I recently converted our infobox templates to portable infoboxes and was at an absolute loss when realizing that we could no longer directly link to our tabs. I ended up using a different code snippet than the one you provided, but I wanted thank you for recreating this older (more useful) functionality in the new infoboxes for posterity - it's going to help many editors! Cheers! JaneBuzJane 02:11, 9 November 2023 (UTC)

RE: Moving InfoboxTabberLinks

Moved now. We had a misconfigured AbuseFilter, which I didn't immediately realize when trying to move the MW page, so I asked Staff to do it. -- Cube-shaped garbage can 21:53, 11 December 2023 (UTC)

Many thanks! - Macklin (talk) 08:49, 12 December 2023 (UTC)

Suggestion on HTML5AudioPlayer

Hi. I'd love this extension to allow a number of audio files to be played automatically in turn, like in an actual online album. FAVA5URko (talk) 07:26, 14 December 2023 (UTC)

Did the visible categories broke all of sudden on the map extended

I haven't touched it for awhile it was working fine.

https://moc.fandom.com/wiki/Towns

https://moc.fandom.com/wiki/MediaWiki:Common.js

Just fixed this, should be live once its reviewed. Thanks for letting me know! Macklin (talk) 05:11, 28 July 2024 (UTC)

Help with MapsExtended

Hello! I am trying to use it for https://northwinds.fandom.com/wiki/Map:Isle_of_Rupert, and I keep getting this error;

ext.fandom.ImportJs-script-0.js:7348 Uncaught TypeError: Cannot set properties of undefined (setting 'marker') at ExtendedMarker.init (ext.fandom.ImportJs-script-0.js:7348:38) at ExtendedMap.<anonymous> (ext.fandom.ImportJs-script-0.js:1298:36)

and the nested categories are indeed visible but it can't interact with the map. I absolutely don't know what I am doing but I have seem to got it down for the most part, do you see anything wrong? NotEmir (talk) 19:10, 10 April 2025 (UTC)

Hey, thanks for reaching out! Unfortunately the script doesn't yet support the new canvas implementation, I just haven't had time to do so. If you want to get it working in the current state, you'll have to contact User:CuBaN VeRcEttI (or Fandom support) and ask if you can switch your wiki over to the old element-based system for maps, although by doing so you'll lose the performance benefits of having the canvas-based system. Plus, I'm not entirely sure if they'll agree to doing so to begin with, as I think keeping wikis (that already had the script installed) on the old system was more to maintain support rather than have it as a "switchable" option for new wikis. Never know unless you ask, I suppose. Or you can check back sometime later, likely a few months time, and I might have updated the script by then :P Macklin (talk) 10:36, 11 April 2025 (UTC)

Let's say I wanted to modify an implementation myself, which parts would I need to modify? NotEmir (talk) 11:01, 11 April 2025 (UTC)

It's basically a rewrite because the fundemental concept is entirely different. The way the script worked before was more of a hack than anything, it intercepted changes to marker elements rather than interfacing with Leaflet or creating a map from scratch. An update would be independent of Fandom's implementation, and would make the maps from scratch, plus all the same features that were handled on the Fandom side (but also implement my own version of canvas markers). There is no API to Fandom's implementation, they've not designed it to be interfaced with, so hacks were the only option if I wanted things to be Fandom-flavoured.

However, I have just looked closer, and it seems they were kind enough to indeed use a canvas depending on a flag (rather than keeping seperate versions entirely like I was led to believe), although I think it's set-on-save server-side based on some internal flag that controls whether the wiki should or should not use the canvas implementation. You can see it being set per-map in the "post-processed" config, the one that is eventually loaded into mw.config client-side (canvasEngineDisabled at the bottom) (example). Still unsure if this is controllable without staff intervention in any way, i.e. using the map namespace config, I checked and I couldn't find the name of a property that influences it, which is what led me to believe it's done internally.

If I wanted the quickest path to just making it work again (again, without staff intervention), I'd override this property on all configurations in mw.config.values.interactiveMaps as early as possible, easy to do but not at all bulletproof because loaded site/user scripts are run pretty late so it's very likely to miss the initialization of the map entirely. There are ways to force reinitialization, but they have their own issues too and it becomes a bit of a rabbit hole. Macklin (talk) 13:27, 11 April 2025 (UTC)