That old disqus.js was discontinued/unsupported by disqus years ago – I’m surprised it still works !
This plugin used to build on it, but it started to get buggy. If I remember right, it would occasionally decide to reject the parameters passed to it.
But I did like how it was 100% client side for exactly this purpose – cache bypass.
As it stands – no I dont believe this plugin would bypass a cache, and not sure it would be easy to either.
Im thinking it would either need to clear the cache for all the pages the shortcode is used – or use it’s own JS script to query the WordPress site and spit out the code.
I’ll have a little think about it and see if it’s possible (or sane) to do.
If you have thoughts on how it might be implemented, please let me know.
I forgot to reply to this message.
Version 2.3.0 introduced a new ‘Use Cache Buster’ setting – which should bypass cache plugins.
It won’t talk “live” to Disqus (like the recent_comments_widget.js) – as this would likely use up all your API calls.
But if that’s important for you – the ‘Cache Time’ setting can be adjusted to a lower amount.
Or as an extreme you can enable ‘Bypass Cache’ to talk “live” to Disqus – but again, each request will use up the limited API calls they allow per hour.
Let me know how you go with it.
