Obviously not a sure this is a bug, at least I cannot explain the behavior…
I have configured a div element with a query loop. Nested within the div element there is among others a rich text element. Within this rich text element I pick up an acf date element and format it using {acf_start_datum:l j. F}. I expected this formatting to be applied to all elements of the query loop. However, unfortunately it seems to be applied only to the first element and the remaining elements are untouched.
Here you see the result, where the dates in bold are differently formatted for the first element of the query loop than the remaining elements.
Any hint welcome as to which other settings I may need to change in order for the formatting to take effect on all elements of the query loop.
Browser: Chrome 110 OS: macOS / Windows / Linux / etc. URL: Link to a page that illustrates this issue Video: Short screen recording that illustrates this issue (free tool: jam.dev)
[Please describe this bug in as much detail as possible so we can replicate & debug this bug]
After a bunch of experimenting I think I can better describe the problem: the behavior seems to be the same across all elements of the loop. However, there appear to be certain dates for which the formatting works and others for which it doesn’t. Dates in May, June and Juli seem to not work while dates in April and August seem to work.
Finally, after your hint of checking the configuration of the ACF field I changed what I would translate to “Return value of the template function” and aligned it with the code I used for formatting in the code. This fixed the problem.
So overall it seems like for certain dates it picked up the configuration from the ACF field and for others it applied the formatting from the rich text element.
So, for me the problem seems to be fixed for the moment. Feel free to close the bug as you wish.
Thank you for your detailed report! I’m wondering why some months would work and some not. I’m happy that you solved the problem!
Since I was not able to reproduce the bug locally, I will close this topic as a NO BUG, but if this will ever happen again, and we will have a way to reproduce it, please met me know