WordPress.org

1. ctvonline
   Member
   Posted 7 months ago #
   

   I need a serious walk-through here as I've been searching on Google and the WP forum all day and still don't get what's going wrong.

   Installed W3TC for a client and immediately was met with 2 red error messages from the start. She's on iPage shared hosting (as am I), but out of the two of us she's the only one getting these errors.

   Error #1. It appears Page Cache URL rewriting is not working. If using apache, verify that the server configuration allows .htaccess or if using nginx verify all configuration files are included in the configuration.

   Changing the Page Cache Method from Enhanced to Basic solves this, but how can I get it to work WITH Enhanced? Like I said we have the same host and mine seems to have no problem, but hers does.

   Error #2. It appears Minify URL rewriting is not working. If using apache, verify that the server configuration allows .htaccess or if using nginx verify all configuration files are included in the configuration.

   The only way I can resolve this error is by just turning it off, but I don't want to turn it off. I've tried everything I could and still can't get this error to go away.

   After all of this, I decided to run a compatibility check, and the results are as follows:

   Server Modules & Resources:

   Plugin Version: 0.9.2.4
   PHP Version: 5.3.13 (PHP5 required for Minify, Rackspace CloudFiles, Microsoft Azure support)
   Web Server: Apache
   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: Installed (Fileinfo) (required for CDN support)
   Hash function: Installed (hash) (required for NetDNA purge support)
   Safe mode: Off
   Open basedir: Off
   zlib output compression: Off
   set_time_limit: Available
   mod_deflate: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_env: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_expires: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_headers: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_mime: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_rewrite: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_setenvif: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   WordPress Resources

   /hermes/bosweb26c/b494/ipg.rudetrendznet/rudetrendz/.htaccess: OK
   /hermes/bosweb26c/b494/ipg.rudetrendznet/rudetrendz/wp-content: OK
   /hermes/bosweb26c/b494/ipg.rudetrendznet/rudetrendz/wp-content/uploads/2012/10: OK
   Fancy permalinks: /%postname%/
   WP_CACHE define: Defined (true)
   URL rewrite: Enabled
   Network mode: No

   1. I get that "not detected" MIGHT not be a bad thing, however when an error is thrown up that's stating Page Cache URL isn't working, and all of the things having to do with that (mod_*) say "not detected"...I'm inclined to be worried about that. Especially when they say that they're "required for Page Cache (enhanced mode) and Browser Cache".

   2. Where does someone on shared hosting find and install the Opcode cache, Memcache, and HTML Tidy extensions?

   3. zlib output compression seems to be off. However I've tried everything possible to get this (which I assume to be gzip compression) on. How can i go about it the right way?

   http://wordpress.org/extend/plugins/w3-total-cache/

2. Chris Olbekson
   Level 12 Bug Squasher & Forum Moderator
   Posted 7 months ago #
   

   mod_deflate: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_env: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_expires: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_headers: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_mime: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_rewrite: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
   mod_setenvif: Not detected (required for Page Cache (enhanced mode) and Browser Cache)

   This doesn't necessarily mean that those modules are not installed it just means that they can't be detected. This is why you are getting the disk enhanced and url page rewriting errors.

   Check with your host and if those modules are installed then just dismiss the errors.

   As far as opcode caching, it is not possible to install this on a shared host.

3. ctvonline
   Member
   Posted 7 months ago #
   

   Ok Chris I've checked and apparently they only support mod_rewrite, and not the other modules. But now I have 2 additional questions...

   #1. In my php.ini file I've turned on "zlib.output_compression", and put it at level 6. When returning to W3TC it gave me a yallow error that I need to diable it server side in order to ensure proper HTTP compresison behavior. Should I comply with W3TC, or turn their's off and use the "zlib.output_compression" from my server instead? Or does it even matter at all?

   #2. How can I get the Minify URL error to go away without turning it off?

   And since I'm currently unable to use most of the big features of this plug-in, would you recommend another plug-in or combinations of plug-ins to gain the same functionality and speed?

4. Frederick Townes
   Member
   Plugin Author
   Posted 2 months ago #
   

   @ctvonline:

   1. You should disable that if you're using W3TC, in fact W3TC has a warning about that.
   2. The next release has some fixes there. If they're not working for you please submit a bug submission form from the support tab of the plugin.

Reply

You must log in to post.