[wp-trac] [WordPress Trac] #20564: Framework for storing revisions of Post Meta
WordPress Trac
noreply at wordpress.org
Thu Mar 28 14:00:13 UTC 2013
#20564: Framework for storing revisions of Post Meta
-------------------------+------------------
Reporter: alexkingorg | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 3.6
Component: Revisions | Version:
Severity: normal | Resolution:
Keywords: |
-------------------------+------------------
Comment (by adamsilverstein):
Replying to [comment:29 markjaquith]:
> We need the exact opposite approach of this patch. :-)
>
> We should have a list of meta keys that we WILL revision, not a list of
ones we WON'T. There should be no filter to opt out of revisioning of post
format postmeta.
ok, this was the method suggested in #20299 so i went with it. a possible
advantage of this method is it will catch new meta options as they are
added or used, but i could also see how it could catch fields you didn't
need.
i can change the method and include all current used metas, maybe add a
filter for plugin authors to register new metas for revisioning?
--
Ticket URL: <http://core.trac.wordpress.org/ticket/20564#comment:30>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list