Konrad Chmielewski

Hello,

You most likely have an issue at the location where you set the photo_id = '...' in your acfe_form() function or acfe/load_form hook.

I would recommend to check the PHP code where you set this photo_id, and log the value there to make sure everything is in order.

If the photo_id doesn’t return a proper Post ID (number), then your “Post Action” will not be executed, as no post can be updated. And thus, the acfe/form/submit_post/form=photo-add2 hook won’t be executed.

You can check your Form configuration using Global Form hooks (see documentation).

On form load with acfe/load_form (see documentation):

// log form on load
add_filter('acfe/form/load_form/form=photo-add2', 'my_form_load');
function my_form_load($form){
    
    // log
    acf_log('load_form', $form);
    
    // return normally
    return $form;
    
}

On form submission with acfe/form/submit_form (see documentation):

// log on submit
add_action('acfe/form/submit_form/form=photo-add2', 'my_form_submit');
function my_form_submit($form){
    
    // log
    acf_log('submit_form', $form);
    
}

Both these logs should show you $form['photo_id'] = 45 (any number, is should be a post id). If there is no post id, then check your PHP code where you set it.

Hope it helps!

Regards.

Hello,

Thanks for the feedback and the detailed report!

In fact, the latest 0.9.0.8 version added some changes in order to make the get_row_index() work with the Flexible Content Dynamic Render in the admin preview.

After some extensive checks, it looks like these changes broke the usage of get_row() and get_row_layout() in the admin preview.

If you’re using these functions in Flexible Content hooks you might run into problems. For example if you change the Layout Template Path programmatically with acfe/flexible/render/template (see documentation) and check get_row() or get_row_layout().

Here is a quick fix you can add to your theme’s functions.php file in order to fix this issue globally.

// ACFE 0.9.0.8: Fix get_row() & get_row_layout() usage in Flexible Content preview
add_filter('acfe/flexible/render/template', 'acfe_fix_flexible_content_preview_get_row', 0, 4);
function acfe_fix_flexible_content_preview_get_row($file, $field, $layout, $is_preview){
    
    if($is_preview){
        acf_update_loop('active', 'i', 0);
    }
    
    // return
    return $file;
    
}

Note this will revert the changes of the 0.9.0.8 update, and make get_row_index() always return 1 in the WP Admin (just like in the previous version).

I’m preparing an update which will fix both functions usage.

Thanks again for the report, and sorry for the inconvenience.

Regards.

Hello,

Thanks for the feedback!

I’ll check the usage statistics of the solution, see if it should be added to the plugin. I try to avoid to bloat the plugin with too many fields/alternative at the moment.

Note that in the meantime, you can create your own ACF Field Type for your solution, using the Creating a new field type guide by ACF.

Thanks!

Have a nice day!

Regards.

Hello,

This plugin is not abandoned, and I’m actively working on it.

It’s not because other plugins get abandoned that this is the case here. This plugin has been around for over 5 years now, and receive updates regularly.

Thanks!

Regards.

Hello,

Thanks for the feedback!

I’m not quite sure to understand you mean by “trying to write custom data value”. The screenshot doesn’t seem to be working.

Can you be more specific? Which field in particular? On which page?

Thanks!

Regards.

Hello,

Thanks for the feedback!

In your Form Export, your “Post Action” use the target {form:photo_id}, which means it’s looking for the photo_id argument in your form to know which “post to update”.

This can be passed either using acfe_form() function:

acfe_form(array(
    'name'     => 'my-form',
    'photo_id' => 45, // pass the 'photo_id' to update the post '45'
));

Or using acfe/load_form filter. See documentation.

It looks like this is the form you tried to setup in your previous Topic here. Please read this topic and my answers again to make sure evberything is in order.

In your case, I would recommend to check how the photo_id is passed to the form in your PHP code.

Hope it helps!

Have a nice day!

Regards.

Hello,

Thanks for the feedback!

Please note this forum is dedicated to the support of the Free version of the plugin.

Thanks!

Regards.

Hello,

Thanks for the feedback!

The acf_get_grouped_terms() function is a native ACF function which allow to query multiple taxonomies at the same time, and regroup terms within their parent taxonomy. It’s pretty standard in the ACF code base, and it’s used at many different place.

The ACF developer left some comment that explain why the array_slice is used in the code, but you probably already seen it:

// compare aray lengths
// if $ordered_posts is smaller than $all_posts, WP has lost posts during the get_page_children() function
// this is possible when get_post( $args ) filter out parents (via taxonomy, meta and other search parameters)

You can quickly check what the function returns using something like:

acf_get_grouped_terms(array(
    'taxonomy' => 'category'
));

Generally speaking, the issue you’re describing (terms that don’t seem to load correctly) is related to Multilingual setups. In fact, if you have setup a multilingual installation, terms that aren’t translated in the “currently selected language” will not be displayed. This is how ACF handle this use case by default.

Is this your case?

Thanks!

Regards.

Hello,

Thanks for the feedback!

Hmm this is not normal. In order to investigate the issue, you’ll have to enable the WP Debug Mode (see documentation).

To do so, please enable the WP_DEBUG & WP_DEBUG_LOG constants in your wp-config.php file, like this:

define('WP_DEBUG', true);          // enable debug
define('WP_DEBUG_LOG', true);      // enable error logs
define('WP_DEBUG_DISPLAY', false); // disable errors on screen

/* That's all, stop editing! Happy publishing. */

Then refresh your WP Admin, and open the file /wp-content/debug.log. This file should show you if there are any PHP errors. If the file doesn’t exist once your refreshed your WP Admin, then it means there is no PHP error.

Additionally, you can open your browser console (F12 on chrome), while refreshing the WP Admin, it will show you if there are any JS error (the problem might come from here too).

Please share any error or message you see either in the /wp-content/debug.log file or in your browser console. It might help the find the cause of the problem.

To investigate a little further the issue, I would recommend clone your website on a development / staging environment using Duplicator, or with your hosting backup solution. Then try to disable all your plugins one-by-one (at the exception of ACF Pro & ACF Extended) until you find which one cause the issue.

If the problem persists, try switch to the native WP Twenty Twenty Two theme, to make sure you don’t have any custom code in your theme which would break the feature.

Let me know if you found something.

Regards.

Hello,

Thanks for the feedback!

You can prevent an action from being processed using the related “prepare” hook. For example, for the Post Action, you can use theacfe/form/prepare_post hook (see documentation), and return false to stop the action, and go to the next one. You’ll find the same “prepare” hooks in other actions too.

Usage example:

add_filter('acfe/form/prepare_post/form=my-form', 'my_post_prepare', 10, 2);
function my_post_prepare($action, $form){
    
    // if user isn't logged in
    // do not create/update the post
    // and go to the next action
    if(!is_user_logged_in()){
        return false;
    }
    
    // return normally
    return $action;
    
}

Hoep it helps!

Have a nice day!

Regards.

Hello,

Thanks for the feedback!

The Polyfill CDN library has been removed in the 0.9.0.6 Pro version, on June 28th. The day after the corruption of the CDN library was discovered. See changelog.

You can read more about the global Polyfill CDN issue here.

Please update the plugin in order to fix the issue, as the patch has been out since some time now. Also please note it is recommended to keep your plugin updated at any time.

Thanks!

Regards.

Hello,

Thanks for the feedback!

Unfortunately this feature is not available in ACF Extended at the moment. It’s on the Feature Requests list tho, and it might come in the future. But I don’t have any ETA yet, as there are others development priorities at the moment.

You can try the ACF Quick Edit Fields plugin in the meantime, which seems to do what you’re looking for. But I’m not sure if it’s compatible with Woocommerce.

I hope this answers your question.

Thanks!

Regards.

Hello,

Thanks for the feedback!

Unfortunately the native ACF Bi-directional or the ACF Extended Bi-directional features are not compatible with the Repeater/Flexible Content field. In fact, there is no way to define how a specific row in a Repeater would be saved on the other side. This option is not sustainable and flawed by design, this is why it cannot be implemented.

• You’ll find the documentation about the ACF Bidirectional feature here.
• And the documentation about the ACFE Bidirectional feature here.

The main difference between the two is that the ACFE Bidirectional feature support the Group field.

I hope this answers your question.

Have a nice day!

Regards.

Hello,

Thanks for the additional details.

Please allow me some time to do some tests, and try to reproduce the issue with the data you provided. I’ll come back to you soon.

Thank you for your patience.

Regards.

Hello,

Thanks for the feedback!

The “Post Date” is a native WordPress feature that is used for all posts, this is why it is part of the front-end form module out of the box. But “Expiration Date” is not. This feature is also kind of an edge case and is not really widely used by the user base.

Note this functionality is also more complex than it looks like, with a lot of different specific usages. Unfortunately, I cannot allocate resources for such specific features. In addition, other plugins such as Post Expirator you quoted, already do that pretty well.

However, I added some context and notes on your other support thread on post Expirator, so the developer will probably give you the good configuration to use.

Thanks!

Regards.