wabetainfo

Thank you @vupdraft for this update. I believe it is worth noting that I experience this issue when wp-cron.php is executed.

Hi @wpmansour
You told us that the next release would have included the fix for this issue. I just updated to the 3.5.0 version and this issue is still not fixed. It’s been over 4 months…

PHP Warning: Cannot modify header information - headers already sent in /home/website/public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692

Hi @wpmansour,

Unfortunately, the 3.4.2 update does not fix this issue. I downgraded to 3.3.1 again where this issue does not occur.

Hi @wpmansour,
I’m using the 3.3.2 versions because newer updates are broken. I am going to test the upcoming 3.4.2 update and I will let you know if the issue persists.

Thank you for this update!

Hi @wpmansour,

The 3.4.0 update has been released but I still experience the same issue. We thank you for the dedication the team puts into this plugin, but please note that we have already been waiting for 2 months and our logs are starting to contain many of these warnings. I hope for a release of the fix as soon as possible…

Thanks.

Hi @wfpeter,

Thanks for your answer. It seems that the issue resolved itself without any action on my part. It’s very strange, but the important thing is that everything is now working as before. Thank you for your availability!

Hi @wpquadssupport,
Thanks for your answer. Here you can find a video where you can see that, when I update a very old post (shared 2 years ago), all options become unchecked. This also happens with other old posts. This issue doesn’t occur with recent posts (for example, the ones shared less than 1 year ago).
URL of the post here.

Hi @vupdraft,

The full error log only contains multiple logs regarding the same warning, so I think it’s useless to post it.
I don’t use wget to run cron from the server, but maybe this happens when opening .php pages that contains these:
header('Content-Type: application/json; charset=utf-8');
header("Cache-Control: no-store, no-cache, must-revalidate, max-age=0");
header("Cache-Control: post-check=0, pre-check=0", false);
header("Pragma: no-cache");

I’m not sure since I downgraded to the previous version, where this issue does not occur. It is only my assumption.

No, I don’t have other caching plugins. In addition, this does not happen when reverting to the previous update. It occurs only when updating to 3.3.2.

Hi @vupdraft,
Yes I tried that but there are same warnings after some time

It appears this one works!

function purge_cache_new_post($new_status, $old_status, $post) {
if ('publish' === $new_status && 'publish' !== $old_status) {
if (function_exists('WP_Optimize'))
WP_Optimize()->get_page_cache()->purge();
}
}
add_action( 'transition_post_status', 'purge_cache_new_post', 10, 3 );

Thank you again for your support!

Thank you @pbevanudp for your reply! I will test it next time I share a new post. How about using transition_post_status instead, so we do not need to use update_post_meta? If it’s possible to use this hook, how can we purge the entire cache in this code?

Thank you again!

Hi,
Thanks for your help. Unfortunately, I tested this code and it still purges the cache when updating posts that I’ve previously published.

Thank you so much @pbevanudp for this suggestion. Is it possible to limit purge only when the status post becomes “published”? So, something like “wpo_purge_all_cache_on_publish”. Purging the cache every time we edit a post may be excessive. I just want to purge the whole cache when I publish a new post. Thanks!