When getting time data via dynamic data from ACF, the shortcode filter does not manipulate the time formatting.
In this case, :H:i:s does nothing to the output. I tried switching the output in ACF and then using g:i a but that didn’t do anything, either.
Thanks so much for your report!
There is no filter to influence the output of the ACF time field. You can set the return value in the ACF field settings. In my case, the set format is returned, even if I change it afterward.
This isn’t sufficient.
Time output isn’t just needed on the front end, it’s needed for accessibility and semantic HTML.
<time> element needs
datetime= attribute. The value of this attribute must be in a machine-readable format. Of course, we never want to use machine-readable format on the front-end. So, we absolutely need control over the output.
I absolutely agree with @digitalgravy. This is especially confusing for users, since all native date fields support the formatting out of the box. I think from the end user perspective, it is expected to have this consistent with all date fields.
Also, i do have the case where I want to display different formats of the same date field throughout my site.
Thanks for the explanation. Nevertheless, this is not a bug but a feature request.
I have discussed the issue with the team. We will extend the ACF time picker logic in one of the upcoming versions.
Please don’t restrict any improvements just to ACF … there are other tools we use ( well I do ).
Don’t worry @alanj , that’s what I already mentioned when I created the task
I use ACPT although that is sadly borked since 1.9.2
We’ve implemented this request for ACF, Pods and JetEngine in Bricks 1.9.3, now available as a one-click update in your WordPress Dashboard.
Changelog: Changelog – Bricks
Please let us know if you are still experiencing issues.