Blank Screen ... Dead Air

[dissignal]

Hi

I checked the trial version of the calendar on my local server and immediately received the error message that my trial version had expired. Since I had the same issue on the server, I purchased a license. The setup works fine - it accesses the calendar via the Event Manager, and I can create events with no problem. However, getting these events to be visible anywhere else (ie, accessing calendar.php) brings up a blank screen at best and a 500 error at worst. Can you point me in the right direction, please? I have a feeling it's a config / permissions issue ...

thanks a lot - Oliver

[ve9gra]

Have you had a look at the instructions for proper Integration?

http://docs.easyphpcalendar.com/

Usually, problems like you're describing are caused by wrong paths being put in the require command.

[dissignal]

I have been through the integration docs. With a php file that contains nothing but <?php $CSS=1; require("calendar/calendar.php"); ?> - and that being the correct path, and as far as I can tell the paths in calendar.php also being correct - all I get for a result is a 500 error.

[ve9gra]

Do you have a link to your calendar installation and your testing page?

A 500 error is an error that occured internally with the server and could be caused by a number of things external to the calendar (PHP install, Zend install, MySQL install, etc...).

[dissignal]

I'm looking into this right now ... for some weird reason I am getting a 500 error for ANYTHING in the /calendar/ folder ... but it's all fine again when I am in calendar/setup

I can't give you the link, I'm afraid, as the site contains confidential material. I do know that the MySQL, PHP, etc installs are all working fine, as I have both PHP and MySQL working fine in general on that server. Let me see if I can find a way to grant you access ... in the meantime, any other idea based on what I've said above?

[dissignal]

[Mon May 14 07:21:55 2007] [error] [client XX.XX.XX.XX] Premature end of script headers: php-script

this is the error
from the log ...

[Brian]

Googling the error lead me to several possible causes and solutions, such as:

The solution to this problem was interesting. I changed the permission of the file and the containing directory from 777 to 755 and that solved the problem!

[dissignal]

Brian, I apologise for my delayed reply. In order to fix this, I switched to a Windows machine and used the auto-installer. It works great, Thanks!