Correct, currently it will duplicate the closure as is and it will require a manual change before save.
We are aware of the feedback and we are already working on improving it.
I’m sorry, but I have to say it. This sort of comment isn’t helpful.
What scripts are broken? Of all the scripts I am using, I have seen a minor impact on one script: an impact probably caused by the changes to the map footer, where Toolbox puts it’s Fancy Permalinks. That change has been in Beta for a while as far as I am aware, so the Toolbox devs are presumably aware.
Changes to WME will inevitably have an occasional impact on scripts. Testing in Beta will often provide advance warning of that: and I freely admit to not testing my script in Beta as often as I should. But when a Beta->Production update breaks my script, that’s my fault, not Waze’s.
In the meantime, Waze are making strong efforts to work with the script-writers compared to a couple of years ago. They try to warn us of changes they think might break our scripts and they are working actively with some of the script writers to develop ways to avoid breaking changes.
At the top of the Scripts sub-forum is a post I made back in 2014 about being nice to the script authors. I asked people to not just complain, but be helpful and try to provide useful information when there’s a problem. I don’t imagine the Waze devs enjoy being criticised any more than I do. Whether you’re paid for it or not, your code is your child and you feel protective of it.
Release topics like this aren’t for scripts. But I don’t see anything wrong in posting here if an update breaks a few scripts: many people will come here when there’s an update, so it’s a good place to let them know. Discussion of individual script problems can then continue on the topics for each script.
In this case, I don’t see any large-scale problem with scripts, so “Scripts are broken once again” doesn’t help anyone at all and is somewhat inflammatory, when most of them aren’t. Let’s get some details of what’s broken and why - and then come back here and help Waze to understand.
Minor issue: the permalinks created from this feature sometimes (maybe depending on current locale?) point to waze.com instead of www.waze.com.
This one doesn’t seem to work quite as expected:
After switching to snapshot mode, I’d expect the dropdown right next to the Waze logo to change from “Map Editor” to “Current live map” but that doesn’t happen. Instead, the only indicators are the light blue highlight (while the dropdown is open) and the informative overlay in the bottom left corner of the map.
After switching back to edit mode by clicking “Back to editing” in the overlay, the light blue highlight in the dropdown stays with “Current live map”.
I did not use this feature enough while in beta because of Falcon raiding, and don’t remember comments made off hand. Once the check box is changed (checked or unchecked), the option should be persistent. Layers should remain off until the editor enables the option again.
Correct, we have an internal bug opened as when changing to Live Map, the drop down menu still shows the text “Map Editor”
Thanks for flagging, we’ll keep you updated!
I think I just found another issue with the new WME release: the list of area managers doesn’t seem to be available from the segment properties panel anymore.
I think, there’s a problem with the URs in the feed. In my editable area (entire Germany and half of Belgium) the latest URs are from yesterday morning (january 26 10:00 UTC). PURs seem to come in (latest PURs about 5 hours ago).
