[Script] WME Validator v2020.11.1 (PLACES BETA)

[Tailszefox]

The first part of this, ie what is after the |

Code: Select all

/^:([0-9]{3,5}|[5-9][0-9]$)/

means that it matches any number with 3 to 5 digits, while the second part is an alternative saying that for 2 digits number, it should only match things that are at least 50. So basically, if you leave out the second part, you'll only match numbers with 3 to 5 digits, effectively from 100 to 99999:

Code: Select all

/^:([0-9]{3,5}$)/

As a side-note, your first example matches anything below 17, not above, though I suppose this is intended as such. If that's the case you can ignore this remark.

[Tailszefox]

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

I assume that's going to at least break the "segment has expired restrictions" check, and any kind of check that relies on the current date, yes. But until then, it is an acceptable workaround. Thanks!

EDIT: Actually, without looking far, it already breaks the estimated time to finish scanning when scanning an area, saying "Finished in NaN minutes". Not a major thing by any mean, though.

[Tailszefox]

There's one major hurdle with having someone else take over the script without any assistance from the original author: the code is heavily obfuscated. Meaning the person taking over would have to reverse engineer it, which would be both hard and time consuming. And that's not even taking into account the fact that it's explicitly forbidden by the script's license.

While the logic behind that decision makes sense (preventing people from accessing features they are not authorized to use), it also has this major side effect of rendering the script unusable without support from its original author...

[tango259]

***TO EVERYONE HAVING ISSUES WITH VALIDATOR AFTER THE WME UPDATE***

Due to the recent update to the Waze Map Editor, many scripts and plugins are not functioning properly. This includes Validator. At this time, all we can do is WAIT for the developers to adjust the code to work with the new UI and backend updates that were done on Waze's side. As editors, we have nothing we can do to make it work.

My Suggestions:
-Go to your extensions list in Chrome each day and click "Update extensions now".
-If you have scripts installed as well, whether they're related to Validator or not, update them within Tampermonkey (or whatever script extension you're running).

Just because Validator is not working right now, DOESN'T MEAN WE CAN'T EDIT. I see too many editors (more so the new editors) rely too much on Validator for getting edits to increase rank. It's true, Validator helps with that. But it's not the only way. Take this time to clean up your areas, work on URs, do interchange scrubs, etc. The developers of Validator are working hard to get this awesome plugin working again! Let's give them the time they need

If any new editors have questions on what they can do to keep getting edits, please PM me! Cheers!

[Taxy57]

This is a great tool, especially for new member like me.

But hard to find it exist

[Taxy57]

Great tool for new member like me.

Can it be more visible like in the https://wiki.waze.com/wiki/Main_Page

[Taxy57]

I got that message

WME Validator v1.0.2 error:
This build of WME Validator has expired. Please upgrade!

Try to re-install from Chrome Web Store.
Don't work.

How do i fix that ?

[Taxy57]

It's hard to find the list of road type

Road type: variable ${typeRank} expands to:
1 for Runways
2 for Railroads
...
14 for Major Highways
15 for Freeways

Can you list them all
Otherwise i have to test each on map

[tel601]

Current version of validator shows June 4, 2016 as the posting to greasy fork. Creator may not be editing but was still working on scripts in the middle of this year.

[tel601]

The code of the script can seen and looked over.
Here is the remarks at the beginning of the script.
// ==UserScript==
// @name WME Validator
// @version 1.1.19
// @description This script validates a map area in Waze Map Editor, highlights issues and generates a very detailed report with wiki references and solutions
// @match https://editor-beta.waze.com/*editor/*
// @match https://www.waze.com/*editor/*
// @exclude https://www.waze.com/*user/*editor/*
// @grant none
// @icon http://s3.amazonaws.com/uso_ss/icon/191 ... 1388868317
// @namespace a
// @author berestovskyy
// @copyright 2013-2016 berestovskyy
// ==/UserScript==
//
/*
* LICENSE:
* This script has some features locked for certain
* countries/editor levels, so there are 2 restrictions:
*
* 1. You may not modify or reverse engineer the script.
* 2. You may not use the script for commercial purposes.
*
* The script is distributed 'as is'. No warranty of any
* kind is expressed or implied. You use at your own risk.
*
* If you do not agree with the terms of this license,
* you must remove the script files from your storage
* devices and cease to use WME Validator.
*
*/

I checked it and found that the coder included some protections in the script. He would need to modify the script some to make it public domain.

His wishes should be respected. All we can do is wait for him to update the script or release it as a modified version for others to fix the issue. If anyone has a way to contact him they may be able to get more information or encourage him to change the script.