Opened 3 years ago
Last modified 17 months ago
#11950 reopened enhancement
Sticky Posts are too aggressive
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Query | Version: | 2.9.1 |
| Severity: | normal | Keywords: | dev-feedback |
| 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?
Change History (6)
comment:1
prettyboymp — 3 years ago
- Keywords dev-feedback added
comment:3
in reply to:
↑ 2
prettyboymp — 2 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.
- 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.
- 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?

You can now pass in ignore_sticky_posts