get_page_by_path $post_type supports string and array but the check in the loop is checking by string

[salimali]

In the get_page_by_path function, $post_type supports string and array, but the check in the loop is checking by string ​https://github.com/WordPress/wordpress-develop/blob/6.8.1/src/wp-includes/post.php#L6135, which throws PHP Warning: Array to string conversion in /var/www/html/wp-includes/post.php on line 6135. Example below:

<?php
$page = get_page_by_path('/parent/child/', OBJECT, array('page'));

Track ticket : https://core.trac.wordpress.org/ticket/63656

[dilip2615]

Patch Testing

Description

Tested the patch for Ticket #63656: Twenty Seventeen theme should use the_excerpt() instead of the_content() on search and archive pages.

Environment

• WordPress: 6.8.1
• PHP: 8.2.23
• Server: nginx/1.26.1
• Database: mysqli (Server: 8.0.16 / Client: mysqlnd 8.2.23)
• Browser: Chrome 138.0.0.0
• OS: Windows 10/11
• Theme: Twenty Seventeen 3.9
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.2.0

Steps to Reproduce

1. Create a post with content and an excerpt.
2. View search results or archive page.
3. See the full content appearing.
4. Apply the patch from the ticket.
5. View again → now only the excerpt appears.

Expected Results

✅ Excerpt should be shown on archive/search pages.

Actual Results

✅ Excerpt is shown. Patch works as expected.

Additional Notes

No layout/design issues. Works well with existing posts.

[mindctrl]

@dilip2615 your test report appears to be for a different ticket?

[dilip2615]

Replying to mindctrl:No testing for this current ticket.

@dilip2615 your test report appears to be for a different ticket?

[mindctrl]

@dilip2615 your test report refers to "Twenty Seventeen theme should use the_excerpt() instead of the_content() on search and archive pages.", but that is not what this ticket is about.

This ticket is about get_page_by_path throwing PHP warnings.

[dilip2615]

Replying to mindctrl:

Okay Thanks for the information sorry about my conversation I will check more.

[mindctrl]

@salimali thanks for the report. Can you provide steps on how you encountered the PHP notices? The attached PR looks correct, but I'd like to understand how the error is/was triggered in WP.

[SirLouen]

Given that several months have passed without additional information about the ticket, as @mindctrl asked, I think it's time to close this as maybelater, as it is unclear how to reproduce it and there has been no follow up by @salimali

@salimali please feel free to comment whenever you see this and provide additional information on how to reproduce it, and I will be happy to test it and review the patch accordingly.