
ACf does not automatically delete images from the media library when they they are removed from images fields.
I have no idea how you would do this with the plugin you are using.
Just looking at ACF what you would do is create an acf/save_post action with a priority <10. In the action you use get_field() to get the current value of the field. The new value of the field will be in $_POST[‘acf’][$field_key]. The you would compare these 2 values. If the post ID for the old image is not present in new submission then you would use WP function to delete the attachment from media.

Yes, you need to use acf/save_post instead of WP hooks.
When using this hook you need to use WP functions to get the other information since it only passes the post ID and not the post data.
There are many topics on this forum about updating the post title from an ACF value.

You need to use the acf/save_post hook instead of the WP save_post hook. The WP hook fires before ACF has saved the new values to the fields.

You will have to contact the developers of your import plugin. Most of the big import plugins include premium add ons for ACF. Either that or there are filters and actions that can be used it extend them.

The value stored in a select field does not include the label. The values stored in the DB is a single text value if the select field only allows a single value. An array of text values are stored in multiple values can be selected.
The values are just the values.
There is no way to retrieve the values without using ACF.
See get_field_object() to get the labels.

I’m not sure you can import serialized data.
But if you can, ACF stores a serialized array of string values representing the IDs.
Your first array
array(0 => "651", 1 => "649")
would be serialized by ACF as
a:2:{i:0;s:3:"651";i:1;s:3:"649";}

what type of field is the sub field “color”?

There will be no change in performance between get_field() and the_field()

yes, a copy will only go into the child theme folder if it is edited.
the other thing you are seeing has to do with the order that the field groups are added when the load point is added.
If the load point for the parent is added in a way that causes them to be loaded first then this field group will override the version in the child theme. You can sync them and save them but this will ultimately not have any effect. Any changes to the field group in the child theme will only be visible when editing the group and have no affect on the field group when editing content.
The condition I described happens when the parent theme json files are loaded after the child theme json files. This is what will normally happen.
The difference is cause by where in the array of load points the parent theme load point is added.

After looking into this, the best I can come up with is to add an acf/save_post action.
In this action you get a list of the images for the gallery
// this will get unformatted value of gallery
// an array of attachment post IDs
// see https://www.advancedcustomfields.com/resources/get_field/
$gallery = get_field('gallery_field_name', $post_id, false);
Then loop over this list of ID, get the attachment post using get_post(), change the “post_parent” value and then use wp_update_post() to save the changes.
Notes: An attachment can only go “attached” to a single post
You must remove your action, inside of the action, before calling wp_update_post(). If you don’t then you create an infinite loop because acf/save_post is triggered by calling that function.
add_action('acf/save_post', 'your_function_name');
function your_function_name($post_id) {
remove_filter(('acf/save_post', 'your_function_name');
}

the feature you are referring to is part of the ACF Extended plugin. You should to talk to the developers of that plugin.

json files in the parent theme, if they are included by adding a json load point do not need t be synced into the database to work. If you don’t want these field groups to be synced then they should not be synced.
Once a field group is synced from the parent theme a copy of that group is saved in that acf-json folder in the child theme if it exists. Once this happens the field group is forever disconnected from the parent theme.
The “private” setting in the json file should be added to prevent syncing of the parent theme groups you do not want to allow editing of. This is explained on this page https://www.advancedcustomfields.com/resources/synchronized-json/
If they have already been synced they will need to be deleted from the database for the child theme site.

Log into your account, go to Licenses, next to the license there is a ling to manage activation, this will list all sites it is used on.

That is what you were looking for.
There is a folder in your theme .../block/content_rows/
In this folder there is a php file for each of your layouts
{$layout_name}.php
To add a layout you need to create a new php file in that folder with a name that matches your new layout name. Then you need to add code to that new file that will be used to display the content of your layout.

Because the options are saved as options and the fields on the page are saved in post meta for that page.
If you want the options to be eitiable on both the page and the options page then you can set the “post_id” argument when creating the options page to the post ID of the page. This will cause all options saved on that options page to be saved to the post_meta for that post ID instead of in options. Changing the post ID for options page after the options are save will cause ACF to ignore that previously saved values.
Usually, when you create an options page it is because you want to edit the values separability from a page.
A field groups field values are unique to the place where they are edited… a page, a post, a user, an options page.

Does the text contain anything like ampersands, single or double quotes, less then or greater than, anything else the might be converted to html entities by wp_kses?
If this it the case it could be a false positive and you should probably contact support so that they can look into it and correct.

You are going to have to look/search the forum. ACF form is not designed to load via AJAX. There have been people that have tried this in the past. I seem to remember that there may have been a solutions.

Uploads cannot be attached to a user. Uploads are attached to posts by using the post_parent value of the post. This does not exist for users.

Have you added acf_form_head() correctly?

Yes, you just need to change the_field() to echo get_field() and the_sub_field() to echo get_sub_field() I was told by the developers that it will not affect get_field() or get_sub_field().

It looks like you have nested repeater fields. You need to use nested have_rows() Loops, or you need to access the nested value in the array from your get_sub_field() call.
$rows[0]['level_one_links'][0]['menu_items'][0]['link_to']

There is a Min/Max setting for each layout, you may have missed it. This is to set minimum and maximum number of times the layout can be used.

You will have to manually delete the CPTs from the other plugin and then recreate them in ACF. You’ll probably want to back up you site before you do this.
I’m not a fan myself of retroactively changing a site. If the site is working I would leave it the way it is unless there was some overriding reason that it needed to be changed.

Somewhere in your theme’s PHP code there is a loop, see this page https://www.advancedcustomfields.com/resources/flexible-content/
In that loop the code is doing something based on the name of the layout. You will have to add new code for your new layout and how you add this code will depend on how the previous developer coded the theme.

You will need to figure out what the error is. While the error might happen when you activate ACF it may not be ACF that is causing the error and could be something else.
It’s been a while since this plugin was updated but it may still work. https://github.com/DavidWells/debug-plugin-activation-errors
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.