Comet Cache does not permit deletion from plugins!

@kbollhorst79 An Internal Server Error is an error that’s coming from your web server, not from Comet Cache. Can you tell me which version of PHP your server is running so that I can attempt to reproduce that issue?

I demand that the developers provide a solution for deleting their plugin!

We have manual uninstallation instructions posted here. If you follow those instructions, Comet Cache will be removed.

• This reply was modified 8 years, 2 months ago by Raam Dev.

My web host service is Bluehost. Currently, I am using the server’s master php.ini configuration file. According to the error message displayed by Comet Cache the PHP version is PHP v5.2.17.

@kbollhorst79, I can understand your comment above when running into an error message like yours. The PHP version v5.2.17 you mentioned above is an old version. Please view the following URL Supported Versions.

It is extremely important to always make sure your server is running the most up to date and stable PHP version.

The above URL link I provide illustrates the PHP versions your server should be running.

Comet Cache is one of the best cache plugins here in the repository with outstanding support. I use it in a few websites without any issues.

Kind regards

Dear Raam Dev,

First, I want to thank you for helpful responses. I have updated my sites PHP to 5.6. For reasons unknown, my web hosting service labels 5.6 as a beta version on their website. Their information is incorrect. I had been using the default version installed by them which was 5.2. So again, thanks for the heads up. I also want to apologize for the negative comments in my earlier responses. The last 2 weeks have been crazy for me ever since the major updates to WordPress, JetPack, & Wordfence. Up until two days ago, I had been fighting a major caching problem (which did not occur before 2 weeks ago) with my front/home page still displaying the 2 week old version dependent upon where the site was viewed. Wordfence Falcon (what I had been using along with JetPack’s Photon, which I now no are not compatible) provides a cache purge option but it does not seem to work. Falcon is fast but I am using Sitelock’s CDN. Wordfence also has no provision for programming in the CDN cname. With the help of Sitelock’s technical staff, the cache purge problem has been resolved.

Unfortunately the traditionally recommended cache plugins, W3 and WP Super Cache, have not updated for compatibility with WordPress 4.6.1. Since Sunday I had been conducting tests using WP Super Cache which some WordPress users indicated would work with 4.6.1. It seemed to work for me up to yesterday. It’s performance was not as fast as Falcon, my web performance grades went from an A to a C (not good). There was a major upgrade to MS Windows 10 that I ran yesterday. Since that upgrade, I have had encountered some problems with WP Super Cache.

Will Comet Cache compatible with a CDN? Can you program in the CNAME (I think I read that the PRO version will)? Will it minify? If I test the free version out will I see a significant speed increase? Is it compatible with Wordfence (with Falcon and all Wordfence caching OFF and with Photon OFF)? I have no problem with paying for the PRO version but I would want to test it out first. I really am looking for a reliable high performance caching plugin.

Thanks again for your time.

@kbollhorst79 I hear your frustration — there are times when it seems like every software application is against cooperating with you!

Regarding Comet Cache and CDN integration with CNAMEs: Yes, Comet Cache Pro‘s Static CDN Filters integrate with a wide array of CDNs, including Amazon’s CloudFront, MaxCDN, KeyCDN, CDN77, and any other CDN that can be sourced by a domain name. I reviewed SiteLock’s website and I wasn’t able to determine if their CDN service can be sourced by a domain name like the most popular CDN providers. If it can, then you should have no problem using Comet Cache Pro’s Static CDN Filters with SiteLock.

We have a KB article here that includes more information and a video to explain the Comet Cache CDN Integration:

Introduction to Static CDN Filters

Note also that Comet Cache Pro Static CDN Filters are fully-compatible with CNAMEs; once you set up the necessary DNS mapping to map the CNAME to your CDN hostname, you simply supply Comet Cache with the CNAME instead of the CDN Hostname and, assuming the DNS is configured and has propagated, the CNAME will work with the Comet Cache Pro Static CDN Filters.

—-

As per WordPress Forum Guidelines, we’re not allowed to discuss Pro features here, so if you have any other questions regarding Comet Cache Pro, I’m happy to answer them via a ticket.