Title: Breeze causing problems even when disabled
Last modified: June 11, 2018

---

# Breeze causing problems even when disabled

 *  [denisgomesfranco](https://wordpress.org/support/users/denisgomesfranco/)
 * (@denisgomesfranco)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/breeze-causing-problems-even-when-disabled/)
 * So here’s the thing (and keep in mind that I’m a Cloudways customer).
 * I tried Breeze for some time, was happy with it. But then I noticed that sometimes
   it caused strange problems and some timeouts in admin screens. Also, minifying
   is sometimes tricky and usually won’t work at all on Woocommerce sites.
 * I figured, this is too much trouble for little return, so I disabled it on some
   of my sites and noticed that they were actually a bit faster. Maybe a caching
   plugin wasn’t needed at all. And with this I proceeded to disable Breeze on my
   60+ sites.
 * And ever since everything was running smoothly – until today. A few days ago 
   one of my customers asked to change some text in his website, which I promptly
   did using Elementor. Today he calls me very angrily asking why the changes weren’t
   up. I fired up the website, and there they are. And now I couldn’t figure out
   why I was seeing the changes and he was not.
 * After some hours of debugging and messing around with the server I finally found
   out what the problem was. Even though Breeze was disabled, it was still serving
   pages from its cache, but only to non logged in users. WTF?
 * In the end I discovered that the ‘advanced-cache.php’ file was still being called
   by WordPress, and it contained calls to Breeze files. And since Breeze was installed,
   it ran even though it should not run (isn’t that what it means to disable a plugin?).
 * After all of that, I proceeded to finally delete the Breeze plugin from all my
   sites, and deleted the advanced-cache.php file from all of them.
 * I understand that caching plugins can sometimes get tricky, but this was really
   unexpected.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Thread Starter [denisgomesfranco](https://wordpress.org/support/users/denisgomesfranco/)
 * (@denisgomesfranco)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/breeze-causing-problems-even-when-disabled/#post-10244415)
 * Sorry Adeel, forgot about this and the forum notification went to my spam folder.
 * I have already deleted Breeze from all my websites. But in case you want to check
   something out, my e-mail is eu @ denisgomes.com.br
 *  Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/)
 * (@jdembowski)
 * Forum Moderator and Brute Squad
 * [7 years, 12 months ago](https://wordpress.org/support/topic/breeze-causing-problems-even-when-disabled/#post-10386351)
 * > (and keep in mind that I’m a Cloudways customer)
 * For pro or commercial product support please contact the author directly on their
   site. This includes any pre-sales topics as well.
 * As the author is aware, commercial products are [not supported in these forums](https://wordpress.org/support/guidelines/#do-not-post-about-commercial-products).
   I am sure they will have no problem supporting you there.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Breeze causing problems even when disabled’ is closed to new replies.

 * ![](https://ps.w.org/breeze/assets/icon-256x256.gif?rev=3352595)
 * [Breeze Cache](https://wordpress.org/plugins/breeze/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/breeze/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/breeze/)
 * [Active Topics](https://wordpress.org/support/plugin/breeze/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/breeze/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/breeze/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Jan Dembowski](https://wordpress.org/support/users/jdembowski/)
 * Last activity: [7 years, 12 months ago](https://wordpress.org/support/topic/breeze-causing-problems-even-when-disabled/#post-10386351)
 * Status: not resolved