Doug Stewart on 7 Mar 2014 07:34:03 -0800

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] Back to wordpress

Stripping the execute bit off directories is problematic. Do a `find /wp-content/ -type d -exec chmod 775 {} \;` and see if that helps.

I'm also a bit concerned about NO error entries showing up in the logs. If you're encountering perms issues *or* a PHP misconfiguration, it should be tossing 403's and 500's into the logs.

Can you verify the traffic in your access logs? Are you getting 301/302/200 in the codes for all requests?

On Fri, Mar 7, 2014 at 8:10 AM, Eric H. Johnson <> wrote:

The owner is the same as for everything else under wordpress, root:www-data.
I forced chmod to 666 for everything under themes to take the owner out of
the equation. No difference. What in the configuration sets the path to the
theme folder, is it possible this is pointing to the wrong place?


In general, files under a WordPress install should belong to (web user):(web
group). On RHEL derivatives, that means apache:apache, on Deb derivatives
it's www-data:www-data, iirc.

Additionally, from the root of your WP install, you should run a `find .
-type f -exec chmod 660 {} \;` and a "-type d/chmod 771" equivalent as well.

The Debug Bar plugin can be helpful in these situations, but only if you're
actually logging errors. What is your display_errors set to in php.ini?

Philadelphia Linux Users Group         --
Announcements -
General Discussion  --


Philadelphia Linux Users Group         --
Announcements -
General Discussion  --