Pascal Birchler 7:11 pm on March 7, 2016
Tags: 4.5 ( 60 ), dev-notes ( 520 ), taxonomy ( 16 )

Changes to the Term Edit Page in WordPress 4.5

Up until recently, the term list table and the term edit form in the adminadmin (and super admin) shared the same page: wp-admin/edit-tags.php. This is inconsistent compared to how the post list table and the editor are split up between wp-admin/edit.php and wp-admin/post.php.

As was reported in #34988, this inconsistency led to some problems when screen options belonging to the list table were shown on the term edit page. This was changed in [36308] by introducing wp-admin/term.php 💪🏽.

What this means for developers

First of all, you’ll notice that the links to edit a single term now look like example.com/wp-admin/term.php?tag_ID=123. (previously: example.com/wp-admin/edit-tags.php?action=edit&taxonomy=post_tag&tag_ID=127). That’s not a big deal actually, but it leads to some changes under the hood:

If you’re specifically targeting the term edit form in your pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, $pagenow changes from edit-tags.php to term.php. The screen base (returned by get_current_screen()) changes from edit-tags to term as well. That’s it 🙂

What to look for

If you want to specifically enqueue scripts and styles on the term edit page, you should hook to load-term.php instead of load-edit-tags.php. That way you won’t unnecessarily load assets on the wrong screen.

Besides that, everything stays the same 😇. If you do however find any quirks related to this change, do not hesitate to leave a comment on this post or the relevant ticketticket Created for both bug reports and feature development on the bug tracker.: #34988

#4-5, #dev-notes, #taxonomy

Misamee 10:53 pm on March 7, 2016
A lot of APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. changed, at least for what concerns dealing with terms, unless I’ve missed these changes in previous versions (which might be very well possible).

Here is a summary of what I’ve found so far:

Changed hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. (some are marked as deprecated, others are just gone):
- add_category_form > {$this>taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.}_add_form
- edit_category_form > {$this>taxonomy}_edit_form
- add_tag_form > {$this>taxonomy}_add_form
- edit_tag_form > {$this>taxonomy}_edit_form
- add_category_form_fields > {$this>taxonomy}_add_form_fields
- edit_category_form_fields > {$this>taxonomy}_edit_form_fields
- add_tag_form_fields > {$this>taxonomy}_add_form_fields
- edit_tag_form_fields > {$this>taxonomy}_edit_form_fields
…well, you got the idea 🙂

As you wrote, the global variable $pagenow used to be ‘edit-tags.php’ for listing, editing and adding terms.

Now:
-> ‘term.php’ -> editing terms
-> ‘edit-tags.php’ -> adding/listing terms

So, this URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org:
```
$edit_link_arguments = array (
  'taxonomy' =>; 'category',
  'action' => 'edit',
  'tag_ID' => '7',
  'post_type' => 'post',
);

$edit_link_url = add_query_arg( $edit_link_arguments, admin_url( 'edit-tags.php' ) )
```
Produce this url: `http://wpml.dev/wp-admin/edit-tags.php?taxonomy=category&action=edit&tag_ID=7&post_type=post`

…which is wrong now.

However, at least for now, WP does an automatic redirect to the right URL, which in the above example, would be: `http://wpml.dev/wp-admin/term.php?taxonomy=category&term_id=7&post_type=post`

Anything else which I’m missing?

The main problem here will be that plugins will need quite some hacks to keep backward compatibility with WordPress 4.4 and older.
- Pascal Birchler 7:39 am on March 8, 2016
  
  Thanks for your investigation!
  
  Filters:
  
  add_category_form, edit_category_form, add_tag_form, edit_tag_form, add_tag_form_fields filters still exist. Nothing changed there.
  
  add_category_form_fields was removed about 6 years ago in [13035].
  
  edit_category_form_fields and edit_tag_form_fields still exist, but have been deprecated since WordPress 3.0.
  
  Term edit link:
  
  That automatic redirect is wanted and by design. Thanks to that, nothing breaks.
  
  But please, do not build that URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org yourself using add_query_arg() You should really use get_edit_term_link(), which has been available since WordPress 3.1
BackuPs 8:14 am on March 8, 2016
Hi

But this would mean i have to check for both as i dont know if the user is already on 4.5
```
function theme_is_post_type_taxonomy($post_types = '') {
 if ('edit-tags.php' != basename($_SERVER['PHP_SELF'])) {
  return false;
 }
 if ('term.php' != basename($_SERVER['PHP_SELF'])) {
  return false;
 }
else the rest of my code.....
}
```
Correct?
- Pascal Birchler 8:43 am on March 8, 2016
  
  It depends on what you want to do.
  
  add_action( 'load-edit-tags.php', ....) will continue to work for the new term edit page, e.g. for enqueueing assets and. If you want to specifically detect the the term edit check, looking for the tag_ID GET parameter is an easy solution. Nothing really changing here for plugins.
  
  NB: Instead of checking $_SERVER['PHP_SELF'] you should use $pagenow and get_current_screen() or alternatively compare $wp_version.
  - darrinb 5:00 am on March 25, 2016
    
    In my testing, `load-edit-tags.php` isn’t being called on the new term edit page (term.php).
    - ScreenfeedFr 3:19 pm on April 3, 2016
      
      Backward compatibility is ensured 😉
      
      do_action( 'load-' . $pagenow ); ... } elseif( 'term.php' === $pagenow ) { do_action( 'load-edit-tags.php' ); }
Yaron Guez 10:52 pm on March 18, 2016

“If you want to specifically enqueue scripts and styles on the term edit page, you should hook to load-term.php instead of load-edit-tags.php.”

Previously I was adding scripts on the term edit page using the admin_print_scripts-edit-tags.php hook. Is the new hook admin_print_scripts-load-term.php? Is it safe to use both to cover both versions of WP?
- Pascal Birchler 4:33 pm on March 25, 2016
  
  Yes, this hook changes to admin_print_scripts-load-term.php because of the changing $pagenow variable. It should be quite safe to use both, but of course it depends on what your script does.