Warning function.session-start Error - Can't Log In

[Zayin]

Hi,
I installed Mysidia ver 1.3.2, and have had errors every, single, possible step of the way. Right now I have this:
Warning: session_start() [function.session-start]: open(/var/chroot/home/content/86/10005386/tmp/sess_t32nvobci8bt4o571g187101g3, O_RDWR) failed: No such file or directory (2) in /home/content/86/10005386/html/classes/class_session.php on line 13

Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/content/86/10005386/html/classes/class_session.php:13) in /home/content/86/10005386/html/classes/class_session.php on line 13

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/content/86/10005386/html/classes/class_session.php:13) in /home/content/86/10005386/html/classes/class_session.php on line 13

It pops up over my home page. I can't log in, because the session can't get off the ground. I've tried reinstalling it multiple times, reencoding files with UTF-8 (No BOM), checking for spaces, updating php, searching forums...

So please help me out. What's going on here? :catfish:

[Zayin]

Well, I figured out the problem. As it turns out, since I'm hosted with GoDaddy, there was a problem with writing session data to a directory that either didn't exist, or was denied permission to write. So for anyone else with this horribly misleading error, here was the solution:
session_save_path('/home/content/blah/blah/html/temp');
I inserted this line into class_session.php, just before session_start(), replacing that path with the absolute file path for my host. I then made a file called "temp" and made it writable, so bazinga. It works now, I can log in to mysidia. :meow:

[Hall of Famer]

Oh interesting, never thought there were hosting companies with this kind of issue. Nice discovery.

[Zayin]

Yeah, it took a long time to come to that conclusion. I kept looking through the code for a space, or reencoding the files, uploading them in binary, the kinds of things you'd expect from a header exception.

Another thing specific to my hosting is that they had the php set to version 5.2 by default, which caused the scripts not to work at all. I eventually found one of the topics here about there being a php bug, so I had to go into my control panel and find the switch to turn in to 5.3. Lol, don't know why they had it set to 5.2 :hmmm:

[Hall of Famer]

Well there are still about half of webhosts using PHP 5.2 right now, in future the situation will get better.