debugging on php 5.3.19

[powerchaos]

hi,
here are some screenshots of errors that happends if php 5.3.19 is fresh installed

First we got the time/date error , if it is not defined in php.ini ( now defined to europe/berlin )
http://puu.sh/1BCge

after that ,we can login and gain acces to the admin cp to encounter the following error
the error shows when you click a link
http://puu.sh/1BCoz

*edit*
login problem is solved after you logout and login again ( system logged me out)
the admin cp ask to login again after you logged in into the homepage
but the date/time problem is still the same

*edit*
seems to be a php setting

error_reporting = E_ALL & ~E_DEPRECATED


; E_DEPRECATED - warn about code that will not work in future versions
; of PHP


*edit*
after your sesion expired in the admin arena ( or you do not relog ) then you get the following error

http://puu.sh/1BKYN

no idea if it has to do with my php config or that is it a script related error

---
i will update this if i find more and how i solved them

Greetings From PowerChaos

[Hall of Famer]

Alright, this does seem somewhat strange. I am running PHP 5.3.19 too on my server and nothing like that ever popped out before. Good luck debugging it, this may be a mistake either on the script side or on your server side:
https://github.com/composer/composer/issues/923

[powerchaos]

updated the log , latest error found is the admin sesion timeout and when no relog is done
after logged in is it fixed ... but it shoulnd happen in first place :D

Greetings From PowerChaos

[Hall of Famer]

I see thats pretty cool, are you able to finally fix the datetime configuration settings now?

[powerchaos]

The date/time error is because of the php.ini setting

you need to specific a date/time in php.ini before it works
on a default instalation of php5.3.19 is it not defined , thats why it trowed out that error :d

that final error is still unknown to me to fix that
it does only happen when you are not logged in and click on a link (after session is expired)

a relog fixes that problem , but no idea why it start showing that error when it should show a error page instead

Greetings From PowerChaos