Waze forum

Ooh, my first script update of 2016... Seems only fitting to give this honour to the script that, for various reasons, ended up receiving rather less of my attention last year than I'd have liked.

2.22 brings the following changes:

• Yellow "cached area" tint can be disabled
• Areas queued for data retrieval are now tinted grey
• PUR filtering fixed for latest WME changes
• Support for "Road closure" MPs

And, fingers crossed, it should also remain operational after Firefox 44 is released...


Firefox+Greasemonkey version: https://greasyfork.org/scripts/1948-livemap-ur-overlay
Chrome Web Store version: https://chrome.google.com/webstore/deta ... niefljookp

2.23 now deliberately supports residential PURs... Also, for PURs with multiple change requests, the type of each request is now shown in the PUR popup, rather than just the type of the first request - this may help to explain why some PURs seemingly used to get filtered incorrectly based on the type filters selected and the type shown in their popup.


Firefox+Greasemonkey version: https://greasyfork.org/scripts/1948-livemap-ur-overlay
Chrome Web Store version: https://chrome.google.com/webstore/deta ... niefljookp

gic78 wrote:Hi!
I guess that LMUR doesn't filters private places now, only public PURs.

They were never deliberately included in the PUR data, so if at any point LMUR was able to show/filter them then it was as a side-effect of the way the Waze server was responding to the data requests I was making... As of 2.23 however, residential PURs are now included as something LMUR expects to see

fjsawicki wrote:I've lost all my check boxes in the LMUR configuration panel. Even the top level one that enables.

I'm running on chrome with release 2.23. I've tried removing and reinstalling.

The only errors showing in console log are three instances of fontawsome failing to load?

Any thoughts or ideas?

Thanks

Waze have added something to the native page CSS which now causes all checkboxes to be hidden. One can only wonder what their reason for doing this might be, given the complete absence of checkboxes in the native Livemap UI...

Yes...

2.24 undoes the UI styles applied by the latest CSS update from Waze...


Firefox+Greasemonkey version: https://greasyfork.org/scripts/1948-livemap-ur-overlay
Chrome Web Store version: https://chrome.google.com/webstore/deta ... niefljookp

Oh, this doesn't surprise me in the slightest, ISTR some native functionality got broken the last time they messed around with the LM code too...

No problems here in either FF or Chrome. Given that the UI expand arrow isn't even working, this sounds like it could be a livemap page loading error that's preventing LMUR from completing its own initialisation...

SuperDave1426 wrote:I've just tried the "disable all scripts except LMUR" trick

There aren't that many scripts targetting livemap, so figuring out which one it was ought to be fairly easy... if you can let me know what you're running and on which browser, I can take a look here.

Hmm. As the thread title indicates, I haven't touched this code in *ahem* a while, so it's entirely possible some recent change behind the scenes has caused it to stop working. I'll take a look at it soon and see what might need fixing, although I might need to spend a day or two just reminding myself how the code works!