Will this issue be resolved with the much-anticipated official 5.8 release?
Any official word on this from ACF?
I love ACF, it’s my favorite plug-in, and our website relies on it heavily. I don’t like the idea of using a plug-in to allow another plug-in to work. Like many, I try to avoid using plug-ins if I can figure out how to code it. So this fix is not ideal, but if we get too far down the line here with WP versions, I might just take that route.
It sounds like they’re working things out, though. I’m excited to get everything back up to current versions ASAP.
I rolled back to 4.9.8 and 5.7.9 and all appears to be well, can save and fun things like that. I will wait (an unspecified period) to update until ACF gives thumbs up to Gutenberg/5.x.
I don’t want to get too far behind WP core updates, so hopefully there’s a fix soon.
I should have read the fine print, I just assumed such a high-profile plug would be updated and work; my bad. I’ve lost several hours figuring this out.
It’s pretty concerning, this. ACF knew Gutenberg was coming and would ideally have had updates queued up when it released. Instead, it’s been a month+ of incompatibility post-Gutenberg release with no updates. Is this, in fact, a really big issue? Will it be updated and work soon? Will ACF remain viable?
Checking with my host to see about reverting back.
Beta3 did not fix things for me. It actually seems worse as now ACF content is disappearing when I go into a Page’s edit screen before I either edit or try to save anything. As a bonus, it will then allow me to save without the error thinking everything is okay, but it is, in fact, not actually saving.
Any ACF official response on this issue?
Same issue. Troubleshooting included barebones theme running only ACF. Running ACF 5.7.9 + WP 5.0.2.
I’ve only tried this in Pages vs. Posts. Other items on Pages save fine, issue appears to be ACF-specific.
