Just wanted to follow-up with the rest of everyone here that is_preview content shows on the front-end in WordPress 5.5, I have as well submitted a bug report.
Hi John,
Thanks for reaching out and providing me some very useful information. This does work for radio button fields, I suspect it would also work for dropdowns and perhaps checkboxes. It does not work for the button group option even though its technically a radio button. I’m guessing the styling or jquery for the button group does not follow the acf disabled protocol at all or correctly.
I’m just going to switch to radio button. I only managed to get it to work by passing all the values as true in the disabled array. Just marketing a radio button field as disabled = 1 or disabled = true does not visually disable the whole field. Programmatically it seems the field object returns values as though it is disabled, but it doesn’t translate visually.
However, for radio button fields this code you’ve provided does work if you add all the values to it, essentially disabling all options.
Thank You
I was just reviewing information presented here: https://craigsimpson.scot/performance-considerations-working-with-acf
We have caching at the server level enabled, but we haven’t been able to use any WordPress level caching, it also interferes with some functionality or another. The site is a larger member-based system with a lot of dynamic features.
There are a lot of plugins which add to load but I can’t control them, so I’m trying to do everything I can to improve performance and code that I’ve built.
I’m quite happy to pay for someone to provide me a good practice to follow through. I’ve been testing looking at saving multiple fields into a single field and compare performance but I thought I’d reach out here to get some suggestions I might not think of or consider from my experienced developers.
