Support Forum
Support Forum
Offline
wp-content is lpdg:lpdg as well
to make sure - I did a [ chown -R lpdg:lpdg * ] in root www dir
still no good -- what can it be??
Offline
phrankerCO said
guppydas said
I found similar problem when I had enabled suPHP.
Check if your Apache PHP handler is suPHP or DOS or CGI?
My hosting provider also experimented with it and was surprised to see this as he was able to replicate similar error. Same configuration ... except the way PHP is handled.
Not quite sure how to check - loaded phpinfo(); searched suPHP - nothing found...
I'm lost?!?!?!?
Ok Look for the value "Server API" ... what does it say? That will tell you which handler is in effect. Some of the answers are :
1) Apache 2 Handler (which also is I guess the DOS handler)
2) CGI
3) suPHP
Want to live like a King tomorrow? Sleep like a King tonight!
Offline
phrankerCO said
Server API = CGI/FastCGI
Sorry My bad, I was wrong. Been up for over 20 hrs and tired so I am bit confused in my head. 
Looks like you ARE ON suPHP ...
http://support.hostgator.com/a.....c-or-suphp this will sort of explain a little.
My guess is for some reason suPHP is messing up with either CSS or the PHP script which uses CSS for final output of the layout for redering as an HTML page.
Well I guess Mr Papa will have to help you on that one. I will keep an eye open for this issue. If you happen to resolve it, please do take a few moments and share the process here. It will be highly appreciated.
Want to live like a King tomorrow? Sleep like a King tonight!
Offline
guppydas, appreciate all the help. please keep throwing the ideas out there...
but for reference we run suphp on this server so its not global to that...
phranker, do you have host support? might be worth asking them why the web user cannot access those files...
might have missed the settings, but the dirs should be 0755 and the php files should be 0644...
Visit Cruise Talk Central and Mr Papa's World
Offline
So - I figured it out. It was the suPHP issue and what it was catching and error out on was; that "wp-content" was GROUP WRITABLE - go figure.
Not world writable, just user and group writable and thats what stopped the script from executing. FYI: I found the error in /usr/local/apache/logs/error_log which is what lead me to change the dirs permissions.
WOW!!
Thanks for all the help.
Hopefully this thread will help others.
Offline
good hunting... glad its resolved... but this in particular is not really suphp issue (especially since you are running fcgi)
thanks for the update!
Visit Cruise Talk Central and Mr Papa's World
All RSS1 Guest(s)