Waze forum

In the past I've seen this multiple-tab error occur whenever the WME code itself gets changed leaving URO searching for page elements that either no longer exist or have been renamed. However, for stable releases of WME where this isn't an issue, I think the problem can also be triggered if WME fails to load properly, but since it happens so infrequently on my systems I haven't been able to nail down exactly how or when it occurs, and therefore haven't been able to put in a fix...

If any URO users are handy with either the javascript console in Chrome or Firebug in Firefox, then I'd appreciate getting a copy of the relevant bits of the console output after this error occurs.

charleskelso wrote:I found that if I remove the showproblem/endshow from the end of the URL the problem goes away.

This is the sort of error report programmers love, leading us directly to the problem - thank you It seems that although the auto-open feature started working again for URs in Chrome, reinstating it for map problems as well was a bit hasty, and so 1.22 disables it again...

http://userscripts.org/scripts/show/145186

With the public roll-out of the former beta version of WME, all the code to support the old public version of WME is no longer required, and so 1.23 rips it all out, resulting in a significantly smaller and easier to maintain script.

I've also taken the opportunity to (hopefully!) fix some of the niggling errors that some people have been seeing, which appear to have been caused by the script attempting to access certain elements of WME whilst the WME code itself was in the process of updating them - under certain, apparently rare, circumstances these errors could cause a browser lockup.

http://userscripts.org/scripts/show/145186

1.24 is a compatibility release to fix some issues with the latest public and beta versions of WME.

http://userscripts.org/scripts/show/145186

1.25 adds a "Delete Camera" link to the camera popup, making it a bit easier to clean up areas of the map infested with all of those randomly placed cameras from world_* and usa_* users...

http://userscripts.org/scripts/show/145186

Yes it would, and thanks for the suggestion 1.26 now provides enhanced camera details in the popup, along with corresponding filtering options...

http://userscripts.org/scripts/show/145186

1.27 brings the following changes to the table:

* a full set of map problem filters, all located on their own config tab
* a new camera filter to show only those cameras created/edited by the logged-in user
* fixed default settings on the camera tab for new installs (requested by rob7mgte and others...)
* removal of the "delete camera" popup link if the camera isn't in the users editable area (requested by rob7mgte)

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/145186
Chrome packaged version: http://crx.chizzum.com/UROverview.crx

rob7mgte wrote:Thanks for the update!

Noticed one issue with the new camera delete feature. The delete link disappears as expected when it is outside of my editing area. However it also disappears in an area outside of an area where I have driven, but is within an area I help manage. Make sense?

Ah, I was wondering if that would happen... My own AM area is also covered by a lot of drive areas, so I wasn't sure if the cameras I was testing this with were covered by both sets of areas or just my AM area - now we know. I'll try fixing this later today.

1.28 now re-enables the "delete camera" link for cameras within a users managed areas but outside any of their driven areas

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/145186
Chrome packaged version: http://crx.chizzum.com/UROverview.crx

1.28.1 undoes the undoing of the default checkbox values fix from 1.27...

Note to self: always check that the code you're editing is the most recent version as opposed to a version that is almost, but not entirely, the same

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/145186
Chrome packaged version: http://crx.chizzum.com/UROverview.crx