-
Notifications
You must be signed in to change notification settings - Fork 191
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
Payment date details #687
Comments
Hey @Rahe I was just thinking about how we need to standardize the date format throughout the plugin. What the best was to do that for all the various date formats is that we use the WordPress default date setting found under WP-Admin > Settings > General: |
Hi @DevinWalker, this was my first idea too, but this setting is for dispalying a date on the frontend and it's not really usefull to have a "Wednesdays, 2 april" displayed at this place, this is most usefull to have a "normal" date format at this place but i18n. I think a setting into the plugin like a "display date format" not bound to the save format. I have seen the date used is the WordPress post_date field, so this is easy to format it into an another format. Rahe |
@DevinWalker, date formats is a known issue. Only the US and it's uses the mm/dd/yy format. Most of the world (including Europe) uses dd/mm/yy. For more info see this link: https://en.wikipedia.org/wiki/Date_format_by_country Last year WordPress core changed the way they handle dates in the admin. In the past core used the Now, each language can use https://translate.wordpress.org/ to set it's preferred date format. Much simpler solution. I guess adding a filter will be a good idea. |
How about a function like The confusing thing though is the various date formats found throughout Woo. For example, here is the frontend checkout page which respects my date option in WP-admin: And here in wp-admin on Woo's transaction edit screen and on the reports page the date is Where it appears hardcoded as this format: What went into this decision by the Woo team and should we follow suit? I'm guessing that the |
@ravinderk please paste your |
@DevinWalker Here is function which I proposed.
|
Thanks @ravinderk |
* release/1.7: (177 commits) Added change log for #964 Make exception message translatable Update give_do_automatic_upgrades function Move upgades to 1.7 Update function version from 1.6 to 1.7 add missing `echo` after 9a2f35d Set gulp textdomain task autocorretion to true Update more action names #957 Update actions to use newly termed ones rather than now deprecated ones #957 Version bump for release/1.7 branch Change log added for #687 Readme logs added for #896 and #773 replace `edd` text-domain with `give` replace esc_attr_e() with esc_attr() add misisng text-domain gulp task Update doc block in formatting.php Refresh current month transient when payment update Add function to get stat transient key Update description in Give Settings Screen ...
Hello,
In the payment admin page there is a metabox for the payment metadate like the date, the status and such.
But the date displayed is at the format m/d/Y wich in french can be very disturbing because '06/30/2016' is not a valid date in France, for us this will be '30/06/2016'.
Can you consider using https://jqueryui.com/datepicker/#alt-field with a filter for the displayed date ? So you can keep the mm/dd/YY format and display the user friendly localized date ?
The text was updated successfully, but these errors were encountered: