• Resolved koolkatwebdesigns

    (@koolkatwebdesigns)


    Fatal error: Uncaught TypeError: array_filter(): Argument #1 ($array) must be of type array, null given in /home/customer/www/bowenrotary.koolkattest.com/public_html/wp-includes/class-wp-user-query.php:483 Stack trace: #0 /home/customer/www/bowenrotary.koolkattest.com/public_html/wp-includes/class-wp-user-query.php(483): array_filter(NULL) #1 /home/customer/www/bowenrotary.koolkattest.com/public_html/wp-includes/class-wp-user-query.php(79): WP_User_Query->prepare_query(Array) #2 /home/customer/www/bowenrotary.koolkattest.com/public_html/wp-includes/user.php(776): WP_User_Query->__construct(Array) #3 /home/customer/www/bowenrotary.koolkattest.com/public_html/wp-includes/user.php(1669): get_users(Array) #4 /home/customer/www/bowenrotary.koolkattest.com/public_html/wp-admin/includes/meta-boxes.php(976): wp_dropdown_users(Array) #5 /home/customer/www/bowenrotary.koolkattest.com/public_html/wp-admin/includes/template.php(1456): post_author_meta_box(Object(WP_Post), Array) #6 /home/customer/www/bowenrotary.koolkattest.com/public_html/wp-admin/edit-form-advanced.php(723): do_meta_boxes(Object(WP_Screen), ‘normal’, Object(WP_Post)) #7 /home/customer/www/bowenrotary.koolkattest.com/public_html/wp-admin/post.php(206): require(‘/home/customer/…’) #8 {main} thrown in /home/customer/www/bowenrotary.koolkattest.com/public_html/wp-includes/class-wp-user-query.php on line 483

    There has been a critical error on this website. Please check your site admin email inbox for instructions.

    Learn more about troubleshooting WordPress.

    PHP 8 WordPress  6.5.3 classic editor plugin 2024 theme. THis appears in the author section.

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    This problem may be a plugin or theme conflict. Please attempt to deactivate all plugins and switch to the default Twenty Twenty-Three theme. If the problem goes away, re-activate them one by one to identify the source of the problem.

    If you can install plugins, install Health Check. On the troubleshooting tab, you can click the button to deactivate all plugins and change the theme for you while you’re still logged in without affecting normal visitors to your site.

    If you can’t access these sections in your Dashboard either, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), navigate to /wp-content/themes/ and rename the directory of your currently active theme. Hopefully, this will force the default theme to activate and rule out a theme-specific issue (theme functions can interfere like plugins).

    Thread Starter koolkatwebdesigns

    (@koolkatwebdesigns)

    I still see the error editing posts after switch from the 2024 theme to 2023. I have the classic editor activated. All other plugins are deactivated.

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Does the issue go away with the Classic Editor plugin deactivated?

    What version of PHP are you running?

    Thread Starter koolkatwebdesigns

    (@koolkatwebdesigns)

    It works without the classic editor. I started looking into the issue because I had a problem with a custom theme where the custom post types (ACF) used the classic editor.

    Thanks.

    Thread Starter koolkatwebdesigns

    (@koolkatwebdesigns)

    PHP 8.0.30

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    In that case, I recommend reporting the issue at https://wordpress.org/support/plugin/classic-editor/ so the plugin’s developers and support community can help you with this.

    Thread Starter koolkatwebdesigns

    (@koolkatwebdesigns)

    Reported. Thanks for your help

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Argument #1 ($array) must be of type array, null given’ is closed to new replies.