Unable to save any dates if the user interface locale is not english (US) in 2.3.1

[ioweb-gr]

Preconditions (*)

1. Magento 2.3.1
2. A user with interface locale set to Greek

Steps to reproduce (*)

1. Create a product using the user that has interface locale set to Greek.
2. Add any date value, news_from_date, news_to_date, special_price_from_date, special_price_to_date
3. Save the product

Expected result (*)

1. The product is saved correctly with the new date.

Actual result (*)

1. Error that says invalid date Invalid input datetime format of value '22/5/2019'

I've found other references in other issues that are closed saying this problem was fixed but unfortunately I'm on 2.3.1 and the issue persists. There's no real solution or workaround yet for this. Apparently it's not just Greek locale but other locales as well.

The bug has been acknowledged in the past, added to backlog even but years later we still face the same issue from version 2.1 to 2.3.1

Unless Magento is operating in a country where the users speak english natively it's pretty much pointless to use Magento if this is not fixed. I opened a new issue for this because any messages in closed issues get burried and never watched upon.

I'm hoping someone who understands the inner workings of this date format validation will pay attention to this or else the biggest question we'll have to ask any potential customer before choosing a platform will pretty much be: "Are you fluent in English?"

PS: at least if you could provide an official way to workaround this or what to change until it's fixed it would be completely fine so we can at least use the platform.

[m2-assistant]

Hi @ioweb-gr. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@ioweb-gr do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[ioweb-gr]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @ioweb-gr. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @ioweb-gr, here is your Magento instance.
Admin access: https://i-22964-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[ioweb-gr]

Reproduced on demo instance.

[orlangur]

@ioweb-gr it's better to search for closed issues and reopen them to track regressions better.

#9743 seems one of those, is it reproducible again? Is this issue introduced by 2.3.1 and not present in 2.3.0?

[ioweb-gr]

@orlangur For me it was never fixed in the first place. I can't seem to be able to track this issue that made me open a new one now, but it was a closed ticket with a few replies spaning over a year that the issue still persists.

I mean if noone reopened that ticket after a year or so, I kinda gave up on reopening closed issues.
Also I've tried to comment on a newer one #13112 which was for 2.2 version but it seems it was ignored as well for quite some time (from Jan 18).

It seems closed issues and old issues are never paid any attention to. You're right that it helps if it's reopened and worked on again, but it doesn't help if no one sees it.

[orlangur]

It seems closed issues and old issues are never paid any attention to

@ioweb-gr well, it is simply impossible, unless anybody finds such issue and reopens it or if we have a proper end-to-end functional test covering this scenario.

[ioweb-gr]

Only collaborators can reopen issues they closed though so it's out of out hands but one choice would be to mark the duplicates when found and reopen the originals I guess in such cases.

I'm sure you agree that since we can't reopen them, and commenting on the closed is never read, our only option as users is to raise a new issue

[m2-assistant]

Hi @Nazar65. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - 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!

• 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

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[Nazar65]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @Nazar65. Thank you for your request. I'm working on Magento 2.3-develop instance for you