Plus 1 on the new tab in UR-MP Tracker.
It is very hard to find the small orange dot for a point MC in large areas.
A new version of WME was pushed to production this morning, and now UR-MP is not finding any URs, except for a handful of very old ones (e.g. notes left to mark long-term closures). The URs themselves are visible in WME. 
Yes I had over 100 in one area and now only 4
Sent from my SM-G935V using Tapatalk
In France too, most of URs have disappeared.
If only this meant they were solved
I only have the problem with Chrome, not with IE.
MPâs still working 
but URâs kaput
Or is is that the script is working fine, but all recent URâs have disappeared from WME?
I think several URs have disappeared. I disabled scripts and am still having difficulty seeing URs.
No, the script isnât finding URs that are clearly visible in WME.
Today, I noticed that I could neither see nor open URs to which UR-MP tracking was taking me.
WME UP-MP tracking showed the URs and when I attempt to open the UR, WME took me to the location, but then acted as if the UR did not exist. In other words, no UR shows up and it does not open.
Occasionally a UR would open.
After clearing the data from WME UR-MP tracking and making a fresh scan, most URs are not being found. Only a few are located. Those DO display.
Iâm guessing that the missing ones from the list are the ones that donât display for me.
Except that they DO display when I open WME in the stealth mode window with all extensions disabled., indicating that they are being found someplace but not âthe right placeâ with all necessary information for them to be found by UR-MP tracking nor for them to display in WME.
I am having the same problem
SM GHO also indicating problems with UR-MP fwiw.
That is related I assume to the disappearance of the URâs in the new WME version.
Notification to Waze staff has been sent earlier today
Shmupi
It seems to me that something has changed in the data model for URs because UR-MP doesnât even find URs in the area any more. Iâve spend some time looking through the data model and also the UR-MP script itself, but havenât found anything significant yet.
Finding that Waze.model.mapUpdateRequests.objects.length is no longer defined. This could be causing the script to think there are no URs visible.
When the script is desactivated, the problem is still present in Google Chrome.
However, I can see some URs (not all) if I refresh screen. But these URs disappear when I zoom in or zoom out.
In Internet Explorer, all is good !
Whatâs the difference between Chrome and IE ?
Further checking I have found that the Features call with mapUpdateRequestFilter=1 is returning zero Update Requests. Changing that to mapUpdateRequestFilter=0 results in many more being found by the UR-MP script. I am not sure what the various values are supposed to represent, but 0, 1, and 2 all appear to have a different number being returned in the JSON.
Changing the value to 0 on Line 4274 in the UR-MP script appears to get more URs than it was before.
I also looked to see what the WME initial load was calling for, and it is using the value of â0â most of the time on initial load. Once you click âShow Closed,â then the loading of the URs is hosed until you reload the page. (Thatâs a WME bug, not a UR-MP bug.)
FYI. The change to â0â appears to have brought back most, if not ALL, of the URs. At any given time, we have minimal URs in the works ⊠making it easier to determine if scripts problems are cleared. For us, Iâm thinking that the fix is a good interim step till updated later.
Hi all!
For information, this is a bug of the WME servers, they are not able to return the data concerning the closed URs.
For the technical détails:
mapUpdateRequestFilter:0 â> Update Requests layer actif with âHide closedâ
mapUpdateRequestFilter:1 â> Update Requests layer actif with âShow closedâ
Patience!
A WME fix should arrive.