DISQUS

Rob Loach · 1 year ago

A discussion of this problem has come up by czar with the Drupal module: http://drupal.org/node/279081 .

Drupal allows you to easily change the paths of content. Because of this, the content can live in a number of different locations:
1) Different domains (example.com or example.mobi)
2) Different URL paths (my/custom/path or node/123)
3) Content is moved from one domain to another

We'll implement disqus_url in the Drupal module, but this isn't a solution for when your content lives under two different domains, or you're switching domains. Any revamp of disqus_url would be much appreciated.

Daniel Ha · 1 year ago

Thanks. We'll discuss this.

Rob Loach · 1 year ago

You rock, Daniel!

Czar · 1 year ago

Indeed, any revamp of disqus_url would be much appreciated. Thanks.

Daniel Ha · 1 year ago

disqus_url does in fact use the absolute URL. To associate a new page with an existing thread, you'd need to set the disqus_url to the original permalink.

Rob Loach · 1 year ago

So, in the case of having multiple domains showing the same threads (main domain and mobile domain, for example), you'd have one domain with disqus_url being the main domain's permanent links, and the mobile domain render disqus_url pointing to the main domain's URLs.

If you were to move the website to a different domain, all old posts would still have to reference the old domain's URLs in disqus_url, while new posts would have to reference the new domain's URLs. Correct?

Daniel Ha · 1 year ago

Correct -- we'd like a more elegant approach to this. There are a
number of users who would benefit from any easy way to modify URL
associations.

Rob Loach · 1 year ago

A descriptor unique to the community portal might do it. Either that or
making it not require the absolute URL...

disqus_url = "my_path/my_post"

By giving the thread a unique identifier (or a unique path) for the
community portal, you could have the same thread listed on multiple
domains, and not worry about having to maintain disqus_url among
different domains.

Any thoughts?

dennyhalim.com · 1 year ago

currently, all forum topics link back to our disqus_url

if i set this
disqus_url = "my_path/my_post"

would that make all the link broken??

this is not quite good for seo.

JC John Sese Cuneta (謝施洗) · 1 year ago

disqus_url = "my_path/my_post"

It still won't suffice. Imagine for some reason you have to change your blog post from "my_path/my_post" to "my_path/my-post" ? That is still a problem.

Instead, I suggest Disqus tagging each post with some unique identifier, so regardless if the URL changed, Disqus will still be able to detect that it is the same post.

Now that is hard to implement. But one way of implementing it is by letting DIsqus detect some "keywords" (if you will) from the post and URL combined, magic it and turn it in to some Identifier (similar in concept with Hashes).

If those "keywords" changed or disappeared, then there's nothing we can do about it. If we want it to be perfect, then Disqus will have to develop plugins for every blog platform our there so it can integrate "Disqus_ID_tag" to every posts, to enable it to deliver regardless of the URL.

Well, just thinking wildly ;)

PS
I think the absolute domain name is important. Actually..... I better email Daniel instead, this is too sensitive. Thought of something evil...

timmillwood · 1 year ago

I am getting a similar problem because of the Drupal Pathauto module.

If a user enters a comment on the original node/123 url it's only visible there and not on the path/alias url.

Laurent J.V. Dubois · 1 year ago

All cms with url rewriting services meet the same problems ...
Drupal, Zikula, Joomla and co ...
On the other hand, a solution is to write an url rewriting rule for our disqus users ...
The simple way is to route our visitor to your prefered website/basic view
by example to the concerned article if your comments are managed in a forum.

For a more advanced usage, it's possible to create in our cms/cmf an intermediate page
with the list of different websites and sections concerned by this comment.

The better way is perhaps to launch discussions and to share dev skills about a dedicated plugin for each cms/cmf ...

on my way, I prefer open source solutions and the buzz is not our priority due to our non-profit activity ...

my 2 cents,
Laurent