snosites

I’m using PHP 8.0.14 and WP 5.9.3

Here’s the full stack trace:
[21-May-2022 16:51:32 UTC] PHP Warning: Undefined array key “exclude_search” in /home/westdela/public_html/wp-content/plugins/ultimate-category-excluder/ultimate-category-excluder.php on line 81
[21-May-2022 16:51:32 UTC] PHP Fatal error: Uncaught TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given in /home/westdela/public_html/wp-content/plugins/ultimate-category-excluder/ultimate-category-excluder.php:81
Stack trace:
#0 /home/westdela/public_html/wp-content/plugins/ultimate-category-excluder/ultimate-category-excluder.php(81): in_array(‘-23’, NULL)
#1 /home/westdela/public_html/wp-includes/class-wp-hook.php(307): ksuce_options_page(”)
#2 /home/westdela/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(”, Array)
#3 /home/westdela/public_html/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
#4 /home/westdela/public_html/wp-admin/admin.php(259): do_action(‘settings_page_u…’)
#5 /home/westdela/public_html/wp-admin/options-general.php(10): require_once(‘/home/westdela/…’)
#6 {main}
thrown in /home/westdela/public_html/wp-content/plugins/ultimate-category-excluder/ultimate-category-excluder.php on line 81

Here’s what this site has stored in the ksuceExcludes option in the wp_options table:
a:3:{s:12:”exclude_main”;a:0:{}s:12:”exclude_feed”;a:1:{i:0;s:2:”-1″;}s:16:”exclude_archives”;a:0:{}}

It looks like this site doesn’t have the “exclude_search” array stored, and so when the plugin is looping through the categories and checking to see if the cat ID is in the exclude_search array, it throws the error because there is no exclude_search array and PHP 8.0 throws a fatal error if in_array is used on null.

Before making the in_array comparison, the plugin should check that $options[‘exclude_search’] is an array to prevent the fatal error.

Or you could edit ksuce_get_options function to check that each of the four nested arrays in this option is set. If one of them isn’t, the array could be set at this point, and that would remove the error from line 81.

Hi Tishu,

Thanks for the reply. I hadn’t seen the ESI setting before — I’ve set that up and I’m now seeing my widgets update after I make a change in them and then save them. So if I set the ESI setting in a widget to “Disable”, that turns off all caching for that widget, correct?

Jason

It looks like the problem is caused by the jquery.metadata.js file.

That fixed the problem — thanks for the update.

Hi Michael,

I was wrong about my earlier test — it still wasn’t working when a category is selected.

I just did some more testing.

The plugin appears to work properly if at least one category is checked to be excluded from the Main Page. If there are no categories selected in that row, that’s when the problem emerges.

Hi Michael,

Thanks for looking into this.

Here’s the info from the settings page:

UCE version: 0.94
PHP version: 5.3.20
MySQL version: 5.1.61-log
WordPress version: 3.6
Current theme: SNO FLEX
Number of categories is: 10

I just tested NextGen 2.0.7, and the problem conflict with the Magic Fields plugin is no longer a problem.

Thank you!

Thanks Erick,

We’ve got 1200 active clients on WordPress sites and we’ve always recommended NextGen as a good slideshow solution for them. I hope we can continue to recommend this plugin.

Thanks for releasing an update! I just tested the 1.6 version, and the media uploader works, but the datepicker still isn’t working with WP 3.5.

The fix posted above does work for Magic Fields 1 as well. Look for line 313 in the main.php file.

I set the date on the General settings page to Custom, and the widget then worked properly with the date displaying.

I also had this php error on a different site:
[14-Sep-2011 18:37:07] PHP Warning: Invalid argument supplied for foreach() in /wp-content/plugins/my-calendar/my-calendar-user.php on line 11

Thanks Joe!

hznmoodi,

What’s the name of your theme, and what’s the name of the folder that your theme is in?

You can also change 'theme_mods_'.get_current_theme();

to 'theme_mods_themename';

Use the actual name of your theme, and make it lowercase.

That fixed it for me. Thanks, rguan!