[Script] UROverview Plus v4.18 (20251103)

Thanks, these are now both fixed in the next release candidate.

3.224 changes:

  • RTC details in popup now indicate how far in advance a future closure will occur - e.g. “Today”, “5 days” etc.
  • Expired closures are now handled correctly.
  • Optimised the segment popup layout.
  • Optimised the search for duplicate URs.
  • Compatibility fixes for latest WME update

NOTE: due to changes in how WME behaves when clicking on report markers, I’ve had to (hopefully temporarily) inhibit the option to disable marker onclick recentering until I can figure out a reliable workaround.

https://greasyfork.org/scripts/1952-uroverview-plus-uro

There seems to be a conflict of some kind between URO+ and UR Comments-Enhanced. Whenever I try to load WME with both of these scripts enabled, Chrome hangs indefinitely. I can load WME with either one of the scripts, but not both simultaneously, with no problems.

Hi Russ - both scripts are working simultaneously in my chrome.

Here’s a minor bug – in the segment pop-up, restrictions are shown as expired even if they have the “Repeat every year” box checked. Those should be shown as future restrictions.

If I activate URO+ the left side panel of the WME becomes completely blank when I select a segment

I can replicate this in WME beta, but as I no longer actively support use of my scripts within that environment, this isn’t something I’d be in any hurry to fix.

If however you’re seeing this in WME Production, then it’s definitely not a generic bug that occurs simply by having URO running, given that it’s something I definitely would have spotted prior to release, and definitely wouldn’t have left in as part of a release. So it’d mean either it was due to some specific settings you’re using in URO that I haven’t tested recently (and given how many settings there are, it’s not feasible for me to test them all on each release), or due to some interaction with other add-ons you’ve also got running.

So please let me know in which version of WME you’re seeing this problem, and then if it’s production, please also let me know if it’s reproducible when URO is the only add-on running.

Good catch :smiley: I’m now sat here twiddling my thumbs for the next 18 minutes waiting for the time to tick past midnight so I can see if the code changes I’ve just made have the desired effect…

If you can replicate in beta, is it something that be shared with us (and maybe can HQ can use it for fixing things) or is it just URO+ only causing this issue?

HI,

It seems that there is an issues (in beta) with streetview for PURs. When I click on the SV incon, the SV pane remains black. It only happens when URO+ is enabled in tampermonkey. When swithes off, the SV pane shows.SV_PUR.jpg
Cheers,

Eddy

Hi,

I found another issue (in beta). When I try to put a new place on the map, the whole window scrolls until I click for a second time on the map. It doesn’t happen when URO+ is disabled.
Here is a video

Cheers,

Eddy

URO is throwing so many errors in beta at the moment that I’m fairly confident the blank side panel is the inevitable outcome of those preventing WME doing what it needs to do, as opposed to something URO is doing which merely causes the native problem to be reliably surfaced vs occurring more randomly.

Yes only in Beta WME, in Production works correctly

3.225 now handles recurring restrictions properly in segment popups, no longer displaying them as expired if their starting time period is in the past - thanks to russblau for noticing this problem.

https://greasyfork.org/scripts/1952-uroverview-plus-uro

3.226 now correctly identifies closures as expired if they ended on the same day the script is being used, and RTC filtering is now compatible with the latest tweaks to the native RTC marker rendering…

https://greasyfork.org/scripts/1952-uroverview-plus-uro

Blank panel problem now preventing use of this script in production WME :frowning:
(looks like a new version of WME today)

Yes - new WME https://www.waze.com/forum/viewtopic.php?p=2429365#p2429365 and some scripts are down.

The default MTE is also not functioning anymore.

3.227 is a work in progress update to address the stuff that broke with the latest WME update - focussing on the most obvious issues first, to get the script back into at least some sort of working order again. It also fixes an issue with RTC filtering if a segment has closures of multiple types (active, expired, future) applied to it.

https://greasyfork.org/scripts/1952-uroverview-plus-uro

Thx for the quick fix.
Pls don’t forget the MTE option set to none when creating RTCs. As I create a lot of RTCs daily, it is really helpful that I don’t need to select an MTE (when there isn’t one)