New Editor version 2.217

Map Editors Community WME Production Version Releases
1

Hi Everyone :wave:

We hope you’re all doing well.

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

Below you can find a summary of the release.

Regarding scripts: We’re aware that during the beta release, some scripts were disrupted, causing inconveniences. We sincerely apologize for this, we were not able to predict the disruption.

We’ve been in touch with script writers and provided all necessary information to update the scripts. After this release, you may notice that some scripts are still not working. We ask for your patience and wait until they are updated.

Thank you in advance for the understanding!

New features/enhancements:

  • Community suggestion: Permanent Hazard: Add shortcuts to WME - enabled.
  • More information in URs: display the EV vehicle type inside the User Preferences section.
  • Closure Status: we enabled the new closure status “Finished Earlier”, when WME closures are overlapped with partner closures or feed closures.
  • Closure Status: Always align the closure status panel with the first item in the closures list - enabled.
    Bug fixes:

We’ve released 7 bug fixes.

  1. Event created/updated timestamp missing - fixed.
  2. PUR: Disabling Places layer causes other PURs to be stuck in Pending Save state - fixed.
  3. Savestack: redundant element is displayed to the right from the savestack popup - fixed.
  4. Empty snackbar when copy permalink twice - fixed.
  5. Layers: turning Issues layer off doesn’t remove URs and MPs from the map - fixed.
  6. Additional Imageries: images fail to load and an Internal error appears in the console - fixed.
  7. Map Suggestions: Rejected MS is not removed from the map with the first map refresh (in case filters are set to Open - fixed.

You can read more here.

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

We look forward to hearing your feedback! :nerd_face:

Thank you,
Nataliia

2

Hi,

For now I get a blank screen when trying to connect to https://www.waze.com/editor?env=row# instead of the WME screen. :?

Access to image at ‘https://editor-assets.waze.com/production/font/b5fc9b87d1286be0/googleMapsLogo.svg’ from origin ‘https://www.waze.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.
googleMapsLogo.svg:1

Failed to load resource: net::ERR_FAILED
app-922e25f3a7293d07.js.gz:1 Uncaught (in promise) Event
clouderrorreporting.googleapis.com/v1beta1/projects/waze-prod/events:report?key=AIzaSyBWB3jiUm1dkFwvJWy4w4ZmO7KPyF4oUa0:1

Failed to load resource: the server responded with a status of 400 ()

Regards,
Dirk

3

Hi Dirk,

Thank you for the report. Do you have scripts enabled? Could you please send the screenshot?

Regards,
Nataliia

4

I added above some debug info.
No scripts, only Tampermonkey.

The only thing I see is this wait animation:2024-03-18 11_40_32-Waze Map Editor.png

1 Like
5

Thank you Dirk, do you have any scripts enabled?

Regards,
Nataliia

6

Hi Nataliia,

After removing Cookies WME works again.

Regards,
Dirk

7

Hi Nataliia,

After removing cookies WME works again.

Regards,
Dirk

8

Hi,

Layers panel is a bit long.

It would be nice if it is possible to collpase the Additional imagery list after selecting an option.layers.png
Best regards,
Dirk

2 Likes
9

Thank you, Dirk, for the update. Indeed, removing the cache is a workaround for this problem.

I’ve checked with the team, and they’re working on fixing the issue. I’ll keep you posted on the progress.

Sorry for any inconvenience caused.

Regards,
Nataliia

10

Thank you Dirk. Good catch!

Regards,
Nataliia

11

Pantalle inicio Waze.png

I find myself in the same situation. I have disabled all the scripts and I can’t get past this screen. The Beta editor starts up for me without problems.

12

Sorry Huakayo for inconveniences. Please try to remove cache. :pray:t2:

Regards,
Nataliia

13

I read you before and I have deleted it twice and it still doesn’t work. I have even disabled scripts that have nothing to do with it and it won’t start.

1 Like
14

Frequently the browser becomes very very slow when we update wrong Street names addresses.

Does anyone suffers like me?

Is there any update able to fix this?

Thank you

rmg

15

Wouldn’t it be better as a select box instead like this?additional imagery.png

1 Like
16

These ideas should be submitted as a feature request in Uservoioce so they can be considered.

17

I find uservoice to be messy. Too many of the same stuff that has never been merged together. Tends to make things get lost. I’m hoping they decide to use Waze Discuss (Discourse) for future suggestions. Like how they plan on integrating the forum into it this year.

18

Hi Huakayo,

Could you please check the issue now? The team has added a related fix and the issue should be resolved right now.

Thanks in advance!
Nataliia

19

Messy or not, if you want to suggest an idea, Uservoice is currently the way to do it.

1 Like
20

Perfect. It now starts correctly. I have done tests by closing the session and reopening it, I have reactivated the scripts that I had activated and everything is correct. Only the URC-E fails me but that is no longer your problem hehehe. Thanks guys.