Disqus discussion not generated because of wrong disqus_url

[simecek]

I was not sure whether to report this because I am new to Hugo and it is possible that I am just doing it wrong. However, I see other blogs running into the sample problem (see below).

The problem is after adding disqusShortname to config.toml and generating HTML page, Disqus says: We were unable to load Disqus. If you are a moderator please see our troubleshooting guide. (see for example Kevin Wong's blog: http://kevinfw.com/post/blogging-with-r-markdown/)

After viewing the page source and some troubleshooting I have found that the problem is disqus_url that miss the baseurl. For example in Kevin Wong's blog above the line 261 is

var disqus_url = '\/post\/blogging-with-r-markdown\/';

but instead it should be

var disqus_url = 'http:\/\/kevinfw.com\/post\/blogging-with-r-markdown\/post\/blogging-with-r-markdown\/';

For my blog https://simecek.github.io/blog I have solved the problem by editing the footer of the theme and replacing default Hugo disqus template by my own. However, this is likely to be a blogdown bug and should be corrected.

[yihui]

When publishing the website, you need to run blogdown::build_site() so that all configurations in config.toml will be respected (see the R help page ?blogdown::build_site). When you blogdown::serve_site(), a few configurations have to be tweaked so you can preview the site locally.

[simecek]

Thank you, yes, build_site(local=FALSE) solves the problem (tested on a newly created blog https://github.com/simecek/test_blogdown).

I apologize for bothering you. It still might be useful to notify the other users because I doubt I have been the only one running into this.

[yihui]

No worries. It is not your fault but lack of a systematic documentation, which is still under development.

[larnsce]

Unfortunately, the blogdown::build_site() solution does not work for me. Disqus is set-up and my disqusShortname "larnsce" entered into the config.toml file. Then build_site is used and the content of the public folder uploaded to my server. The site is hosted at: http://lse.de/r-tistic/

After clicking on either "About", "Resources" or "Slides" in the header of the page, I receive the following message from disqus:

We were unable to load Disqus. If you are a moderator please see our troubleshooting guide.

After clicking on "troubleshooting guide" the disqus load button shows up with the message

Disqus seems to be taking longer than usual. Reload?

I am grateful for any additional suggestions.

[yihui]

@larnsce Try to set baseurl = "http://lse.de/r-tistic/" in config.toml.

The other way is to add layouts/partials/disqus.html

<div id="disqus_thread"></div>
<script>
(function() {
var d = document, s = d.createElement('script');
s.src = 'https://larnsce.disqus.com/embed.js';
s.setAttribute('data-timestamp', +new Date());
(d.head || d.body).appendChild(s);
})();
</script>
<noscript>Please enable JavaScript to view the <a href="https://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>

[larnsce]

Try to set baseurl = "http://lse.de/r-tistic/" in config.toml.

Worked out, thanks! :)

Also set relativeurls = false in this case.

[yihui]

I actually recommend the second way. The one thing I dislike most about Hugo is baseurl. It makes the website not portable.

Unfortunately you cannot set relativeurls = false in your case (your website is in a subdirectory). You will run into issues when you have R plots in your posts. See https://bookdown.org/yihui/blogdown/methods.html

[jarvmiller]

Hi,
My issue is that I don't even get an "if you are a moderator please see the troubleshooting guide" message on my blog. Nothing loads or attempts to load. I've got the following in my config.toml
baseurl = "https://jarvmiller.github.io/"
disqusShortname = "jarvmiller-github-io"

I've also added the layouts/partials/disqus.html as mentioned above. I'm not sure what the issue could be..

Edit: ack, Sorry I just saw that this was closed right after I posted my comment.

[yihui]

@jarvmiller Not sure which page you were looking at, but Disqus won't work for local preview (127.0.0.1) by default. I'll document how to make it work. For now, you can only see comments on the published website.

[taraskaduk]

Try to set baseurl = "http://lse.de/r-tistic/" in config.toml

This finally worked for me, too!
I've spent days troubleshooting!
Thanks!

[taraskaduk]

...and somehow my previous solution stopped working. Back to square one

[dsaada]

I try to use disqus with radix, I can see post your comment at to bottom of the post, but when I push, nothing come, any idea?
thx
David

[IanniMuliterno]

Hello, so I am using a recent version of blogdown, the archive is now config.yaml instead of config.toml. My config looks like this

baseURL: "https://iannimuliterno.github.io/blog2021/"
languageCode: en
DefaultContentLanguage: en
title: config yaml draft do meu blog
theme: anatole
summarylength: 10
enableEmoji: yes
enableRobotsTXT: yes
publishDir: "docs/"
pygmentsUseClasses: yes
pygmentsCodeFences: yes
pygmentsCodefencesGuessSyntax: yes
disqusShortname: annymuliterno

markup:
  goldmark:
    renderer:
      unsafe: true

Only adding disqusShortname: annymuliterno wasn't enough, so I've also tried

• 1 creating disqus.html at themes\anatole\layouts\partials\
• 2 running build_site()

and it did not work, so I noticed that inside themes\anatole\layouts\partials\ exists a directory called comments and tried moving disqus.html to themes\anatole\layouts\partials\comments, then ran build_site() again and still I bump into the trobleshooting issue, I'd love to add comments to my blog so any help will be greatly appreciated.

for the record, my disqus.html looks like this :

<div id="disqus_thread"></div>
<script>
(function() {
var d = document, s = d.createElement('script');
s.src = 'https://annymuliterno.disqus.com/embed.js';
s.setAttribute('data-timestamp', +new Date());
(d.head || d.body).appendChild(s);
})();
</script>
<noscript>Please enable JavaScript to view the <a href="https://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>