Warning: Trying to access array offset on value of type bool in /sites/site.com/wp-includes/media.php on line 795 801

[vladte4]

Hello! Maybe someone knows what the problem is? Photo files avif.

It seems to me that the error began to appear after updating the WordPress. I tried regenerate thumbnails but it didn't work for me. I disabled all plugins and left only WooCommerce, WPBakery, Woodmart Core.

[vladte4]

a little more information. I installed ubuntu 22.04 on a new server, but the error remained, so I think it's in WordPress 6.6

[vladte4]

The photo had a size of 1920x1920 . Everything is fine with 800x800 resolution. Photos with the webp extension also break. Photos in 790x796 wepb resolution are also broken. JPG also broken. For me, only photos with a size of 800x800 started working properly. The problem remained on php 8.3

[vladte4]

I can provide access to the server so that you can view the error, I have a test site

[antpb]

We've seen recent reports similar to this issue (example: #59573) It might be worth adding a bool check to be safe here and avoid future reports. It would be nice to understand more what value is being passed through here to better understand why we are making the change.

@vladte4 thanks for this report and all the info! One thing we are still lacking to diagnose the issue is the call stack that is resulting in the error. Is there any way that you can share with us the calls that are triggering the warning? Knowing if it is a theme or plugin, a certain function, or any other information about where its coming from would be very helpful. I'd like to better understand how a bool is getting to this point in the code so we can bypass this logic in the case of a bool.

[vladte4]

The error was in the WPBakery plugin, you need to update to version 7.8 . After the update, the error seems to have disappeared and everything is fine

[vladte4]

Hello! The error remains, the update did not help :(

[niravsherasiya7707]

@vladte4 Could you please mention the steps to recreate it?

[vladte4]

I deleted the data for access to the site

[vladte4]

@niravsherasiya7707 @antpb Here are the data to the server and the website. The error is visible in the product and on the main page. The site has just started to be developed, so you can install plugins for diagnostics and more

[vladte4]

If anyone has time, can you review it? I disabled all plugins and activated the standard theme, but the error remains. I left only WooCommerce. Also, the error is sometimes displayed in the panel when adding a photo to a product or updating a product. Exactly Avif file

[vladte4]

I disabled the error. With this code. I don't know when the problem will be solved, this post is no longer viewed, so for now

ini_set('display_errors', 'Off'); 
ini_set('error_reporting', E_ALL);

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

Hello @narenin, Thank you for this patch. In reviewing it, I don't think this is the way to fix the issue. Why?

1. The root cause is not yet known.
2. The Warning may be appropriate as is the indicator to developers and contributors that something upstream of this function is wrong.

Please note, this part of the function requires both the width and height, meaning they should both always be in the array. One or both not being in the array could mean there's an issue upstream before this function gets called. That's where the fix IMO should happen.

What about adding defensive guard? Yes, can be good, but should still alert developers and contributors (throw an error, doing it wrong, etc.).

This assumes both the width and height (as the code is now) are required and should always be there. Maybe @antpb can share some thoughts.

[hellofromTonya]

Hello @vladte4,

Welcome to WordPress Core's Trac.

As @antpb noted, #59573 was a similar report. Setting the Version (the WP version that may have introduced the bug) to match #59573.

I don't think this ticket is actionable yet. What does it need? As @antpb noted in comment:6:

• Step-by-step instructions for how to reproduce the issue.
• The call stack that accompanies the Warning posted.

These will give contributors the starting point to produce and investigate to identify the root cause.

I suspect the root cause may be upstream, i.e. before the image_get_intermediate_size() function runs. While defensive guards can be added to image_get_intermediate_size(), they will not resolve an upstream bug.

Updating the ticket Version and keywords to help denote current state.