[Plugin: W3 Total Cache] Disk (enhanced) option disabled

@mtprower

you’re right!
but not works and not cached!
I await new release or I’ll have to change plugin.

Have you run the ‘Compatibility Check’ to see if it flags anything?

PHP Version: 5.2.17
PHP Timezone: Not set
Web Server: Lite Speed
FTP functions: OK (required for Self-hosted (FTP) CDN support)
Multibyte String support: OK (required for Rackspace Cloud Files support)
cURL extension: OK (required for Amazon S3 support)
zlib extension: OK (required for compression support)
Opcode cache: Not installed
Memcache extension: Not installed
Mime type detection: Not installed
Hash function: hash (required for NetDNA purge support)
Safe mode: Off
Open basedir: Off
zlib output compression: Off
mod_mime: Not detected
mod_expires: Not detected
mod_deflate / mod_gzip: Not detected
mod_headers: Not detected
mod_env: Not detected
mod_setenvif: Not detected
mod_rewrite: Not detected

WordPress Resources
Uploads directory: Write-able
WP_CACHE define: OK
Fancy permalinks: OK
Network mode: Off

Just upgraded to 0.9.2.2 and the problem persists… ??

For reference, here are my compatibility settings:
Server Modules & Resources:

Plugin Version: 0.9.2.2
PHP Version: 5.2.15 (PHP5 required for Minify, Rackspace CloudFiles, Microsoft Azure support)
Web Server: Lite Speed
FTP functions: Installed (required for Self-hosted (FTP) CDN support)
Multibyte String support: Installed (required for Rackspace Cloud Files support)
cURL extension: Installed (required for Amazon S3, Amazon CloudFront, Rackspace CloudFiles support)
zlib extension: Installed (required for compression support)
Opcode cache: Not installed
Memcache extension: Not installed
HTML Tidy extension: Not installed (required for HTML Tidy minifier suppport)
Mime type detection: Not installed (required for CDN support)
Hash function: Installed (hash) (required for NetDNA purge support)
Safe mode: Off
Open basedir: Off
zlib output compression: Off

WordPress Resources

: Not write-able
/home/(…): OK
/home/(…): OK
Fancy permalinks: /%postname%/
WP_CACHE define: Defined (true)
Network mode: No

I’m with the same error =/

Compatibility Test

Plugin Version: 0.9.2.2
PHP Version: 5.2.17 (PHP5 required for Minify, Rackspace CloudFiles, Microsoft Azure support)
Web Server: Lite Speed
FTP functions: Installed (required for Self-hosted (FTP) CDN support)
Multibyte String support: Installed (required for Rackspace Cloud Files support)
cURL extension: Installed (required for Amazon S3, Amazon CloudFront, Rackspace CloudFiles support)
zlib extension: Installed (required for compression support)
Opcode cache: Not installed
Memcache extension: Not installed
HTML Tidy extension: Installed (required for HTML Tidy minifier suppport)
Mime type detection: Not installed (required for CDN support)
Hash function: Installed (hash) (required for NetDNA purge support)
Safe mode: Off
Open basedir: On: /home/thiagome:/usr/lib/php:/usr/php4/lib/php:/usr/local/lib/php:/usr/local/php4/lib/php:/tmp
zlib output compression: Off

WordPress Resources

: Not write-able
/home/thiagome/public_html/blog/wp-content: OK
/home/thiagome/public_html/blog/wp-content/uploads/2011/06: OK
Fancy permalinks: /%category%/%postname%
WP_CACHE define: Defined (true)
Network mode: No

WordPress 3.1.3

Just upgraded to 0.9.2.3, and the problem still persists. One thing that I noticed (which is probably causing the issue) is that W3TC didn’t add rules to my .htaccess.

I tried uninstalling, changing permissions in htaccess to 777, reinstalling it, but W3TC doesn’t seem to touch htaccess. I don’t get any error messages or warnings, so I’m not sure how to proceed.

Any help is appreciated!

I think W3 Total Cache don’t use .htacess with litespeed servers.

It does in W3TC 0.9.1.x.

Digging into the code I finally found what’s causing this. And yes, it’s related to LiteSpeed. It turns out that LiteSpeed is 100% compatible with Apache (uses htaccess, etc.), but the code that detects compatibility looks specifically for ‘apache’ as the server name.

IN version 0.9.2.3, replace the line 440 in w3-total-cache/inc/define.php:
return (isset($_SERVER['SERVER_SOFTWARE']) && stristr($_SERVER['SERVER_SOFTWARE'], 'apache') !== false);

with
return (isset($_SERVER['SERVER_SOFTWARE']) && (stristr($_SERVER['SERVER_SOFTWARE'], 'apache') || stristr($_SERVER['SERVER_SOFTWARE'], 'LiteSpeed')) !== false);

Hope this helps someone!
(I’ll try to contact Frederick directly regarding this issue in case he’s not listening to this thread)

Litepseed is not 100% compatible with apache in practice. For that that reason apache is detected and handled reliably, just like nginx is. Litespeed needs more testing to handle it’s nuances.

Thanks for your response, Frederick!

For the record, I’ve been using W3TC pre-0.9.2 for a long time with Litespeed and never ran into any issues, but thanks for letting me know that compatibility is a bit more messy than it seems.

Do you plan to add support for Litespeed in future versions of W3TC?

Thank you for finding this Luciano!!

Frederick – maybe add this to the FAQ? A lot of people have wasted a lot of time trying to find this answer/solution

Sorry for the trouble, Litepseed support is coming in the next release, so there’s no need for a FAQ update, it still works for some people as Luciano noted.

Any news about the next release with Litespeed support? I’ve been having problems using W3TC with Litespeed for CDN/Rackspace. As it’s working perfectly with Apache, I think it has to do with Litespeed…

Using litespeed fine with w3tc here, what i did was moved all .htaccess into httpd.conf which litespeed reads from and supports. Then in w3tc disable browser caching and httpd compression (both already enabled by litespeed).