I'm hosting my site on GoDaddy and I've uploaded all the Gallery2 files and I've created a database through GoDaddy but haven't yet installed any Graphics toolkit (not sure how/which one/if i really need to yet). But when I go to the installer I have these warnings at the top:
Quote:
Warning: session_start() [function.session-start]: open(/var/chroot/home/content/j/v/n/jvnimages/tmp/sess_f6c5ab0384968a305021ac249ffef170, O_RDWR) failed: No such file or directory (2) in /home/content/j/v/n/jvnimages/html/gallery2/lib/support/GallerySetupUtilities.class on line 357
Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/content/j/v/n/jvnimages/html/gallery2/lib/support/GallerySetupUtilities.class:357) in /home/content/j/v/n/jvnimages/html/gallery2/lib/support/GallerySetupUtilities.class on line 357
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/content/j/v/n/jvnimages/html/gallery2/lib/support/GallerySetupUtilities.class:357) in /home/content/j/v/n/jvnimages/html/gallery2/lib/support/GallerySetupUtilities.class on line 357
Any ideas? Seems like it's some kind of PHP error? If that's the case, I'll probably have to go through GoDaddy for any changes that need to be made, right?
Posts: 16504
What version of Gallery? What hosting plan are you using on GoDaddy?
____________________________________________
Like Gallery? Like the support? Donate now!
Posts: 3
Gallery 2.3.1 and the Linux hosting plan.
Posts: 8339
Those warnings are harmless and can be ignored during install.
But if they persist after install let us know.
-s
FlashYourWeb and Your Gallery with The E2 XML Media Player for Gallery2
Posts: 3
I tried ignoring them and on the next step, authenticating, I get these errors:
That's when I create the login.txt file myself with notepad. If I click on the link to get the provided file I get these errors:
Posts: 1642
Refer this issue to your host and ask them to verify that the current setting of session.save_path is correct and that your php user can write to this location.
--
dakanji.com