WME Release v2.11-53

Hey all,

A new WME version has been released, here is what inside:

*Time Based difficult turns - ENABLED

  • Moving node disables turn arrows - FIXED
  • Walking Trail can be merged with another segment - FIXED
  • Merging 3 segments, of which one is a WT, does not add the virtual node - FIXED
  • Long addresses in search results are not fully shown - FIXED
  • Segment restriction title is garbled - FIXED
  • Restriction help tip is wrong - FIXED
  • Keyboard shortcuts are not sort by category - FIXED
  • Keyboard shortcut allow to edit HN for unnamed street - FIXED
  • Don’t show turn arrows after saving house numbers - FIXED
  • Unable to edit house numbers if multiple segments are selected - FIXED
  • Selecting a junction box disable permalink - FIXED

*Restored Waze object for script support
*Added Waze deprecation message

  • MoveNode component to update segment geometries - FIXED

  • Update translations

Known issues we’re working on fixing:

  • Unable to add closure after editing name and direction of a closure
  • Able to move HN pin outside the highlighted area of the road

Enjoy,
Ruben

Just a note, we talked about this in the beta version. You need to elaborate on the ā€˜issue’ here, as the ability to force HNs outside the highlighted area is a necessity, especially in rural areas. See this (BETA ONLY) post.

I’m still getting a ā€œWe’re sorry, but something went wrongā€ (500) with the latest Firefox ESR version.

Seems H does not work as the built in shortcut for adding a house number once in the ā€˜Edit house numbers’ mode.

This occurs scriptless too.

Whenever I make many many edits in one save, it always throws a ā€œSave Errorā€ while the servers actually process the map edits. I have to hard refresh WME in order to see the changes I make. I hope this will be fixed.

This appears to be a pretty decent set of bug fixes, thanks.

Status update on those getting the server errors who can’t access WME?

Anything that can be shared about policy discussions regarding the new draconian edit limits for new editors, or regarding the many requests to consider backward compatibility, older OS/browser setups, and smaller (laptop) monitors? At least to acknowledge that these issues have been seen by staff?

This was reported in WME beta testing already, according to a staff (QA or dev?) that answered, he thought H was only supposed to open HN Editing mode and never to trigger adding a new HN inside HN Editing. Of course we all know that is wrong and a few people responded that it always worked like that before, yet this still made it to production.

Hi, I think this issue may be a bug, since it’s not listed in the changelog: editors now cannot even see HN in segments locked above their editing level.

The LA map editors praise you! TBDTs Hallelujah!

I am having the same experience with HN option not showing on segments locked above level. Before you could view (not edit) to check, now it seems you cannot.

Now that I am actually back into WME since the update… yeah, losing ā€˜press H’ to add a new HN is a huge PITA.

STAFF! For seriousness, and Vince says you were warned by many… why do you do this to us? So easily avoidable… :evil:

PLEASE FIX.

Not fixed.

And this screenshot taken with all scripts disabled… turn arrows shown after HN edits, no segments selected.

We always re-test/check each issue reported as fixed by staff and already made them aware that the fix hasn’t worked a few days ago. Thanks for posting and glad that you got your access back.

I found a Windows XP compatible browser working with the latest WME releases : Yandex Browser.

However there is still a bug but with an easy workaround : you can’t login directly on the WME page, you have to do it through other waze.com login pages, and then (re)load WME to get logged.

I tried to report that bug through Yandex dedicated form, but it’s also buggy and I couldn’t send my report ! So I tried to write an e-mail to their public relations address… To be continued !

Edit : I also encountered the login problem on the forums access page. After deleting waze.com cookies it worked back again.

Edit 2 : those bugs won’t be addressed as Windows XP is not supported in newer versions.

does it support user scripts?

Hi AlObaili,

I can’t tell you as I don’t use such scripts. But as Yandex Browser is based on Chromium, and is compatible with Chrome extensions (they are even automatically imported with your favorites when you install it), I guess the answer is yes :slight_smile:

When I choose a route from drives in WME it does not zoom in on it.
Is this related to the new version ?

Yeah, you’re right. Disabled all scripts and get only this but not my route.

Yandex’ editor informs me that they neither don’t support Windows XP, the latest installable version being 17.4.1, and the current 18.3.1. So we’ll have to deal with that bug.