Title: PHP error Last modified: January 14, 2023 --- # PHP error * Resolved [cfm168](https://wordpress.org/support/users/cfm168/) * (@cfm168) * [3 years, 4 months ago](https://wordpress.org/support/topic/php-error-564/) * Hello, I have WP6.1.1. and [Twenty Eleven](https://wordpress.org/themes/twentyeleven/) v4.2. Get this error log every day recently: * [Jan 14, 08:51:30] PHP Warning: Undefined array key “width” in /home/SorryHided/ SorryHided.com/wp-content/themes/twentyeleven/image.php on line 39 [Jan 14, 08: 51:30] PHP Warning: Undefined array key “height” in /home/SorryHided/SorryHided. com/wp-content/themes/twentyeleven/image.php on line 40[Jan 14, 08:58:14] PHP Warning: Undefined array key “width” in /home/SorryHided/SorryHided.com/wp-content/ themes/twentyeleven/image.php on line 39[Jan 14, 08:58:14] PHP Warning: Undefined array key “height” in /home/SorryHided/SorryHided.com/wp-content/themes/twentyeleven/ image.php on line 40[Jan 14, 09:15:10] PHP Warning: Attempt to read property “ ID” on null in /home/SorryHided/SorryHided.com/wp-includes/link-template.php on line 405 * Please help to fix it. Thanks in advance! Viewing 15 replies - 16 through 30 (of 34 total) [←](https://wordpress.org/support/topic/php-error-564/?output_format=md) [1](https://wordpress.org/support/topic/php-error-564/?output_format=md) 2 [3](https://wordpress.org/support/topic/php-error-564/page/3/?output_format=md) [→](https://wordpress.org/support/topic/php-error-564/page/3/?output_format=md) * Moderator [Kathryn Presner](https://wordpress.org/support/users/zoonini/) * (@zoonini) * [3 years, 3 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16492304) * I just tested again using the [Debug Bar](https://wordpress.org/plugins/debug-bar/) plugin and I’m seeing one error: * ```wp-block-code ( ! ) Error: Call to undefined function nocache_headers() in /Users/REDACTED/app/public/wp-admin/admin.php on line 36 ``` * I’m going to investigate further, but since you’re still seeing more errors than I am, please still do the conflict testing I suggested and let me know how it goes. * Moderator [Kathryn Presner](https://wordpress.org/support/users/zoonini/) * (@zoonini) * [3 years, 3 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16492339) * Alright, I tested again on a fresh install with the following: - [Debug Bar 1.1.4](https://wordpress.org/plugins/debug-bar/) plugin active and [debugging](https://wordpress.org/documentation/article/debugging-in-wordpress/#example-wp-config-php-for-debugging) turned on in wp-config.php - **No other plugins active** - PHP 8.0.22 - Twenty Eleven 4.2 * I’m not seeing any errors at all this time. * Let me know how it goes on your end. * Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/) * (@cfm168) * [3 years, 3 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16506194) * I am asking Debug Bar plugin support and waiting reply from them. * I can see I already have define( ‘WP_DEBUG’, false ); in my wp-config.php. If I add again and turn on it will cause any conflict? * Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/) * (@cfm168) * [3 years, 3 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16507633) * [@zoonini](https://wordpress.org/support/users/zoonini/) – I installed the Debug Bar and turned my existing the ‘WP_DEBUG’, true’.  * I don’t see the error like yours, but I can see 5 warnings and 1 notice report from the Debug. By the way I can see some Deprecated notices on top of my site for public: * ```wp-block-code Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/SorryHided/SorryHided.com/wp-includes/Requests/Cookie/Jar.php on line 63 Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/SorryHided/SorryHided.com/wp-includes/Requests/Cookie/Jar.php on line 73 Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/SorryHided/SorryHided.com/wp-includes/Requests/Cookie/Jar.php on line 89 Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/SorryHided/SorryHided.com/wp-includes/Requests/Cookie/Jar.php on line 102 Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/SorryHided/SorryHided.com/wp-includes/Requests/Cookie/Jar.php on line 111 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/SorryHided/SorryHided.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/SorryHided/SorryHided.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/SorryHided/SorryHided.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/SorryHided/SorryHided.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/SorryHided/SorryHided.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91 SorryHidedy.com/wp-content/plugins/woo-conditional-product-fees-for-checkout/includes/class-woocommerce-conditional-product-fees-for-checkout.php:160) in /home/SorryHided/SorryHided.com/wp-content/plugins/docket-cache/includes/src/Plugin.php on line 1183 SorryHidedy.com/wp-content/plugins/woo-conditional-product-fees-for-checkout/includes/class-woocommerce-conditional-product-fees-for-checkout.php:160) in /home/SorryHided/SorryHided.com/wp-content/plugins/wp-cloudflare-page-cache/libs/cache_controller.class.php on line 556 SorryHidedy.com/wp-content/plugins/woo-conditional-product-fees-for-checkout/includes/class-woocommerce-conditional-product-fees-for-checkout.php:160) in /home/SorryHided/SorryHided.com/wp-content/plugins/wp-cloudflare-page-cache/libs/cache_controller.class.php on line 557 ``` * Moderator [Kathryn Presner](https://wordpress.org/support/users/zoonini/) * (@zoonini) * [3 years, 3 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16515122) * Hi [@cfm168](https://wordpress.org/support/users/cfm168/) – I see that some of the errors above are a PHP incompatibility issue with a WooCommerce extension, which you’ve [already reported](https://wordpress.org/support/topic/debug-errors-report/) to the plugin devs. * Could you please re-test whether there are still any errors with all **your plugins temporarily deactivated**? As mentioned earlier, you can use the [Health Check plugin](https://wordpress.org/plugins/health-check/)‘ s troubleshooting mode if you don’t want to change your live site. * Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/) * (@cfm168) * [3 years, 3 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16545991) * Hi [@zoonini](https://wordpress.org/support/users/zoonini/), * Still get these php error log: * [Mar 09, 20:55:28] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/SorryHided/SorryHided.com/wp-includes/media. php:779 Stack trace:image_get_intermediate_size(312, Array) /home/SorryHided/ SorryHided.com/wp-includes/media.php:234image_downsize(312, Array) /home/SorryHided/ SorryHided.com/wp-includes/media.php:954wp_get_attachment_image_src(312, Array, false) /home/SorryHided/SorryHided.com/wp-includes/media.php:1032wp_get_attachment_image( 312, Array) /home/SorryHided/SorryHided.com/wp-content/themes/twentyeleven/image. php:104include(‘/home/xxx…’) /home/SorryHided/SorryHided.com/wp-includes/template- loader.php:106require_once(‘/home/xxx…’) /home/SorryHided/SorryHided.com/wp-blog- header.php:19require(‘/home/xxx…’) /home/SorryHided/SorryHided.com/index.php: 17{main}thrown in /home/SorryHided/SorryHided.com/wp-includes/media.php on line 779[Mar 09, 20:56:58] PHP Warning: Attempt to read property “ID” on null in / home/SorryHided/SorryHided.com/wp-includes/link-template.php on line 405 * I still try to find the conflict by Debug Bar. * [thelmachido a11n](https://wordpress.org/support/users/thelmachido/) * (@thelmachido) * [3 years, 3 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16552993) * > Could you please re-test whether there are still any errors with all **your > plugins temporarily deactivated**? * Hi [@cfm168](https://wordpress.org/support/users/cfm168/) did you manage to test while your plugins are temporarily deactivated as zoonini mentioned? * Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/) * (@cfm168) * [3 years, 3 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16558909) * [@thelmachido](https://wordpress.org/support/users/thelmachido/) – Thank you for your advise. Temporarily deactivate all plugins will causes my live site loose business. I have to wait 1 day for each plugin to get error log report if it is good one. I have more than 20 plugins so I will loose 20 days business. * Moderator [Kathryn Presner](https://wordpress.org/support/users/zoonini/) * (@zoonini) * [3 years, 3 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16558921) * [@cfm168](https://wordpress.org/support/users/cfm168/) as I’ve explained earlier, using the Health Check plugin temporarily deactivates plugins **only for your own logged-in session**. This tool **does not** deactivate plugins on your live site or for anyone else. * Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/) * (@cfm168) * [3 years, 3 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16559031) * [@zoonini](https://wordpress.org/support/users/zoonini/) – Thank you for your explanation again. I just understand temporarily deactivates plugins no effect to my live site by using the Health Check plugin. I will delete the Debug Bar plugin and use the Health Check plugin instead. Will let you know. Thank you! * Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/) * (@cfm168) * [3 years, 2 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16572676) * [@zoonini](https://wordpress.org/support/users/zoonini/), * I installed the health check plugin but it doesn’t work. * [https://wordpress.org/support/topic/plugin-does-not-give-health-check-options/#post-16572673](https://wordpress.org/support/topic/plugin-does-not-give-health-check-options/#post-16572673) * Moderator [Kathryn Presner](https://wordpress.org/support/users/zoonini/) * (@zoonini) * [3 years, 2 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16577535) * Hi [@cfm168](https://wordpress.org/support/users/cfm168/) – when you click the Troubleshooting link that looks like this: * ![](https://i0.wp.com/cldup.com/lBydNH32rX.png?ssl=1) * …could you please provide a [screenshot](https://wordpress.org/support/forum-user-guide/block-editor/#sharing-images) of the page you arrive at? * Clicking “Troubleshoot” is supposed to bring you to page that looks like the following. It sounds like you’re seeing something else, and I’d like to better understand what it is. * ![](https://i0.wp.com/cldup.com/Nv2t-q7crP.png?ssl=1) * Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/) * (@cfm168) * [3 years, 2 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16577701) * Hi [@zoonini](https://wordpress.org/support/users/zoonini/), * Yes I have the same as yours: * [https://ibb.co/1Zrx7YR](https://ibb.co/1Zrx7YR) * [https://ibb.co/m57xpH3](https://ibb.co/m57xpH3) * What should I do next to find the conflict? * Moderator [Kathryn Presner](https://wordpress.org/support/users/zoonini/) * (@zoonini) * [3 years, 2 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16577824) * OK great! So what the plugin does is temporarily deactivate your plugins. When you look at the Plugins page in Troubleshooting mode, you should see no plugins active except for Health Check. * While in this mode, check the areas of your site where you were seeing those PHP errors earlier to see if they are still present or not. * If they are no longer present, activate your plugins one-by-one while still in Troubleshooting mode. Recheck your site in between each reactivation to see if the errors come back. If they come back, then you know the problem is with the last plugin you reactivated. * Once you’ve found the culprit, you can turn off Troubleshooting mode. * There’s a [full guide here](https://wordpress.com/support/plugins/solve-problems-with-plugins/#health-check-amp-troubleshooting-plugin) on how to do this as well. * Let me know how it goes! * Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/) * (@cfm168) * [3 years, 2 months ago](https://wordpress.org/support/topic/php-error-564/page/2/#post-16595994) * There are no Deactivate option for plugins after enabled troubleshooting mode. * [https://ibb.co/wzbQ9Td](https://ibb.co/wzbQ9Td) Viewing 15 replies - 16 through 30 (of 34 total) [←](https://wordpress.org/support/topic/php-error-564/?output_format=md) [1](https://wordpress.org/support/topic/php-error-564/?output_format=md) 2 [3](https://wordpress.org/support/topic/php-error-564/page/3/?output_format=md) [→](https://wordpress.org/support/topic/php-error-564/page/3/?output_format=md) The topic ‘PHP error’ is closed to new replies. * ![](https://i0.wp.com/themes.svn.wordpress.org/twentyeleven/5.1/screenshot.png) * Twenty Eleven * [Support Threads](https://wordpress.org/support/theme/twentyeleven/) * [Active Topics](https://wordpress.org/support/theme/twentyeleven/active/) * [Unresolved Topics](https://wordpress.org/support/theme/twentyeleven/unresolved/) * [Reviews](https://wordpress.org/support/theme/twentyeleven/reviews/) ## Tags * [outside scope](https://wordpress.org/support/topic-tag/outside-scope/) * [php](https://wordpress.org/support/topic-tag/php/) * 34 replies * 3 participants * Last reply from: [cfm168](https://wordpress.org/support/users/cfm168/) * Last activity: [2 years, 9 months ago](https://wordpress.org/support/topic/php-error-564/page/3/#post-16982039) * Status: resolved