Still Please check permissions, all set

I’ve installed Quick cache in domainnaam.nl/intranet, and get the warning:

Could NOT enable Quick Cache. Please check permissions on /wp-config.php, /wp-content/ and /wp-content/cache/. Permissions need to be 755 or higher.

In DirectAdmin I ‘ve set the 755 permissions in domain.nl/public_html/intranet, domain.nl/public_html/intranet/wp-content and domain.nl/public_html/intranet/wp-content/cache. Still I get this error.

Which steps can I take to make this plugin work?

Hello Martijn,

Could you try what Jason says in this post:
http://www.s2member.com/forums/topic/cannot-get-quick-cache-to-work-no-mutex-lock/#post-42218

– Eduan

Thanks for your reply. There were no files in that folder, and the permissions on [domainname]/public_html/intranet/wp-content are set on 755.

So sadly this is not the solution.

Have you set the 755 permissions on the /wp-config.php file? This file is in the same place as the wp-content folder, in other words they’re both located at the root of your WordPress install.

– Eduan

Yes, wp-config.php has 755 permissions.

That’s strange. Could you please try these common trouble shooting tips:
Knowledge Base » Common Troubleshooting Tips

– Eduan

Sure, these are the results:

Conflicting Plugin
When I deactivated all plugins the issue persists.

Conflicting Theme
With the theme Twenty Twelve the issue persists.

Server Configuration
Everything seems ok, see this PDF. I’ve changed the memory allocated to PHP to 64M, this was 40M.

Outdated Installation
All the plugins and WP itself are up to date

Have I checked all the necessary things?

That’s strange… Could you try just re-installing Quick Cache?

Do you have any other cache plugins besides Quick Cache?

– Eduan

I’ve reinstalled it but that doesn’t help. Quickcache is the only caching plugin I use…

Hmm… don’t know what else it could be… OH! Try chown, you used chmod to give it the right permissions, now make sure it’s owned by the right user. ;)

If that doesn’t work…

Could you try making another new installation of WordPress (in the same server) and see if it works there?

If it doesn’t, could you try with another server? If it works there then it’s an issue with your server.

If none of this works then I am completely out of ideas. :/

– Eduan

On one of my other sites (same host) Quick cache runs fine.

I don’t know how to use CHOWN, when I chose ‘Reset owner’ in DirectAdmin I get the following error ‘An error occured while resetting the file ownership’. Details isn’t clickable.

What could this mean? I get the same error on my other sites.

Ah so you’ve been doing this stuff through a cPanel or through the command line? You should do this stuff through the command line (aka terminal BTW)…

You would change permissions with sudo chmod 755 wp-config.php wp-content wp-content/cache and you would change user with sudo chown [your unix username] wp-config.php wp-content wp-content/cache.

Again, this is through the command line/terminal.

– Eduan

Ok…
I don’t know how to do this and if it’s supported by my hosting company, so I asked them a question on their forum. I’ll come back to you If I have a reaction.

The hosting company wants to investigate this case further (they’re also puzzled), but I have found a solution, sort of.

I’ve installed the plugin withing the WordPress installation of our intranet.

Today I found out that I don’t get the error if i give the cache folder as wp-config.php in the directories /public_html/intranet and /public_html 777 rights. When I change one of these three I get the error again.

To put everything on 777 seems a bit risky to me. Do you agree?

Yes it is risky and not recommended at all. That gives any able hacker full and total access to whatever has 777 permissions.

– Eduan

That’s what I thought. I’ve set the persissions back to 755 and wait for the replay of my hosting company.

Strange that the error disappears if I set the permissions to 777.

I’m just thinking… Perhaps the user WordPress uses doesn’t have the right permissions.

This is the only thing that comes to mind now to be honest. I’m not sure if WordPress even uses a different Unix user, but it’s worth looking into once we run out of options…

– Eduan

That could be the case but I’m administrator (more permissions aren’t possible… ;-), so I don’t think that’s the problem.

Maybee my hosting company has an idea, let’s wait for that. Thank you for all your help so far!

No problem. Hope your server providers can help you, because I’m out of ideas. ;)

The problem is solved!! My hosting company moved the site to another server, now there are no errors anymore… :-)

Great! Glad you found the source of the problem, and fixed it. :)

I’m glaad too! :-)