I know users are tweeting about my content, but their tweets aren't showing up as reactions. There are at least two issues in play here:

  1. If reactions were working, the fact that the Disqus module uses the node/# url instead of the path alias means that most tweets would not get linked to the Disqus thread because they would be using the wrong url. However, this is only a secondary concern to be addressed after looking into why...
  2. even if I use the node/# url Disqus.com doesn't seem to be noticing the tweets, even though they show up on BackType.com (which is the engine for Disqus.com's reactions). I'm unsure whether this is a problem with Disqus.com or with the way the Drupal module is creating threads.

Has anybody gotten reactions working at all with this module? Is this by any chance a limitation of the widget version, and therefor dependent on the non-existent API version (see #298540: Add support for API version 3 in migrate module)? This seems unlikely, because the failure point is between BackType.com and Disqus.com, but it sure feels like something is amiss in the Drupal module, or this would just be working automagically.

CommentFileSizeAuthor
#10 Screen Shot 2012-12-30 at 10.49.32 AM.png14.45 KBiraszl
#5 disqus_url.patch1.46 KBel7cosmos

Comments

bradweikel’s picture

bradweikel commented
Title: Comments appear but social media reactions do not » Social Media Reactions don't appear when path aliases are used
Category: support » bug

OK, strike the second issue in the original description -- turns out that issue was 100% Disqus.com's fault, nothing related to the Drupal module. It's working on new posts.

Only the first issue remains, but I think it's pretty important: anybody using path aliases (which is a huge percentage, given the popularity of pathauto) will not have their social media reactions show up because their users will use the path alias but Disqus will only look for social media reactions linking to the underlying node/# url.

Why was the decision made to use the node/# url instead of the path alias? Other than coping with changes to the path alias, I see no upside and a huge downside.

el7cosmos’s picture

el7cosmos
Primary language Indonesian
Location 🇮🇩 GMT+7
commented

I change my disqus to use url alias sometimes ago, and i start seeing reaction coming to my site. I absolutely agree with the use of url alias instead of node/#

  • Disqus have disqus_identifier variable, which make node that have multiple url will have same disqus thread for same identifier.
  • Disqus just launched a migration tool, in case the node url alias change, we can always tell disqus.
bradweikel’s picture

bradweikel commented

@el7cosmos - can you post your changes as a patch so I can start using it?

http://drupal.org/patch/create

bradweikel’s picture

bradweikel commented
Status: Active » Closed (duplicate)

Marking as a duplicate of #343363: Use the node alias for the Disqus displayed URL / Reactions broken

el7cosmos’s picture

el7cosmos
Primary language Indonesian
Location 🇮🇩 GMT+7
commented
Status: Closed (duplicate) » Needs review
StatusFileSize
new disqus_url.patch1.46 KB

Using diff, please review my patch

el7cosmos’s picture

el7cosmos
Primary language Indonesian
Location 🇮🇩 GMT+7
commented
Status: Needs review » Closed (duplicate)
cloud’s picture

cloud commented

Quick question el7cosmos -

What does removing the line:

- $output .= 'var disqus_url = '. drupal_to_js($disqus['url']) .';';

do?

I can understand dropping the alias bits.

Thanks

John

el7cosmos’s picture

el7cosmos
Primary language Indonesian
Location 🇮🇩 GMT+7
commented

disqus will use the current url for disqus_url variable

ggarron’s picture

ggarron commented

What I have done, is to take the Universal code, insert it into a block.
Then I added that block to appear in every 'node/*' page, and dissable the disqus module.

Then I asked disqus to crawl my website for 301 redirects, as path alias was on, all comments were moved.

Hope it helps.
Of course I have no comments count, but I do not care.

iraszl’s picture

iraszl commented
StatusFileSize
new Screen Shot 2012-12-30 at 10.49.32 AM.png14.45 KB

Has this bug been fixed? I have the dev version of the module installed on my blog: http://raszl.com and still shows zero reactions on all posts yet I know for sure there are several reactions. Did I do something wrong? Can you please help me!?