Rafa Poveda

I also tried to activate it in the network, just to test. Same result.

Sorry, Kaiwen, for answering so late.

It was a very concrete implementation for a client and I’m now working in the settings page. It will be working soon.

Hello there.

I’m seeing this

If you are not seeing this, maybe you need to clean your browser’s cache.

It’s a yes for me.

And that’s why I was making it delete itself. I don’t want to be deleting it all the time. Disqus itself should be doing it. I hope they update soon also.

Thanks for this, archon810. In first place, this is what created a busy server for me. If you wait 10 minutes, then you have 160 new elements in the wp_options cron. Which is no good at all, and it’s happening in a server with 0.10 load. If your blog has been running for 2 years, you have more than 16 million elements in the cron, exhausting the server.

I tried your solution before, but it was also adding more elements to the cron, which is not the best idea. There must be a way to remove old crons.

I’m still testing the sync after adding this cleanup. No new comments so far. I’ll keep you posted ??

Solved with a single line. https://github.com/disqus/disqus-wordpress/pull/115

If you add a wp_clear_scheduled_hook( 'dsq_sync_forum' ); before adding the schedule again in disqus.php, the wp_options cron maintains only one element.

Sorry. You already solved my problem in your forum.

Thanks ??

You can update now. 3.9.1 es_ES is ready (at last).

Thank you!

Same here :/

I need to work on it. In the first place I was only sharing the code that we use for our clients. In our projects, we always need to send all the info to everyone involved (traceabilty and stuff like that).

Now that seems that the plugin is being more used and that the users have needs, I’ll work on it.
I’ll keep you all informed.

We are updating to the new WordPress version.

You’ll see changes soon.

Thank you.

Working in the new version.

Thank you