[wp-trac] [WordPress Trac] #37914: Taxonomy: Allow terms to be previewed before publishing
WordPress Trac
noreply at wordpress.org
Wed Oct 5 18:55:42 UTC 2016
#37914: Taxonomy: Allow terms to be previewed before publishing
--------------------------------------+--------------------
Reporter: celloexpressions | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 4.7
Component: Taxonomy | Version: trunk
Severity: normal | Resolution:
Keywords: needs-patch dev-feedback | Focuses:
--------------------------------------+--------------------
Comment (by johnjamesjacoby):
Playing devil's advocate, and without being fully educated on the most
desirable workflow, is it possible to mock all of this in the customizer
UI, and not write anything to the database until the results are complete?
Outside of the customizer, it's still possible for an Editor/Admin to
draft a blog post, add a bunch of new categories and tags, then
immediately trash the post, leaving the newly added categories and tags in
place. If we want to change this behavior, that should happen within the
context of the current UI before it's transitioned to the customizer.
Maybe I've been working around schema quirks for too long, but if I
understand the problem correctly, there may be at least 1 way to achieve a
less complex data object relationship...
If I were trying to build a plugin to do this, I'd stash an associative
array of potential taxonomy terms in post-meta on the draft or revision.
It would need to be diffed/merged on edit/update (to not duplicate terms
that might have been added since the last edit.) We couldn't use the
metadata API to do this (#11049, #20564) but that is where it belongs, so
it would need direct DB queries to get by.
I can also imagine odd behavior for active sites with multiple authors and
frequent taxonomy term updates. Imagine this scenario:
* Author 1 starts writing a post, tagged "Puppies
* Author 2 notices a "Puppies" draft tag exists, and deletes it
* Author 1 publishes a new post with the now deleted "Puppies" tag
* Imagine if "delete" is now "trash" - what's the end look like, and why?
This isn't a new scenario, it could happen today, but introducing the
concept of statuses carries with it the user-expectation that they are
reliable. We understood this with posts, so we introduced Post Locking a
few versions back. Not to let perfection get in the way of the good-
enough, but we'd probably eventually want some kind of Term Lock in place,
too, so that in-progress terms don't get destroyed in some other way.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/37914#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list