[Script] WME Junction Node Fixer v0.2.1 2017-08-16

ModImmo · February 5, 2014, 4:44pm

same here

Bigbear3764 · February 5, 2014, 4:54pm

New WME version was released today. I’m sure he will be on this to update it. Stay tuned…

qwaletee · February 5, 2014, 5:14pm

ArlenBystander:

I am getting the following error on the beta version of WME for the USA:
WME Junction Node Fixer has failed to load due to API check: wazeModel
I’m running the latest version of Chrome for MacOS and version 0.0.7.6 of JNF. FYI, I do not see the error on the regular version of WME.

I get it in production WME on Chrome via TamperMonkey, 0.0.7.6.

ModImmo · February 5, 2014, 5:20pm

qwaletee:

ArlenBystander:
I am getting the following error on the beta version of WME for the USA:
WME Junction Node Fixer has failed to load due to API check: wazeModel
I’m running the latest version of Chrome for MacOS and version 0.0.7.6 of JNF. FYI, I do not see the error on the regular version of WME.
I get it in production WME on Chrome via TamperMonkey, 0.0.7.6.

known issue

bgodette1 · February 5, 2014, 5:31pm

Updated to current dev.

goodolsen · February 5, 2014, 6:22pm

Working again, thanks bgodette.

no1ne · February 5, 2014, 9:33pm

to allow JNF to work with localized WME
please add:

// @include             https://*.waze.com/*/editor/*

AlanOfTheBerg · February 5, 2014, 9:39pm

That’s a good point. I didn’t realize it wasn’t working with the language localizations, where the language code is in between the hostname and /editor.

bz2012 · February 6, 2014, 6:11am

I had to install the latest Chrome because the WME update seems to be broken on the older, portable version of chrome I was using. Everything was very slow, some turn arrows missing. I don’t know what else was broken.

The latest chrome will not install the WME JNF because it is not on the chrome.google.com/webstore.
Does anyone know a workaround?

ModImmo · February 6, 2014, 6:12am

use tampermonkey

Sent from my Nexus 5 using Tapatalk

bz2012 · February 6, 2014, 6:37am

Thanks. Installing now. Will see if it helps.

Edit: I was in the developer mode. Using Version 32.0.1700.107 m
Tampermonkey DID solve the problem.

AlanOfTheBerg · February 6, 2014, 6:41am

I’m on Chrome 32 and don’t use tampermonkey and loaded JNF .user.js file just fine. Probably do have to be in developer mode…

goodolsen · February 6, 2014, 1:18pm

Or you can download the .js file and drag it into your extensions window.

That will install it also.

AlanOfTheBerg · February 6, 2014, 5:11pm

Well, yeah, that’s the normal way. But I think you need to have Developer Mode on.

goodolsen · February 6, 2014, 5:54pm

My Developer Mode option isn’t checked and I can install the .js files with drag and drop, either from the download bar at the bottom of the browser or the actual folder I downloaded to.

Arnoniem · February 7, 2014, 8:05am

I installed the latest JNF yesterday by dragging into ext. window. It worked OK, with develop mode on.
But today i got the message that all extensions were disabled, if not coming from the chrome store. and there’s a checkbox to re-enable them, but on the JNF and other waze tools, its grey. So not working currently, also in dev.mode as said.

Using Chrome 33.0.1750.70 beta-m

Going to install the tampermonkey now.

goodolsen · February 7, 2014, 4:19pm

What happens if you uncheck the Developer Mode option?

masvbr · February 7, 2014, 4:21pm

I updated to 0.0.8.2 with FF v27.0 and it doesn’t work.
Error message: WME Junction Node Fixer has failed to load due to API check: Waze.map

What is wrong?

goodolsen · February 7, 2014, 4:23pm

Do you have more than one version of JNF installed?

Not sure how it works on FF, but on Chrome you can have more than one version.

JimmyK1 · February 7, 2014, 4:25pm

Same here. Its been like that for the past few days.
I’m using the editor at https://www.waze.com/editor/ and not in a Developer mode. (as mentioned in previous pages).
Nevertheless i even did try to add the
// @include https://.waze.com//editor/*
but that didnt work either.