Posted 05 March 2010 - 03:48 PM
I've discovered the problem, but don't have a satisfactory workaround yet.
The problem, in my case (your situation may be different or a variation): I have a .htaccess file at the root level of the site. This file uses an AddHandler directive telling the webserver to handle any php code it finds in .html pages.
The reason for this is a server-side app that executes php embedded in some html pages. The problem was that GoDaddy (the site's host) has apparently configured their servers to not handle php code found in .html pages. So to get their servers to handle php properly the handler directive was needed.
But, PageLines themes (I've tried iBlog, WH) get confused by the .htaccess and end up seeing the wrong version of PHP. This is confirmed by renaming the .htaccess file. When that is done the PageLine themes are happy. But now the webserver doesn't handle php in html pages. Change the name back to .htaccess the themes are unhappy.
Here's 3 fixes I've thought of so far.
Renaming .html pages to .php pages and then removing the .htaccess file will solve the problem. But, then any links to those pages (inbound and internal) would have to be corrected. Not great mature popular sites. If that's not an issue to you then this would work. Apparently .php and .html pages are equal in the minds of spiders.
PageLines could examine why their themes get confused by this situation. Maybe that could be fixed.
GoDaddy could reconfigure their webservers to handle php code in html pages without a special AddHandler directive for each such site. (I'll try this again, but they went not keen about it a couple of years ago when this issue was raised)