Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #12702, comment 67


Ignore:
Timestamp:
03/10/2016 06:42:39 PM (9 years ago)
Author:
MrGregWaugh
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12702, comment 67

    initial v1  
    37373.  Same as above I would suspect.  I don't believe anybody believes that the current implementation is ideal either, and we'd all like for a new way to do it.  Once again though, it is the implementation we have today and there is no roadmap that I'm aware of to replace it in core.
    3838
    39 In terms of performance concerns, I get that it's far from the idea solution.  However there's nothing that would prevent those concerns from occurring the way it works now, and there's no way to be sure that just by having this enabled would be any worse than now.  If it's really as so bad as to be a great concern, let's deprecate the entire thing in a future version.
     39In terms of performance concerns, I get that it's far from the idea solution.  However there's nothing that would prevent those concerns from occurring the way it works now, and there's no way to be sure that just by having this enabled would be any worse than now.  If it's really so bad as to be a great concern, let's deprecate the entire thing in a future version.
    4040
    4141The fact that sticky posts on CPTs work out of the box, limited only by the display of the checkbox in the UI is the source of this ask.  The functionality is 98% complete, so can we just do the last 2%?  Since there is no imminent replacement, and no imminent plan to remove sticky posts for 'post' post types from core, I'm suggesting this one small tweak.