[TYPO3-mvc] Issues with DateTime objects and PHP 5.2.14 - always return present day

[Christian Zenker]

Hi Franz.

> I need some help before going totally nuts.
Take a deep breath first or do something else! :)

> For what reason ever all DateTime objects have the date of the present  
> day and not the value stored in DB and I have no clue why.
This usually happens when the DateTime constructor is called without a  
property (same behavior like date() with the second parameter).
Have you tried fetching the value of database as integer? Maybe your  
mapping of property name to column name is not correct. It should return  
the timestamp (obviously).

After all I did not experience that behaviour on Extbase 1.2 (non-trunk).

> I try to get a update to PHP 5.3.x by the admins, but that might not be  
> possible.

This should not have to do anything with the PHP branch.

Christian.

On Mon, 11 Apr 2011 07:15:21 +0200, Franz Koch  
<typo3.RemoveForMessage at elements-net.de> wrote:

> Hey folks,
>
> I need some help before going totally nuts. I've just installed a  
> extbase (current GIT version) based extension on a live server running  
> PHP 5.2.14 and have serious issues with DateTime objects.
>
> For what reason ever all DateTime objects have the date of the present  
> day and not the value stored in DB and I have no clue why. Anybody ever  
> came across such a curiosity?
> I try to get a update to PHP 5.3.x by the admins, but that might not be  
> possible.
>
> Any ideas?