InformAction Forums

When I navigate to http://hypo.smugmug.com/homepage/stats/ I get an empty panel containing the following text, instead of the expected stats graph (n.b. login is required to access this page -- sorry!):

Warning: Cannot establish communication between YUI Charts and JavaScript. YUI Charts must be served from HTTP and cannot be viewed locally with file:/// protocol unless location is trusted by Flash Player.

For more information see:
http://www.adobe.com/products/flashplay ... alcontent/

I have used this browser and the same set of add-ons to access all features of SmugMug without a problem until mid-January or so (i.e. through various software revisions). NoScript is configured to allow scripts from smugmug.com. Other features of smugmug are working fine (e.g. galleries and Flash slideshows).

At the suggestion of the NoScript FAQ, I upgraded to the development build, but it did not fix the problem.

I'm running

• Fx 3 aka Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.19) Gecko/2010120923 Iceweasel/3.0.6 (Debian-3.0.6-3)
• Flash 10.2 r152
• NS 2.0.9.9rc2

There are no relevant errors or warnings reported on the Error Console. SmugMug support have been unable to help beyond suggesting that I use a different browser or OS.

Can you suggest how I should debug this? Thanks in advance!

Anything relevant in FF Error Console?

Does smugmug require login?

Unfortunately the page in question requires a smugmug account login.

I'm happy to debug if someone can give me some pointers. Alternatively, it is possible to create a free "trial" account.

I can confirm that the feature works if I disable NoScript. My other active Fx add-ons:

• DOM Inspector 2.0.0
• S3Fox 0.6
• SimpleTranslate 0.41
• Tab Mix Plus 0.3.8.4
• Web Developer 1.1.9

As I said, nothing on the Error Console.

[sorry for the separate posting and forgetting to enter my username previously]
... and further to my previous posts, I have restarted Fx with various combinations of add-ons enabled/disabled, and I can confirm that the problem relates to NS, and NS alone.

If possible, I'll check to see if the same problem is present on Fx under MS Windows.

I've done some additional testing and can add the following information:

• the error goes away if I revert to NS version 2.0.8.1
• the error is not present with Fx 3.6.13/NS 2.0.9.8/MS Windows NT 6.1

Is there any further information I can provide to help the developers find a fix?