Title: Normal behavior? Last modified: February 28, 2021 --- # Normal behavior? * Resolved [Greendroid](https://wordpress.org/support/users/greendroid/) * (@greendroid) * [5 years, 4 months ago](https://wordpress.org/support/topic/normal-behavior-2/) * Hi, in the last few weeks I have recognized a few strange things which were not there before. Therefore I just want to check with you, if the following things are a normal behavior or if anything is wrong with my setup/configuration. It seems, that these “issues” came up with the last updates. - My scheduled posts are not published correctly anymore. I can see a “Missed schedule” in my post overview. As I have read, it is necessary to have a visitor on the page to get this “cron” activated. Is this perhaps cached, so that this php-call is not executed? I have setup a external cron via my webhoster now. - If I install a new plugin it is necessary to “Purge all caches” before usage, otherwise the plugin shows errors sometimes. - After deactivating a plugin, a deletion of the plguin is only possible if I “Purge all caches” before. - In general: If something is not working properly in my backend wordpress admin panel I click on “Purge all caches”. Most likely it is working then. * One question for understanding: What is the “Purge All Cache” button doing? Just deleting all the cache files or is the button event also recreating them afterwards? * I am using nearly always the standard settings in the plugin. Caching/Minifying is disabled for logged-in users. * Is this a normal behavior? Thanks and kind regards Greendroid - This topic was modified 5 years, 4 months ago by [Greendroid](https://wordpress.org/support/users/greendroid/). Viewing 4 replies - 1 through 4 (of 4 total) * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [5 years, 4 months ago](https://wordpress.org/support/topic/normal-behavior-2/#post-14114189) * Hello [@greendroid](https://wordpress.org/support/users/greendroid/) * Thank you for your inquiry and I am happy to assist you with this. - This seems to be a conflict with the Preload corn and the scheduled posts. SO in this case you may want to consider disabling the Cache Preload to avoid conflict or start the preload once the post is published and the best way is by calling it with wp-cli – wp w3-total-cache pgcache_prime - Yes once the new plugin is installed, you should purge the cache. - In some cases, depending on the options used, some redundant files need to be cleared before deleting the plugin - This depends on the hosting environment. Yes, that may be expected behavior, especially if using Object caching or Database caching. Purging the cache is always good to perform when making changes so that those changes can take effect. * Thanks! * Thread Starter [Greendroid](https://wordpress.org/support/users/greendroid/) * (@greendroid) * [5 years, 4 months ago](https://wordpress.org/support/topic/normal-behavior-2/#post-14116114) * Hi, thanks for your fast response and the confirmation, that this behavior is normal. One question to the following point: `This seems to be a conflict with the Preload corn and the scheduled posts. SO in this case you may want to consider disabling the Cache Preload to avoid conflict or start the preload once the post is published and the best way is by calling it with wp-cli – wp w3-total-cache pgcache_prime` What do you mean with the `wpi-cli` call? Is this again a cron execution script for my webhoster platform? All the “Cache Prelod” options in the settings are disabled. Is this good? Thanks and kind regards Greendroid * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [5 years, 4 months ago](https://wordpress.org/support/topic/normal-behavior-2/#post-14117088) * Hello [@greendroid](https://wordpress.org/support/users/greendroid/) * Thank you for the information. I was under the assumption that you were using Cache preload as the wp-cron for the cache preload fires once the cache is visited. So if you are not using cache Prelaod you can ignore that suggestion. I’ve tested the post scheduling with the native WordPress schedule and the posts are published on time and the cache is purged so the visitors can see the updated page. Thanks! * Thread Starter [Greendroid](https://wordpress.org/support/users/greendroid/) * (@greendroid) * [5 years, 4 months ago](https://wordpress.org/support/topic/normal-behavior-2/#post-14117121) * Hi, thanks! Then perhaps I have another issue on my webpage. I will check the other plugins which I have updated/installed in the past weeks. * Currently I am not using Cache Preload. Perhaps I should enable it, so that every visitor will get the cached page directly and not, that the first visitor has to wait for cache-creation. * Thanks and kind regards Greendroid Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘Normal behavior?’ is closed to new replies. * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806) * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/) * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq) * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/) * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/) * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/) * 4 replies * 2 participants * Last reply from: [Greendroid](https://wordpress.org/support/users/greendroid/) * Last activity: [5 years, 4 months ago](https://wordpress.org/support/topic/normal-behavior-2/#post-14117121) * Status: resolved