Page 115 of 236

Re: [Script] WME Validator 1.1.20 / 03.11.2016

PostPosted: Mon Feb 13, 2017 2:02 pm
by johnsninja58
dbcm wrote:In the case you are using WME Validator through Tampermonkey, here is a fix.

https://github.com/dbcm/waze#valfix-tm-plugin


A very big THANK YOU

Re: [Script] WME Validator 1.1.20 / 03.11.2016

PostPosted: Sat Jul 01, 2017 2:54 pm
by johnsninja58
Validator has been a hugely valuable tool for the wme community. The efforts of a single editor have greatly contributed to a much more efficient editing experience. For this they should be applauded. They have also continued to support this script well after life priorities changed and they didn't have time for editing anymore. Again a huge thank you.

Howver I am happy to hear hints of a long term solution coming soon as the frequency this script has been breaking recently and patch work to keep alive shows the need for a more active maintenance approach. I look forward to what is coming soon

Re: [Script] WME Validator 0.7.3 (BETA) / 24.02.2014

PostPosted: Wed Feb 26, 2014 11:57 pm
by JoniX3000
I have not read the thread, so this maybe already have been reported, but if not, I've found a bug: using the Swedish language on WME makes Validator use Spanish instead of Enligsh.

Re: [Script] WME Validator 1.1.17 / 01.06.2016

PostPosted: Thu Jun 02, 2016 12:17 am
by JoshJMM
Is that the Chrome Extension version or the Script version?

Re: [Script] WME Validator 1.1.17 / 01.06.2016

PostPosted: Thu Jun 02, 2016 12:53 am
by JoshJMM
Ya, I'm not getting anything except the yellow bubble in the lower left corner with either of them.

Re: [Script] WME Validator 1.1.20 / 03.11.2016

PostPosted: Sat Apr 01, 2017 3:42 pm
by JoshJMM
Ok, I don't know if this is working for anyone else but even with the most current Valfix and Chrome extension, the report is almost blank. None of the roads that should be getting flagged in the report are flagging at all. I have even thrown out some bad roads to test it and only 1 flagged and it only flagged as not having a name but showed up Blue instead of Red as it did in the past.

In the past, when I did a run of Denver, the report would pause at least 5 times due to "too many roads segments". Now it runs in less than 4 minutes (used to take over 15 for a full scan) and never pauses. I want to say it's missing about 90% of the road segments or something close to that.

So here's the question- Since this script is one of the core troubleshooting scripts out there, are we really going to just let this one die on the vine trying to "patch it" via external scripts? Does anyone have a plan to replace this with another script? I know that it would be a moderate to heavy undertaking and should be a community project like WMEPH is, but I think that this script is that important that something like this needs to be done.

And no, I'm not talking about taking the current Validator and "reverse engineering it".

Thoughts anyone?

Re: [Script] WME Validator 1.1.20 / 03.11.2016

PostPosted: Sat Apr 01, 2017 3:49 pm
by JoshJMM
that's no problem if you are looking at a small town, but I'm talking Denver, Atlanta, LA. If you want to pan around at 500ft you are going to be panning for a week.

Re: [Script] WME Validator 1.1.16 / 29.01.2016

PostPosted: Tue May 24, 2016 10:16 am
by Jujuapika
It is not working at my side neither firefox nor chrome :(

Re: [Script] WME Validator 1.1.19 / 04.06.2016

PostPosted: Mon Sep 12, 2016 12:34 pm
by Jujuapika
I have the same problem too. But as I see the problem is just on that objects, what I (or somebody) have edited in the last days.

Re: [Script] WME Validator 2018.07.18 (BETA)

PostPosted: Mon Jul 23, 2018 12:52 am
by julianLechere
Thank you so much for bring it back!