Sorry, my bad. I was running the version from chrome store which is not v. 2022.8.25. Just installed the script via Tampermonkey and everything seems to be working!firecul wrote: ↑Sun Aug 28, 2022 1:03 pmStrange, that's what the most recent update is to fix. Is your script definitely v. 2022.8.25?SebastianJM21 wrote: ↑Sun Aug 28, 2022 9:58 am
So the venue ID is correct but the coordinates seem to be messed up.
Chrome and Script (from Chrome Store) are both up to date.
Best regards,
Sebastian
Sebastian
Con la actualización del WME son varios los scripts que han dejado de funcionar. Entre ellos el Validator.
- Attachments
Nilson Sánchezhttps://storage.googleapis.com/wazeoped ... 2/Gnat.gif
Waze Local Champ/Mentor
Colombia
Country Manager/WME Beta Tester
Whatsapp
Telegram
Waze Local Champ/Mentor
Colombia
Country Manager/WME Beta Tester
Telegram
The same action is repeated when scanning the map.SuperDave1426 wrote:Yup, I can confirm this behavior as well. I've got Fix Map Objects installed, so at least it does its thing while I'm editing. But doing a scan to get a report goes nowhere.iangpowell wrote:Click play, and it tells me "starting! layers are off to scan faster", and then nothing. It doesn't strictly crash, as I can still click around, and pause/stop, but no report appears and nothing else happens.
Nilson Sánchezhttps://storage.googleapis.com/wazeoped ... 2/Gnat.gif
Waze Local Champ/Mentor
Colombia
Country Manager/WME Beta Tester
Whatsapp
Telegram
Waze Local Champ/Mentor
Colombia
Country Manager/WME Beta Tester
Telegram
I think the following regex should work for you:Raiden38 wrote:I'm trying to do a custom code but I can't get it to work. Can you help me?
The goal is to highlight all the Primary roads that don't have a name, and they are longer then 50 ft.
First issue: it highlight some ramps
2nd issue: Depending on the test, it will highlight all roads bigger than 50ft!
Here is what I tried:
Code: Select all
/^1[1,3-5]#@:(([5-9][0-9])|([1-9]\\d{2,}))$/
If you are still having issues or if you see it highlight all segments, put a 'D' in front of the regex (i.e., D/regexgoeshere/) and check the JavaScript console to see what's going wrong.
I have to admit I'm one of the ignorant masses who had no clue that there was a difference between the two - until I read this and Googled for the explanation. We learn something new every day. Thanks!
Is anyone has news Berestovskyy?
Because I feel he edits no more...
https://www.waze.com/fr/user/editor/Berestovskyy
And what is the future of the script?
Because I feel he edits no more...
https://www.waze.com/fr/user/editor/Berestovskyy
And what is the future of the script?
How long have you sent the PM?jarkaz wrote:I wrote to him, but did not even read the message. [emoji20]
Ok, thanks for this newkarlcr9911 wrote:It's a known issue that Validator isn't working in this latest WME release. The script writer has been contacted. If he chooses to update it, he'll do so as soon as he has time.
Wait & see..
Hi all,
On FF(46.0.1) for ubuntu, it doesn't want to work...
It start, but i don't have any HTML...
@berestovskyy: I would like to help you, but your script is encrypted...
On FF(46.0.1) for ubuntu, it doesn't want to work...
It start, but i don't have any HTML...
Code: Select all
WME Validator v1.1.17: waiting for login...
WME Validator v1.1.17: login seb-d59
Hi,
I just try this:
just this:
I just try this:
But it do nothing.taco909 wrote:It was working on the old version when using this login, but I haven't been able to get it to load on FF since it updated to .17Code: Select all
javascript:Waze.loginManager.events.triggerEvent('login');
just this:
Code: Select all
WME Validator v1.1.17: already logged in!
Re: [Script] WME Validator v2022.4.16 (+ PLACES BETA)