Following community feedback, the team has announced a revamp of the Update Request (UR) email flow. This new version focuses on clarity, better context, and more informative automated communication to support your map-editing contributions.
This change has gradually rolled out to IL and NA over the past week. Next week, the updated email flow will launch in ROW as well.
Please share your feedback, suggestions, or thoughts about the feature in the feature thread.
SDK improvements: please refer to the change log for the latest updates .
Bug fixes:
We released 4 bug fixes:
Suggest an Edit: We have addressed one of the scenarios of the issue where a white space added to an existing city or street name was not trimmed. This created duplicate entities and forced manual ‘Suggest an Edit’ requests instead of applying updates directly. Spaces are now automatically trimmed. (Bug ID: 402340)
Turn Locks: We fixed a known issue (mentioned in the WME 2.352 post) where connecting a node to another segment incorrectly showed a green (allowed) U-turn icon before saving. The icon now correctly displays as red (disallowed) both before and after saving.
Reduced URs load: The team resolved an issue where multiple URs submitted in a single session sent email notifications referencing only the first report, forcing editors to manually search for the others. (Bug ID: 402961).
UR Responses: The team fixed a bug that caused a single reply to an Update Request to be posted multiple times, resulting in duplicate emails for the same Update Requests ID. With this fix, replies won’t be duplicated, ensuring only one email is sent per response. (Bug ID: 403998)
Apparently there is a new script incompatibility in this version with WME Image Overlay, which is totally strange, considering the “bug” that appears when it is enabled.
After selecting multiple segments, on deselect the middle nodes, the FL2 Far turn icon and/or merge icon stay visible, along with the “selected state” direction arrows on the segments (in dark green color). Obviously, as this is a script, this is just for information.
The inbuilt streetview seems to fail since this new WME update. When I drop the streetview peg on the map, it opens the right hand streetview window up, but no imagery is displayed, with it having a layers panel that you can’t interact with instead.
I have tried multiple combinations of refreshed tab load and without scripts.
Also, intermittently when clicking through various open URs, the map doesn’t move to that UR location or open that UR, it just stays where it is. A reload of the WME tab resolves this, but it starts again after a few minutes.
Why is the closure event field without a default value after the update? Most small closures don’t have an event and it’s quite tedious to select None now. Can we please bring the default “None” back?
Why do we get changes that aren’t mentioned in the change log?
Bonus question: could we get the default “None” for turn closures as well?
As it was pointed out, it’s a script problem. My bad.
Hi Nataliia, this happens 100% of the time, anywhere in the UK for me, so there’s no benefit to me sharing specific permalinks (unless you really want a couple??).
I’ve just tried it again today with my usual scripts, but also with all scripts (and the script manager) turned off and I get the same experience as pictured above.
Firefox 151.0.3 on a Macbook Pro, if that matters.
“That change isn’t allowed at this time and won’t be sent for review”
on some edit suggestion (not all), I can’t approve the suggestion, I got the error message : That change isn’t allowed at this time and won’t be sent for review (in a text box below) and save button stays grey out.
