ryanv12

Frank, is there anything a plugin can do to be automatically excluded so we don’t have to recommend this to each site that has the issue?

On my test site the script complains that embedVars is not defined. It looks like those are lumped into a minified file that are deferred, so it’s not available once disqus.js loads

It is free, but it has to be approved and enabled for you (instructions are in the doc)

I believe you’re looking for SSO, which is described here: https://help.disqus.com/customer/portal/articles/1148635

If you’re having errors where the comments aren’t appearing, please send your debug information (it’s output in the Disqus plugin settings) to our support team so we can get more context and test different scenarios: https://disqus.com/support/

Have an example site we can investigate?

The plugin does pass page-specific variables to this js file, and it would be best to exclude it from the cache, or make sure each instance is cached per-page.

See question above – do you have any caching plugins enabled? From what we’re seeing it looks like they aren’t aware of the new files in the plugin yet, so they aren’t being served.

That error is coming from a file the embed script loads, so it wouldn’t be an issue with the plugin itself. A better place to report that would be here: https://help.disqus.com/customer/portal/topics/629071-community-q-a/questions

We’ve seen a couple of reports, and one thing I noticed is that all external .js and .css files are being read from a CDN. One thing this update did was move the javascript to separate files, so it’s likely those files aren’t on the CDN yet.

Does this sound consistent with what you’ve been seeing?

Given that behavior, it’s likely an issue with how the iframe interacts with the page, but not the plugin. Try contacting support instead and be sure to include browser(s) where you can see this behavior so we can reproduce: https://disqus.com/support/

It’s used to match the WordPress post to the Disqus thread. After looking at the code, there’s definitely no attempt to remove it during uninstall so that’s something we can consider adding.

As far as removing it now, usually a simple SQL query will remove the column, like:

ALTER TABLE 'wp_postmeta' DROP COLUMN 'dsq_thread_id'

^ Note: I haven’t tested that, be very careful about running SQL queries on your blog!

Keep in mind with Tom’s suggestion that it would require changing the plugin, which wouldn’t support this kind of functionality out of the box yet. If it’s important enough to you, you could always not use the plugin and integrate the universal embed code with the suggestions from the above link.

Thanks again, tested and looks fixed now. Should be out in v 2.8

Thanks for catching that, would you mind submitting as a pull request here? https://github.com/disqus/disqus-wordpress

If not, no problem – just let me know.

See https://www.ads-software.com/support/topic/move-info-in-other-notes-to-changelog-for-viewing-in-managewp?replies=9