http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692016-04-24T18:09:18ZTYPO3 ForgeTYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3029372016-04-24T18:09:18ZNicole Cordestypo3@cordes.co
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul><p>Hi Sebatian,</p>
<p>Thank you for your bug report.</p>
<p>Your problem should be solved with <a class="external" href="https://review.typo3.org/#/c/47136/">https://review.typo3.org/#/c/47136/</a></p>
<p>Can you please test this patch, which was also backported to 7.6 <a class="external" href="https://review.typo3.org/#/c/47846/">https://review.typo3.org/#/c/47846/</a> and give feedback if this solves your problem as well.</p> TYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3078042016-06-27T19:33:14ZSebastian Mazzasebastian@mazza.at
<ul></ul><p>Hi Nicole,<br />thank you for this patch, it solves my Date/Time update problem with the Exbase DataMapper.</p>
<p>But, while testing, I found an other, in my opinion inconsistent behaviour with the backend.<br />If you store Date/Time values in the DB as UNIX Timestamp (<code>int</code>). The values, displayed in backend forms are increased by the time offset of your local Timezone. But if you store the Data/Time values in table columns of type <code>datetime</code>, the backend form displays the exact UTC time that are stored in the DB.<br />In other words: If you store your Date/Time values as UNIX Timestamps the frontend output is exact the same as the backend form output. But if you use <code>datetime</code> columns instead, your frontend output is increased by the time offset of your local time zone. (e.g. submit 27.06.2016 10:00 in backend, leads to an output of 27.06.2016 12:00 in the frontend)</p> TYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3143972016-09-27T10:56:14ZRiccardo De Contardierredeco@gmail.com
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>New</i></li></ul> TYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3295452017-04-15T01:15:12ZMona Muzaffar
<ul><li><strong>Related to</strong> <i><a class="issue tracker-10 status-5 priority-4 priority-default closed" href="/issues/80852">Epic #80852</a>: Datetime handling in backend</i> added</li></ul> TYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3345502017-06-06T18:19:41ZMarkus Kleinmarkus.klein@typo3.org
<ul><li><strong>Parent task</strong> set to <i>#77562</i></li></ul> TYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3345832017-06-06T19:12:35ZMarkus Kleinmarkus.klein@typo3.org
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-2 priority-3 priority-lowest child" href="/issues/68651">Bug #68651</a>: Datetime() properties have wrong timezone</i> added</li></ul> TYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3345852017-06-06T19:14:07ZMarkus Kleinmarkus.klein@typo3.org
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/74376">Bug #74376</a>: Extbase persistence not working with datetime fields</i> added</li></ul> TYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3345872017-06-06T19:14:28ZMarkus Kleinmarkus.klein@typo3.org
<ul></ul><p>Closing as duplicate of <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Extbase persistence not working with datetime fields (Closed)" href="http://forge.typo3.org/issues/74376">#74376</a>.</p>
<p>The other mentioned issue is dealt with in <a class="issue tracker-10 status-2 priority-5 priority-high3 parent" title="Epic: Misbehaviors with datetime values and timezones (Accepted)" href="http://forge.typo3.org/issues/77562">#77562</a></p> TYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3345882017-06-06T19:14:40ZMarkus Kleinmarkus.klein@typo3.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul> TYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3345992017-06-06T19:25:50ZMarkus Kleinmarkus.klein@typo3.org
<ul><li><strong>Parent task</strong> deleted (<del><i>#77562</i></del>)</li></ul> TYPO3 Core - Bug #68849: Unstable persistence handling of DateTime (don't get what you set)http://forge.typo3.org/issues/68849?journal_id=3346462017-06-07T11:02:54ZMarkus Kleinmarkus.klein@typo3.org
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-10 status-5 priority-4 priority-default closed" href="/issues/80852">Epic #80852</a>: Datetime handling in backend</i>)</li></ul>