up vote 1 down vote favorite
share [g+] share [fb]

I'm having some issues trying to make my Wordpress installation "bullet proof". I was installing Wordpress on my testing server, when I noticed that I had a permission problem with folders and themes installation. I tried to fix it using the following commands, located in this SF answer:

For Directories:

find [your path here] -type d -exec chmod 755 {} \;

For Files:

find [your path here] -type f -exec chmod 644 {} \;

You have to omit to use this command for /wp-includes/.

Now I just see a blank screen in my Wordpress directory. I don't want to chmod 777 the Wordpress directory. That would fix the problem, but would create a security issue.

link|improve this question
0% accept rate
check your error log why you are white screening – Mike May 17 '11 at 16:13
well I just change the permissions to 777 again hahaha and now I'm able to see my regular wordpress, now I'm wondering why in my Mac OSX I did not have problems like this one, I just intalled MAMP, downloaded the last wordpress package and that's it! is it any other setting in Apache or something that I have to check? – mckain May 17 '11 at 16:21
I got it! Finally It's working! I just switch my user for root and then reInstalled wordpress, and that's it! I didn't have to chmod any file! pffff! I'm tired! need a beer! hahahaha – mckain May 17 '11 at 16:41
feedback

1 Answer

up vote 0 down vote

Depending on your setup it can happen that those settings are not permissive enough. You may need to grant write access (77*) to the group (HTTP server process) too, at least to selected files/directories.

See Changing File Permissions on WordPress.org for more information.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.