We’ve just released a new version of WME prod, v2.242.
Below you can find a summary of the release.
Known issues:
Compact mode: Road details: Selected chip looks pale while hovering in compact mode.
Issue Tracker: clicking comment number buttons does not always light them up blue (selecting them).
Venues: The last category under the venue could be deleted, but the save stack is empty. When you re-select the venue, category is still there.
Remove my own suggestion: The status of the suggestion may temporarily display as “Awaiting Removal” after clicking the “Save” button. This can be resolved by refreshing the page.
Saved search: ‘All issues’ should be marked as default in case custom default search is deleted. EDIT: Notice, updated after a sync with the Script Author
We’ve discovered a compatibility issue with certain scripts and this new WME version.
If you are using the PIE script , you may find the Map Editor crashes. We suggest to disable the place name ability of the script, until the script is updated. We apologize for any disruption and inconvenience this causes. We understand how crucial these scripts are to your editing flow and are in touch with script writers to further solve the issue.
We’re also actively working on a WME SDK that will hopefully provide a more stable framework for scripts and ensure better compatibility between scripts and WME. Community suggestion: We have implemented 1 community suggestions
- Include layers settings NOT marked as default: going forward, we won’t include the layer URL parameter by default. New features/enhancements:
1.Unify Action Areas- Welcome Revamped Design: We’ve taken your feedback to heart and completely redesigned the Unify Action Areas feature. Please read all the details about added changes and improvements in the dedicated post.
Please find more details and share your feedback in the dedicated post: link here. 2. More Complexity for House Numbers: We are happy to announce that with this release we are expanding the types of House Numbers you can now map in the WME.
For more details and to share your feedback, please visit the dedicated post link here.
Bug fixes:
We released 14 bug fixes:
MapComments - Follow Conversation status wrong - an additional part of the fix has been implemented
Junction Box: Selecting the entry/exit segment of the JB causes WME to be stuck - fixed.
Closures don’t appear on streets when zooming in (require refresh) - fixed.
Street view arrow is not visible until you move the map - fixed.
Lane guidance (selection pop-up) out of place - fixed.
Saved search : Open Issue tracker tab while opening the shared filter - fixed.
Saved search: Update zero state (All issues) filters configuration - fixed
Saved search: predefined searches should have the option to set as default - fixed.
Saved search: There is too much spacing between the action buttons for set as Default filters - fixed.
Saved search: No space is needed between the section header and menu - fixed.
Saved search: Unnecessary scroll in case there are 7 saved searches - fixed.
Permanent hazard: mapping new PH doesn’t have a visual indication of which segment it is added to - fixed.
Venues: Merge popup is out of the screen - fixed.
Hamburger menu does not close the left panel - fixed. We apologize that we can’t attach the standard release notes today. Please use the link below to read about the changes in this version. We’re addressing some technical issues and will update you once they’re resolved. You can read more here.
We look forward to hearing your feedback!
I’m sad to inform you and note that the new release breaks the normal editing process again. The Issue tracker stopped displaying any issues in the list, they are only displayed on the map (using saved searches). Now I see they started appearing again, but can’t be certain what is there and what not.
The Saving process led to white overlay freeze several times. As the script that had anything to do with this overlay is disabled due to the previous updates, I can’t think of the reason this happens. However this is preliminary reporting without extensive testing.
The URComments-Enhanced script is once again broken and does not load properly the URs (after filtering stopped working with the previous update) and sadly the Issue tracker does not yet provide enough flexibility to filter URs by their lifecycle status (answered/not-answered in the last 3/7 days etc.). The date filtering is still very limited and doesn’t provide the necessary logic and the Issue tracker does not provide the functionality for handling issues with the predefined answers and actions we get from the script. So, again, breaking scripts is not nice at all. We already have to work with a limited feature set and a limited number of scripts as many authors just don’t want to invest the time to keep changing the scripts to account for WME changes. A very sad situation, as this influences our “work” with the WME.
P.S. The “Update results when map moves” check box status is not saved with the search, but is getting reset when a managed area search filter is selected. Thus, it always gets deselected and we need to remember to manually select it each time. Please make this option either savable with the search or saved together with the other settings in the profile. Thanks!
I also want to report a bug regarding the Magic script, which seems to be broken. When I use it to display a section, the panel goes completely blank, and it’s impossible to interact with the interface at all. I’ve attached some images showing the issue:
I’ll also mention this to the script creators. As EloheiYishi said, “Breaking scripts is really unfortunate. We already have to work with a limited feature set and a limited number of scripts, as many authors don’t want to keep updating them to accommodate WME changes. It’s a very sad situation since it affects our work with the WME.”
It would be nice if Waze ‘tested’ changes to the editor by first presenting them in the beta version of WME and allowing a suitable test period to elapse before the changes are made to the production version.
Said ‘test period’ to be a minimum of several days or a week. You should be able to estimate the length of the period by studying the disruption time that previous releases made without such a delay have caused.
It would also be a good idea to make sure that those who edit the editor are familiar with the use of it AND the extensions that we volunteer editors use on a daily basis in order to make our jobs easier.
Best to address this in the forum thread/Discord channel for the Magic script.
If by “changes” you mean the new side panel, that was in WME beta for some time before being released to WME production today.
For a variety of reasons the developers have never designed WME around the community-developed addons/extensions/scripts. That’s just not how it all works.
They do all of those things. Feel free to ask your RC to be added to the WME beta program to help test for issues. They even announce to the script writers all (or most) of the changes that are coming ahead of time.
To be honest, I didn’t like the new layout. I’ll miss the old layout :(. Whose idea was it to hide frequently used tools in an additional menu by changing their location??? I didn’t like or use compact mode anyway, but this update is similar to it. I’ll have to learn the shortcut keys.
The new side menu is not translated at all and is not up for translation on Transifex at the time I’m writing this message. I’ve highlighted some French text to show you that I’m using the French localization.
The new left panel has been in Beta for several weeks, if not longer. As for the scripts, there have been many, many, many conversations between script writers and developers over the past year+. Developers understand there is a role for scripts in the editing process. Many script writers choose not to test in the beta environment because it’s often different than production, and it’s not practical or feasible to maintain 2 different sets of code within one script, especially if the beta code breaks the production script and vice versa.
Finally, as a general aside, Waze and Geo staff are VERY AWARE of how important the community is to keeping Waze a viable entity. Complaints (and I’m not singling you out this time Bob) about failing to take community feedback into account when making design changes are simply unfounded at this time.
Good afternoon, I believe that some study, or analysis, or etc. has been carried out.
But I didn’t particularly like it and I don’t see how adding another menu layer can “make editing easier”.
We have no idea where you are referring to and this is not the right forum to post. Please contact your local community via the appropriate forums here
A very sad situation, as this influences our “work” with the WME.
