WordPress.org

Make WordPress Core

Changes between Version 11 and Version 36 of Ticket #14746


Ignore:
Timestamp:
09/01/2010 04:48:44 PM (9 years ago)
Author:
ryan
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14746

    • Property Cc mikeschinkel@… added
  • Ticket #14746 – Description

    v11 v36  
    33This can be implemented as a custom taxonomy. wp_post_style, for example.  Terms within wp_post_style would be the styles.  Some core styles will be pre-populated.  The slugs and names will be stored as English. Dummy gettext calls will get the strings into the catalog and later the fetched names can be run through translate().
    44
    5 It can also be implemented as a post meta field.  Since there can be only one type per post, a taxonomy could be overkill. Using meta would also save us an extra taxonomy query. Using a taxonomy would, however, make it easier for plugins to add new types persistently.
     5It can also be implemented as a post meta field.  Since there can be only one type per post, a taxonomy could be overkill. Using a taxonomy would, however, make it easier for plugins to add new types persistently.
    66
    77UI on the edit post form will allow selecting from one of the types.  Themes will be provided some simple API such as get_post_style() and has_post_style().