Well, I hope it gets figured out and fixed soon. I’ve gotten quite fond of (most of) the WMEPH features.
I tried firing up WME Beta just to see how it would behave over on that side. Strangely enough, I can’t even get WMEPH to run on that side. The button to “Run WMEPH” is visible, but when I click it, nothing happens. So I can’t verify what the interface looks like on the Beta side from my end.
Ok, when I say Beta, I’m not talking about WME Beta, it’s WMEPH Beta
Oh ok, sorry for the confusion. Figured you meant the beta editor it was behaving differently in.
Regardless of the slight difference in the way they loo, though, I still can’t figure out why I’m getting the squish and lack of usual information, and you’re not… (No, I don’t expect you to have an answer to that; I’m just mussing out loud. 
)
I am seeing what you are, but only in production WMEPH. It’s not as pronounced as yours but it is there.
Correct. There is currently not a localization outside of North America (I think US and Canada is it).
Something changed and now it goes to this site https://raw.githubusercontent.com/WazeUSA/WME-Place-Harmonizer/master/WME-Place-Harmonizer.user.js#bypass=true but I am not able to access this site when I am at work. So I can no longer get updates of this script 
I came up with a workaround due to this issue. Basically I take the script and manually post it to my GreasyFork site and imported then set to sync the jquery-ui script automatically. Then I edit the @require line in the main script to point to the GreasyFork copy of jquery-ui.
I can show you what I did if you want.
My WMEPH got updated to 1.2.19 this morning. Now, when I select a PP and click the WMEPH button, nothing happens…I shut down all scripts, leaving only Toolbox running. Still no joy. Running Chrome on a Mac.
Welcome to my world… Since 1.2.17 it hasn’t been working right for me. Doesn’t run if I click the “run WMEPH” button, no place colored highlighting on the map, everything squished at the top as per the image I included in my first posting on this… Unlike you, abc1357, I’m running Windows, but I am using Chrome. And I’ve turned off all scripts except for Tampermonkey and WMEPH, and the problem doesn’t clear. I’m really hoping that whatever is causing the issue gets corrected soon…
I just tested WMEPH Beta 1.2.19 in WME production and it seemed to work for me.
Have you updated your Language Settings? You must be in US English, not just English in order for it to work.
Holy cow! That was it. I haven’t bothered going to the Waze settings (haven’t needed to) in a long time. When did they separate that out to “English” and “US English?”
But yes, I checked that setting and it was in fact “English.” Changed it to “US English” and then my map refreshed, I got a popup inviting me to something called the Great Race (or something like that), which I dismissed, and all the Place areas on the map on the map showed up in color again according to what WMEPH liked or didn’t about them. I clicked on a place, and for one frightening moment, the top of the side panel looked wrong, but it corrected itself, WMEPH ran and provided me the usual info.
Yay! :mrgreen:
Thanks x1000 for spelling that out to me - I was seeing the map information in English, so I didn’t realize that they’d added a new language type there.
That was just changed a few days ago. Glad that fixed it!
I am glad the information was useful.
WMEPH just updated to 1.2.20, now I get this in the console and WMEPH won’t load in beta or prod:
Syntax error @ “WME Place Harmonizer”!
##########################
JSHINT output:
require: (W041) Use ‘===’ to compare with ‘null’ on line: 28 at character: 87
require: (W041) Use ‘!==’ to compare with ‘null’ on line: 46 at character: 158
require: (W030) Expected an assignment or function call and instead saw an expression on line: 89 at character: 65
require: (W030) Expected an assignment or function call and instead saw an expression on line: 96 at character: 200
require: (W030) Expected an assignment or function call and instead saw an expression on line: 152 at character: 530
require: (W030) Expected an assignment or function call and instead saw an expression on line: 231 at character: 1137
require: (W030) Expected an assignment or function call and instead saw an expression on line: 241 at character: 195
require: (W030) Expected an assignment or function call and instead saw an expression on line: 255 at character: 712
require: (W030) Expected an assignment or function call and instead saw an expression on line: 341 at character: 1683
require: (W030) Expected an assignment or function call and instead saw an expression on line: 404 at character: 947
require: (W030) Expected an assignment or function call and instead saw an expression on line: 466 at character: 149
require: (W030) Expected an assignment or function call and instead saw an expression on line: 500 at character: 301
require: (W041) Use ‘===’ to compare with ‘null’ on line: 528 at character: 754
require: (W041) Use ‘!==’ to compare with ‘null’ on line: 623 at character: 600
require: (W041) Use ‘!==’ to compare with ‘null’ on line: 756 at character: 2001
script: (E030) Expected an identifier and instead saw ‘1.2.18: FIXED - Some categories throw an error when being set from PNH.’ on line: 282 at character: 13
script: (W084) Expected a conditional expression and instead saw an assignment on line: 7505 at character: 36
script: (W084) Expected a conditional expression and instead saw an assignment on line: 7561 at character: 37
##########################
SyntaxError: Unexpected string
at new Function (<anonymous>)
at Object.E_c (<anonymous>:3:114)
at E (eval at exec_fn (:1:108), <anonymous>:57:175)
at Object.create (eval at exec_fn (:1:108), <anonymous>:65:282)
at z (eval at exec_fn (:1:108), <anonymous>:14:88)
(anonymous) @ VM38400:58
Its amazing what a single misplaced typo “(” can do to a script… my fault… . update to v1.2.21 and it should go away.
Scripts are so picky, except I am getting the same error with 1.2.21. :lol:
On another note, thanks to Mike (MapOMatic), WMEPH has been updated to work with any language now. The WME-PH specific text will still appear in English but as long as you are in USA or Canada the script will work. The country lockouts are still in place, but we have plans to expand to other countries as soon as our refactor is done (as stated in a previous post).
If WME-PH wont load please change your language to any other language, and then change it back to your preferred language. That should fix the issue that is preventing WME-PH from loading.
Same errors still with 1.2.22
1.2.23 should work.
Sent from my iPhone using Tapatalk
3rd time’s the charm. Works again. Thanks!