http://www.magentocommerce.com/bug-tracking/ en MagentoCommerce Copyright {gmt_date format="%Y"} {gmt_date format="%Y-%m-%dT%H:%i:%s%Q"} http://www.magentocommerce.com/bug-tracking/issue?issue=4300 Posted: 2008-12-02 01:36:12
Category: Orders
Version: 1.1.8
Priority: normal
Status: closed
Reported By: capple_

When viewing an order in admin's view (Sales > Orders), it seems the two order dates, one normal, one based on time zone, do not correspond at all.

Example of an order:
In the database (sales_order table), the created_at is 2008-12-02 04:43:11
But in admin's order view (Sales > Orders):
Order Date Dec 1, 2008 11:43:11 PM
Order Date (America/New_York) Feb 11, 2008 11:43:11 PM

Note that since I'm in Eastern Standard Time, the Order Date shown is correct. However, the Order Date (America/New_York) is totally off by 10 months, only the time is right.

I found the adminhtml file here:
appdesignadminhtmldefaultdefaulttemplatesalesorderviewinfo.phtml (line 30, 54-59)
$orderStoreDate is the affected variable, maybe there's a bug in the function: getCreatedAtDate(), which is called to get the date based on time zone.

I assume this is the getCreatedAtDate() located here:
appcodecoreMageSalesModelOrder.php (line 1268)

I compared 1.1.6 and 1.1.8 code and it seems this new order date by time zone is introduced after 1.1.6.

Is this a bug? Or something that can be fixed with a configuration or setting change?

Thanks!

---

]]> #1 / Comment by kathys

I am experiencing the same problem after upgrading to 1.1.8.]]> #2 / Comment by batman

This appears to be a new "feature" in 1.1.8. It does not occur in 1.1.7.

Here is what one of my orders looks like:

Order Date Dec 2, 2008 8:06:13 PM
Order Date (America/Mexico_City) Mar 11, 2008 8:06:13 PM]]> #3 / Comment by xrussx

Yup, I have the same issue. Two dates, second date doesn't correspond with anything within the order.]]> #4 / Comment by mikefifield

I have the same issue.]]> #5 / Comment by joyously

It looks like it's reversing the month and day, plus or minus one.]]> #6 / Comment by Thoths Tablet

This issue DOES happen in 1.1.7.

I read that someone noticed that it didn't begin to happen to their orders until after January 1 - my own order history also supports this theory.]]> #7 / Comment by Killoff

Hi all responders.

Those who have problems with timezone dates output, please run script below from you web-root directory.
Will glad to see your results due to the fact that we cannot reproduce this issue.

<?php
require_once 'app/Mage.php';
Mage::app();

$_testDatetime = '2008-12-02 04:43:11'; // capple_'s example

// 0, 2, etc. - store view Ids you want to test, you can use string codes as well
echo Mage::app()->getLocale()->storeDate(0, strtotime($_testDatetime), true).'</br>';
echo Mage::app()->getLocale()->storeDate(2, strtotime($_testDatetime), true).'</br>';
?>]]> #8 / Comment by Thoths Tablet

Killoff,

I ran the script and my results for storeviews 0 and 1 are:

Dec 1, 2008 11:43:11 PM
Dec 1, 2008 11:43:11 PM

I'm not sure what to make of that - but perhaps you do.

More information: No orders placed on or after the 12th of January have shown the extra order date. My earlier orders from the beginning of 2009 through Jan 11 still have them though.

Thanks for helping out here!]]> #9 / Comment by Thoths Tablet

Killoff,

I tried a couple of order dates from my own orders, and I get the same -5 hour time difference. I'm guessing that this might be tied to my timezone (GMT -5). This display difference doesn't seem to have any relationship to the pattern we've seen though:

It seems that in the second (fake) date, the Month that is shown gets its value from the Day of the actual order date (the order date in the database - not your Timezone corrected display date!!). Hope this is helpful.]]> #10 / Comment by Magento Team

Hello capple_,

This issue was fixed. The changes will be available in the next bugfix release.

Thank you.]]>