global-styles-and-settings.php in wp_theme_has_theme_json

[cocasio45]

Wordpress 6.3.1 , php 8.1.23

<?php
function wp_theme_has_theme_json() {
        static $theme_has_support = array();

        $stylesheet = get_stylesheet();

        if (
                isset( $theme_has_support[ $stylesheet ] ) &&
                /*
                 * Ignore static cache when the development mode is set to 'theme', to avoid interfering with
                 * the theme developer's workflow.
                 */
                ! wp_is_development_mode( 'theme' )
        ) {
                return $theme_has_support[ $stylesheet ];
        }

        $stylesheet_directory = get_stylesheet_directory();
        $template_directory   = get_template_directory();

        // This is the same as get_theme_file_path(), which isn't available in load-styles.php context
        if ( $stylesheet_directory !== $template_directory && file_exists( $stylesheet_directory . '/theme.json' ) ) {
                $path = $stylesheet_directory . '/theme.json';
        } else {
                $path = $template_directory . '/theme.json';
        }

        /** This filter is documented in wp-includes/link-template.php */
        $path = apply_filters( 'theme_file_path', $path, 'theme.json' );
        
        /* ADD THIS SECTION */
        if( ! $path ) {
                $theme_has_support[ $stylesheet ] = false;
                return false;
        }
         /* END OF SECTION */

        $theme_has_support[ $stylesheet ] = file_exists( $path );
        /* file_exists THROW DEPRECATION ERROR WHEN RECIEVE NULL */

        return $theme_has_support[ $stylesheet ];
}

Trac ticket: https://core.trac.wordpress.org/ticket/59507

Please add a test to proof the issue and safeguard the fix.

[spacedmonkey]

@cocasio45 Can you explain the reason for this ticket and the benefit of it. Thanks.

Please add a test to proof the issue and safeguard the fix.

@jrfnl The issue could only happen if $path was set to null using the theme_file_path filter. Can I just use the hook in the unit test and assert false is returned instead?

@AbdiTolesa You can.

[cocasio45]

@spacedmonkey it's written in the code i forget to write it in the ticket but file_exists, when recieving the null value throw a DEPRECATION ERROR that's why

[jrf]

Replying to cocasio45:

@spacedmonkey it's written in the code i forget to write it in the ticket but file_exists, when recieving the null value throw a DEPRECATION ERROR that's why

To be honest, the only time that could happen is if a plugin/theme would hook into that filter and return a value of null, which is not a valid return type for ​the filter (it expects type string and only string).

In my opinion, this deprecation should not be hidden away. The plugin/theme doing it wrong should get fixed instead.

[cocasio45]

Replying to jrf:

Replying to cocasio45:

@spacedmonkey it's written in the code i forget to write it in the ticket but file_exists, when recieving the null value throw a DEPRECATION ERROR that's why

To be honest, the only time that could happen is if a plugin/theme would hook into that filter and return a value of null, which is not a valid return type for ​the filter (it expects type string and only string).

In my opinion, this deprecation should not be hidden away. The plugin/theme doing it wrong should get fixed instead.

I'm ok with that point of view, in this case we need to make the exception more visible because the only way that I could get the error is when I run xdebug

[spacedmonkey]

The only time this happens is from developer error, when someone misuses theme_file_path filter. This DEPRECATION ERROR seems valid to me.

@cocasio45 In the future, please write a description. Not everyone on trac can read code. Even me, who can, I didn't read it.

I would vote for #wontfix on this ticket.

[cocasio45]

Replying to spacedmonkey:

The only time this happens is from developer error, when someone misuses theme_file_path filter. This DEPRECATION ERROR seems valid to me.

@cocasio45 In the future, please write a description. Not everyone on trac can read code. Even me, who can, I didn't read it.

I would vote for #wontfix on this ticket.

As told it will not appen again

Also I am not using a theme.json and this hook is executed so you sure the error the error is comming from me ?