A2 Hosting
Forum Replies Created
-
Please open a ticket with our support team (https://www.a2hosting.com/support) so we can troubleshoot your install directly.
Hello Johan,
What version of Chrome as you seeing this on?
Hello,
It looks like you’re running PHP 5.2. You’ll need to update your PHP version on that site to at least PHP 5.3.
2.0.10.2 resolves this.
Hello,
The warning is due to Wordfence Security having compatibility issues with caching plugins.
Litespeed cache is available on all A2Hosting Turbo accounts. You can enable it via cpanel.
Hello,
Can you try disabling the various features of A2 Optimized to determine which one is causing the conflict?
The following plugins will display the warning, as they may cause issues with A2 Optimized:
WP Super Cache
WP Fastest Cache
WP File Cache
Better WP Security
WordfenceVersions of W3 Total Cache higher than 0.9.5 are also not supported, but we offer a walk through to install a community support version if we detect that you are running incompatible version.
Version 2.0.9.2 of A2 Optimized now displays the plugin or plugins that are triggering the warning along with additional information related to the W3 Total Cache change.
Hello,
Which version of A2 Optimized are you running?
Forum: Plugins
In reply to: [A2 Optimized WP - Turbocharge and secure your WordPress site] Time to UpdateWe have an update coming in the next week to address this.
W3 Total Cache may cause these issues. You can disable Object Caching and Database Caching through A2 Optimized to resolve this.
We would recommend leaving Page Caching on at the very least.
Glad to hear that fix is working. We currently do not support the 0.9.5.x branch of W3 Total Cache and will be issuing an update shortly to address this.
Hi all,
We wanted to stop by and let everyone know that we’ve received all of the tickets, and the links to this thread. Thank you for pointing our attention here. This is top priority right now.
The team is currently crowded around our office meeting room attempting to resolve this precise issue.
I’ll try to provide updates here, while they continue to work. We’ll be responding to individual tickets once the larger issue is resolved. Please keep in mind that you’ll likely see a public update here before a responses to individual tickets.
Again, many thanks to those who pointed here. We appreciate the opportunity to resolve these with a single fix.
-Kylebot