[wp-trac] [WordPress Trac] #20564: Framework for storing revisions of Post Meta
WordPress Trac
noreply at wordpress.org
Mon Jul 7 17:08:34 UTC 2014
#20564: Framework for storing revisions of Post Meta
-------------------------------------------------+-------------------------
Reporter: alexkingorg | Owner:
Type: enhancement | Status: reopened
Priority: normal | Milestone: Future
Component: Revisions | Release
Severity: normal | Version: 3.4
Keywords: needs-testing needs-codex dev- | Resolution:
feedback | Focuses:
-------------------------------------------------+-------------------------
Comment (by p51labs):
Replying to [comment:102 adamsilverstein]:
> In [attachment:20564.15.diff]:
>
> * Don't store blank meta values
> * Track meta keys stored for each revision
> * Updated unit test to test restoring blank meta
I think that blank meta should be stored if exists on the current post.
Sometimes a blank value is the intended value. A case an point would be a
field with checkboxes, by setting I blank value I know they purposely
didn't select anything from the list.
Thoughts?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/20564#comment:105>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list