I’ve been using Editorial Calendar for a while now without issue. But I recently installed the Varnish HTTP Purge plugin and ever since I’ve been getting the dread “There was an error contacting your blog” error message when dragging posts from one day to another or deleting them.
If I disable the Varnish plugin, it works fine. Varnish itself is not the problem though, as I’ve been using it all along. This issue began when I recently installed the aforementioned plugin.
The Varnish plugin itself is simple – it just sends an HTTP PURGE request to URLs of changed posts (eg, rescheduled or deleted posts). The problem seems to be that scheduled posts managed via Editorial Calendar are by definition not yet published and so the PURGE request returns a 404 (confirmed in my Nginx log).
That’s not your problem, of course. I’m just wondering if you see any reason this error should be triggered by this. And, if so, if there’s a way to make EC a little more resistant to it.
The entirety of the Varnish HTTP Purge code is about 50 lines, many of which are whitespace, so it’s pretty easy to see what’s going on:
(the action happens in
Any insights on this? Thanks.
- The topic ‘Possible issues using Editorial Calendar with Varnish HTTP Purge’ is closed to new replies.