New WME v2.318

Hi Everyone :waving_hand:

We hope you’re all doing great.

We’ve just released a new version of WME v2.318 :tada:

Below you can find a summary of the release.

Community Suggestions:

  1. With this release, we are happy to announce that you will now receive 1 map edit point for each UR that you close.
  1. Based on your feedback (available for WME Beta testers only), we have added a warning when applying restrictions to an entire segment.
  • This change introduces a warning mechanism to prevent editors from mistakenly applying high-impact restrictions to an entire segment. It also enforces lane selection by disabling the “Add” button until a choice is made.

  • Key changes:

    • The “Applies to” dropdown now defaults to “None” and is a required field.
    • A warning is displayed when applying high-impact restrictions (Bus, HOV, etc.) to the “Entire Segment”.
  • Uservoice Suggestion: Warn if adding restrictions (bus, hov, …) that apply to all lanes

  • Thank you @sh-oded for raising this suggestion and all others for upvoting.

  1. Suggest an Edit and URs: Removing submissions from inactive users.
  • Following a request from the Italian community, we’ll be removing both Map suggestions and Update Requests (URs) submitted by inactive users. This will help keep the map clean and clutter-free by removing outdated or no longer relevant suggestions.
  • The process will be run periodically meaning such suggestions and URs will not be removed straight away; however, if you see any inactive users’ suggestions/URs exceeding 63 days, please let us know.
  1. Additional House Number patterns in RPPs and venues: following your suggestions for adding additional formats - adding a space and point (.) is now allowed in HNs for segments as well as HNs in RPPs and Venues.
  1. We’ve made a change: the snackbar notification (pop-up “Click on map to start drawing…”) that appeared when creating polygons is now disabled for editors with level 2 and above.
  • Thank you @JohnDoe75 for submitting this suggestion and everyone for voting!

New features/enhancements:

  1. Koi Fish permissions: We introduced a change in WME to improve permissions handling forKoi Fish suggested segments. When an editor does not have editing rights in a specific area, they will no longer be able to accept or reject Koi Fish suggestions there. Instead, a note will be displayed in the panel to inform the user about the restriction.
  2. Closure Status: With this version we changed the “Finished” closures string to “Ended”.
  • This update has been implemented for several reasons:
    • Clarity: “Ended” is a simpler, more accurate word for an event that has concluded.
    • Natural Language: This change uses the same language people use in real life. We say “the meeting ended” or “the quarter ended,” not “the meeting finished.”
    • Better User Experience: By using a word that feels natural, we make the site easier to use and understand for everyone.
  1. Style update: We have updated the UI of the spinner upon WME reload.
  2. SDK improvements: please refer to the change log to check the SDK additions.

Bug fixes:
We released 18 bug fixes:

  1. Error loading object history: resolved an issue where it wasn’t possible to view the history of a segment or place.

  2. Hazard icons: rectified the bus lane camera icon.

  3. School Zones & Scheduler: we addressed an issue where a ‘Schedule is expired’ message and red ‘Expired’ dot are shown, even though the schedule is set to repeat annually and functioned correctly in the app.

  4. On Segment suggestions (OSS): resolved the issue that the invalid tooltip was displayed in case the change was already applied to the map.

  5. Closures: resolved an issue where clicking on ‘locate’ on closure cards would not allow selecting any segments before map refresh.

  6. Search bar: fixed an issue where trying to navigate to the same searched location would fail on subsequent attempts.

  7. Location marker: previously, the marker was cleared whenever the map was moved. Now, the marker is cleared only when selecting another feature on the map.

  8. Venues: an issue was fixed where uploading an image to a Venue in the WME would generate a PUR that didn’t include the image. Approving the PUR would not add the image to the venue.

  9. Map Events Filtering / Duplicating:

  • Fixed the issue that the unverified, failed or finished closures are not highlighted on the map after hovering them.
  • Addressed the problem that when refreshing the map button doesn’t refresh the event’s list in case the user filters by specific area.
  • Resolved the issue that there is no alert to activate the closures layer.
  • Handled the issue that the failed closure isn’t locked for editing and verifying.
  • Implemented a change and removed redundant elements from the edit closure/proposal view.
  • Fixed an issue where the duplicated event’s details window closed automatically after opening the ‘Road closures’ tab. It now remains open.
  • Resolved the issue that the ‘Back to closure list’ button was missing at the closure details menu.
  • We addressed an issue in event duplication where updated closure end times were not saved and the original values were sent instead.
  • Handled an issue where events either didn’t appear or appeared twice in the closure association list until the page was refreshed.

Known issue:

  1. Koi Fish: ‘No grants’ banners instead of disabled buttons are shown for low level editors.
  2. WME search: Location pin instead selected venue is shown on the map after selecting it from search

You can read more here.

We look forward to hearing your feedback! :memo:

Thank you,
Nataliia

52 Likes

image
This needs correcting. :wink:

3 Likes

Thank you @Keith_KJ - good catch! I missed that.

Regards,
Nataliia

3 Likes

Great new features! Thanks for the update.
Found one issue/conflict with ClickSaver script. If you select ‘Hide unchecked road type buttons in compact mode’, all road types are hidden.

3 Likes

Hello,

Great news, this will finally encourage editors to process URs, as many prioritise editing over processing URs.

To take this further, could this new rule be made retroactive in order to count URs that have already been processed?

4 Likes

Make sure you report script issues in the script thread or script discord server. This thread should be limited to discussions about WME without scripts.

5 Likes

Let me say: I’m scared by editors processing URs just for earning an edit.

8 Likes

I understand.

In any case, people who want to cheat will cheat, but depending on the rules of local communities, you won’t pass L4 or L5 just by closing all the UR you find. You will need to have an area, and this will also limit your actions.

For example, for the past year and a half, I have been very active in processing my URs in my zone (anyone who wants to can check, I respond to each one, follow up when there is no response, and then close it). With all that, I’m at around 11k URs processed, which is not going to allow me to bypass the editing levels.
11k URs that have not earned me anything in terms of editing because, until now, they were worth 0, yet I have processed a large number of them.

I also think it’s entirely possible to control this, and in any case, editors who only want to earn points have other options.
Adding RPPs instead of HNs earns 7 editing points…

I think this is good for new editors because the map are becoming more and more mature and there are no more big edits to be made that allow you to progress easily. It takes a lot of time and investment to edit properly and progress in term of rank (several years).

4 Likes

Great news!
Help engage our community!

8 Likes

Wow! Lots of good fixes! :heart_eyes:

5 Likes

Great improvements and Fixes. thank you :+1:

3 Likes

Does this include using a dash in address for RPP?

4 Likes

Good news, thank you for the updates!

5 Likes

This is more of a UX comment than a performance one: I’m a big fan of the first loading screen animation. It has a very modern look! :joy:

5 Likes

Understood. Thx.

3 Likes

@fuji2086 has made a PR/fix for ClickSaver here: v2.318-4-g276514d544 compatibility by fuji2086 · Pull Request #60 · WazeDev/WME-ClickSaver

4 Likes

Thanks, @gncnpk and @fuji2086! Itʻs working now… Thank you and everyone that pulls the real weight maintaining the scripts that make our edits possible.

4 Likes

Issue has been move to the proper Script Thread [Script] URComments-Enhanced (URC-E) - #492 by locojd1

4 Likes

Thanks a lot for your feedback @YvesWi!

We do hope this will serve as additional encouragement.

Regarding your suggestion to make the point addition retroactive to include URs that have already been processed, it has already been brought up internally, however, it is not currently on the roadmap. Therefore, to bring this enhancement closer, it’s worth raising on UserVoice so we can prioritize it in the future

Best regards,
Olesya.

6 Likes