New WME v2.278

Map Editors Community WME Production Version Releases
1

Hi Everyone :wave:

We hope you’re all doing well.

We’ve just released a new version of WME, v2.278.

Below you can find a summary of the release.

New features/enhancements:

  1. We’ve continued to refine the unify action areas menu based on your input: we’ve added diagonal transitions for submenus, a slight delay when moving away from a menu item and safe zones. You can read more about it here.
  2. Added a missing tooltip to the Request Updated Imagery button for better UX clarity.
  3. Added a tooltip to the New City Name Suggestion on the Suggest an Edit suggestion card, informing users that the suggestion cannot be accepted or rejected with the current Editor rank.
  4. Reduced the list of countries in the Community Schedules create scenario to only show those where users can create a schedule.
  5. Added sorting functionality to Community Schedules by Name, Last Updated and Country fields. Sorting by Used in will be introduced later.
  6. Updated Timeframes to now start on Monday for both Community Schedules and Local Schedules.
  7. Updated minimum zoom level for house number editing to zoom level 18 to strike a balance between usability and map performance. This is an infrastructure change needed to display HN starting at zoom level 17, following community feedback. In bigger screens, HN might not appear in zoom level 18.
  8. Removed the “Forced” badge from house numbers for a cleaner UI. This is a UI-only change, and the underlying functionality remains unchanged, still allowing the same behavior for house number management.
  9. SDK improvements: please refer to the change log to check the SDK additions.

Bug fixes:

We released 15 bug fixes:

  1. Fixed a crash occurring when clicking the PUR “Review” button.

  2. Fixed issue where the “Add House Numbers” button was unresponsive when streets contained both locked and open segments.

  3. Fixed an issue where nodes were unintentionally detaching due to a visual bug.

  4. Ensured the “Apply” button remains visible and functional regardless of the number of restrictions.

  5. Fixed an issue preventing segment splitting after a geometry change when house numbers were present.

  6. Fixed an issue where tooltips in the top bar were obstructing interactive elements in Firefox.

  7. Updated UI to correctly reflect the disabled state of the ‘Voice Prompt’ on the turn card.

  8. Fixed issue with the ‘Back to the List’ button in Community Schedules returning to the first page instead of the correct one.

  9. Fixed an issue where the bottom edge of the ‘Except on’ section was cut off on the Community Schedule Summary page.

  10. Fixed an issue where buttons on the Share on Waze Forum feature were unreachable in the English (Australia) language setting.

  11. Updated the tooltip for Clustering to reflect plural instead of singular.

  12. Fixed an issue preventing Editors from deleting closures on a segment in some scenarios.

  13. Fixed an issue where using the keyboard shortcut to create roundabouts would cause the system to get stuck in ‘roundabout creation’ mode.

  14. Fixed an issue where the “Restriction’s date range has expired” tooltip incorrectly displayed for restrictions set to repeat every year…

  15. Fixed an issue where search results details were being cut off in the UI.

You can read more here.

We look forward to hearing your feedback! :disguised_face:

35 Likes
Nova versão do WME v2.278
New WME v2.275
Wme - search results (off screen)?
2

Also this was fixed. When I reached over 25,000 edits, I can no longer save edits and my level hasn't increased to L3 Thanks to everyone who was involved.

6 Likes
3

It’s great to see so many bugs fixed in one update🤩

2 Likes
4

Excelent update!!
A lot of bugs fixed!
thanks!

1 Like
5

A post was split to a new topic: Inability to Connect Segments After Split

6

Thanks for these improvements!
The diagonal transitions and menu sensitivity tweaks will definitely make editing smoother

Appreciate the team’s effort in addressing these issues - it will help a lot of editors! :clap:

1 Like
7

This fix made using the menus much easier! :slightly_smiling_face:

1 Like
8

Appreciate the effort on updates and bug fixes.

I have a new one that has been a problem for at least a week and still happens with this new update.

I click on a UR and it takes me to the new location for that report (no problem).
But, often (but not all the time) if I drag the screen in that area to click on a segment, or even click to open Waze Street View, I will get jumped back to the previous location where I last edited.

I have not yet determined the cause, but it happens about 70-80% of the time - - unless I do a full refresh.
JB

3 Likes
9

Hi @JB15TM
This bug is reported here

1 Like
10

Since this is regressions of an existing functionality (displaying why a HN needs to be or cannot be forced), are there plans to improve communicating the nature of each HN error to editors?

5 Likes
11

This was addressed here.

1 Like
12

Excellent, thanks!

1 Like
13

Thanks for an update well done. Lots of bugs are gone now. So far, I haven’t found anything to mope about at all. :wink:

1 Like
14

Great to see so many improvements and BUG fixes, thats going to make editing better :+1:

1 Like
15

Hi @Daria_Staff,
It seems that the rejected image reappearing bug still remains in this version. Any update on when this will be fixed?
Cheers,
Eddy

16

Thank for the submenus update. It is much better. Adding shelters over the last week has been, shall we say, challenging :upside_down_face:

1 Like
17

Muito bom. Facilitou na criação de novos lugares, já que o nome está no local.

1 Like
18

i’ve noticed that, you are unable to double click on the name field of a street or venue to highlight it (to either remove text or copy)?

19

A post was merged into an existing topic: Cannot add more than one HN at a time

20

Hello, thank you for bringing this issue to our attention. We’ve reviewed it carefully and found that the area affected is scheduled for significant improvements in the near future. These planned changes will address this issue as well, and we’ve decided to prioritize those improvements. To avoid unnecessary rework, we’ll be focusing our efforts there rather than on a direct, immediate fix. In the meantime, we recommend using the workaround. I’ll be sure to keep you updated on the progress of the upcoming improvements.

3 Likes