I can confirm both that the “No Metabox” option does not work for the block editor (WP 6.6.1) and that @fzs’s solution resolves it. Thanks for sharing that!
@colinf While it is only a partial fix, this pull request may get you most of the way there for some of your clients.
I’ll try to get a full fix out soon, but I’m leaning toward a fuller rewrite so that it’s a little less break-prone in the future…
FWIW, you certainly have my complete blessing to make the plugin obsolete 🙂
If your fields are conditionally displayed based on a Page Template, I’ve seen fields disappear. They come back if you change the page template and then change it back (no save/refresh required). That might not be your issue but seems worth checking. Now off to see if I can figure out a fix for it…
Seeing this same issue:
when I deactivate ACF 5 Pro and reactivate ACF 4, and then go back to ACF 5 Pro, I get prompted to upgrade the database again, and each time I perform the upgrade I get another copy of the field groups.
Seems like ACF should be avoiding this duplication somehow or tracking whether the upgrade has already happened. (I’m on the edge of whether ACF should support upgrading, downgrading, making changes, and upgrading again.)
FWIW, I found this thread from http://core.trac.wordpress.org/ticket/25294. Maybe that’s useful. I haven’t seen this problem myself though.
@admin, is there any chance that this can be resolved in future versions of ACF or is this something I should bother pleasantly request WP-Engine look into.
Turning off caching is doable while in development, but I’d like to avoid it when the site is in production.
This was resolved in version 3.0.2 of The Events Calendar.
Yup, I’m with @shauny. This always felt like a TEC problem and it seems to be more and more clear that it is. However, let’s not quite resolve this thread yet until we’ve got a resolution. Just in case… 🙂
Running a var_dump on the $value before and after the foreach loop in update_value shows that the value is the same before and after. Trying to save one relationship field with one post selected gives me this: array(1) { [0]=> string(1) "8" }
As I mentioned earlier, the value can be set without The Events Calendar activated and, when activated it hides the values and doesn’t allow updating but also doesn’t delete the values. When you deactivate it again, the values selected before activating are back and visible.
In addition, this also effects the_field()/get_field() which similarly cannot access the value stored in the DB when TEC is activated even though the data is still there.
I’ll dig some more…
Glad you like it, @admin 🙂 It seems like the big initial decision in building something would be whether to house the code or just serve as an index. Theoretically, it could even just be a forum thread, though that could get unwieldy pretty quickly.
Hopefully some others chime in here and throw out other ideas!
I’m not the best but I’m willing to try.
