New Editor version 2.173&Hotfix v.2.173-1

Hi Everyone,

We hope you’re all doing well.

We’ve released a new WME prod v2.173.

Below you can find a summary of the release.

Note: We released a hot fix, v2.173-1 for the bug that speed limits were rounded incorrectly (using Imperial settings).

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. UR, MP: wrong state after saving Solved/Not identified UR or MP, the button “Reopen” appears, but it doesn’t allow actually to change the state.
  4. Map suggestions: After approving a suggestion, saving the changes, and deselecting the approved segment, upon selecting the segment again, the map suggestion is displayed as open, instead of displaying the segment’s details.
    New features/enhancements:
  • Issue Tracker: Added option to filter URs by “Sources”.
  • House numbers feature: now the street name title is displayed, when we enable the editing mode .
  • The Place Images tab now includes an icon for the “no photo” state.

Bug fixes:

We’ve released 7 bug fixes.

  1. Adding segments sometimes stops working when the screen moves - fixed.
  2. WME (beta & production) pixelates when dragged, when browser zoom is utilized - fixed.
  3. Data belonging to another map comment could be displayed and also saved - fixed.
  4. Railroad crossing/ Camera is locked for L4 users - fixed.
  5. PUR on existing EVCS incorrectly displayed as “New” - fixed.
  6. Issue tracker: Issues number became truncated and not visible - fixed
  7. Practice Mode banner isn’t removed after logging in - fixed

You can read more here.

[doc]https://docs.google.com/document/d/e/2PACX-1vSBUCvTGdDpMxnOTgAujEi9HQ6GFAGsGDfea8S7BprL2J_nlu_Xre33fZygLDNuritq9USvqenEXdy-/pub[/doc]

We look forward to hearing your feedback! :geek:

Thank you,
Nataliia

Scriptless
Using Imperial settings
Typing 10, 20, 40, 80 as the speed limit to a segment and clicking away sets it as 11, 21, 41, 81 etc in the text box
Saving sets the speed limit to the correct number (40 instead of the shown 41 etc)

Visual bug

Hey @Nataliia_Staff

I am not able to see any map sugestions (koi-fish) ohn the map using Chrome and WME production.
Microsoft Edge is fine and also WME Beta in Chrome
I disabled tampermonkey and used 100% the same MS settings in the issue tracker.Screenshot_2.pngScreenshot_3.png

I head from other editors having similar problems. Maybe some can help? It is also no matter of zoom level or map refreshing.
This happes since the second import of segments.

Regards
Andy

it appears to have broken Rapid House Numbers. Can we get that script function baked into Waze please? So labour intensive to add a series of house numbers manually.

thanks

Kieran

Hi,

Selecting a drive from the Drives tab shows neatly the green line of that specific drive.
Selecting another drive doesn’t do anything.

After refreshing / reloading the screen another drive can be visualized.

This issue occurs always after editing first the map and then selecting a long drive first (~175 km)
Or after editing the map and then selecting several drives, after 3 - 6 drives the next drive isn’t displayed anymore.

Regards,
Dirk

Hi Pasciakd,

Thank you for flagging this issue. Could you please send links to segments where you noticed the problem?

I can’t recreate the issue on my side using testing environment.

Regards,
Nataliia

I’m also noticing this in both prod and beta, with scripts and without scripts. Tried in Chrome and Firefox, both say 71mph for this 70mph road. Some kind of rounding error perhaps? It doesn’t seem to affect all segments.

71 instead of 70:
https://waze.com/en-GB/editor?env=row&lat=51.18519&lon=-1.39789&zoomLevel=17&segments=261466414![speed71.png|264x42](upload://lDRRATiBNMThj9dXtfT78vqDVf9.png)

Weirdly, these two segments (connected to each other, with the same speed limit) are different. One says 60, one says 61:
60: https://waze.com/en-GB/editor?env=row&lat=51.18744&lon=-1.40209&zoomLevel=17&segments=395115742
61: https://waze.com/en-GB/editor?env=row&lat=51.18744&lon=-1.40209&zoomLevel=17&segments=191887341
speed60.png speed61.png

Thank you Craig24x7 for your help and examples. I am checking this issue with the team. Also reproducible on my side, using these links.

Regards,
Nataliia

You will have to zoom in to zoomLevel=12 to select another drive.
With large drives the window is zoomed out to much.
Has been mentioned already many times that this is unwanted behavior.
Can you please fix this?

Hi Andy,

Could you please send the link to the map suggestions, which are not visible?

Thanks in advance,
Nataliia

Hi Dirk,

Could you please record the video for this issue? Also please try to change the zoom level and check results.

These additional details would be helpful for the team!

Thanks in advance,
Nataliia

I am pretty sure this is WAD at this point. I would suggest making a feature request in Uservoice.

Hello Nataliia

Here is one example https://waze.com/de/editor?env=row&lat=51.63121&lon=13.40999&zoomLevel=16&segmentSuggestions=8150506
The other ones above and below this example are also invisible. But I cannot see any map suggestion in Chrome in the whole map.

Andy

1 Like

Thank you Andy! We are checking this issue with the team.

Regards,
Nataliia

Hi Everyone,

We released a hot fix, v2.173-1 for the bug that speed limits were rounded incorrectly (using Imperial settings).

The issue is no longer reproducible on our end.

Please check the behaviour and share with us your experience.

Thanks in advance,
Nataliia

1 Like

Hi Nataliia,

See my video https://youtu.be/E58x2cVRxwc documenting my above comments.

Remark: This can’t be WAD: it is just not working. Selecting a drive adjusts the zoom level to display the complete drive from start to finish. Why should this be impossible for a next drive.

Best regards,
Dirk

I can’t seem to get the GPS points layer working on Chrome & Edge. Is this a bug? Thanks

Same here.

Hi Maporaptor,
Hi Leocylau,

I have filed an internal issue for this. The team is checking the problem. Thanks for flagging!

Regards,
Nataliia

I have tried 4 different browsers FF, Brave, Chrome and IE and can not get HN’s to work.
You can highlight the segment, hit edit house numbers and it will do nothing, also tried prod and beta doing the same thing.