[wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The Ability To Edit Tags
WordPress Trac
noreply at wordpress.org
Sun Mar 5 22:06:01 UTC 2023
#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+------------------------------
Reporter: ademos | Owner: oglekler
Type: enhancement | Status: reopened
Priority: normal | Milestone: Awaiting Review
Component: Quick/Bulk Edit | Version:
Severity: normal | Resolution:
Keywords: needs-patch needs-design | Focuses:
--------------------------------------+------------------------------
Comment (by azaozz):
Replying to [comment:59 rutviksavsani]:
Thanks, thinking this is a good start.
> support custom taxonomies other than Categories and Tags
Yes, ideally the Bulk Edit would support custom taxonomies too. For that
purpose it seems it will need one generic UI and method for hierarchical
taxonomies (categories) and another for non-hierarchical (tags). Looks
like this would be a major UI change and fairly major functionality
change.
> - When selecting the option we can ask for taxonomy selection. It can
be Categories, Tags or any other custom taxonomy.
Do you mean that the Categories, Tags, etc. selection UI will be initially
hidden like in tabs? Perhaps it would be better if they are all visible.
Less confusing and a lot better for accessibility.
> - The reason for selecting one kind of taxonomy is to reduce the
complexity for the user as well as less heavy query.
It reduces the "area" of the UI, but increases the complexity for the
user, and I think makes it harder for screen reader users.
> - We can allow users to select/deselect the posts per term as well by
providing an option to do so alongside the terms.
Not sure if this is a good idea. This is "Bulk Edit" of all selected
posts. It would be easier for the users to select only the posts they want
to change/edit. That's the main design principle in Bulk Edit.
> - We can keep the same format/signs as suggested above for
distinguishing between selected posts and partially selected posts.
The "three state checkbox" approach seems a bit confusing imho. A bigger
difficulty there is how to convey the default state. I.e. once clicked the
checkbox will have to go through the three states: all, default, none.
Problem is, how to "tell" the users about that as it doesn't seem to be a
common convention for checkboxes.
> - Provide a search bar to select new terms.
Assuming that there will be some form of auto-complete on that field. That
will work for Tags (non-hierarchical taxonomies) but not sire how it would
work for Categories. Also the accessibility of this autocomplete was the
main reason updating of Bulk Edit was postponed.
> - By providing limited number of terms, It may become easier to loop
through them and update.
> - By limiting one taxonomy at a time we can reduce the complexity of the
query and also maintain good user experience for user by reducing clutter.
I'm assuming the suggestion here is to do AJAX requests as soon as a user
selects or deselects something? This was proposed before but was rejected
as it would need to also "lock" the posts and taxonomies while a user is
bulk-editing them. Such locking would need to be implemented first
(currently only posts can be "locked", there's no lock for adding/removing
categories and tags).
Frankly I'm not sure if this is worth doing. It will also be super
confusing if a user changes a category or tag and then notices they have
selected a wrong post and deselects it. If saved "on change" the wrong
post would be changed anyway and the "Update" button at the bottom becomes
somewhat pointless.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/19859#comment:61>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list