@acf-support is there any response? 😉
I’ve figured out the following. If I copied the field group and test the export again, all fields are included in the JSON file. After this I have to reconnect this field group with other field groups by including it as clone field. After this I test it again to export the field group and the error occurs. The JSOn file is missing the all the fields. I think this is a bug.
I get headache when I think of the new gutenberg editor. I have installed the pre version and can see, there is no space for ACF field groups like the currently wordpress post or page admin layout. I don’t know why wordpress leave the good old tinymce editor.
@hube2
Thank you, but I need a solution without any changes in the database or in the templates. I won’t change any IDs or something. It must be compatible with the old field ids. So I have used the “Message Field” and I have modified it to have field like an separator / sub headline. 😉
@acf-support
I think a separator field with an easy headline is a good feature for the next ACF version 🙂
I think I misunderstood the meaning of the group fields. I thought they were designed for the structure of the backend content only.
For example, if I using a tab field to group some of the field I don’t need any changes for the including fields and the IDs.
I think this isn’t a nice idea. 🙁 It’s very complicated for all developers, which using older ACF Version without grouping fields. I need a grouping layout possibility to structure the fields for the backend. Therefore I don’t need new group field names and changes of the database or template.
@acf-support @hube2 I’ve created a new ticket for this critical bug.
@acf-support @hube2 Without a solution, I can’t update my themes for my user. This is very very important to fix this issue. All field content or values inside a new group field will be displayed as a empty field at the backend 🙁
I’m using ACF PRO 5.6.1 with WP 4.8.1
I have figured out, that the field settings are saved and all is fine at the frontend. But at the backend, the fields show an empty value. For example, the image field is empty or a saved radio button selecting is set to default after grouping the existing fields. This is confusing for the user.
@elliot @cloud9 @ttws @contex @drumba
hey, is there any update or a solution to fix this issue? I have the same issue like all other user of this thread. I know I can use the “Seamless Mode”, but this have not the “Conditional Logic”. But I need the Conditional Logic, to show the clone field not for each user selection. If I’m working with the “Group Mode”, the fields from the clone will not saved. I’m working with an clone repeater field inside a repeater.
I hope for an solution to fix this issue 🙂
EDIT: the only workaround for me is to change the field from “Group” to “Seamless” and add a “Tab” field before this clone field. After this I can use the “Conditional Logic” for the Tab field and his children fields.
I have issues, while saving a page with many fields (at the backend). It sometimes takes up to 16 seconds or more, until the page is saved.
I tested something and find out, if I deactivate the WordPress revisions, the issue is gone.
define('WP_POST_REVISIONS', false );
Apparently the matching of the many fields takes very long time.
@hube2 Thank’s for testing. I have added a new ticket.
@hube2 I have tested this on an other WordPress installation and I get the same issue after updating from 5.5.5. to 5.5.7. There is really a bug of the layout. What can we do?
I can get you a json file of this field group and you can import this and test it on your installation?
@hube2 oh so sorry, I’m confused. I meant the 5.5.7. version.
Can you confirm with this issue at the version 5.5.7. ?
@acf-support can you confirm with this?
@acf-support oh, thanks! That’s it 🙂
@sododesign thanks, it works 🙂
ok, after removing return $value; the repeater fields will saved after clicking the update button.
@sododesign I tested your function and I found an error.
if ( ! function_exists( 'acf_wp_kses_post' ) ) :
function acf_wp_kses_post($data, $post_id=0, $field=array()) {
if (isset($field['type']) && ($field['type'] == 'repeater' || $field['type'] == 'flexible_content')) {
// no need to run it on repeaters
// will be called again for each subfield
return $value;
}
if (!is_array($data)) {
return wp_kses_post($data);
}
$return = array();
if (count($data)) {
foreach ($data as $index => $value) {
$return[$index] = acf_wp_kses_post($value);
}
}
return $return;
}
endif;
add_filter('acf/update_value', 'acf_wp_kses_post', 10, 3);
I use repeater fields at option pages. If I use this function, after clicking the update button, all values are lost and not saved.
What is the reason for this issue?
@acf-support Oh yes, that’s it. Thank you 🙂
@acf-support Is this a plugin bug?
