Just a quick tip for wordpress users.
We saw a lot of “broken themes” when we were installing our new blog. WordPress complained about the style.css fire being unreadable.
We set the directory permissions to 755 but still saw the error.
We fixed it !
SOLUTION
Ensure the file owner and group owner is the same as your webserver owner and group
In this example
drwxrwxr_x 2 apache www-data 4096 Aug 11 19:47 classic
drwxrwxr_x 3 apache www-data 4096 Aug 11 19:47 default
drwxrwxr_x 3 ftp-usr wheel 4096 Sep 9 09:00 eximius
drwxrwxr_x 3 ftp-usr wheel 4096 Sep 9 08:45 jules-joffrin
drwxrwxr_x 3 apache www-data 4096 Sep 9 08:37 wp1
classic loads
default loads
eximius fails
jules-joffrin fails
wp1 loads
Try the chgown and chgrp commands under *nix to fix the ownerships.
The same solution works with plugins and widgets -
Good luck and have fun
[...] WordPress – cannot read style.css-Solution Posted by WPCitrus on 9 September, 2009 No comments yet This item was filled under [ Themes, WordPress ] tweetmeme_url = 'http://wp.lemonandlimedesigns.co.uk/?p=5549';tweetmeme_source = 'SaveForWeb'; Just a quick tip for wordpress users. We saw a lot of “broken themes” when we were installing our new blog. WordPress complained about the style.css fire being unreadable. We set the directory permissions to 755 but still saw the error. We fixed it ! SOLUTION Ensure the file owner and group owner is the same as your webserver owner and group In this example drwxrwxr_x 2 apache www-data 4096 Aug 11 19:47 classic drwxrwxr_x 3 apache www-data 4096 Aug 11 19:47 default drwxrwxr_x [...]
[...] the original: WordPress – cannot read style.css-Solution alegria-tech, apache-www-data, archives, archives-september, author, broken-themes, cannot-read, [...]