500 Server Error - Error Log Shows Pagelines Issue
Posted 20 November 2012 - 09:07 PM
Each time the issue occurred when I was updating pages. The issue did not occur due to adding or updating or deleting any plugins. I was working on updating multiple pages within the site without issue and then suddenly a '500 Server Error' would happen without warning while updating a page.
Host Gator (my webhost) resolved the issue both times and then logged into my CPanel to investigate the error. They pinpointed the issue to the Pagelines Theme. Here is what they shared with me:
Premature end of script headers: index.php
stat("/home/mejohns1/public_html/runneracademymembership.com/wp-content/themes/pagelines-template-theme/style.less", 0x7fff13fb1970) = -1 ENOENT (No such file or directory)
What can be done to resolve this?
Posted 20 November 2012 - 09:18 PM
is_file() uses stat() to check if the file exists, and that would not produce an error of any kind. If your getting a 500 error apache should produce a log, ask to see it. Also turn on WP_DEBUG in wp-config.php to view any php errors as they happen.
We code everything with full debugging turned on so can pretty safely say it isnt the framework generating errors.
Posted 20 November 2012 - 09:23 PM
Posted 20 November 2012 - 09:28 PM
As i said, the framework looks for that file, and if it exists it uses it, if not it just carries on, it isnt needed.
Turn on WP_DEBUG and see what is actually causing the errors.
Posted 20 November 2012 - 09:52 PM
[Tue Nov 20 15:29:10 2012] [error] [client 184.108.40.206] Premature end of script headers: index.php
[Tue Nov 20 15:29:11 2012] [error] [client 220.127.116.11] Premature end of script headers: index.php
Since it is tied to the Child Theme I reverted to the base Pagelines installation and we'll see if that resolves it. Not ideal, but I feel I am in an infinite loop. The only other thing I can think of is I deleted Buddy Press from my install not too long ago, including the Pagelines supported integration for it. But I would think that would cause an immediate issue rather than things working for a bit and then throwing an error later.
Posted 20 November 2012 - 09:57 PM
Premature end of script headers means nothing, its just PHP reporting an error, and as you have all errors suppressed ( wp does this unless you turn ON debug ) thats all you will ever see.
Posted 20 November 2012 - 10:29 PM
Posted 21 November 2012 - 08:26 PM
Posted 25 November 2012 - 01:14 AM
For some unknown reason, I can no longer save custom CSS in the custom CSS/LESS input area. What was happening is that the custom code was only saving the first 16 lines or so resulting in parse errors. I deleted all code in the custom code input area and instead inserted it into the Pagelines Customize Plugin. Problems are solved.
Again, no idea why this started happening, but I have not received any further 500 errors since taking the steps above.