[wp-trac] [WordPress Trac] #19570: Post Formats: admin UI + fallbacks for themes that don't support them

[WordPress Trac]

#19570: Post Formats: admin UI + fallbacks for themes that don't support them
-----------------------------------------------+------------------
 Reporter:  alexkingorg                        |       Owner:
     Type:  task (blessed)                     |      Status:  new
 Priority:  normal                             |   Milestone:  3.6
Component:  Post Formats                       |     Version:  3.3
 Severity:  normal                             |  Resolution:
 Keywords:  has-patch ui-feedback needs-codex  |
-----------------------------------------------+------------------

Comment (by aaroncampbell):

 Replying to [comment:128 azaozz]:
 > Why not one meta field that keeps all needed data? What happens when
 more than one format meta is set on a post? Do we need to keep all unused
 meta for the main post in addition to having it in the revisions?

 I think it makes sense to keep all non-empty post format meta.  That way
 switching to a different post format and back again doesn't have the
 appearance of losing data (even if that data could be retrieved from a
 revision).  They could all be put in one post meta field as a serialized
 array, but they you couldn't query based on them (such as "give me all
 quotes from xyz source" which could be easily accomplished with a postmeta
 query using _wp_format_quote_source that also specifies the quote term).
 Still, adding empty keys seems pointless.

 As for what happens if more than one format meta is set...nothing.  The
 ones that aren't used for the current format are just...not used.  The
 format itself is determined based on a term from the post format taxonomy.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/19570#comment:130>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software