[Script] UROverview Plus v3.113 (20170926)

by **SuperDave1426** » Wed Jul 02, 2014 3:00 pm

That seems to be working now, thanks!

BTW, you might want to put in some kind of "disclaimer" (for lack of a better term) regarding the new feature that's supposed to show what Area Managers have been assigned to the area under the mouse. If it's getting that information from the AM layer of the map, then it's going to be of limited usefulness. At least here in the US, there's been a long-standing issue with that layer not showing the current AMs. I had noticed several months ago that my username doesn't show up when I turn on that layer in the map and I asked my RC about it - who informed me of the long-standing issue.

So until Waze programmers get around to fixing that particular issue, that feature of the extension is going to be, as I said, of limited usefulness.

by **GeekySmurf** » Wed Jul 02, 2014 12:42 pm

It is now working for me!

by **Twister-UK** » Wed Jul 02, 2014 6:46 am

Well that was odd... the package I uploaded to the CWS contained the 3.11.1 code in the main user.js file, yet the filename was still set to 3.11. Meanwhile both manifest.json and bootstrap.user.js were referencing the main file with the expected 3.11.1 filename, which is something I normally only change once I've changed the filename of the main file. So I'm really not sure how the main filename ended up being wrong in the uploaded package.

Anyway, I've uploaded another package which should now work as planned - note that to get around the "you can't upload a new package with the same version number, you muppet" problem (nice of the CWS to sanity check the version number for you, be even nicer if it'd also check that the files referenced in your manifest are present in the package...) it'll show up as 3.11.1.1 in CWS, but the script itself still calls itself 3.11.1 as that hasn't changed. The .crx packed version checks out OK in Canary, so it looks like all the filename references tie up correctly this time.

Fingers crossed :oops:

by **SuperDave1426** » Wed Jul 02, 2014 6:24 am

glomp wrote:Version 3.11.1 works for me

Oh, so YOU'RE the one! :lol:

Mac OSX 10.9.3, Firefox v31(beta)

Oh, well that's probably why - the version for Firefox probably doesn't have whatever bug is keeping it from working in Chrome. I'm sure he'll get it fixed soon. :-)

paulkok_my wrote:I've tried Greasyfork update and it works on my Chrome.
Firefox+Greasemonkey version: https://greasyfork.org/scripts/1952-uroverview-plus-uro

I just gave that a try myself - I disabled the Chrome extension and then added that to Tampermonkey, and it seems to be working just fine. I wonder what the heck crept into the Chrome extension version that's causing the trouble...? Anyway, I've got it working again via the Greasyfork script, so I'm happy again. :-)