Background of the issue:
I am trying to use an ACF date field in dynamic data in a Bricks template. The template uses the Bricks dynamic data syntax of {acf_huxx_project_end_date:Y}. On the original language (English), this correctly outputs '2025' as the year only.
Symptoms:
On the translated page (Spanish), it outputs the full date and doesn't respect the 'Y' format being passed.
Questions:
Why does the ACF date field not respect the 'Y' format on the translated page?
How can I ensure the date format is consistent across languages?
Hi There!
Thanks for contacting WPML Support. Sorry for the delay in responding due to the holiday.
Before this thread gets assigned to my colleague, I'd like to offer some initial guidance or potential solutions.
I understand the issue you're facing. Since you've used attributes with Dynamic Data, we are aware of a known issue with the Bricks theme where custom attributes do not appear on the frontend after translation. Please refer to the Errata below for more details.
Since the attribute is not being added during translation, the only workaround I can suggest at the moment is to open the translated version in the Bricks Builder and manually add the attribute, which is your case, the Year(Y).
I hope you can understand. feel free to let us know if you have any other questions or need further assistance, we'll be happy to help!
Wishing you a Merry Christmas and a joyful holiday season! 🎄✨
Best regards,
Prosenjit
The topic ‘[Closed] ACF dynamic date field in Bricks not respecting formatting on translated template’ is closed to new replies.
