WordPress.org

Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #8592, comment 162


Ignore:
Timestamp:
02/02/2014 04:57:54 AM (6 years ago)
Author:
plocha
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8592, comment 162

    v1 v2  
    1212'''Status limitation instead of strict inheritance'''
    1313
    14 Example: published parent, draft child. If you set parent to "future", the children gets the same status. Such a feature can be annoying. Maybe we should switch to a status limitation feature: A parent status limits the possible status for the descendants. The 'top down' inheritance code should only force a descendant to have the same status if the descendant has an 'higher' status. Example: published parent, future child. If you set the parent to draft, the child should also be set to private.
     14Example: published parent, draft child. If you set parent to "future", the children gets the same status. Such a feature can be annoying. Maybe we should switch to a status limitation feature: A parent status limits the possible status for the descendants. The 'top down' inheritance code should only force a descendant to have the same status if the descendant has an 'higher' status. Example: published parent, future child. If you set the parent to draft, the child should also be set to draft.
    1515
    1616Other example: future parent. A child can be for example draft,private or future but it cannot be published.