[Script] WME Validator 1.1.20 / 03.11.2016

Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.

Moderators: Unholy, bextein

Forum rules
Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

DO NOT START a new thread unless it is about a new idea. Keep discussion of existing tools within the main thread for that tool.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby shmupi » Tue Mar 29, 2016 4:44 pm

Confirmed...it's broken :cry:
shmupi
Waze Global Champs
Waze Global Champs
 
Posts: 18541
Joined: Tue Jan 06, 2009 7:16 am
Has thanked: 3651 times
Been thanked: 1262 times

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby lg1992 » Tue Mar 29, 2016 4:23 pm

The new beta version of the editor broke the Validator (at least on Chrome). The error is:

Uncaught TypeError: Cannot read property 'length' of null
WME_Validator.user.js:129
lg1992
Country Manager
Country Manager
 
Posts: 2467
Joined: Fri May 04, 2012 9:50 am
Has thanked: 69 times
Been thanked: 311 times

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby EnGxBaDeR » Thu Mar 24, 2016 11:08 am

I can confirm there is a bug I think with WME Validator when taking/creating a permalink.
I had to log out and then in in order for the Validator to appear. (Reloading chrome didn't fix the problem).
EnGxBaDeR
 
Posts: 12
Joined: Sun Dec 13, 2015 5:07 pm
Has thanked: 1 time
Been thanked: 1 time

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby lg1992 » Wed Mar 23, 2016 4:53 am

I lose the Validator rather often, but I haven't notice a pattern so far. Usually it's enough to reload the Chrome page to get the Validator back.
lg1992
Country Manager
Country Manager
 
Posts: 2467
Joined: Fri May 04, 2012 9:50 am
Has thanked: 69 times
Been thanked: 311 times

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby FlySR » Tue Mar 22, 2016 4:17 am

is anyone having trouble with the WME Validator? sometimes it doesnt appear in chrom? After i log out - and back in it appears, and when i create a permalink for example, it disappears from the tools sidebar on the left?
FlySR
Area Manager
Area Manager
 
Posts: 50
Joined: Thu May 14, 2015 9:05 pm
Location: Paramaribo, Suriname,South America
Has thanked: 12 times
Been thanked: 2 times

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby Glodenox » Wed Mar 16, 2016 7:36 pm

Guys, isn't there some USA-specific thread about Validator in which such discussions can take place? Right now it's just cluttering this topic.

Another (easier) issue: would it be possible to fix the FontAwesome icons? This is what WME Validator looks like at the moment:
[ img ]

The problem is that the classes used to get FontAwesome icons were changed a month or two ago. You now need to apply the "fa" class and the icon-specific class. I've gone over the classes in Validator for you to make it easier:
icon-check -> fa fa-check-square-o (empty: fa fa-square-o)
icon-filter -> fa fa-filter
icon-search -> fa fa-search
icon-user -> fa fa-user
icon-wrench -> fa fa-wrench
icon-question-sign -> fa fa-question-circle
icon-list -> fa fa-list
icon-magic -> fa fa-magic

After these changes (I couldn't find any other occurrences of "icon-"), Validator looks like this again:
[ img ]
Glodenox
Map Raider
Map Raider
 
Posts: 307
Joined: Tue Aug 11, 2015 9:04 pm
Location: Belgium
Has thanked: 122 times
Been thanked: 337 times

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby K-L-B » Wed Mar 16, 2016 7:33 pm

I have one :)

https://www.waze.com/editor/?env=usa&lo ... s=83046199




PesachZ wrote:
nidnarb wrote:Anyway possible to get validator to stop saying roads that have a period are invalid. Example G.5 Rd NE, Q.1 Rd NE, T.7 Rd NE etc..

Thanks!

Sent from my Nexus 6P using Tapatalk

Do you have any permalinks for these roads, should they really have a period in the name? This is a check which is specific to USA and checks that names are in accordance with our recommended abbreviations.
K-L-B
Area Manager
Area Manager
 
Posts: 11
Joined: Mon Jan 11, 2016 4:39 am
Location: Pasco, FL
Has thanked: 3 times
Been thanked: 18 times

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby nidnarb » Wed Mar 16, 2016 6:24 pm

Part of the reason for the check is to avoid TTS issues. We may have to do something to accomodate here, or work around.


Well it does look like you got the TTS fixed. now the roads say the right name. Before they said ten zero 2 road north east. Now it says ten point 2 road north east. So hopefully you guys can get validator to work around this. Thanks again!
nidnarb
State Manager
State Manager
 
Posts: 149
Joined: Wed Apr 27, 2011 5:43 pm
Location: Bellingham, WA
Has thanked: 24 times
Been thanked: 48 times

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby PesachZ » Wed Mar 16, 2016 6:09 pm

nidnarb wrote:
PesachZ wrote:
nidnarb wrote:Anyway possible to get validator to stop saying roads that have a period are invalid. Example G.5 Rd NE, Q.1 Rd NE, T.7 Rd NE etc..

Thanks!

Sent from my Nexus 6P using Tapatalk

Do you have any permalinks for these roads, should they really have a period in the name? This is a check which is specific to USA and checks that names are in accordance with our recommended abbreviations.


Yes in Douglas and Grant County in WA have periods in the street name. When its a parralel road from the main one. Example G Rd NW, streets between that and F Rd NW would be something like G.7 Rd NW or G.3 Rd NW. I have confirmed from County GiS and one person who lives in the area thats how the streets are named. These are the same streets where i have the issue with TTS. Here is a PL of one of the road signs in that area. https://www.waze.com/editor/?env=usa&lo ... lter=false

Here is another PL of a road example at intersection. https://www.waze.com/editor/?env=usa&lo ... lter=false

If you need any other info let me know.

Part of the reason for the check is to avoid TTS issues. We may have to do something to accomodate here, or work around.
PesachZ
Wiki Master
Wiki Master
 
Posts: 4339
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1979 times
Been thanked: 2174 times

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby nidnarb » Wed Mar 16, 2016 5:53 pm

PesachZ wrote:
nidnarb wrote:Anyway possible to get validator to stop saying roads that have a period are invalid. Example G.5 Rd NE, Q.1 Rd NE, T.7 Rd NE etc..

Thanks!

Sent from my Nexus 6P using Tapatalk

Do you have any permalinks for these roads, should they really have a period in the name? This is a check which is specific to USA and checks that names are in accordance with our recommended abbreviations.


Yes in Douglas and Grant County in WA have periods in the street name. When its a parralel road from the main one. Example G Rd NW, streets between that and F Rd NW would be something like G.7 Rd NW or G.3 Rd NW. I have confirmed from County GiS and one person who lives in the area thats how the streets are named. These are the same streets where i have the issue with TTS. Here is a PL of one of the road signs in that area. https://www.waze.com/editor/?env=usa&lo ... lter=false

Here is another PL of a road example at intersection. https://www.waze.com/editor/?env=usa&lo ... lter=false

If you need any other info let me know.
nidnarb
State Manager
State Manager
 
Posts: 149
Joined: Wed Apr 27, 2011 5:43 pm
Location: Bellingham, WA
Has thanked: 24 times
Been thanked: 48 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: No registered users