Themes: Prevent null deprecation in previous_posts().#11264
Themes: Prevent null deprecation in previous_posts().#11264dan-zakirov wants to merge 1 commit intoWordPress:trunkfrom
Conversation
Add a null guard to previous_posts() matching the existing pattern in next_posts(), so calling it on a singular page no longer passes null to esc_url() and triggers an ltrim() deprecation on PHP 8.1+. Props dd32. Fixes #64864.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
This adds a null guard to
previous_posts(), matching the existing pattern used innext_posts()Without this check, calling
previous_posts()on a singular view can passnulltoesc_url(), which in turn triggers anltrim()deprecation notice on PHP 8.1 and newerProps
@dd32Fixes #64864
Trac ticket: https://core.trac.wordpress.org/ticket/64864