Timeline for Query Nopaging action not having effect
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23, 2021 at 7:30 | vote | accept | Ronald Langeveld | ||
| Jan 21, 2021 at 13:18 | answer | added | Tom J Nowell♦ | timeline score: 1 | |
| Jan 21, 2021 at 10:52 | comment | added | Tom J Nowell♦ | if that's the case then ask for 500 posts, never say you want everything. That way instead of saying it should be okay, you can say with certainty and guarantee that will always be okay | |
| Jan 21, 2021 at 7:49 | comment | added | Ronald Langeveld | @TomJNowell Going to try that code now, thank you! | |
| Jan 21, 2021 at 7:48 | comment | added | Ronald Langeveld | @TomJNowell thanks for the warning. It's only for a very specific post type with minimal data, so won't be an issue for most servers to handle. :) | |
| Jan 20, 2021 at 21:27 | comment | added | Tom J Nowell♦ | Also note that fetching all posts can be dangerous, it's much safer to fetch a high number of posts you never expect to hit, otherwise accidents, changing business cases, etc can lead to memory exhaustion or intense slowness | |
| Jan 20, 2021 at 21:14 | comment | added | Tom J Nowell♦ |
You should be calling the methods on the query object, not the helper function, e.g. $query->is_post_type_archive...... Otherwise, nopaging doesn't do what you think it does. Likewise it looks like you've re-implemented sticky posts
|
|
| Jan 20, 2021 at 20:38 | history | asked | Ronald Langeveld | CC BY-SA 4.0 |