(Wrong): Sounds to me like JSON2.js failed to load or timed out for you, probably accounting for the slow load & eventual failure. Refreshing should do the trick!
Update: Your site, Beeets.com, doesn’t seem to be working for me, either. It loads fine but I can’t select a content area. Probably some sort of JS conflict — though this is, encouragingly, the first time we have actually seen this in the wild! We’ll take a look.
Update2: It looks to me like Mootools, which your site is including, redefines window.JSON (which is native in modern browsers, and which we include for old browsers) with an object that is incompatible with the browser-native JSON method "stringify". https://developer.mozilla.org/en/JavaScript/Reference/Global.... But in my jsfiddle attempt to confirm this, Mootools is playing nice… maybe some other script on the page is doing this.
Glad I could help you guys improve ;). You can reach me at andrew [at] beeets.com if you want to stay in touch, I'd love to try it out and possibly work with you guys on a fix (maybe something is terribly wrong with my site)
Really sorry for that failure, it's definitely on our end somewhere, but appears to be unique to your site. That's the beauty of the problem we're solving - unknown inputs. Can I email you when it's fixed?
Comments
(Wrong): Sounds to me like JSON2.js failed to load or timed out for you, probably accounting for the slow load & eventual failure. Refreshing should do the trick!
Update: Your site, Beeets.com, doesn’t seem to be working for me, either. It loads fine but I can’t select a content area. Probably some sort of JS conflict — though this is, encouragingly, the first time we have actually seen this in the wild! We’ll take a look.
Update2: It looks to me like Mootools, which your site is including, redefines window.JSON (which is native in modern browsers, and which we include for old browsers) with an object that is incompatible with the browser-native JSON method "stringify". https://developer.mozilla.org/en/JavaScript/Reference/Global.... But in my jsfiddle attempt to confirm this, Mootools is playing nice… maybe some other script on the page is doing this.
Glad I could help you guys improve ;). You can reach me at andrew [at] beeets.com if you want to stay in touch, I'd love to try it out and possibly work with you guys on a fix (maybe something is terribly wrong with my site)
My site (http://dan.cx/) uses MooTools and it seemed to work fine with Blogic. So it might not be MooTools.
Multiple tries, two different browsers, no reported resource loading failures from my dev tools (All scripts are loading).
Really sorry for that failure, it's definitely on our end somewhere, but appears to be unique to your site. That's the beauty of the problem we're solving - unknown inputs. Can I email you when it's fixed?