Blank page in setup

[WarlockInc]

When I first ran setup on version 5.7 it asked for the username and password to be created, but then when it went to next page it's blank. And continues to be blank if I try and access setup...

www.dallasbrat.com/escal/setup (http://www.dallasbrat.com/escal/setup)

[Brian]

Is this the full version or the trial?

[WarlockInc]

It must be the trial as I haven't purchased anything.

[Brian]

Did the test script report everything was okay for running the calendar script? Are you using the Zend Version? Did you try the ionCube Version?

[WarlockInc]

There were no error messages at all, just went from the screen where it asks for a username and password to a blank screen and has been a blank screen ever since. The demo.php shows up fine.

[Brian]

This is a common bug with the trial version due to the Zend encoding. Unfortunately, I don't have any way around this other than trying the ionCube version (link in your license email).

I also would be willing to try uploading the full version to make sure it would work before you purchase the script.

[WarlockInc]

If the full version fixes this, then I'll just get the full version. I'll keep you posted...

[WarlockInc]

Uh oh, same thing... unless I did something wrong in the purchase/download process...

[Brian]

Did you delete the trial files before uploading the new ones. Also, the paid version should be uploaded in ASCII (opposed to the trial which is binary.)

[WarlockInc]

I completely deleted the trial version, WS_FTP picks for me the type of upload. Have never had a problem before. and everything else seems to work. It asked for the username and password again. demo works... etc

[Brian]

Can you send me a PM with your FTP information so I can take a look?

[LoflandConsulting]

The problem turned out to be session handling. We have a more complex php setup and our default session handling in php.ini is definitely not the default (we do DB storage, but our other sites are setup to initiate the DB connection for doing the session storage using custom session handlers). Anyways, long story short, the easy fix for this prob was to drop an .htaccess file in to the escal folder with the following entries:
php_value session.save_handler files
php_value session.save_path /tmp
We have apache set to look for .htaccess files. With this work-around, session handling works fine as does EScal.