https://forge.joomlapolis.com/https://forge.joomlapolis.com/favicon.ico?17095821032011-03-29T18:08:09ZJoomlapolis forgeCB GroupJive - Bug #2456: events date and time calculations offhttps://forge.joomlapolis.com/issues/2456?journal_id=43332011-03-29T18:08:09Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Fixed in r1675</p>
<p>Issue is non-critical and most users should not notice it's affects. Typically only applies to editing an event. Next release will have new db date function removed as is too unreliable.</p> CB GroupJive - Bug #2456: events date and time calculations offhttps://forge.joomlapolis.com/issues/2456?journal_id=43422011-04-04T07:24:23Zjojo12
<ul></ul><p>krileon wrote:</p>
<blockquote>
<p>The date and time calculations are not accurate when a Joomla global offset is applied. Anything but +0 appears to throw off the accuracy of the dates and times.</p>
</blockquote>
<p>I suggest this belongs to my problem too, but is not yet solved:<br />on my j1.5.22, cb1.4, gj2.2 (I use 24 hours)<br />I enter in frontpage an event with date and time f.e: 19:00. After saving the time is one hour less => 18:00. So all my groupmembers ask me, when (because they know it would normally be at 19:00).<br />That's very bad and not usefull. How can I (we) change that quickly?? Thank you for your quick help!<br />It depends on Timezone in j15: this problem is when I have set UTC+1.<br />When I set Timezone UTC+3.3 and enter an event, then I have 15:30!</p> CB GroupJive - Bug #2456: events date and time calculations offhttps://forge.joomlapolis.com/issues/2456?journal_id=43442011-04-04T14:12:19Zkrileonkrileon@joomlapolis.com
<ul></ul><p>It is fixed for next release, there is no quick fix for this issue.</p> CB GroupJive - Bug #2456: events date and time calculations offhttps://forge.joomlapolis.com/issues/2456?journal_id=44372011-05-02T14:52:56Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>