Warning: Missing argument

On upgrading the Boxzilla plugin to Version 3.2.13 on two different sites running the Uncode theme, the entire website crashes with an error like this. Disabling 3.2.13 restores the website.

Fatal error: Uncaught ArgumentCountError: Too few arguments to function {closure}(), 3 passed in [redacted] on line 286 and exactly 4 expected in [redacted]wp-content/plugins/boxzilla/src/default-filters.php:24 Stack trace: #0 /home/[redacted]/public_html/wp-includes/class-wp-hook.php(286): {closure}(Array, Object(WP_Post), Object(stdClass)) #1 /home/[redacted]/public_html/wp-includes/plugin.php(208): WP_Hook->apply_filters(Array, Array) #2 /home/[redacted]/public_html/wp-content/themes/uncode/core/inc/wp-bootstrap-navwalker.php(164): apply_filters(‘nav_menu_link_a…’, Array, Object(WP_Post), Object(stdClass)) #3 /home/[redacted]/public_html/wp-includes/class-wp-walker.php(145): wp_bootstrap_navwalker->start_el(‘<li id=”menu-it…’, Object(WP_Post), 0, Object(stdClass)) #4 /home/[redacted]/public_html/wp-content/themes/uncode/core/inc/wp-bootstrap-navwalker.php(238): Walker->display_element(Object(WP_Post), Array, 0, 0, Array, ‘<li id=”menu-it…’) #5 /home/[redacted]/pu in /home/[redacted]/public_html/wp-content/plugins/boxzilla/src/default-filters.php on line 24
The site is experiencing technical difficulties.

I’m getting the same problem. I just deactivated it for now until someone here can help. Isn’t there a chat or an email we can send somewhere? I can’t find anything.

Hi there @bobthebirdkids I see you reported this thread to the moderators. Please note that we are just the folks who enforce the rules around all of www.ads-software.com.

Reporting to moderators doesn’t get any faster support, instead it just kind of attracts attention from folks whose radar you probably don’t want to be on. ??

If you really do need a moderator, please add a reply letting us know why before you hit the report button.

Otherwise, please hang in there for the plugin’s support to reply when they can.

Hey everyone, we just pushed an update in which this is resolved. Sorry for the hiccup!