ryanv12

Interesting, especially because we didn’t really change the conditions of how the new plugin appears on certain posts. We might have to dig in a little deeper – would you be able to create us a temporary admin account, and email the credentials to our support team from the link in the plugin? Just write a note that Ryan asked for these.

Do you have an example page available where you see this behavior?

We found a decent way to handle this, which should appear in the next update: https://github.com/disqus/disqus-wordpress-plugin/commit/062d737a3dfab660a826a4ebef214457ff8bb313

You can always patch your current plugin by editing it with these additions, if you’d like to use it now.

The affiliate linking should not overwrite any existing affiliate links or cause broken links, and feel free to send our support team any examples that you see where that happens.

In any case, this is still optional, and you can disable it. See here: https://help.disqus.com/customer/en/portal/articles/2425431-how-to-disable-affiliate-linking

Do you have an example of a request which fails, and the URL of the page you’re accessing from?

We don’t seem to have any code which explicitly requests the configured site URL, but perhaps the APIs we’re using for the admin and REST URLs do. I’ll have to see if there’s any way to handle this, but I can at least point to what you need to update in the plugin to get it working for now.

The $post global should already be set if Disqus is being called in the “loop”. Adding some logging (I’d check $post->ID) will certainly help just to validate those variables to make sure we’re looking at the right problem.

hmmm, that error doesn’t make sense at first glance. Have you contacted support yet? We probably need to look at the internal information (WordPress version, plugins, etc.). You can find the link to contact support and the diagnostic info in the “Support” tab of the plugin.

Do you happen to have http and https versions of your site?

What’s the domain, so I can try looking it up on our end?

@rfischmann Is your site https by chance? Our backend has had some trouble connecting to sites that are listed as https but don’t have a certificate.

That might also explain the nonce/cookie issue you saw randomly earlier, as a cookie marked as “secure” wouldn’t be available to regular http connections.

Hi Niels,

We plan on implementing a feature to sync back comments and can be tracked here: https://github.com/disqus/disqus-wordpress-plugin/issues/33

Perhaps it was caching? Hard to say, but thanks for closing the loop!

Hmmm, there are some extra conditions for Disqus to replace the comments, which is in code here: https://github.com/disqus/disqus-wordpress-plugin/blob/master/disqus/public/class-disqus-public.php#L275

Because the counts load on that page, then this condition would not be the issue: ! $this->dsq_can_load( 'embed' )

My guess is perhaps the $post object is not set, but it’s difficult to guess at without debugging. Are you able to verify which part of that check fails?

1. You don’t need the dsq_sync_forum cron job. One major point of the new plugin was to stop using wp_cron so it would not cause harm on a site if it worked incorrectly

2. Right now there’s no way to sync those missed comments, but we’re building that feature for the next feature release of the plugin, so you’ll be able to fix that soon. We may use a cron job again as well, but with a more conservative, scheduled approach.

I’m also seeing Disqus on that page, did you figure this out?