Problem with acfe-ui.min.js file

Hello,

Thanks for the feedback! You probably have a compatibility issue with a plugin or a custom code. Please make sure that you use the last WordPress + ACF Pro + ACF Extended version.

I would recommend to use SCRIPT_DEBUG (see documentation) to use unminified javascript version and check your browser console to see if you have a JS error. You can then try to disable plugins one-by-one, and use the default Twenty twenty one theme until you find which plugin cause this issue.

If you don’t want to debug your installation, you can simply disable the Enhanced UI module, but you’ll probably still have an underlying bug which may cause problems in the future. Here is how to disable the module if you need to:

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

    // Disable Enhanced UI
    acf_update_setting('acfe/modules/ui', false);
    
}

Hope it helps!

Regards.

Thanks for reply! I forget to say that name of our custom taxonomy “tags”, and if we change it for example to “tagss” problem is solved. Maybe problem in name “tags”?

We just tried it on new WP instalation with all updated plugins – same result.

Hello,

You should avoid to register a Taxonomy named tags since it will create a collision with the native edit-tags WordPress admin screen.

When using a taxonomy named tags, you’ll get the following PHP notice when creating a new term, since WordPress cannot correctly recognize the taxonomy name:

PHP Notice: Trying to get property 'term_id' of non-object in \wp-admin\includes\class-wp-terms-list-table.php on line 432
PHP Notice: Trying to get property 'name' of non-object in \wp-admin\includes\class-wp-terms-list-table.php on line 433
PHP Notice: Trying to get property 'slug' of non-object in \wp-admin\includes\class-wp-terms-list-table.php on line 436
PHP Notice: Trying to get property 'parent' of non-object in \wp-admin\includes\class-wp-terms-list-table.php on line 437

Those errors can be reproduced using a fresh & blank WP Install without ACF and without ACF Extended.

The problem with the Enhanced UI from ACF Extended is just an extension of this native WordPress issue, since metaboxes aren’t correctly recognized, and thus the sidebar cannot be correctly generated. To see the error, you have to enable the WP_DEBUG & WP_DEBUG_LOG (see documentation) since it is thrown during the ajax request when creating a new term.

Using a taxonomy tag seems to work correctly since there is no admin screen id called edit-tag, and thus no collision. But tag is also listed as a Reserved Term so I would recommend to not use it either.

You can create a Core Trac Ticket about that issue, but I’m afraid that tags will be simply added to the WP Reserved Terms.

Hope it helps!

Regards.

I understand you… but if we deactivate ACF Extended plugin problem is solved. Even on fresh WP instalation.

Hello,

Please read again my last answer. You can disable ACF Extended, you’ll still get the following errors when creating a term in a taxonomy called tags:

PHP Notice: Trying to get property 'term_id' of non-object in \wp-admin\includes\class-wp-terms-list-table.php on line 432
PHP Notice: Trying to get property 'name' of non-object in \wp-admin\includes\class-wp-terms-list-table.php on line 433
PHP Notice: Trying to get property 'slug' of non-object in \wp-admin\includes\class-wp-terms-list-table.php on line 436
PHP Notice: Trying to get property 'parent' of non-object in \wp-admin\includes\class-wp-terms-list-table.php on line 437

This is due to WordPress not working correctly with such taxonomy name. ACF Extended Enhanced UI missing sidebar is an extension of this WordPress incompatibility with tags taxonomy name.

Regards.

You can disable the ACFE module using the code from my first answer if you still want to keep using tags as taxonomy name.

But as WordPress already throw some errors even without ACF Extended when using this name, I would strongly recommend to choose something else. This kind of error on a fresh WP install without any plugin is a bad sign and could potentially raise more unknown problems during your development.

You can try to submit a ticket on the core trac to poke the WP core team. If they patch that issue it will most likely also fix the ACFE module (both are kinda tied).

I’ll see if I can fix the module for that specific taxonomy name, but it won’t fix WordPress on its own, and errors will still be there. Added to the Trello Board.

Hope it helps.

Regards.

Hello,

Just a heads up to let you know that the latest 0.8.8.2 update fix the issue.

Have a nice day!

Regards.