[Script] WME Validator 2020.04.12 (PLACES BETA)

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, Glodenox, JustinS83

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 2018.07.18 (BETA)

Postby jajarom » Thu Jul 19, 2018 7:19 am

Great news ;)
jajarom
Map Editor - level 2
Map Editor - level 2
 
Posts: 61
Joined: Thu Dec 29, 2016 9:38 am
Location: Romania
Has thanked: 2 times
Been thanked: 9 times

Re: [Script] WME Validator 1.1.0 / 29.08.2014

Postby james890526 » Fri Aug 29, 2014 6:56 am

berestovskyy wrote:29.08.2014 v1.1.0:
- Compatibility with beta WME
Note: some checks are still disabled
- Updated for BE #160 'Incorrect Freeway name'
- Disabled for IL #91 'Two-way Ramp segment'
- Removed 1 sec startup delay introduced in v0.6.2


Thank you very much
Best regards,
Lee Zhong Zhen
Local Champ - Malaysia

[ img ][ img ][ img ][ img ]

Waze Malaysia [ img ] [ img ]
james890526
Waze Local Champs
Waze Local Champs
 
Posts: 247
Joined: Sun Jun 22, 2014 7:00 pm
Has thanked: 52 times
Been thanked: 42 times

Re: [Script] WME Validator 1.1.7 / 06.03.2015

Postby james890526 » Thu May 07, 2015 9:12 am

Thanks again to this wonderful script where many of us have felt like a hole in our heart when it's not available for using. Thank you for spending your quality time to make us this great feature and may your work continue to inspire us to be a better editing community :D
Best regards,
Lee Zhong Zhen
Local Champ - Malaysia

[ img ][ img ][ img ][ img ]

Waze Malaysia [ img ] [ img ]
james890526
Waze Local Champs
Waze Local Champs
 
Posts: 247
Joined: Sun Jun 22, 2014 7:00 pm
Has thanked: 52 times
Been thanked: 42 times

Re: [Script] WME Validator 1.1.8 / 07.05.2015

Postby james890526 » Fri May 08, 2015 9:27 pm

SuperDave1426 wrote:Thanks for maintaining this highly useful WME addon. It's appreciated, and this is a highly useful tool used by many.

That said, this recent flurry of messages here is a prime example of why hardwiring an arbitrary "expire" date into such an important and widely used tool is a bad thing, regardless of what the "motivation" behind it is. If you happen to not be able to get around to doing an update (especially if it's for no other purpose than to update the "expire" date) by the deadline, then a lot of people get inconvenienced for no reason. It isn't broken - it just refuses to work because the date has passed.

Just sayin'....


It's a tool berestovskyy created. If it's a mean to help motivate him, why not? It's one of those perfect script that we've been using daily and taking for granted sometimes, so I'm satisfied if an update comes quick or slow or maybe never ;)
Last edited by james890526 on Thu May 14, 2015 8:13 pm, edited 1 time in total.
Best regards,
Lee Zhong Zhen
Local Champ - Malaysia

[ img ][ img ][ img ][ img ]

Waze Malaysia [ img ] [ img ]
james890526
Waze Local Champs
Waze Local Champs
 
Posts: 247
Joined: Sun Jun 22, 2014 7:00 pm
Has thanked: 52 times
Been thanked: 42 times

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Postby james890526 » Wed Mar 30, 2016 7:40 pm

shmupi wrote:Confirmed...it's broken :cry:

Ya it's not loading in Chrome. Weird much :( :(
Best regards,
Lee Zhong Zhen
Local Champ - Malaysia

[ img ][ img ][ img ][ img ]

Waze Malaysia [ img ] [ img ]
james890526
Waze Local Champs
Waze Local Champs
 
Posts: 247
Joined: Sun Jun 22, 2014 7:00 pm
Has thanked: 52 times
Been thanked: 42 times

Re: [Script] WME Validator 1.1.17 / 01.06.2016

Postby james890526 » Thu Jun 02, 2016 9:11 am

Nimbus- wrote:
mrsmith66 wrote:In Chrome - Validator seems to be preventing the left pane from scrolling, making the other tools unusable.


As a temporary fix, I've toggled it to move to the bottom. But now I can't hide the bubble blimp at the bottom.

Same here, now I can't access Validator and the only solution is to reinstall it if I need to use it and never to put it at the bottom
Best regards,
Lee Zhong Zhen
Local Champ - Malaysia

[ img ][ img ][ img ][ img ]

Waze Malaysia [ img ] [ img ]
james890526
Waze Local Champs
Waze Local Champs
 
Posts: 247
Joined: Sun Jun 22, 2014 7:00 pm
Has thanked: 52 times
Been thanked: 42 times

Re: [Script] WME Validator 1.1.20 / 03.11.2016

Postby jangliss » Wed Apr 19, 2017 2:39 pm

dbcm wrote:valFix 1.0.3 is out
https://dbcm.github.com/waze/valfix/valfix.user.js

Also adds Validator to layer menu.


Thanks to justins83


First off, I want to echo the communities appreciation for the work that's been done to patch Validator with external fixes to get it working again. It's hugely appreciated. That said...

Not sure if it's just me or not, but when you set your language in WME, say "US English" for example, none of the custom titles, solutions, or problem descriptions come across. For example:

Code: Select all
   "titleEN": "Wrong banner abbreviation",
   "problemEN": "Banner abbreviation may be incorrect. Abbreviations ALT, BUS, BYP, CONN, LOOP, and SPUR should be in ALL CAPS",


When you mouse over a road that is impacted by the issue, all you get is "The segment matched custom conditions", like it couldn't find the fields that had the message.

Another thing to note is that when you change your language to "US English" the localization becomes "en-US" and not just "en". This might be where the issue comes up if it's just doing a simple case change for the language. I've only briefly tried to understand the obfustication and such in the validator script, so I could be way off.

The change in the localization also means that the translations hack in the valfix.user.js may be an issue.

Code: Select all
if (typeof I18n.translations.en == 'undefined') {
    I18n.translations["en"] = {
        "layers": {
            "name": {}
        }
    };
}


I've not spent a huge amount of time digging through the valfix and utils code, so I'm not sure if there is a way to squeeze some "fix" in there. I might try going through it this weekend and seeing what I can come up with, unless you already have an idea.

Thanks again!
jangliss
State Manager
State Manager
 
Posts: 177
Joined: Tue Jul 13, 2010 9:56 pm
Location: Plano, TX
Has thanked: 119 times
Been thanked: 97 times

Re: [Script] WME Validator 1.1.20 / 03.11.2016

Postby jangliss » Wed Apr 19, 2017 6:57 pm

ldriveskier wrote:jangliss - is that a problem with Validator and its fix or with a validator Localization script? I know the Localization scripts that I use were modified after the language change, so yours might need that also.


By "localization script" I'm assuming you mean the one we use to put our own validation rules in, in which case I'm not past thinking that is the issue, but it works when we use the default languages (just set to "English" [en]) but not "US English" [en-US], which means we'd need to know what validator is looking for to match when the language is [en-US]. I may have missed the page that mentioned what that new localization values should be. I'll go back through the posts and see what I can see.
jangliss
State Manager
State Manager
 
Posts: 177
Joined: Tue Jul 13, 2010 9:56 pm
Location: Plano, TX
Has thanked: 119 times
Been thanked: 97 times

Re: [Script] WME Validator 1.1.20 / 03.11.2016

Postby jangliss » Wed Apr 19, 2017 8:05 pm

So I did some further testing, and it seems if you use the following in the "header" section it kicks in for both languages, the problem is that it doesn't really match the languages later on.

Code: Select all
window.WME_Validator_United_States = {
    ".country": "United States",
    ".codeISO": "US",
    ".author": "jangliss",
    ".updated": "2017-04-19",
    ".link": "TODO: ",
    ".lng": ["EN","EN-US"],


With ".lng" set to both "EN" and "EN-US" it picks up both languages. That said, if you use the "en" (or "en-us") in the title, problem, or solution text, it doesn't pick it up in either platform. For example:

Code: Select all
    "130.title.en": "The segment is assigned to another state",
    "130.title.en-us": "The segment is assigned to another state",
    "130.problem.en": "The segment is assigned to another state",
    "130.problem.en-us": "The segment is assigned to another state",
    "130.solution.en": "Make sure you are editing in TX, OK, MS, LA, or AR, and change it or disable script when working in another state",
    "130.solution.en-us": "Make sure you are editing in TX, OK, MS, LA, or AR, and change it or disable script when working in another state",


This is what you end up with:
2017-04-19 14_46_14-Clipboard.png



If however, you just put it in like this:

Code: Select all
  "130.title": "The segment is assigned to another state",


It works across both "English" and "US English" platforms, but that doesn't really seem like it is being "localized", more overriding the default title.

Either way, I think I got it working so I just need to do some tweaking, and such.
jangliss
State Manager
State Manager
 
Posts: 177
Joined: Tue Jul 13, 2010 9:56 pm
Location: Plano, TX
Has thanked: 119 times
Been thanked: 97 times

Re: [Script] WME Validator 2018.08.01 (BETA)

Postby jangliss » Thu Aug 02, 2018 9:50 pm

turbomkt wrote:
Olestas wrote:No more GF version? Only market?


https://greasyfork.org/en/scripts/1571-wme-validator


I get an error that reports the script has been deleted with that link. Is it correct? I did some quick searching on GF and found https://greasyfork.org/en/scripts/370783-wme-validator which appears to be the right one, but I'd rather the author(s) update the link, and correct the front page as well.

Cheers!
jangliss
State Manager
State Manager
 
Posts: 177
Joined: Tue Jul 13, 2010 9:56 pm
Location: Plano, TX
Has thanked: 119 times
Been thanked: 97 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: Alex-ti, JimboBaggins1966, jm6087, mudge42, vince1612