Critical error after update from 0.9.2.4 to 0.9.2.6

Hello,

Thanks for the feedback!

By any chance, do you have the entire error message? Because without it, it’s hard to tell what’s going on.

I’m constantly monitoring tickets, and since some time now (even during the previous 0.9.2.5 update) it’s pretty quiet. But it doesn’t mean a bug isn’t hidden somewhere. This is why the error message is important.

The 0.9.2.5 & 0.9.2.6 versions include a lot of code cleanup and deprecated ACFE functions. If a developer still use one of them, it will work and log a “warning message” in the debug log, but not throw an error.

Maybe you could try to clone your website on a local/staging environment and update it there again, see if you can still get the message? Duplicator is a nice and free plugin to do that easily.

Thanks!

Regards.

Hello,

Oh okay I see, that’s a sneaky one. That would make sense.

In fact, since ACFE 0.9.2.6, Field Groups ACFE settings have a new cleaner structure.

If you need to use the old field group settings structure, you can add the following code in your theme’s functions.php:

add_action('acf/init', 'my_acfe_modules');
function my_acfe_modules(){

    // ACFE 0.9.2.6: Field group acfe settings structure change
    // new structure: $field_group['acfe']['autosync']
    // old structure: $field_group['acfe_autosync']
    // with this code, the old structure remain available with the new one:
    acf_update_setting('acfe/compatibility/legacy_field_group', true);
    
}

This will make the $field_group['acfe_autosync'] available again, just like before (alongside the new structure), and let you migrate slowly when needed.

Note: you can safely use this code in previous ACF Extended versions, it won’t break anything. It’s only checked in the newest version. So you can keep it during your upgrade/downgrade tests if needed.

Let me know if that helped!

Thanks!

Regards.