InformAction Forums

The current version of NoScript is breaking the SWTOR website for me.

Enabled, I cannot log in to my account or view any of the flash content on the page. Disabling NoScript corrects this problem for me.

This addon is getting harder and harder to want to keep around, no matter how much it helps security.

Update after update breaks this site or that site. It's getting really, really old. It's getting even older to come here and mention the problem in the "ask for help" section, only to have no one from development even BOTHER to say "thanks, we'll look into it" or something. It's not like there are 600,000 new threads in this section every day or anything... hell, this thread hasn't even budged from its original spot in the thread list.

What browser are you running?
How is it "breaking"?
What domains have you allowed?

What does happen when you try to log in?

Any related messages in Error Console?

If you revert to an older version do things work again, http://noscript.net/feed?

If you leave NoScript enabled, but disable all other extensions, do things work?
If you create a new Profile & only install NoScript, do things work?


I'm seeing 3 Flash objects on the SWTOR main page.
Not sure what to expect in regards to login?

I've registered a "NoScript" test account and could successfully login with NoScript 2.0.3.5 (allowed "swtor.com" and "ea.com").

therube wrote:What browser are you running?
How is it "breaking"?
What domains have you allowed?

What does happen when you try to log in?

Any related messages in Error Console?

If you revert to an older version do things work again, http://noscript.net/feed?

If you leave NoScript enabled, but disable all other extensions, do things work?
If you create a new Profile & only install NoScript, do things work?


I'm seeing 3 Flash objects on the SWTOR main page.
Not sure what to expect in regards to login?

Browser:
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.11) Gecko/20101012 Firefox/3.6.11

How is it "breaking?":
I covered that in the original post. With NoScript enabled and running, I cannot view most of the flash content on the site and I cannot login to the site. Disabling NoScript fixes the problem.

What domains have you allowed:
swtor.com and ea.com are allowed for that site. SWTOR.COM for obvious reasons, and EA.COM because EA are the parent company of BioWare, the developer.

What happens when you try to login:
Nothing happens. Because the login screens require java and a little flash and entering my information in those fields with NoScript running yields "wrong username or password" errors because the default "Email Address" and "Password" values in those fields is not cleared when I click in there and cannot be cleared with delete or backspace.

Does reverting to previous versions fix it:
Not sure I should have to revert, but it worked before the most recent update came across. I will try, but using the current version is what I would prefer to do.

Any errors in error console:
6 errors and all say the same thing - "cookie is undefined : chrome://noscript/content/ScriptSurrogate.js"

Enabling or Disabling other extensions:
I went one step further in tracking this down initially. I completely removed all extensions and added them back one at a time until I got the problem. NoScript was the one where it started. It also exhibits the same behavior when I run under a different and new profile.

The only flash objects I can see on the main SWTOR site are the bottom boxes that say "newsletter signup" and "testing signup." The main information flash object above those won't even load at all and, as I said, the login is non-functional for me.

Giorgio Maone wrote:I've registered a "NoScript" test account and could successfully login with NoScript 2.0.3.5 (allowed "swtor.com" and "ea.com").

I am using 2.0.35 as well and it's just not working unless I disable NoScript.

It works for me. (Minefield 4.08bpre, NoScript 2.0.3.5rc1)

SWTOR wrote: Enabling or Disabling other extensions:
I went one step further in tracking this down initially. I completely removed all extensions and added them back one at a time until I got the problem. NoScript was the one where it started. It also exhibits the same behavior when I run under a different and new profile.

Does it mean that a fresh profile, with NoScript installed and all default options except the two aforementioned permissions break?
Then it might be a Flash problem.
Have you got latest Flash version?
Could you check the downgrade thing, to rule out a recent NoScript change (even though we've got at least two people here, me and hfjimenez, who made it work with latest build)?

SWTOR wrote:I completely removed all extensions and added them back one at a time until I got the problem. NoScript was the one where it started. It also exhibits the same behavior when I run under a different and new profile.

Disable all your extensions except NoScript. Does the problem persist with all your other extensions disabled?

Giorgio Maone wrote:Does it mean that a fresh profile, with NoScript installed and all default options except the two aforementioned permissions break?

Do this with just NoScript installed, i.e. no other extensions.

No extensions installed with the exception of NoScript:
v2.0.3 - Works
v2.0.3.1 - Works
v2.0.3.2 - Works
v2.0.3.3 - Does not work
v2.0.3.4 - Does not work
v2.0.3.5 - Does not work

Something was changed and it is no longer working from 2.0.3.3 I guess. Which is odd to me, because it worked originally in v2.0.3.4 and only stopped when .35 was pushed.

It's still not clear to me if you try in a default configuration (i.e. after NoScript Options|Reset or installing NoScript from scratch in a virgin profile).

Giorgio Maone wrote:It's still not clear to me if you try in a default configuration (i.e. after NoScript Options|Reset or installing NoScript from scratch in a virgin profile).

Yeah, I tried it in a fresh profile. In fact, I just now tested it on another machine which did not have Firefox on it. It breaks when 2.0.3.5 is installed and it does the same thing... stops working at v2.0.3.3 and above when I revert to older versions. Not sure what the deal is since it is working for some other people here but, then again, it works for me up until I replace it with 2.0.3.