You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a potential bug for updating orders from control panel for Craft Commerce.
The dateOrdered for completed orders or paid orders will increase 23hours by itself after clicking "Update Order" button if I don't change "Date Ordered" input.
It works fine if I change the ordered date or time.
I tested on Chrome and Firefox, and same problem occur.
Steps to reproduce
Click on one order;
Click on "Edit" button;
Click on "Update Order" button without any changes.
Additional info
Craft version: 3.4.1 Commerce: 3.0.3
PHP version: 7.2.18 (WAMP server)
Database driver & version: MySQL 5.7.26
Plugins & versions:
Amazon S3 1.2.7
Contact Form 2.26
Contact Form Extensions 1.2.0
Craft Commerce 3.0.3
Field Manager 2.1.1
Freeform 3.6.1
Redactor 2.5.0
Stripe for Craft Commerce 2.2.3
Super Table 2.4.1
The text was updated successfully, but these errors were encountered:
Thanks for reporting this. We have pushed up a fix.
It will be included in the next release, if you would like to get the update early you can do that by updating your Commerce requirement in your composer.json
"require": {
"craftcms/commerce": "dev-develop#2450608ac46aa1bc242ef1bf222c89a19b84c8aa as 3.0.3",
"...": "..."
}
Description
There is a potential bug for updating orders from control panel for Craft Commerce.
The dateOrdered for completed orders or paid orders will increase 23hours by itself after clicking "Update Order" button if I don't change "Date Ordered" input.
It works fine if I change the ordered date or time.
I tested on Chrome and Firefox, and same problem occur.
Steps to reproduce
Additional info
Amazon S3 1.2.7
Contact Form 2.26
Contact Form Extensions 1.2.0
Craft Commerce 3.0.3
Field Manager 2.1.1
Freeform 3.6.1
Redactor 2.5.0
Stripe for Craft Commerce 2.2.3
Super Table 2.4.1
The text was updated successfully, but these errors were encountered: