We have a Dutch website. When the user (admin) is logged in, the date display’s correct, in Dutch. But, the visitors who are not logged in, see the date in English. (See also screenshot). This should be in Dutch also.
The Date is displayed by a ACF date field (datepicker)
Unfortunately, there are a lot of ongoing bug fixes and feature implementation at the moment and I don’t have great visibility into the prioritization and timeline. Our lead developer has confirmed the bug and the intended behavior seems clear, so we’ll just have to be patient for this fix to get implemented. Sorry that I can’t provide any more specifics on this! I’m sure you’ll understand that given that it’s a free plugin, we have to be strategic about where/when/how we invest time and money into its development. Development seems to be quite active right now so I can’t imagine it’ll be too much longer.
And furthermore it seems as if acf_time is not working at all. It just renders the date of today in the frontend (in English) instead of the time set in the ACF time picker in the backend. Can’t find a workaround …
The date set in an ACF date picker field can’t be formatted at the moment, as you already said above and in the github thread. Something like this line in the documentation is currently not working:
<Field acf_date=field_name format="l j F Y" locale=fr />
But formatting with the format tag is working:
<Format date="j. F Y" locale=de><Field acf_date="termin_datum" /></Format>
Do you know how long it will take until this will be resolved?
Yeah I noticed that as well and reported it to the dev and that also seems to have been resolved. I’m not sure what the timeline is as far as when the next L&L release will be since I think there are a few additional things being worked on for the next release.
That being said, you can always download the latest version of the template system module directly from Github (direct download link) and install it just like a normal plugin alongside L&L to get these fixes before they’re bundled into an L&L release.
Hi Benjamin, for me acf_time is still not working. It just renders the date of today in the frontend (in English) – instead of the time set in the ACF time picker in the backend. I can force it with format to display as a time instead of the date of today, but it only shows as “0:00”.
Wow, I somehow missed the fact that you were talking about a different field type despite you mentioning it three times. Sorry about that haha!
Can confirm, acf_time seems to display today’s date by default. Sorry for accidentally gaslighting you.
That being said, I just tested this on a fresh WordPress installation and by specifying a format with something like <Field acf_time=time_field format="g:i a" />, I’m successfully able to display the correct time from the field. Obviously this shouldn’t be necessary, but I’m wondering why you’re seeing “0:00”. Are you sure the time field is set on the post you’re referencing?
No problem. Thank you for taking a look into the problem
I have some acf_time fields. They all show the date of today in the frontend. In the backend I have the acf time field (no date & time field, only time) and select the time in the dropdown provided by acf.
Shows only “00:00” (I tested it in multiple posts and different entries).
And with the acf_date time I have the same problem as mentioned above. It is shown correct in the frontend if I add a format. That’s why I thought I could do the same for acf_time but it is not working for me (only “00:00” as I already mentioned)
Ah, this actually seems like the expected output, considering the bug we identified earlier. What’s happening here is that the inner <Field acf_time="uhrzeit" /> part isn’t displaying the correct format, as per the bug. It’s displaying the current date instead of the time, something like “February 22, 2024”. Then your Format tag is trying to convert the value “February 22, 2024” into a time value, which understandably fails and outputs the time “0:00” as one might expect, since there’s no time value to format.
That’s odd. When I test on my end, I have an ACF date field that contains the value “21/02/2024” and when I output it with something like <Field acf_date=date_field format="F j, Y g:i a" /> it displays “February 21, 2024 12:00 am”, as expected.
In any case, as far as I can tell, specifying a format using the attribute seems to work across all field ACF date/time field types on my end, so that would be the workaround until the devs fix the bug and L&L displays the intended format without needing to specify it.