Customize Map Feature not working

I'm new here and trying things out. I am a paying subscriber. When I try to change the map style and Click 'Save these Settings', I get a a yellow "Saving" message , but it never goes away, and the customization is not kept.

That is annoying! I just tested it, and the functionality works for me, so we're going to need to isolate what's different for you that's causing this bug.

Which browser are you using?

Could you hit F12 to open the developer tools, switch to the "Console" tab in there, click on that "Save these Settings" button and see if any new errors or warnings appear in the console?

Are you using any adblock/privacy extensions which might be blocking part of the necessary JavaScript for this functionality? (tp.daa.ms, mapbox.com and maptiler.com all need to be allowed) - this is unlikely to be the issue, since you probably wouldn't have a functioning map in the first place, but just ruling it out.

[ Edit: Edited on 29 Jan 2023, 09:50 GMT by Sander ]

I have tried it in Safari (Venture 13.1) also on apple in Microsoft Edge, Google Chrome and also on Microsoft Edge in Windows 10. I have the same issue using iPhone and iPad.

Error message is
Unable to perform style diff: Unimplemented: setSprite.. Rebuilding the style from scratch.
hr @ Map.b8461330.js:1

Thanks. I think this'll need Peter (the admin) to have a look. I still can't reproduce, but maybe this is an issue only affecting people who have never set a custom style yet. In any case, the error message should help Peter pinpoint where the issue is. I know he's busy working on map updates at the moment, so a fix might take a while, depending on how closely related this is to other things he's working on.

Thanks for looking into this.

Quoting Sander

I still can't reproduce, but maybe this is an issue only affecting people who have never set a custom style yet..

Good guess there! That was indeed the issue and kind of crazy that no-one else (to my knowledge) has hit this yet until now. The changes this is related to date back at least 4/5 months by now.

I've just pushed a fix for this. Should be working on the site in the next 5-10 minutes.

Thanks for alerting us to the problem @williamhamilton

[ Edit: Minor ]

It is indeed working now. Thanks.