| 40 | | The key part is picking up the "sets up the post". It all started in the `WP_Query::next_post()` method, with the `iterate current post index` and this has been tricking me for the whole time as a massive performance issue. I noticed that many sites were using the previous implementation, "benefiting" of this "unexpected behaviour" with the fact that since full posts were not retrieved, even after the initialization of the loop, you could just retrieve single elements like `get_the_title` and `get_the_permalink` for example for listings within the loop, with some gains in performance as I showed in my tests. |
| | 40 | The key part is picking up the "sets up the post". It all started in the `WP_Query::next_post()` method, with the `iterate current post index` and this has been tricking me for the whole time as a massive performance issue. I noticed that many sites were using the previous implementation, "benefiting" of this "unexpected behaviour" with the fact that since full posts were not retrieved, even after the initialization of the loop, you could just retrieve single elements like `get_the_title` and `get_the_permalink` for example for listings within the loop, with some little gains in performance as I showed in my tests |