Here’s one that’s good until noon your time. Until I edited it in incognito mode it was marked yellow and I could only delete. Now I can edit or delete but not copy. Added by wazefeed (appears as -5 if username isn’t showing), reported by Kleinfelder_Global.
When I create a new RTC, the “clone” button doesn’t appear over the new RTC in the side panel. I have to switch to “General” and back to “Closures” to see the “clone” button.
Thanks, that’s consistent with the ones we get here, so the same fix will prevent them being classified as in-app.
I’ve noticed that if you add an closure via the editor for a time after the in-app closure is set, it also turns the in-app closure editable and no longer highlighted.
and
Thannks for reporting these - they’re two different symptoms of the same underlying issue, which has now been fixed in the development code…
3.160 is here…
- WazeFeed RTCs are no longer incorrectly treated as in-app closures
- WazeFeed RTCs now have their own filter options
- Closure panel now continues to mark in-app closures and clone buttons correctly after editing closures
- a bunch of refactoring, optimisation and other programmmery-type stuff…
Plus for Beta users, some long overdue compatibility updates…
Userscript version: https://greasyfork.org/scripts/1952-uroverview-plus-uro
Chrome Web Store version: [s]https://chrome.google.com/webstore/detail/uroverview/amdamgkgchnbaopmphhjapmjcdghdphi[/s]
1 Like
3.161 fixes an error in the new closure panel handing code…
Userscript version: https://greasyfork.org/scripts/1952-uroverview-plus-uro
Chrome Web Store version: [s]https://chrome.google.com/webstore/detail/uroverview/amdamgkgchnbaopmphhjapmjcdghdphi[/s]
URO+ does not seem to be playing well with this morning’s new version of WME. Many problems with screen not refreshing and freezing after saves; most (but not all) went away after disabling URO+.
Do you get anything in the developer console that looks like a URO triggered error?
I haven’t seen any problems in the past few hours since the new version hit the RoW servers, nor had I seen any issues in beta during development of the earlier compatibility fixes, so I’m surprised that you seem to be able to resolve most of the problems you’re seeing just by disabling URO.
I wonder if the fact that you can’t resolve all of them indicates that URO is just making it more likely that whatever is still wrong with WME itself will manifest itself, as opposed to it being something which is directly triggered by something URO is doing…
No, I don’t see anything in the console from URO+ at all.(*)
I tried turning it back on again, and was having problems creating a place point, converting it to an RPP, and saving. Address disappeared repeatedly, then after save the point was back to a non-residential one. After turning URO+ off, I was able to save the RPP.
Still, your final point may very well be correct; even with URO+ off, I’m still having frequent freeze-after-save issues and other glitches. Could be one of my other 33 scripts acting up. 
(*) Speaking of no messages on console, I was checking to see if WMEAltCity would work with the new version. Although it does work, none of its messages are appearing on the console! Has something happened to console.log (maybe being overriden by another script somewhere)?
Thanks for narrowing it down to a specific testable issue 
I’ve tried and failed to reproduce this problem here, so unless you’re still having problems with this procedure and only when URO is enabled, then I’m going to assume it was just coincidence that it started working when you disabled URO.
3.162 provides a compatibility update for the RTC filtering code
To follow up on the earlier report about RPP problems. I was not able to get the “SAVE” button to “light up” when I do anything on a PP or RPP (approve PURs, change any of the fields, etc.).
I’m using 3.162 on Chrome and have URO+ as the only script running (I’ve disabled Toolbox extension also and have no other WME extensions).
In the console, I see these errors when I force a refresh of WME:
userscript.html?id=6f6e333e-d0e3-4c3b-bac1-06757f92d413:3366 Uncaught TypeError: Cannot read property 'attributes' of undefined
at uroFilterPlaceMarker (userscript.html?id=6f6e333e-d0e3-4c3b-bac1-06757f92d413:3366)
at uroFilterPlaces (userscript.html?id=6f6e333e-d0e3-4c3b-bac1-06757f92d413:3889)
at uroFilterItems (userscript.html?id=6f6e333e-d0e3-4c3b-bac1-06757f92d413:5562)
at uroFinalizeListenerSetup (userscript.html?id=6f6e333e-d0e3-4c3b-bac1-06757f92d413:9653)
at uroMainTick (userscript.html?id=6f6e333e-d0e3-4c3b-bac1-06757f92d413:11059)
When I select a RPP or PP, I see this in the console:
Error getting features TypeError: Cannot read property 'attributes' of undefined
at uroFilterPlaceMarker (userscript.html?id=6f6e333e-d0e3-4c3b-bac1-06757f92d413:3366)
at t.uroFilterPlaces (userscript.html?id=6f6e333e-d0e3-4c3b-bac1-06757f92d413:3889)
at f (vendor-86dc9f4c83949efd6718.js:1)
at T (vendor-86dc9f4c83949efd6718.js:1)
at h (vendor-86dc9f4c83949efd6718.js:1)
at t.u.trigger (vendor-86dc9f4c83949efd6718.js:1)
at t.mergeObjects (app-1d3e5c24957b318a3943.js:1)
at app-1d3e5c24957b318a3943.js:1
at Array.forEach (<anonymous>)
at e.mergeObjects (app-1d3e5c24957b318a3943.js:1)
Same here.
Even the “SAVE” button been ‘light up’ by adjusting road segment, some of the edited info. will lost after saved.
My browser is Fire Fox.
Please can you provide a permalink to a place which triggers this problem, as I’ve not been able to reproduce this here.
I suspect this is a seperate issue, as we had the same problem in the UK a couple of days ago which definitely wasn’t being caused by any scripts.
Try these PURs:
https://www.waze.com/en-US/editor?env=usa&lon=-121.41459&lat=38.51745&zoom=4&venues=156369281.1563627276.6517279
When I try to approve the PURs, I can’t get the SAVE button to highlight and be selectable.
Again, running Chrome with URO+ 3.162 as the only script running.
Thanks.
I get the following errors in the console when doing a hard refresh of WME (no objects selected):
Uncaught TypeError: _.contains is not a function userscript.html?id=4ac37217-05e9-4f66-aaac-843e7870c782:3771
at uroFilterPlaces (userscript.html?id=4ac37217-05e9-4f66-aaac-843e7870c782:3771)
at uroFilterItems (userscript.html?id=4ac37217-05e9-4f66-aaac-843e7870c782:5562)
at uroFinalizeListenerSetup (userscript.html?id=4ac37217-05e9-4f66-aaac-843e7870c782:9653)
at uroMainTick (userscript.html?id=4ac37217-05e9-4f66-aaac-843e7870c782:11059)
Uncaught TypeError: _.contains is not a function
at uroFilterPlaces (userscript.html?id=4ac37217-05e9-4f66-aaac-843e7870c782:3771)
at initialize.uroFilterItems (userscript.html?id=4ac37217-05e9-4f66-aaac-843e7870c782:5562)
at initialize.triggerEvent (vendor-86dc9f4c83949efd6718.js:1)
at initialize.moveTo (vendor-86dc9f4c83949efd6718.js:1)
at initialize.setCenter (vendor-86dc9f4c83949efd6718.js:1)
at initialize.updateSize (vendor-86dc9f4c83949efd6718.js:1)
at initialize.resize (app-1d3e5c24957b318a3943.js:1)
at dispatch (vendor-86dc9f4c83949efd6718.js:1)
at f.handle (vendor-86dc9f4c83949efd6718.js:1)
at shrinkTopBars (userscript.html?id=d2a40421-bf92-4e26-87f1-8c4343872158:776)
I realize that “shrinkTopBars” is a WME FU object, not from your code, but in the console it appears as a part of the call chain under uroFilterPlaces. (?)
After the recent update of WME I have few problems with URO+.
- I set to hide URs with last comment less than 8 days ago. Now such URs are shown, but when I click one of them, it disappears from the map. No panel of UR appears, but I see its route.
- I set to hide PURs that I cannot edit. Now they aren’t hidden.
- When I zoom up and down, on some zoom levels all places disappear.
The only errors that I see in the console are:
userscript.html?id=50fd45e1-6500-4f60-862e-b5e0ec48b082:3366 Uncaught TypeError: Cannot read property ‘attributes’ of undefined
at uroFilterPlaceMarker (userscript.html?id=50fd45e1-6500-4f60-862e-b5e0ec48b082:3366)
at uroFilterPlaces (userscript.html?id=50fd45e1-6500-4f60-862e-b5e0ec48b082:3889)
Thanks, it appears the contains() function has been replaced by the apparently identically performing includes() function - it at least does what I need it to do in this context, so that was a nice easy fix…