wabetainfo

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!

thank you @wpquadssupport, I will patiently wait your response after your investigation

Hi @wpquadssupport,

I haven’t disabled the “Lazy Loading for Adsense” option and I keep experiencing the same issue. I also tried using different browsers and devices in incognito mode. The problem occurs in just a few milliseconds, so maybe that’s why you haven’t noticed it. Try continuously refreshing the homepage to see the issue highlighted in the videos. I also asked other people, and they noticed the same bug.

Hi @wpquadssupport,
Thanks for your reply. The theme is https://www.ads-software.com/themes/kenta-groovy-blog/.

Please, keep me up to date. Thanks!

Hi @wpquadssupport

Thanks for your reply. There is no screenshot for this error as I often find multiple logs regarding this warning in the debug log file. As a result, I don’t know on which page this error occurs. This happens with the latest update, it didn’t know in the previous version.

Hi @erania-pinnera,

I confirm that I experimented with temporarily disabling Jetpack some time ago, and the error ceased to occur. It began occurring a few days again, after I enabled Jetpack.

Hi @olliejones,

I found some logs when this issue occurred and I wanted to share them with you:


[20-Feb-2024 01:06:21 UTC] SQLite Object Cache: 3.39.4 igbinary: php 8.0.30: Apache: get_by_name database disk image is malformed (11) Unable to execute statement: database disk image is malformed (0) #0 /home/website/public_html/wp-content/object-cache.php(1386): SQLite3Stmt->execute() #1 /home/website/public_html/wp-content/object-cache.php(1333): WP_Object_Cache->get_by_name() #2 /home/website/public_html/wp-content/object-cache.php(1796): WP_Object_Cache->cache_item_exists() #3 /home/website/public_html/wp-content/object-cache.php(2499): WP_Object_Cache->get() #4 /home/website/public_html/wp-includes/option.php(173): wp_cache_get() #5 /home/website/public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/legacy/class-jetpack-options.php(225): get_option() #6 /home/website/public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/legacy/class-jetpack-options.php(208): Jetpack_Options::get_option_from_database() #7 /home/website/public_html/wp-content/plugins/jetpack/class.jetpack.php(2160): Jetpack_Options::get_option() #8 /home/website/public_html/wp-content/plugins/jetpack/class.jetpack.php(784): Jetpack::get_option() #9 /home/website/public_html/wp-content/plugins/jetpack/class.jetpack.php(498): Jetpack->__construct() #10 /home/website/public_html/wp-content/plugins/jetpack/load-jetpack.php(78): Jetpack::init() #11 /home/website/public_html/wp-content/plugins/jetpack/jetpack.php(201): require_once('/home/website...') #12 /home/website/public_html/wp-settings.php(473): include_once('/home/website...') #13 /home/website/public_html/wp-config.php(100): require_once('/home/website...') #14 /home/website/public_html/wp-load.php(50): require_once('/home/website...') #15 /home/website/public_html/wp-blog-header.php(13): require_once('/home/website...') #16 /home/website/public_html/index.php(17): require('/home/website...') #17 {main} [20-Feb-2024 01:06:21 UTC] sqlite_object_cache failure, deleting sqlite files to retry. 0

Hi @gaurav984 and @erania-pinnera,

Sorry for the delayed response. Actually, I’ve never had any issues with the synchronization process, despite those warnings. It has become less frequent now, but it can still happen occasionally. For example, it may occur once every 10 days. It’s worth noting that when it does happen, Jetpack works without any issues.

Thank you @kowsar89 for this information. I appreciate it! I believe this happens when sending requests to websites using WP-Optimize with an empty User Agent, but this is only my assumption. I did several tests by enabling all my plugins except WP-Optimize and this issue did not happen. It only happens when WP-Optimize is enabled (even with all other plugins disabled). It’s true that some errors are from WordPress Core but every time there is an error from the WordPress Core, this appears in the log file:

PHP Warning: Trying to access array offset on value of type bool in /home/user/public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 723

Thanks for your dedication to improving your plugin!

Hi @kowsar89,

Unfortunately, it’s been 3 months since the previous update and I wanted to confirm that this issue is not fixed in the latest 3.3.0 release. This also happens with all other plugins disabled and only WP-Optimize enabled. This didn’t happen with a prior version of WP-Optimize.