Map Editor major ver (Nov 5, 2012) Official Feedback

[skbun]

Yeah, okay, nailed it. Here's the deal.

THIS Permalink (don't move, just zoom in and out), will generate exceptions.
https://www.waze.com/editor/?zoom=5&lat ... FFTFTTTTFT

THIS one (again, just zoom in and out), won't.
https://www.waze.com/editor/?zoom=5&lat ... FFTFTTTTFT

It's the same location, but in the one where the exception is thrown, the landmarks layer is turned on.

When Waze enabled addresses for landmarks a week or so back:
* All landmarks by default appear to have a cityID of (null).
* When the landmarks layer is turned on, landmarks are polled for their cityIDs.
* There is no error checking for the condition in which (null) is the city ID (it really should be ignored), so an error happens, and now you have to re-zoom, or reload the page to edit.

[douglasr007]

I'm glad I'm not the only one who has problems with selecting road segments on the WME. The only way to "fix" it is to deselect the road segment, zoom all of the out, and zoom all of the way back in to the section you're editing and hope the segment can be changed when you select it again.

Also, I thought it was a conflict with WME Color Highlights script but it's definitely the server causing these issues.

[skbun]

I'm glad I'm not the only one who has problems with selecting road segments on the WME. The only way to "fix" it is to deselect the road segment, zoom all of the out, and zoom all of the way back in to the section you're editing and hope the segment can be changed when you select it again.

Also, I thought it was a conflict with WME Color Highlights script but it's definitely the server causing these issues.

Try this, because it doesn't seem to help whether landmarks in view have names or even addresses: just turn your landmark layer off and work like that.

I'm betting it'll be fine, until they fix this on their end. It doesn't seem to help whether landmarks in view have names or even addresses, which means that's a red herring, so there's really nothing we can do.

[davipt]

The only way to "fix" it is to deselect the road segment, zoom all of the out, and zoom all of the way back in to the section you're editing and hope the segment can be changed when you select it again.

Also, I thought it was a conflict with WME Color Highlights script but it's definitely the server causing these issues.

Try this, because it doesn't seem to help whether landmarks in view have names or even addresses: just turn your landmark layer off and work like that.

I'm betting it'll be fine, until they fix this on their end. It doesn't seem to help whether landmarks in view have names or even addresses, which means that's a red herring, so there's really nothing we can do.

In my case zooming out or in or taking layers out doesn't solve it. And it's no extra script either. There is a javascript error (I've posted both on Firefox and Safari) and from that point on the javascript login is broken and only a refresh will solve it. I'm sure with the javascript error lines they can easily solve this. And I'm pretty sure this is a bug introduced days after the launch of the new version.

[skbun]

In my case zooming out or in or taking layers out doesn't solve it. And it's no extra script either. There is a javascript error (I've posted both on Firefox and Safari) and from that point on the javascript login is broken and only a refresh will solve it. I'm sure with the javascript error lines they can easily solve this. And I'm pretty sure this is a bug introduced days after the launch of the new version.

I myself am on Chrome, so maybe I'm getting a different error based on a different condition.

[douglasr007]

I use Firefox and Chrome and the editor seems more picky on Firefox than Chrome when choosing road segments.

[scruffy151]

I'm glad I'm not the only one who has problems with selecting road segments on the WME. The only way to "fix" it is to deselect the road segment, zoom all of the out, and zoom all of the way back in to the section you're editing and hope the segment can be changed when you select it again.

Also, I thought it was a conflict with WME Color Highlights script but it's definitely the server causing these issues.

Try this, because it doesn't seem to help whether landmarks in view have names or even addresses: just turn your landmark layer off and work like that.

I'm betting it'll be fine, until they fix this on their end. It doesn't seem to help whether landmarks in view have names or even addresses, which means that's a red herring, so there's really nothing we can do.

Another quick fix is to hit permalink to force a reload.

[jasonh300]

Try this, because it doesn't seem to help whether landmarks in view have names or even addresses: just turn your landmark layer off and work like that.

Now that I've seen your example, I remember that this happened to me the day they enabled the new Landmark functionality. There was some discussion in the forum that day about it and that turning off landmarks layer prevents it from happening.

I haven't had my landmarks layer on since then, so I'd forgotten completely about this since it hasn't happened to me again.

I'm going to forward your error code that you posted to the appropriate department.

Thanks for the details!

[jasonh300]

In my case zooming out or in or taking layers out doesn't solve it. And it's no extra script either. There is a javascript error (I've posted both on Firefox and Safari) and from that point on the javascript login is broken and only a refresh will solve it. I'm sure with the javascript error lines they can easily solve this. And I'm pretty sure this is a bug introduced days after the launch of the new version.

While I was testing it just now, simply turning off the landmark layer didn't fix it for me. But once I turned off the Landmark layer and did a permalink, I couldn't get it to happen again.

Is that not the case for you?

[fvwazing]

No, doesn't work here. (Chrome/OSX)