Skip to content
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

Closed
maddisondesigns opened this issue Nov 30, 2017 · 17 comments
Closed

ACF (Pro) fields dont save #3730

maddisondesigns opened this issue Nov 30, 2017 · 17 comments
Labels
[Type] Bug An existing feature does not function as intended [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.

Comments

@maddisondesigns
Copy link

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)

  1. Create ACF fields and display them on a Page (I have numerous fields, diaplying but I only added content into one simple text field
  2. Click Update and Update

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

@youknowriad
Copy link
Contributor

This is a duplicate of #3277 AFAIK and #3616 should fix it for most fields.

@maddisondesigns
Copy link
Author

@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
ACF Pro Version 5.6.7

@youknowriad
Copy link
Contributor

@maddisondesigns Good catch, actually it's working but only on "saved" post but not "new" posts.

@amandablum
Copy link

A few more notes:

  1. custom fields used in any other part of WP than posts/pages/CPTs work fine (options pags, menu items, etc).
  2. In my case, ACF is only saving the original values the first time you save the page. You can't edit any of the fields later.
  3. Regardless of where you are where you save the initial values (classic edit or edit) if you then open the page in gutenberg, all values are lost.

@danielbachhuber danielbachhuber added [Type] Bug An existing feature does not function as intended [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes. labels Jan 23, 2018
@dmje
Copy link

dmje commented Jan 30, 2018

Same issue for me, latest version of Gutenberg (2.1.0) and ACF Pro (5.6.7)

@tomatillodesign
Copy link

Same issue here, same latest versions.

@gubbigubbi
Copy link

gubbigubbi commented Feb 27, 2018

Just letting you all know that ACF just released an update which should fix issues with the fields not saving:
https://www.advancedcustomfields.com/blog/acf-pro-5-6-9-update/

@maddisondesigns
Copy link
Author

maddisondesigns commented Feb 27, 2018

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.

@pento
Copy link
Member

pento commented Feb 27, 2018

Awesome, thanks for the continued testing and feedback!

@pento pento closed this as completed Feb 27, 2018
@Shulidomains
Copy link

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.

@audetcameron
Copy link

audetcameron commented Dec 20, 2018

this is happening again....
Wordpress Version 5.0.2 ACF Pro Version 5.7.9
image

UPDATE: using 5.8.0-beta3 fixed the issue

@strarsis
Copy link
Contributor

strarsis commented Feb 3, 2019

I have the same issue with latest ACF PRO (5.7.10) and Gutenberg plugin (4.9.0),
also with the warning message as above.

@audetcameron: Thank you for the hint! It saves correctly with the 5.8.0-beta3.

@guytzhak
Copy link

guytzhak commented May 7, 2020

I have the same issue with ACF PRO (5.8.9) and can't solved this

@leo277
Copy link

leo277 commented Jun 5, 2020

Hi, I have updated ACF Pro to 5.8.11, and the checkbox field value is gone. Nor can I update the checkbox.
My checkbox is in a repeater. but other repeater fields works fine.
Is the database corrupted or something?

@leo277
Copy link

leo277 commented Jun 5, 2020

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

@aircrescio
Copy link

Same issue with Avada Wordpress Theme. When i try to Update my post, ACF fields not saving value.

@bilalmalkoc
Copy link

Same issue on 5.9.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug An existing feature does not function as intended [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.
Projects
None yet
Development

No branches or pull requests