-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACF (Pro) fields dont save #3730
Comments
@youknowriad Can you please re-open this as custom field content still isn't saving. I just tried adding content into a simple text field and it didn't save, as per my original issue above. Gutenberg Version 1.8.1 |
@maddisondesigns Good catch, actually it's working but only on "saved" post but not "new" posts. |
A few more notes:
|
Same issue for me, latest version of Gutenberg (2.1.0) and ACF Pro (5.6.7) |
Same issue here, same latest versions. |
Just letting you all know that ACF just released an update which should fix issues with the fields not saving: |
Have just tried out the 5.6.9 ACF Pro update and my sample fields are saving now too. Haven't tried every ACF field but my sample text field and repeater fields seem to be saving ok. |
Awesome, thanks for the continued testing and feedback! |
I was running into a similar issue when using ACF Pro along with SiteOrigin Page Builder. After a lot of testing and troubleshooting, I figured out the problem: Inside the PageBuilder settings, there is a checkbox for "Field Groups" under Post Types (where the page builder should appear/be active) and there is a checkbox for "Default To Page Builder Interface". If both are checked, the problem exists. If only one is checked, there doesn't seem to be an issue. This may not be a solution for everyone, as not everyone uses SiteOrigin or page builders for that matter. Most page builders do offer similar settings, so it's something to look out for when troubleshooting. Hope this was able to help someone. |
I have the same issue with latest ACF PRO (5.7.10) and Gutenberg plugin (4.9.0), @audetcameron: Thank you for the hint! It saves correctly with the 5.8.0-beta3. |
I have the same issue with ACF PRO (5.8.9) and can't solved this |
Hi, I have updated ACF Pro to 5.8.11, and the checkbox field value is gone. Nor can I update the checkbox. |
I have checked, all the checkboxes values are gone. Something must be different for checkboxes. I have tried 5.8.0-beta3, still not saving |
Same issue with Avada Wordpress Theme. When i try to Update my post, ACF fields not saving value. |
Same issue on 5.9.3 |
Issue Overview
I have some test ACF Pro fields that display at the bottom of a Page. When I added content into one of the fields, a simple text field, and then clicked Update, it didn't save.
I'm raising this because #952 was just recently closed and it was stated that Custom Fields were "Feature Complete". I can't see how they can be called "Feature Complete" when they still don't save your content.
Steps to Reproduce (for bugs)
Expected Behavior
Custom Fields should save
Current Behavior
Custom Fields don't save
You can download the json files for the fields that I have, from here. I had two sample Field Groups set up...
https://www.dropbox.com/s/npdoeqahfqq0ps3/group_58e48c86cc51e.json?dl=0
https://www.dropbox.com/s/tb9sayjy2c34wv8/group_5911300e9f97c.json?dl=0
Firefox Quantum 57.0
Gutenberg Version 1.8.0
macOS Sierra 10.12.1
The text was updated successfully, but these errors were encountered: