Opened 15 years ago
Last modified 6 years ago
#11950 reopened enhancement
Sticky Posts are too aggressive
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.9.1 |
Component: | Query | Keywords: | has-patch stickies |
Focuses: | Cc: |
Description
I don't think the default behavior should be to have sticky posts included every time a query_posts() is used. I realize you can set the 'caller_get_posts' argument to avoid sticky posts from being added, however having to do this everywhere becomes a burden.
What are your thoughts on having the WP class add 'include_sticky' var to the_query if it isn't already set and then not include the sticky posts by default?
Attachments (1)
Change History (18)
#3
in reply to:
↑ 2
@
14 years ago
Replying to westi:
You can now pass in
ignore_sticky_posts
I understand there are options, but I still don't think that sticky posts should be included in every query call by default. They really only make sense to be included in the main loop, which could easily be added by an argument passed from the WP class, though I understand, we're fighting a backwards compatibility issue at this point.
#4
@
13 years ago
- Milestone Future Release deleted
- Resolution set to wontfix
- Status changed from new to closed
13 months with no comments indicates a lack of community interest/support for the ticket. Closing as wontfix. If re-opening, please include a patch.
#5
@
13 years ago
- Resolution wontfix deleted
- Status changed from closed to reopened
I really like this idea. Patch is trivial — it comes down to whether we can get away with breaking this. westi, ryan?
#7
@
12 years ago
- Keywords has-patch added; dev-feedback removed
- Milestone changed from Awaiting Review to 3.7
11950.diff breathes some oxygen into this. I am not sure if where I set include_sticky
query var in WP::parse_request
is appropriate
Moving to 3.7 for discussion. @nacin endorsed this ticket 20 months ago.
You can now pass in
ignore_sticky_posts