Timeline for When listing child pages run out of memory
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 16, 2016 at 15:45 | comment | added | Cl0udSt0ne |
var_dump($post); before your code, and check it.
|
|
| Nov 16, 2016 at 15:44 | comment | added | Cl0udSt0ne | <?php global $post; wp_list_pages( array( 'child_of' => $post->ID, // Only pages that are children of the current page 'depth' => 1 , // Only show one level of hierarchy 'sort_order' => 'asc', 'title_li' =>$post->post_title )); | |
| Nov 16, 2016 at 15:44 | comment | added | Cl0udSt0ne |
No, i'm not saying execution time, like you replied in another answer, you are not trying to pull 60000 results, just 10-40 pages. if the post_id specified to child_of is correct, it should only return the child pages, most time it will not spend more than 1 second.
|
|
| Nov 16, 2016 at 15:28 | comment | added | Third Essential Designer | Execution time and such things are there... | |
| Nov 16, 2016 at 15:14 | review | First posts | |||
| Nov 16, 2016 at 15:56 | |||||
| Nov 16, 2016 at 15:14 | comment | added | Artem Ankudovich | it displays 50 % of the time and the other 50 i get out of memory error which i think is caused by query checking far too many pages | |
| Nov 16, 2016 at 15:09 | history | answered | Cl0udSt0ne | CC BY-SA 3.0 |