I solved this with acf/render_field_settings/type=wysiwyg and acf/render_field/type=wysiwyg, like this: https://gist.github.com/stianandreassen/6dc87c88c43b2bc43d0ea1a94bd5cd1e
With this I get a number
field on each WYSIWYG where I can define the desired height for the Editor.
It might be of value in the future, when/if I need this filter on a future project. Now I can’t even remember which site(s) I needed it for – it’s probably 25 projects ago.
16 months is long, yes. Things happen fast. For a website, it’s almost a lifetime.
Is it simply that it’s the post_ID that gets passed to the filter, and not the post object? And it only took 16 months …
Hi @Elliot,
After more testing, I think this bug is a «false positive». It seems the problem was due to files being added to the translated post before WPML Media was activated. As a result, the Media modal tries to get the data for the file in the original langauge, which it doesn’t have access to after WPML Media is installed. I created a new translation, and the problem wasn’t replicated.
This particular project is huge, and I have editors adding content while I’m developing, thus the blooper. Cancel red alert.
@elliot Is this a bug?
I’ve tried it exactly like that – doesn’t work.
No go on my end. ACF Pro 5.0.7.
Have tried this, it does not work. The filter only accepts 0 (i.e. returns only top-level pages). It does not take an ID.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.