That’s absolutely correct. I drove (as I frequently do) outside of my AM area. Once that drive had registered in Waze, URs from along it - but outside my AM area - were being picked up by UR-MPT when doing a ‘managed area’ scan.
How would that help? I want to see URs only from within my AM area - excluding any from driven areas which I don’t manage.
Sorry - I misread your post.
In that case have you tried the “Managed Area” link? If that doesn’t work then you’ll need to create a WKT file of your managed area and use that as a “Custom Area” in UR-MP. You probably created a WKT when you applied for your managed area, if not there are some tools available if you need. The easiest is the script Waze Editor Profile Enhancements, which shows an icon on the far right of your profile page that will generate a WKT
Hello,
First of all, thank you for your great work on the UR-MP Tracking script. It is really helpful and makes editing much easier.
I would like to suggest two possible improvements that could make it even more powerful:
- Sorting by last reply – It would be very useful to have an option to sort map comments according to the most recent comment.
- Editor comment filter – An additional filter to display only comments written by editors.
Thanks again for your continued effort and support of the community!
Best regards,
Fo_tis
You can already sort on the most recent comment by clicking on the comment bubble in the right hand side of the second column header.
I meant the map notes, maybe I wasn’t clear that I was referring to the map notes, sorry.
Is there a similar function as URs?
1 Like
That’s a good idea actually, it would be useful.
1 Like
I would like to suggest two possible improvements that could make it even more powerful:
- Sorting by last reply – It would be very useful to have an option to sort map comments according to the most recent comment.
This should be possible. I’ll take a look during the work on getting SDK working.
- Editor comment filter – An additional filter to display only comments written by editors.
This will likely not be possible. Unlike URs that are marked with a user ID of -1 and an editor with their actual User ID, map notes/comments have the users’ ID because if you logged into WME you are now an editor. This makes everybody an editor that uses a MC. I could probably do something like if username like "usa_*" or equivalent to other locations, but that is still not a guarantee they are not editors.
Thanks!
1 Like
WME UR-MP seems to be partially down in the latest WME. is not opening URs and PURs.
2 Likes
Looks like…
getAsync() is deprecated and will be removed soon app-bcdf292e868449db.js.gz:1:1832382
UR-MP Tracking v3.9.23 - Can not select UR 25025700. Trying again 9/10…
and Uncaught (in promise) TypeError: can’t access property “objects”, e.updateRequestSessions is undefined
throughout the debug console.
Yes, unfortunately this is a Waze bug that we cannot work around. Waze Devs have identified it and are hoping to release a fix.
2 Likes
The latest WME beta and also prod made it even worse, debug screen is full of errors, the script doesn’t even load anymore in beta and doesn’t open the URs in prod..
Uncaught TypeError: can’t access property “onclick”, WMEURMPT.getId(…) is null
connectPURTabHandler https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:3573
setTimeout handlerWMEURMPT_Injected/WMEURMPT.initialiseURT https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:2788
setTimeout handlerWMEURMPT_Injected/WMEURMPT.arealistLoaded https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:8229
_waitForData https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:12
_waitForData https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:17
setTimeout handler*_waitForData https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:16
_waitForData https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:17
setTimeout handler*_waitForData https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:16
load https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:27
setTimeout handlerload https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:26
load https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:8241
initializeElements https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:354
initializeWazeObjects https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:408
setTimeout handlerWMEURMPT_Injected/WMEURMPT.initializeWazeObjects https://beta.waze.com/de/editor?env=row&tab=userscript_tab line 10 > injectedScript:400
Any chance to see an update like URC-E did?
It seems today’s WME update killed URMP. The tab in the script panel is not loading so there is zero functionality. Here is the console with only URMP running.
Bad news… UR-MP is the most important script for many editors working on URs and PURs. 
2 Likes
Finding the same thing here. UR-MP Tracking is now dead thanks to WME “improvements”, as well as URC-E being partially crippled. That’s my UR workflow borked. Until things work properly again, I’m done.
2 Likes
Work around provided by @jushag:
Make sure to open WME with the “settings” tab then wait couple of seconds before going to scripts
For USA editors try this link: https://www.waze.com/en-US/editor?env=usa&tab=prefs
WME UR-MP Tracking seems to be fully functional using above “fix / work around”
3 Likes
Although considering the frequent pothole crashes of WME, this is not a real option…