Leaves leftovers on my websites on unistallation & Bad Dev attitude

Cache Enabler should remove everything added by itself during the installation. This was explained to you multiple times. You’re the only one reporting such an issue with no changes made around these steps for over six months, which means it’s likely a case with your specific install or the steps you’re taking.

Unfortunately you’re placing blame in the wrong area as you clearly don’t understand how your page is being tested by Lighthouse. Cache Enabler has nearly no effect on that test other than what was previously explained to you. I would strongly recommend taking the time to educate yourself in this subject as it will help you improve your website’s performance. Another developer has even provided you great resources and explanations into this as well, so I’m not the only one.

The fascinating thing about plugins here is that they’re all open source. This is great because you can actually inspect the code and know exactly what is occurring. Now, I understand you have no idea what this code means, but I’m happy to let you know the steps that are taken in the hope of bringing you some clarification for what’s occurring when the plugin is deactivated and then uninstalled:

1. Cache_Enabler::on_deactivation() will prepare the plugin to run the deactivation steps.
2. Cache_Enabler_Disk::clean() will remove the settings file, the advanced-cache.php drop-in file, and unset the WP_CACHE constant in the wp-config.php file. Cache_Enabler::clear_site_cache() will clear the site cache.
3. Cache_Enabler::on_uninstall() will prepare the plugin to run the uninstall steps.
4. Cache_Enabler::uninstall_backend() will remove the database option.

Thanks for giving Cache Enabler a try.

Cache Enabler should remove everything added by itself during the installation.

But it isn’t in my case, and I think you should provide a solution/support for that, doesn’t matter if nobody else has reported it. So lets say there is a bug, then you won’t fixed till it is reported by many users? What kind of logic is that.

You know why this plugin is getting this review? Is not only about those leftovers but that attitude. I have reported countless of confirmed bugs, of course I know what open source is but yes if I had the knowledge to understand the code of your plugin I’d already done so. Said that in the past PageSpeed has worked as an indicator of bugs/problems, and I considered as such, if there’s a significant and persistent variation it is caused by something. I’m not expecting to improve the scores but to not make them worst.

@snippet24, I love helping others, especially when it comes to web performance. It’s something I’ve done for thousands and thousands of people. I’m baffled at your expectations given your behavior. You came to our plugin support forum for assistance, which I duly provided. Unfortunately you already made a conclusion on your issue and disregarded what I, the person who wrote 90%+ of this plugin and have several years of experience in web performance, told you. That immediately makes it difficult.

Then, when a response didn’t come your way fast enough you proceeded with an extorting-like behavior by leaving a negative review with false claims and then continued to use our plugin support forum for assistance. This, in addition to using this review as a support thread, is against the forum guidelines. Given your behavior you can count on the level of support I provide will be different because acting like that is not something that I will tolerate.

I take all negative criticism seriously. In fact, it’s important because it helps bring better iterations of any project that is being worked on. I do recognize I’m not perfect and make mistakes. That criticism helps me identify what I may have done wrong and make improvements. However, when a claim is made that is completely false I will refute it accordingly.

You’ve shared your opinion on this matter and I’ve shared mine. It’s now time to move on. Thanks again for trying Cache Enabler. I do sincerely wish your experience could have been better.

Okey thanks for the reply Corey.

You’ve shared your opinion on this matter and I’ve shared mine. It’s now time to move on.

I do make mistakes as well, and I think I stand corrected, I’m editing the review accordingly since none of this is set into stone.

Then, when a response didn’t come your way fast enough you proceeded with an extorting-like behavior

I disagree there.

You came to our plugin support forum for assistance, which I duly provided.

But no steps on fixing the leftovers.

This, in addition to using this review as a support thread, is against the forum guidelines.

I was only mentioning the reasons behind the review, not using it as a support.

I do make mistakes as well, and I think I stand corrected, I’m editing the review accordingly since none of this is set into stone.

Thank you. That is appreciated.

But no steps on fixing the leftovers.

My first response provided support links indicating what the plugin attempts to do automatically when deactivated and uninstalled.

My third and fourth response provided the locations to manually remove what the plugin adds during the installation.

Thank you. That is appreciated.

??

My first response provided support links indicating what the plugin attempts to do automatically when deactivated and uninstalled.

My third and fourth response provided the locations to manually remove what the plugin adds during the installation.

And what about on clarifying whats going on? and therefore actually fixing it on the plugin?

• This reply was modified 3 years, 5 months ago by snippet24.

And what about on clarifying whats going on? and therefore actually fixing it on the plugin?

To preface, I guess I should have mentioned this in my last response, but I presumed you’d know given I’ve already mentioned to not use this as a support thread to which you acknowledged. Continually asking questions is using it as such. If you feel the need to reply to this please do so in the appropriate way. This will be my last response here and likely my last reply on this entire topic in general as your quest to prove me wrong is something I can no longer contribute to.

I’ve provided you with much more clarification than needed in my opinion. You must understand that I’ve tested this on several installations as soon as you opened the related support thread as I take any bug report very seriously. If I had identified an issue I would have let you know right away and fixed it. No issues were identified. All procedures worked as expected.

I just tested this again for you with the latest Cache Enabler version (1.7.2) across several installation types. I again found no issues with the following taking place in each test:

1. Upon plugin deactivation in the plugins page the settings file is deleted in the wp-content/settings/cache-enabler directory. If wp-content/settings/cache-enabler becomes empty it will be deleted. The same goes for wp-content/settings.

2. Next, if the wp-content/settings/cache-enabler directory has been deleted, the advanced-cache.php drop-in file is removed from the wp-content directory and the WP_CACHE constant, if set by Cache Enabler, is removed from the wp-config.php file. The wp-content/settings/cache-enabler directory is always removed on a single site installation as there is only one settings file. In a multisite it’s only removed after all of the settings files have been removed to ensure the advanced-cache.php file is only removed when deactivated across all sites in a multisite installation.

3. Next, the cache is cleared in wp-content/cache/cache-enabler. Since the wp-content/cache/cache-enabler directory becomes empty it will be deleted. If the wp-content/cache directory becomes empty it will be deleted. As of version 1.7.2, the database transient containing the cache size is deleted when the site cache is cleared.

4. Lastly, upon deleting the plugin in the plugins page the single cache_enabler database option is deleted from the options table in the database.

To preface, I guess I should have mentioned this in my last response, but I presumed you’d know given I’ve already mentioned to not use this as a support thread to which you acknowledged.

You know you could reply back in the appropriate forum as well I suppose, please do so in the future here: https://www.ads-software.com/support/topic/deleting-the-plugin-causes-problems-of-performance-pagespeed-warnings/

I just tested this again for you with the latest Cache Enabler version (1.7.2) across several installation types.

You never mentioned that and I don’t read minds, then it may be a plugin collision. I honestly don’t know, I think I told/asked me you the related cache plugins I use?

as your quest to prove me wrong is something I can no longer contribute to.

Well that’s your decision not mine, do note whatever that I’m not lying in regards to what happens to the websites in which I used your plugin. And is not to prove you wrong/it isn’t “about you” but rather to try to recover my websites. I guess I could live with the workaround I discovered, but trust me I would avoid at all your plugin in the future. Your attitude is far from ideal.
So no matter how brilliant your are attitude is more important, take it or leave it, I did my part in letting you know that.

You’ve shared your opinion on this matter and I’ve shared mine. It’s now time to move on. Thanks again for trying Cache Enabler. I do sincerely wish your experience could have been better.

Easy to “move on” when is not your creation that’s broken. I will update my review here accordingly and trust me is not extortion as I want nothing more from you since you just want to move on, the decision is easy. I gave you proof that there were leftovers in my case, and is your responsibility to find it out as you are the developer. You earned 1 star review for bad attitude.`

• This reply was modified 3 years, 5 months ago by snippet24.
• This reply was modified 3 years, 5 months ago by snippet24.
• This reply was modified 3 years, 5 months ago by snippet24.

But you explained many things, and this plugin worked just fine before uninstalling it, hence 3 stars