Since upgrading to 6.x-1.5, all my old Disqus comments are not showing up beneath their respective posts.
The module is configured and working fine, but the problem seems to be that the old comments are defined against path aliases rather than node ids. New comments that I add to Disqus use the node id [visible in Disqus control panel], and are displayed with no problems.
One possible solution would be to import the comments into Drupal's own comments engine, although again the import process using Disqus's comments.xml file doesn't process entries if the Disqus comments are referencing a path alias rather than a node id.
Comments
Comment #1
jmbarlow commentedComment #2
aserdaten commentedWow. Hard to believe 1.5 was released with this defect.
Comment #3
robloachEh? I'm not experiencing this problem. The upgrade path was tested with two different sites (one of mine and someone else who is using the module) and it worked in both cases. The problem before 1.5 was that it was using the path alias, so if you changed the path alias or turned off the Path module, then you'd loose all your comments. 1.5 and up use the node ID, so that the comments stay persistent even when the path changes.
So would you guys please try to figure out what's wrong with the upgrade path? I know it's a pretty long function, but please run through disqus_update_6000() and try to see what's wrong with it. I'd really appreciate it.
It's us who determine when releases come. There were a lot of features in 1.x-dev that people wanted and I got a number of requests for an official release, so I made the release. If you're not happy with that release, then please help us fix it and make it work better for you. This is an open source project and the only way it will succeed is with your help. If you don't think 1.x-dev is ready for a release, then please get involved in the issue queue, submit bug reports, suggest possible solutions, and let's get it working for you. Thanks!
Comment #4
jakemonO commentedI've upgraded to the latest release and 'm having a problem seeing comment counts in views. Nota Bene: I'm overriding the comment count on my view:
and raw JavaScript on the view's page.tpl.php:
So obviously my views are expecting path alias referenced disqus URL's where there are no longer any. Older posts that did use the path alias for Disqus references still properly show their comment counts, though, which I thought would break as the disqus_update_6000() was supposed to migrate to all NID format (based on my cursory look at it.) My question is how do I transition this to the supposed views2 comment count support in Disqus module? I've tried to just put a comment count on my view from the views2 edit page, but don't get any Disqus functionality.
I'm not sure where to post this question to get the attention of someone who can assist, but if this is an inappropriate forum, indicate as such & I'll remove with humblest apologies.
Comment #5
jmbarlow commentedI've got a bit more info that might help on this one. I've got around 500 nodes and 800 disqus comments on my personal blog, and the problem seems to be that the update_6000 script was failing with the error "Failed: Failed to retrieve thread information for (path alias)."
I ran upgrade.php and a few times and it would fail on a different path alias each time. Fraid there doesn't seem to be a pattern I can spot such as number of entries processed or time. Eventually update_6000 is marked as complete. But, at this point it hasn't actually processed all the comments (messages in disqus terminology).
If I run update.php again, and explicitly run update_6000, it will burn through a few more aliases. This isn't a critical problem for me, so I've "solved it" by knocking up a quick script to keep plugging away using drush overnight until all the comments are done.
Comment #6
jakemonO commented@jmbarlow Thanks. I reran update_6000 per your suggestion and fixed the comment count code to point to the node/n url instead of the pathalias and all seems well.
Comment #7
robloachThanks for helping debug the update script, guys. I'm glad to know that it works, but just has to be run a few times in order to process through all the comments.
Comment #8
robloachLater versions of Disqus use the Node ID as the identifier. That'll help ya out.