I just encountered this with a client, and though the Screen Options was my first thought, I’d not run into this before since switching to Gutenberg. Screen Options were so easily accessible in Classic, now they’re fully buried. For anyone searching, they’re located here: Top Righthand Hidden Menu (three vertical dots) -> Preferences (at the very bottom of the menu) -> Panels tab (lefthand tab in the popup) -> “Additional” section.
…and… on further research (why do I always make progress immediately after I post?)…
I found that the hide-if-js is related to WordPress core’s Screen Options, and when I clicked on screen options, sure enough, the field group was an option there, and unchecked. Checking it revealed the fields.
So my only question now is: Why did those fields change to being hidden after the update? They were set to display prior to the update.
I just discovered one more thing immediately after I posted. It’s not that the the fields aren’t loading — they are — they’re there in the DOM. But the ACF field container is being assigned a hide-if-js class that styles them with display:none;.
e.g. the containing element looks like this:
<div id="acf-group_[xxx]" class="postbox hide-if-js acf-postbox seamless">
Why?
Still a problem as of October 2021. Still no solution?
This still appears to be an issue nearly two years later.
Everything was fine — except I had a missing ‘p’ in ‘supports’. 🙄
I’m finally delving into Gutenberg, and this is a major issue for me as well. As there is no “Gutenberg-style” WYSIWG-type option, it means that if you need to add a WYSIWIG field, you have to repeat all custom theme style programming for compatibility with both Gutenberg and TinyMCE — more than twice the code (since TinyMCE requires more). Are there any solutions in the works for this yet?
Yep, here too. I would be nice to have this resolved.
I’ve had this issue randomly at multiple times throughout multiple sites (just happened again — why I’m here), and it doesn’t seem to have anything to do with conflicting plugins or queries. I have always been able to resolve it by switching the output option to “ID”, publishing, then switching it back to “Array” and publishing again. In my case, these were fresh fields, and not saved as another field type prior to being an image field.
Just adding another “me too!” to needing this feature.
Thanks, @alancolyer for posting your workaround. I’ll be taking a look at that next…
– – – – – –
ETA for anyone else using @alancolyer’s workaround:
The example in the link provided which used:
$(document).live('acf/setup_fields', function(e, div){
as a trigger no longer works for me. It simply would not fire (I am on ACF Pro, if that makes a difference—I couldn’t find documentation regarding this change).
After doing some digging, I used:
acf.do_action('ready', function(e, div) {
…which worked.
Hope that helps.
Just a vote in support for adding this feature. It would really help out. Thanks for your responsiveness, Eliot! Every new update I install always has new features or fixes that were on my wishlist!
