We did.
“No inbound/outbound connectivity of driveable road”
That function went away in August 2014 when turn restriction data was moved from the segment to the junction (likely in preparation for JB). This was the same time we lost Validator visibility/flagging of Revcons and unconfirmed turns.
Given that Validator can pull flags from WMECH and TB, I would really like to get RevCon and Unconfirmed Turn flags back in the Validator report…
Getting back the “no inbound/outbound” may be more daunting as it requires the analysis of both the segment data (determine directionality and if routable) and the junction node, then comparing the two.
It may be too much complexity for what is essentially a fairly simple script.
I agree, it was a good feature when we had it (so long as that specific feature is locked so as not to display “errors” on segments locked above the editor’s level, as there are many times that we create these intentionally)
Since this morning, after installing the new version of Firefox (44) Validator don’t work anymore
No highlight and it don’t appear in the left panel.
Tested on versions 32 and 64 bits of Firefox (and Firefox Beta) and under WME prod and WME Beta
No problem with Chrome.
I’ve warned about this and even PM’ed the author about this with the simple fix that is needed. The script is now failing on a bit of code that doesn’t even work any more.
It is related to the removal of the Components object as of Firefox 44. This makes the logic so that the script tries to overwrite unsafeWindow (as it wrongly expects it’s not running Firefox), which then results in an exception being thrown.
Why is Validator taking up its own dedicated space in the lefthand side of the sidebar instead of being a separate tap? I’m going to have to disable it for now, it’s in the way. I only need it every so often. Maybe I’m missing an option, or this is a bug? Interaction with another script maybe? Same in prod and beta editors.
@khaytsus, believe me, you’re not the only one who wishes that we’d get an option to put Validator on its own tab since access to the interface itself is needed so infrequently… :?
As of this Forum Post in Aug 2015 (Thread Link from Wikipage above) it is now drivable.
Since then we use in the WME the ferry type and get a normal routing on these (tested them just now).
Hello guys! How long ago validator stopped notifying about same-level roads crossing?
I’ve found this bug recently. I.e. here we have a roadcross, wheere streets (yellow) are connected with nod and primary (blue, selected) is intersecting them. Validator is calm.
Please fix ASAP.
WME Validator - Raport wygenerowane przez tomi43 na 2016-02-07 Źródło raportu: No City SLOW: Brak połączenia w węźle B (#108) Węzeł B segmentu jest w odległości od innego, również przejezdnego segmentu, ale nie są połączone skrzyżowaniem.
Przeciągnij węzeł B na najbliższy segment, by się dotykały, lub odsuń go dalej.
No City
No Street, No City 269890894 [/*] Podsumowanie Liczba sprawdzonych segmentów: 4 Zaraportowanebłędy - 1 (250‰)
Żeby zmotywować mnie do pracy nad skrpytem, zostaw komentarz w Waze forum thread.
Wanted to submit an issue about an information box, that hangs over the user stats in WME. Is it possible to fix it anyhow? Looks annoying, actually.
This how it looks now in Russian interface:
Like most other scripts, the WME Validator seems to be broken by the WME 1.13 update. The Validator is an invaluable tool and I miss it very much. Is there any hope of an update soon that will fix these issues?
