This worked on 2.2.5
Hi @Cristiano81. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento-engcom-team give me $VERSION instance
where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.
@Cristiano81 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
G1 Passed will be added to the issue automatically. Please, edit issue description if needed, until label G1 Passed appears.[x] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add G2 Passed label to the issue by yourself.
[x] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[x] 4. Verify that the issue is reproducible on 2.3-develop branchDetails
- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
[x] 5. Verify that the issue is reproducible on 2.2-develop branch. Details
- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x
[x] 6. Add label acknowledged once verification is complete.
[x] 7. Make sure that automatic system confirms that report is acknowledged.
Hi @Cristiano81 thank you for you report, i'm not able to reproduce following steps you described.
I'm have saved product.
@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-95124, MAGETWO-95125 were created
yes i can reproduce on vanilla Magento https://i-18157-2-2-6.engcom.dev.magento.com
i have to add some precondition
to reproduce the issue after edit the product to insert the special price, save it again, elsewhere in first instance it works (when special price date from is empty)
i think i have found the reason.
in /vendor/magento/module-catalog/Controller/Adminhtml/Product/Initialization/Helper.php
has been added a new function on line 463
private function convertSpecialFromDateStringToObject($productData)
{
if (isset($productData['special_from_date']) && $productData['special_from_date'] != '') {
$productData['special_from_date'] = new \DateTime($productData['special_from_date']);
}
return $productData;
}
comment the call to that function on line 162
//$productData = $this->convertSpecialFromDateStringToObject($productData);
the product has been saved successfully again
Hi @hiren0241. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:
Component: XXXXX label(s) to the ticket, indicating the components it may be related to.[ ] 2. Verify that the issue is reproducible on 2.3-develop branchDetails
- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
[ ] 3. Verify that the issue is reproducible on 2.2-develop branch. Details
- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x
[ ] 4. If the issue is not relevant or is not reproducible any more, feel free to close it.
Hi @Cristiano81. Thank you for your report.
The issue has been fixed in magento/magento2#18578 by @hiren0241 in 2.3-develop branch
Related commit(s):
The fix will be available with the upcoming 2.3.1 release.
This is a fairly major problem, why the decision to wait until 2.3.1 to rollout any fix?
@Cristiano81 this issue present in 2.3-develop instance with Account locale set to en_GB

Hi @paul-blundell , we expecting 2.3 release very soon, but current fix will be available in 2.3.1 version according to the previous comment.
@sidolov but that fix apparently hasn't resolved the issue anyway. Any idea when this will be resolved?
I created a fix to solve this problem, following the hint of @Cristiano81, follow the link of the repository, just download and put in app/code, and follow the installation standard of the module.
Hi @Cristiano81 , thank you for you report, this issue has already fixed in 2.3-develop branch, and will be available on 2.3.1 release.
Hi @Cristiano81. Thank you for your report.
The issue has been fixed in magento/magento2#21273 by @tufahu in 2.2-develop branch
Related commit(s):
The fix will be available with the upcoming 2.2.9 release.
Most helpful comment
i think i have found the reason.
in /vendor/magento/module-catalog/Controller/Adminhtml/Product/Initialization/Helper.php
has been added a new function on line 463
comment the call to that function on line 162
//$productData = $this->convertSpecialFromDateStringToObject($productData);the product has been saved successfully again