[Script] WME Validator v2021.3.5 (+ PLACES BETA)

[AlanOfTheBerg]

My suggestion is to add set City and Street default fields to 'None'.

This should not be a global option. We catch lots of new/bad editors by being able to see the red roads at very wide zoom levels.

[AlanOfTheBerg]

Sheesh, I can't even get Validator to load at all. The only line in the console on load is "WME Validator v1.1.8: login AlanOfTheBerg". Win7/Chrome 46.0.2490.71 m. Ideas?

[AlanOfTheBerg]

Sheesh, I can't even get Validator to load at all. The only line in the console on load is "WME Validator v1.1.8: login AlanOfTheBerg". Win7/Chrome 46.0.2490.71 m. Ideas?

Are you in WME Beta? Validator is broken in the latest beta.

Nope, I wish it was that simple. I knew that it wasn't working in beta.

[alexschrod]

Being a software developer, I find it extremely frustrating when code is obfuscated and its license prevents you from trying to figure out what it does. Especially so in a community setting such as Waze.

Luckily, Javascript itself is incredibly malleable, so instead of modifying the script, let's modify a part of Javascript that the script relies on instead ... at least in Firefox, adding this peace of code directly under the LICENSE comment in the Greasemonkey script makes the script work again:

Code: Select all

Date.now = function() { };

Mind you, this may break all kinds of things, but as an emergency procedure while we wait for a new update, it works.

[alexschrod]

So, technically we're breaching the license, as it says "You may not modify [...] the script", although it could also be argued that we've modified a part separate from what actually constitutes the script part...

And, come on. If you're going to write code that expires, at least update it a while before it does. Even if the update consists of nothing more than extending the expiration date. In the next update, if the author wants this kind of behavior in place, they should add another check first that sends a request to see if there is an actual update ready before telling people the script has expired.

[alexschrod]

For this reason, I can see the point in having an expiration date in the script. Not everyone has their scripts set up to auto-update.

Hence my comment earlier about first checking if there is an actual update available before telling people to upgrade, when there's nothing to upgrade to.

I also second the question made about why this script is so locked down. If (and sorry for being morbid here) the author dies or disappears from the Internet, or whatever, nobody can pick up where they left off, at least not without violating the license on the script, and we'd simply lose out on all the time and effort spent making and maintaining this script. It would be a great shame.

It also prevents others from helping improve the script in various ways, so I really see no benefit whatsoever in keeping it locked down.

[alexschrod]

Any reason the Custom Templates are locked to having only two, and having non-configurable colors? It would be nice to be able to add/remove Custom Templates at will, and also to set their colors manually. I'm already using both the ones available, but I have a "need" for several more.

[alhonaifi]

Thanks Berestovskyy , Glodenox

[ali_zali]

my version is 1.1.20 and it is says it is out of date and should be upgrade
how?

[ali_zali]

hi guys
what should i do with this error???