Disqus error in Google Chrome dev (22.0.1201.0)

222 views
Skip to first unread message

Leonard Ehrenfried

unread,
Jul 12, 2012, 4:07:45 PM7/12/12
to disqu...@googlegroups.com
Hi,

I'm on Google Chrome's dev channel and have just noticed that since the latest update to Google Chrome 22.0.1201.0 (Mac) that the Disqus plugin no longer works on my Wordpress blog, for example: http://lenni.info/blog/2012/05/installing-ruby-1-9-3-on-ubuntu-12-04-precise-pengolin/#disqus_thread

The commets aren't being shown at all and the Javascript console spews out the following error:
Uncaught TypeError: Object function (a,c){var b;a||(a={});c&&c.parse&&(a=this.parse(a));if(b=A(this,"defaults"))a=f.extend({},b,a);if(c&&c.collection)this.collection=c.collection;this.attributes={};this._escapedAttributes={};this.cid=f.uniqueId("c");this.changed={};this._silent={};this._pending={};this.set(a,{silent:!0});this.changed={};this._silent= {};this._pending={};this._previousAttributes=f.clone(this.attributes);this.initialize.apply(this,arguments)} has no method '_bindRoutes' mediacdn.disqus.com/1342029028/build/next/lib.js:121
Uncaught TypeError: Cannot read property 'Lounge' of undefined

In the latest Firefox (v 13.0.1) the comments work. I'm also running the latest version of the Wordpress plugin (v2.73).

I can't tell definitely since what version the comments broke, but Chrome pushed out an update today and this one could potentially be the culprit.

If it turns out to be a Chrome bug, I'm happy to file a bug with them.

Thanks for your help,
Leonard

Anton Kovalyov

unread,
Jul 12, 2012, 4:15:09 PM7/12/12
to disqu...@googlegroups.com
Hi Leonard,

I've just tried your link in Chrome Canary (22.0.1183.0) and it works—so I'd say this was a dev channel bug?

Anton


Ben Vinegar

unread,
Jul 12, 2012, 4:16:30 PM7/12/12
to disqu...@googlegroups.com
Hi Leonard,

There was a bug in Chrome Canary for a brief period that caused exceptions in Backbone.js, a library used by Disqus 2012 and many other web applications.

You can find more about the bug here:


As Anton mentions, a fix has been made and is already available in the latest version.

- Ben

On Thu, Jul 12, 2012 at 1:07 PM, Leonard Ehrenfried <leonard.e...@gmail.com> wrote:

Leonard Ehrenfried

unread,
Jul 12, 2012, 4:29:17 PM7/12/12
to disqu...@googlegroups.com
Thanks for the link. The broken Chrome version is exactly the one I'm running and hence this is definitely a Chrome bug.

Thanks for your time,
Leonard

Reply all
Reply to author
Forward
0 new messages