Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

PRO: advanced-cache.php warning false alarm #16

Closed
ethanpil opened this Issue · 4 comments

2 participants

@ethanpil

When I update my quickcache pro settings, I get the error message

Failed to update your /wp-content/advanced-cache.php file. Most likely a permissions error. Please create an empty file here: /wp-content/advanced-cache.php (just an empty PHP file, with nothing in it); give it permissions 644 or higher (perhaps 666). Once you've done this, please try again. 

Here is the thing. My file is set to 777 and it actually is updated by the plugin.

I created a new file, /wp-content/advanced-cache.php and uploaded via FTP. It was 0 bytes.

I then updated the plugin settings and checked the FTP. The file was now 21k. So actually it is writeable by the plugin.

@jaswsinc jaswsinc was assigned
@jaswsinc
Owner

Thanks for reporting this important issue.

This error could be slightly misleading in a specific scenario. I'd like to find out for sure though. In addition to the /wp-content/advanced-cache.php file, Quick Cache also creates an identifier inside the /wp-content/cache directory. Can you please confirm that your /wp-content/cache directory is also writable?

TIP: You should also find this file; if all was successful.
/wp-content/cache/qc-advanced-cache

@ethanpil

That was a good question, after playing with things a bit, here is the conclusion.

  1. I had the /wp-content/cache/qc-advanced-cache file already from a previous install. Even though the /wp-content/cache folder was writable, it seems that the qc file itself was incorrectly permissioned.

  2. I renamed /wp-content/cache/qc-advanced-cache and saved my settings again, and /wp-content/cache/qc-advanced-cache was generated correctly without the error message

  3. Just to put the final nail in the coffin, I deleted the newly generated /wp-content/cache/qc-advanced-cache file and restored the original /wp-content/cache/qc-advanced-cache and saved settings again via wp-admin. Sure enough, I got the error message again.

So, in conclusion, it seems that I did have a permissions error, but the error message the plugin provided was misleading, indicating the error was with a different file.

@jaswsinc
Owner

So, in conclusion, it seems that I did have a permissions error, but the error message the plugin provided was misleading, indicating the error was with a different file.

Thank you for that detailed report. I'm looking into this now.

@jaswsinc jaswsinc closed this in 749c119
@jaswsinc jaswsinc referenced this issue from a commit in websharks/zencache-pro
@jaswsinc jaswsinc Bug fix. Closes websharks/zencache#16 2e4e8df
@jaswsinc
Owner

Improved error reporting in this scenario.

11-27-2013 8-41-25 am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.