Disable plugins have dramatic negativ impact

  • First of all, I’m rewriting exactly what I wrote in the review:

    I tried to disable the plugin, all pages become DYNAMIC. Why is this happening? It is not normal to disable CF if I disable plugins!

    And now let me answer to question you asked me in the email:

    “when you disabled the plugin how the caching is supposed to work”

    When the plugin is disabled or uninstalled, it should leave the blog as it was before installation, and the cloudflare settings should remain as they were, without any changes! This is the logic, the right way and the common sense of any plugin in wordpress!

    * My Cloudflare settings were simple before and the resources were cached correctly, after I installed and deactivated the plugin, all the resources were no longer cached, they were served by cloudflare as DYNAMIC (Header Response from CF)!

    Now, in response to email from Saumya Majumder (@isaumya), from which I received an answer in the email!
    You reproached me that:

    “Asking questions in the review section is against WP community guidelines.”

    Rhetorical ask question in the review section is not against WP community guidelines. You can’t take the question out of context, otherwise we already fall into the censorship area!

    A rhetorical question is a question that is not expected to be answered. It is used to emphasize a point of view and to express a mood or attitude that the speaker has at that moment.`

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    When the plugin is disabled or uninstalled, it should leave the blog as it was before installation, and the cloudflare settings should remain as they were, without any changes!

    – That’s exactly what the plugin does. When you disable/uninstall the plugin it removes the page rule or the worker code (depending on which option you selected) that was added by this plugin and was not present in your CF account before. Also as the plugin is no longer active it won’t be able to manage the cache-control header which is essential to manage to cache. So, basically you will be exactly from where you have started from without the plugin. At this point your static files will get cached by Cloudflare like it used to before but the dynamic pages won’t get cached as the plugin was handling the cache.

    * My Cloudflare settings were simple before and the resources were cached correctly, after I installed and deactivated the plugin, all the resources were no longer cached, they were served by cloudflare as DYNAMIC (Header Response from CF)!

    – After deactivating the plugin if your static files (e.g. css. js, images) are not getting cached, then you need to check what cache-control header you are providing for those static files as Cloudflare will look at your cache-control header and will do what you will ask it to do. So, you better look at that.

    You didn’t understand, before installing the plugin any page was cached, so I have the settings in cloudflare:

    Cache Level: Cache Everything

    After disabling the plugin, the cache in Cloudflare didn’t work anymore.

    I’ve been using CF for years, believe me I know when it should and when it shouldn’t work!

    * I activated the plugin, and then I deleted it manually from the server (without deactivating it) and everything returned to normal!

    Plugin Contributor iSaumya

    (@isaumya)

    The Cache Level: Cache Everything page rule is automatically added by the plugin. So, when you disable the plugin it removed that page rule. If you want you can recreate the Cache Level: Cache Everything page rule your self manually from within the CF dashboard.

    I activated the plugin, and then I deleted it manually from the server (without deactivating it) and everything returned to normal!

    – Yes this time when you activated the plugin, it added the Cache Level: Cache Everything page rule in Cloudflare. Then as you have manually removed the plugin instead of deactivating/deleting via the plugins section it did not delete the page rule it added.

    But if you would have deactivated the plugin it would have removed the Cache Level: Cache Everything page rule that was added by the plugin.

    So the plugin is to blame for not leaving the filters as it found them. I use such a filter (Cache Level: Cache Everything) for many sites. I did not expect it to be deleted by a plugin installed on the blog.

    It’s not good, you need to restore both the previous state of the blog and the CF account!

    Plugin Contributor iSaumya

    (@isaumya)

    First of all (Cache Level: Cache Everything) page rule on a WordPress site will break WordPress when not being used with this plugin as in that situation logged in pages and many other cases will return cached content. If you would just like to use the page rule (Cache Level: Cache Everything) without this plugin feel free to do that.

    While when using this plugin it will create the (Cache Level: Cache Everything) page rule automatically in the cloudflare and there is no need for the user to create any page rule. So, if/when the plugin is disabled (e.g. to test the site without caching) the plugin will remove the page rule that was added by itself.

    Again after your test is done, and you enable the plugin back and enable cache via the plugin, it will add back the (Cache Level: Cache Everything) page rule automatically.

    There is no problem here. If you would like to use the (Cache Level: Cache Everything) page rule without this plugin just set it up in your cloudflare and use your site. When using this plugin it will take care of your caching along with adding/deleting the (Cache Level: Cache Everything) page rule from cloudflare.

    Yes, I know, but I rarely use the ADMIN and the content is 99% static.

    Anyway, WordPress admin transmits cache-control: no-cache, and otherwise I have no comments or other dynamic stuff, except for searches, but the results rarely change.

    I configured the cached pages through another plugin (my own) to expire periodically (using Expires and Cache-Control headers), depending on how often there are important changes / additions to the database. By default, Cloudflare honors the cache expiration set in your Expires and Cache-Control.

    I deactivated your plugin after I wanted to test my own simple cache plugin, which I am working on because most of them are too complex, and they have long lost their perspective on simplicity, utility and performance!

    I’m not saying that yours is “too complex”, I used to use W3TC at the same time and I want to give up W3TC, it’s too “heavy”!

    P.S. And today I understand that the world is heading for disaster, when we have come to no longer understand the meaning of words in context and to censor because we are “without knowledge”!

    In conclusion: you have to consider the existence of other CF filters and restore them, this is the natural order of things!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Disable plugins have dramatic negativ impact’ is closed to new replies.

Tags