Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set date format to dd/mm/YYYY not working in product details #8849

Closed
jgodart opened this issue Mar 10, 2017 · 5 comments
Closed

Set date format to dd/mm/YYYY not working in product details #8849

jgodart opened this issue Mar 10, 2017 · 5 comments
Labels
Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release triage wanted

Comments

@jgodart
Copy link

jgodart commented Mar 10, 2017

Preconditions

  1. Magento 2.1.3

Steps to reproduce

  1. Define date format to dd/mm/yyyy in Stores/Configuration/Catalog/Date
    capture d ecran 2017-03-10 a 17 25 00
  2. Try to create a new product with New product date

Expected result*

  • Exemple with attribute : "news_from_date"
  1. Normal that show you a date with this format :
    capture d ecran 2017-03-10 a 17 32 48

Actual result*

  • Exemple with attribute : "news_from_date"
  1. capture d ecran 2017-03-10 a 17 31 17

Details

This blocking point is all the more strange because in the details of the attribute "news_from_date", the date that you can assign by default appears correctly, with the format dd / mm / yyyy but not correctly on the details of the product.

@korostii
Copy link
Contributor

By any chance, did you save this setting at or Website or Store level? If so, I would try setting it at the global(Default) level (store-specific settings are usually effective in the storefront only and not in admin)

It is also a bit funny that there isn't a similar setting to use for the frontend: the actual format used for showing review dates, order dates etc. to the customer is just randomly hardcoded as either \IntlDateFormatter::LONG or \IntlDateFormatter::SHORT.

@magento-engcom-team magento-engcom-team added G1 Passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed and removed G1 Passed labels Sep 5, 2017
@magento-engcom-team magento-engcom-team added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Oct 4, 2017
@magento-engcom-team
Copy link
Contributor

@jgodart, thank you for your report.
We've created internal ticket(s) MAGETWO-80799 to track progress on the issue.

@rohit-wagento
Copy link

I am working on this at #dmcdindia

@magento-engcom-team
Copy link
Contributor

Hi @jgodart

This ticket has been marked as "Triage Wanted" due to low user involvement over time. Over the next 2 weeks we are looking for additional community feedback to decide if it should be archived or not. More information on this is available on the GitHub wiki.

Thank you for collaboration.

@magento-engcom-team
Copy link
Contributor

@jgodart, thank you for your report.

Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.

You may learn more about this initiative following this link.

Please feel free to comment or reopen the ticket if you think it should be reviewed once more. Thank you for collaboration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release triage wanted
Projects
None yet
Development

No branches or pull requests

5 participants