fails to load in FF+GM

[moondoggeh]

hi, so far i had no luck with loading old versions in firefox. today i upgraded firefox and installed the new version of the script, and it loads up, but now it doesn't show the right window, with info of portals and such. just the arrow to minimize maximize that window and a button to change skins.

how and what am i doing wrong ;)

[jonatkins]

I'm not sure. Firefox+Greasemonkey does have some oddities when it comes to userscripts, so the following suggestions might help.

1. The remove process is only partial, with an 'undo' option, until Firefox is restarted - so I suggest uninstall IITC and all plugins, restart Firefox, and install from the website again.
2. A manual update check in Greasemonkey don't always seem to work. I think something caches the version info for a period of time. A manual install from the website will install the latest version.

[moondoggeh]

did number one a long time ago, and i do it everytime there is an update. I always update direct from the site, not via update button.The manual update can cause more clashes than usual. still a no go here. tried almost anything i could think of, including manually deleting the script folders in FF via TC, just to be sure something wasn't leftover while installing.

[jonatkins]

Just to be sure - you're installing from http://iitc.jonatkins.com/, yes? Not from Github.

The original breunigs version was installed from Github and not all documentation here has been updated to reflect this change.

[moondoggeh]

affirmative.

[moondoggeh]

http://www.dodaj.rs/f/h/hE/94Ir2zU/1.png

this is what i get

[breunigs]

which Firefox version do you use? Does it work when you deactivate GM and use Scriptish instead? Scriptish is effectively GM with a different name and their authors state that it "is better" or faster or some such. Maybe it’s an GM specific issue?

[moondoggeh]

same problems with scriptish. same look. FF 20.0.0.1 Win 8 x64bit

[jonatkins]

Odd.

Can you try the current dev version? http://iitc.jonatkins.com/?build=dev I've tested this on Firefox (20.0.1) + Greasemonkey (1.8)

Are there any errors shown in the Firefox web console?

Does your agent name have any "unusual" characters - things other than plain ASCII letters and numbers?

Perhaps clearing cookies + local data for ingress.com would help?

[breunigs]

it works here so it definitely is win8 fault. Nah, just kidding. Try this: hit ctrl + shift + k or activate the web console in Tools → Web Developer. Make sure the JS button is selected (the orange one) and reload the page. Are there any errors? If so,please copy them here.

[moondoggeh]

no unusual characters in name. Errors? just a "few", check the attached SS :p

p.s. don't get me wrong, i blame MS for this too lol http://www.dodaj.rs/f/Y/4b/1jIvpsMH/1.png

[jonatkins]

I get those same CSS-related errors, so it's not that.

[moondoggeh]

[17:01:37.068] TypeError: L.LayerGroup is not a constructor @ https://www.ingress.com/intel/:11

[17:01:37.706] TypeError: localStorage is not an object @ https://www.ingress.com/intel/:2139

[jonatkins]

Well those are errors I don't get - so probably part of the problem. Still, I'm scratching my head as to why it doesn't work for you.

Did you try clearing cookies for ingress.com? And localstorage too? (seems tricky for Firefox though)

Try opening a private browsing session to test - this should start with all cookies/storage cleared.

[moondoggeh]

private window = no go still. same thing. the last version didnt even work at all, showed midnight blue wallpaper in the tab and that's it. Just when i installed this new version i got something working :)

[jonatkins]

Did you try the dev version? http://iitc.jonatkins.com/?build=dev

It could be some kind of clash with another Firefox addon or Greasemonkey script - can you try all others disabled?

If it still doesn't work, I'm really scratching my head as to why it fails. Reinstall Firefox? Seems a bit extreme though..

You could try Google Chrome + Tampermonkey - 7 out of 10 IITC users prefer it :)

[moondoggeh]

i'm using the dev version since your post. i have tried with disabled addons, all. As far as GM scripts, i have only that and iitc scripts running on ingress tab. i will try to disable all scripts in FF to try. I'm not fond of reinstalling FF, as i'm a heavy "i want it to look and work how i want" guy, and that takes an eternity or two to setup :p

chome + tamper is my choice for now, when planing some actions, but i revert back to ff for normal usage

[jonatkins]

All very odd.

I've just created a test dev build - version 0.10.5.20130414.155900, with an updated leaflet.js (latest 0.5.1 and non-uglified) - give this a go. I'll leave it there for the next hour or so.

[moondoggeh]

i'm almost afraid to report that it's the same deal still :P

[JoeSyr]

It's been my experience with FF over the years that when all else fails, try making a new profile. Info: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

At the very least you can test a new profile to see if it doesn't have the same issues, and it's pretty easy to migrate your personal effects from one profile to another and still get the "clean slate" effect without redoing everything from scratch.

[jonatkins]

If it's the same deal, it eliminates one area for further investigation. I'd try the profile thing suggested - sounds pretty easy and worth a go.

[moondoggeh]

hmm..totaly forgot about that. It works in a new profile, and works like a charm. cheers now back to the drawing board to migrate

[moondoggeh]

ok,played a bit... c:\Users\zane dreadweep\AppData\Roaming\Mozilla\Firefox\Profiles\diill5ga.default\prefs.js <-this files makes all the hubbub....

[breunigs]

this is your firefox settings (i.e. everything you can set in Tools → Options or all the quirks you changed in about:config and forgot about). You can always dig down, but this is going to be a LOT of effort.

[jonatkins]

Very odd - but there again I've got my own share of oddities with Chrome profiles too, so it's not just Firefox.

I'll close this issue now. If you do discover the specific cause it would be nice to know.

[moondoggeh]

good morning :) the culprit is found. "user_pref("dom.storage.enabled", false);" when i remove this line from prefs.js, everything works great. Hopefully it will help you identify the problem, and prevent it in future. perhaps someone can even tell me what it does. I think it has something to do with TOR, a tunneling program.

cheers, and thanks for all your help. much appreciated.