New Editor version 2.179

Hi Everyone,

We hope you’re all doing well.

We’ve released a new WME prod v2.179 :rocket:

Below you can find a summary of the release.

Known issues:

  1. Header Menu: header items menu slightly covers the header.
  2. Header Menu: the sub-menu items in the right area of the Roads menu are currently missing.
  3. Map Problems: wrong state after saving Solved/Not identified MP, the button “Reopen” appears, but it doesn’t allow actually to change the state.
  4. Map suggestions: After approving a suggestion and saving the changes, the icon near the segments remains visible. However, after refreshing the map, the icon disappears.
  5. Issue Tracker: bad layout in case the user expands UR filters.
    New feature/enhancement:
  • Issue Tracker: centered the banner “Zoom in to see if there are more issues”.

Bug fixes:

We’ve released 4 bug fixes.

  1. Segment manual lock level deleted when clicking existing lock level or clicking new lock level twice - fixed.
  2. Issue Tracker: Specific area - country is not saved after the user applies the filter - fixed.
  3. Map Suggestions’ segments are occasionally not visible on the map - fixed
  4. We have identified and resolved a bug related to speed limits set in imperial values. Previously, when attempting to change the value, the displayed result would show the entered value plus one. This issue has been fixed.

You can read more here.

[doc]https://docs.google.com/document/d/e/2PACX-1vR2tnG0XlpfndZPdRLbE8uDk9c6Avb_rqPGVWZqmWFdx-0E56OOWNJ3qETlgLnT6X-kyNJnZMAEHen-/pub[/doc]

We look forward to hearing your feedback!

Thank you,
Nataliia

1 Like

Nataliia_staff - I am still seeing place photos dated May 15, 2023 (https://www.waze.com/forum/viewtopic.php?p=2377465#p2377465). Is there an update on this?

Hi G_W1Z,

I am checking with the team and will update you.

Regards,
Nataliia

Hi
I’m still seeing SL that are off by one.

Here’s some examples:
https://waze.com/en-US/editor?env=usa&lat=33.03285&lon=-82.40206&zoomLevel=16&segments=85934357

(If you follow the road north of the above segment, you’ll see 7 other segments with incorrect SL)

Here’s another:

https://www.waze.com/en-US/editor?env=usa&lat=30.46393&lon=-84.39322&zoomLevel=17&segments=79556841

I missed the previous discussion about the MPH being off by 1. BUt I’m still seeing it.

Some examples;
<https://waze.com/en-US/editor?env=usa&lat=36.99302&lon=-76.28776&s=4777433364478&zoomLevel=15&segments=510795228,510795229,61623087,61623090&gt;

Ref the hot fix, v2.173-1 for the bug that speed limits were rounded incorrectly

This may be intended behavior, but I wanted to check. When there is a segment with lane guidance that is locked above my level, I get a permissions error when trying to edit the geometry of unlocked segments connected to it. This doesn’t seem to impact my ability to make other changes to the unlocked segment, like street name/city name changes, or attaching other segments to the unlocked segment.

Here’s an example of a segment that causes the error, versus a segment that does not. The major highway segments are all locked above my level, and you’ll notice that the first highway segment has lane guidance, while the second does not:
https://i.imgur.com/EE5hUDx.gif

Speed limit +1mph still a problem in the UK too on every 60 or 70mph road segment I click on.

Major intersection of two motorways here for example: https://waze.com/en-GB/editor?env=row&lat=51.68739&lon=-0.22659&marker=true&s=8095564562430&zoomLevel=15&segments=121792492,146675295

Hi MrNicGuy,
Hi Langpowell,

Thank you for reports. We are checking this issue with the Team.

Regards,
Nataliia

I have a strange bug, maybe not so strange, could be known issue :smiley:

Anyway in the new version i have no satelite imagery anymore.
Even when enabled, see image below. SatNotWorking.jpg

Try again now ;). There was an issue with the layer not loading about an hour ago but seems to be back up and running.

1 Like

Perfect, it’s up and running again :sunglasses:

1 Like

Hi,
Did I miss something, but when I plan a closure in the future, the end date doesn’t adjust automatically to the start date anymore but remains today?
Cheers,
Eddy

Hey Nataliia

Map Suggestions’ segments are still not visible for me (Chrome)
(Information here: https://www.waze.com/forum/viewtopic.php?p=2372147#p2372147)

This is my actual screen, I can see GM-pins but no segments to click on.Screenshot_4.png

Regards
Andy

Still experiencing a problem with place points disappearing temporarily after approving a new place PUR and saving. It seems to only be a visual/layer bug, as it doesn’t impact saving changes or the data of the place. This problem occurs across multiple browsers with and without scripts.

Steps to reproduce:

  1. Locate a “New Place PUR”, and select “Add and Edit”.
  2. Add details as necessary.
  3. Save.
  4. Select a blank spot on the map to deselect the place. The place should disappear from view.
  5. Toggle the places layer to show the place again.

No error shows up in the console upon clicking save or deselecting the place. Toggling the places layer or performing another action that causes the layer to refresh will make the place point reappear. Once you make the place reappear by toggling the places layer, it doesn’t seem to disappear again, regardless of any edits or changes made to the PP.

Here’s a couple of screen recordings of the issue:
https://i.imgur.com/LCIhsOc.gif
https://i.imgur.com/rzEr3wH.gif

PURs (specifically an EVCS PUR in this case) that are too long still clip the “Add and Edit” and “Reject” buttons at the bottom. Only appears to happen at certain window sizes, oddly enough. Can access the buttons by making the window smaller or by zooming the window out. Here’s a screenclip of the issue (screenclip is on a browser with scripts, but the issue persists in a scriptless browser as well):

https://i.imgur.com/nEVhjWM.mp4

I have a new construction road that I’m unable to add house numbers to, without any scripts running. I was able to add them to neighboring roads.

https://waze.com/en-US/editor?env=usa&lat=39.96268&lon=-85.89095&zoomLevel=19&segments=534095188,534095241,534095242

I’m observing the same behaviour in the beta WME. Is this a (desired) new feature? IMHO, I find this a drawback as the end date can’t never be before the start date and one needs explicitly change it. That might seem as peanuts, but when one needs to add hundreds of closures, this becomes a time consuming and tedious thing. Therefore I would ask to bring back the old behaviour where a new closure has the end date will be changed automatically to the start date.

Hi Andy,

The team is working on this bug. I have updated the related post: https://www.waze.com/forum/viewtopic.php?t=383469

Regards,
Nataliia

Hi Rehmedy,

Could you please open a separate bug for this problem in this section: https://www.waze.com/forum/viewforum.php?f=1524

Thank you in advance,
Nataliia