You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Fix title.
- Clarify description.
- Avoid re-using key in same example array.
- Make valid and invalid examples be a mirror.
- Add missing `<em></em>` tags.
Copy file name to clipboardExpand all lines: WordPress/Docs/WP/PostsPerPageStandard.xml
+26-11Lines changed: 26 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
-
<documentationtitle="Flag returning high or infinite posts_per_page.">
1
+
<documentationtitle="High Posts Per Page Limit">
2
2
<standard>
3
3
<![CDATA[
4
-
Using posts_per_page (or numberposts) with the value set to an unreasonably high number or setting nopaging to true opens up the potential for scaling issues if the query ends up querying thousands of posts.
4
+
Using "posts_per_page" or "numberposts" with the value set to an high number opens up the potential for making requests slow if the query ends up querying thousands of posts. The default limit of 100 is configurable.
5
5
6
6
You should always fetch the lowest number possible that still gives you the number of results you find acceptable.
7
7
]]>
@@ -11,43 +11,58 @@ You should always fetch the lowest number possible that still gives you the numb
0 commit comments