#36905 closed enhancement (fixed)
Add caching to get_page_by_title
Reported by: | spacedmonkey | Owned by: | spacedmonkey |
---|---|---|---|
Milestone: | 6.1 | Priority: | normal |
Severity: | normal | Version: | 2.1 |
Component: | Posts, Post Types | Keywords: | has-patch good-first-bug has-unit-tests dev-feedback commit has-dev-note |
Focuses: | performance | Cc: |
Description
Add caching to get_page_by_title so it doesn't call the posts table.
Attachments (9)
Change History (41)
#2
@
9 years ago
- Keywords good-first-bug added
- Milestone changed from Awaiting Review to Future Release
Change seems OK, but get_page_by_title()
has no automated test coverage at all. We'll need basic tests to introduce this kind of change.
#4
@
8 years ago
I propose to let WP_Query handle this.
I'd also propose to deprecate this function. Is not used by Core so plugins could use their own functions instead. Querying by title is not a very good idea so we would be discouraging developers to use this function (maybe just a little but more than nothing). @scribu said the same in here: https://core.trac.wordpress.org/ticket/20350#comment:1 I don't know if she would think the same today.
Anyway, here are my changes: Unit tests + changes inside the function (not deprecated though) so now it uses WP_Query instead.
#5
@
8 years ago
- Keywords has-unit-tests added; needs-unit-tests removed
- Owner set to igmoweb
- Status changed from new to assigned
Assigning to mark the good-first-bug as "claimed".
@igmoweb Can you please combine 36905.2.patch and 36905.2.tests.patch into a single patch?
#6
@
8 years ago
Done.
Do we now upload changes + tests in the same file? I thought it was the other way.
#7
@
8 years ago
Do we now upload changes + tests in the same file? I thought it was the other way.
We used to do it separately as they were in two different repo's, they're now combined so doing it in one patch is easier to keep track of everything (especially when things start getting into multiple iterations)
#8
@
8 years ago
36905.5.patch includes some improvements to the function:
- orderby is set to 'none' so it preserves the same order than the original function
- post_status is now an array with 'any' + all existent statuses even those that are excluded from search. This way, the query has less conditionals in WHERE clause and post_status field is not even filtered, like the original function.
- I added tests to check that the function query every single post status.
#9
@
6 years ago
Added a refresh based on current trunk. A duplicate copy was added due to internet issues :P. Refresh has not been tested, but mainly fixed to apply properly, and explicitly return null.
#10
@
6 years ago
@igmoweb @pcfreak30 Looking at your patches, I have one simple question, how does this fix the issue? Using WP_Query is nice, but WP_Query isn't have any query caching out of the box. Even if are you using advanced-post-cache or enhanced-post-cache neither of which, cache queries with 'fields' => 'ids' set.
See that #36711 is basically the same code and @boonebgorges merged that. We should go back to my original patch. This will likely need a refresh after all coding standards changes.
#11
@
6 years ago
@spacedmonkey your patch looks nice however wp_query does cache with 'cache_results' if wp_using_ext_object_cache() is true, so the extra cache check in your version is unneeded. Even with it, it only helps if doing memory caching, which is up for debate if the extra complexity matters vs using core wp_query.
Also, I generally feel direct DB access for stuff like this should be avoided overall. We have a query system, it should be used if possible.
#12
@
6 years ago
@pcfreak30 Sadly, you are incorrect, with the cache_results
flag set, all that does is prime post caches and the query it's self is not cached. See this and the related ticket #22176 .
However, I do agree, we should be using WP_Query
, as it is clearer that way. I will update the patch to fix the caching in with the query call changes.
#14
@
3 years ago
@igmoweb Are you willing to work on this patch still? I am willing to pick it up otherwise.
This ticket was mentioned in PR #2384 on WordPress/wordpress-develop by pbearne.
3 years ago
#16
refresh and tests
Tests not working
Trac ticket: https://core.trac.wordpress.org/ticket/36905
This ticket was mentioned in PR #3236 on WordPress/wordpress-develop by spacedmonkey.
2 years ago
#17
Trac ticket: https://core.trac.wordpress.org/ticket/36905
spacedmonkey commented on PR #2384:
2 years ago
#19
Closing in favour of https://github.com/WordPress/wordpress-develop/pull/3236
spacedmonkey commented on PR #3236:
2 years ago
#20
CC @pbearne.
#21
@
2 years ago
- Milestone changed from Future Release to 6.1
- Owner changed from igmoweb to spacedmonkey
#23
@
2 years ago
- Keywords commit added
Commit ready as of 88bee5302227b0a27e8f2a0d8b2691b509c065a2 on the linked pull request.
peterwilsoncc commented on PR #3236:
2 years ago
#25
Merged in https://core.trac.wordpress.org/changeset/54234 / 7ad9e7d
This ticket was mentioned in PR #3285 on WordPress/wordpress-develop by peterwilsoncc.
2 years ago
#26
https://core.trac.wordpress.org/ticket/36905
cc @costdev
peterwilsoncc commented on PR #3285:
2 years ago
#28
Merged https://core.trac.wordpress.org/changeset/54242 / f450acf7afdce2859d5ede3656626ca5538b592b
Related: #36711