Open aerni opened 3 years ago
Yeah, not much we can do about it now.
That's the whole point of https://github.com/statamic/ideas/issues/551
Sorry, I don't think I follow. In the opening comment of the idea you're saying the date would be localized. How is this not a bug?
This is the entry listing:
This is the entry fieldtype:
@jasonvarga I stumbled upon this in a new project again. Only to find my own issue here, lol. Maybe I misunderstood you. Are you saying this can't be fixed until statamic/ideas#551 is implemented? Or that you don't think that this is a bug?
To clarify the issue again. The date in the entry listing doesn't take the date setting into account.
Yeah, can't/won't. Probably a fair amount of effort involved in fixing this, equal to addressing that issue completely.
Ok, thanks for clarifying. Should this issue be opened again to keep track of it? As it is a bug that should be addressed at some point?
Bug Description
The date is not localized in the entry listing. It displays
18. May 2021 13:17
. It should be18. Mai 2021 13:17
instead. The date is localized correctly in the fieldtype itself.How to Reproduce
Set
'date_format' => 'j. F Y'
in thecp.php
configCreate a user and add a locale setting:
Extra Detail
Environment
Statamic 3.1.18 Pro Laravel 8.44.0 PHP 7.4.16 aerni/social-links 2.2.0 jonassiewertsen/statamic-livewire 2.5.0 visuellverstehen/statamic-classify 2.1.1