Hello site founders, admins, and moderators!
The bottom line: This updated code helps you tighten your Disqus integration so that your site doesn’t create duplicate or invalid Disqus threads. If you last updated your install prior to 2014, there are other updates that are critical.
Or forward this blog post to your site developer or admin for help.
So What’s New?
First off, it’s important to note that this update of the embed code doesn’t affect how Reveal and Engage look on your site. In summary, this update does two main things:
Recommended Configuration Variables
The code now includes 2 important configuration variables (url and identifier) that we strongly recommend that you start using if you aren’t already. These variables give your site full control over the Disqus threads your site creates and the data used for those discussions.
For more information on why it’s important to explicitly set your discussion URL and identifier, see Use Configuration Variables to Avoid Split Threads and "Missing" Comments.
If you decide not to use these configuration variables, this section of the code is commented out and you can simply leave the embed code as is.
Other Important Changes If You’ve Never Updated
- Protocol relative embed.js URL means if your site updates to HTTPS, Disqus continues to work
- Key linking scheme update, to ensure the most current assets
- Removed the extra “powered by Disqus” link that loaded in the embed footer
- Added "nofollow" attributes to footer links to prevent unnecessary crawling
Have questions about this update? Leave a comment below, or get in touch with us at firstname.lastname@example.org.