cptjump

Hi,
probably I didn’t explain myself clearly the first time.

I do want to set a default author automatically — that’s exactly why I’m using this plugin.
The issue is that when a user with the “Author” role creates a post, the plugin immediately tries to assign the default author, and this results in a permission error, because Authors are not allowed to assign posts to other users.

So at the moment, the plugin breaks post creation for non-admin users.

What I was suggesting is an option to assign the default author on publish (or only for users who don’t have permission), instead of during post creation.

Hope this clarifies the actual problem.

Just to follow up after more tests: the slowdown happens consistently every time I enable version 1.9.4.2 (and disappears when I roll back to 1.9.4).

To understand what was going on, I enabled debug logging of the Cloudflare API calls. Here’s what I’m seeing:

• 1.9.4 → saving a post triggers 2 purge requests (same payload).
• 1.9.4.2 → the same save triggers 4 purge requests (identical payloads, just duplicated).

This lines up with the delay I observed — the extra API calls are likely what cause the overall slowdown, so doubling the number of requests readily explains the regression.

Looking at the code, I noticed that in 1.9.4.2 there’s a new hook:

add_action('post_updated', [$this, 'purgeCacheByPostIds'], 1048576, 3);

in addition to the existing one:

add_action('transition_post_status', [$this, purgeCacheOnPostStatusChange'], 1048576, 3);

My guess is that in some situations (like a post update) both hooks are firing and causing duplicate purge calls for the same set of URLs. That seems to match what my debug traces show.

Your idea of moving the purge into a register_shutdown_function when DISABLE_WP_CRON is set is solid; if that hides the latency from the user, I think it would be great.
As a side note, if I may, rather than exploring every third-party cron replacement, it might be more pragmatic to simply check whether Action Scheduler is available. It’s widely used by many plugins and fairly common across WP sites, and would give you a reliable async queue without depending on WP-Cron.

Great, yet another time… thanks! 😉

…and apparently they won’t 😂
Thanks for looking into it!

Totally agree, having this filter (noticed later) it’s amazing. Maybe, in the future, you could consider adding an area in the plugin settings to allow users to put urls to “force purge” there (e.g. one per line) but for sure it’s not a priority. Thanks again!

I usually edit a post content, sometimes the title. I don’t change the slug but wordpress will if the date differs from the original post, since the permalink structure is like this (/news/%year%/%monthnum%/%day%/%postname%)

Just to be sure, i also tried directly changing the slug but (at least in my case) the old URL is not being purged.

Thanks!