Personally I’d rather these stayed as separate extensions, as I tend to use SRS more than URO. Uploading scripts to Chrome Web Store is very easy (but then, I only have 2 so far). 
via mobile
I don’t plan on pulling the existing versions from userscripts or my own server, but neither do I plan on doing anything more with them (or sticking them on CWS in the case of the Chrome versions), so the standalone versions will still be useable until Waze decide to mess around with WME again…
I’m not sure whether any of you guys are facing this but it seems the filter to not show approved cams is not working for the beta editor. On the public editor I do not face any problems.
On the beta editor, the approved cams is still appearing even though I ticked not to show.
sigh it never ceases to amaze me just how many different ways the Waze coding team manage to find to implement the same outward functionality with every WME refresh… I’ve just had a similar bug report from another user, so I’ll look into it when I get some free time - probably next week at the earliest.
The hide function not working on UR’s, and possibly MPs in the current beta editor. Works fine in the regular editor.
Someone suggested disabling Toolbox, which I did, but its still not hiding UR’s and MPs I’ve told it to. Hover is working though. Seems to be affecting at least some of the other beta editors as well.
I guess I should add:
URO+ 3.1
Chrome 31.0.1650.63 m
+1
3.2 restores WME beta compatibility…
Firefox+Greasemonkey version: http://userscripts.org/scripts/show/145186
Chrome packaged version: http://crx.chizzum.com/UROverview.crx
Is there a way to show only URs where the Reporter is the last commenter?
Yes 
Version 3.3 revises the comments-related UR filter options, the correct combination of which now allows only URs where the last comment was made by the reporter to be shown, as requested above…
3.3 also marks the debut of URO on the Chrome Web Store. Users of the older CRX-packaged versions should uninstall them first before installing 3.3 from CWS.
Firefox+Greasemonkey version: http://userscripts.org/scripts/show/145186
Chrome Web Store version: https://chrome.google.com/webstore/detail/uroverview/amdamgkgchnbaopmphhjapmjcdghdphi
Having a problem with the script. For UR’s, it is not waiting for me to hover or click n a UR. It is getting hung up on whichever UR it finds first when it loads (either on-screen already or nearvy), and instantly displaying the pop-up for it, no hover or anything required. It then refuses to let go of that one UR until it scrolls well off screen. I can’t get another UR on the same screen to show the pop-up – the first one latched onto is apparently a love affair. Monogamy until she leaves me.
Firefox or Chrome?
Userscripts or Chrome Web Store version?
Production or Beta WME?
Which other scripts are installed?
Chrome
Webs tore
Production
Tampermonkey: Street to river, WME Livemap, Highlights, JNF; direct: LMUR, URO, WME route checker, Toolbox, Junction angle,
You’ve got both URO+ and URO installed?
URO+ 3.3 and LMUR 2.4. The latter operates on Livemap, not WME, or at least is advertised as such.
I’m pretty familiar with the scope of LMUR’s operations (I did write it, after all 
) so yes, I can confirm that LMUR has no effect in WME. My query was more to do with your listing URO in response to me asking which other scripts you had installed - I wasn’t sure if this meant you had both URO and URO+ installed, or if you’d just listed all the scripts…
Since I need to do a new release of URO to fix whatever Waze have done to break it in the latest beta release, I’ll take the opportunity to both ponder the code relating to UR popup generation in case there’s something obvious which might be causing the problem, and to add in some extra diagnostics output to the debug console - if I don’t find anything to change in the popup code, at least the next release will give me some more clues as to why it’s behaving the way it is on your system.
As mentioned in the reply above, I’m aware of an issue with URO+ 3.3 and the latest WME beta release which is preventing UR popups from appearing at all (rather ironic given the problem qwaletee is having…), so I’ll be looking into that soon - if anyone spots any other beta-related issues please let me know ASAP.
If it would help you, I can do a screen share with you so you can see what’s going on and tweak Chrome to debug.
3.4 restores compatibility with the latest WME beta, fixes some styling/layout glitches caused by the site-wide CSS update, and optimises the UR/problem/camera popup generation code - this isn’t expected to fix the problem noted by qwaletee (though if it does it’ll be a nice bonus), it’s just something I did notice whilst trying to work out why their problem might be occurring…
Firefox+Greasemonkey version: http://userscripts.org/scripts/show/145186
Chrome Web Store version: https://chrome.google.com/webstore/detail/uroverview/amdamgkgchnbaopmphhjapmjcdghdphi