New version (1.2.6) immediately throws an Uncaught ArtumentCountError

  • Resolved rbrunskill

    (@rbrunskill)


    2 years ago

    I don’t know about others, but it looks like, for me, the newly released version needs to be avoided. Even when it’s the only plugin, AllAccessible throws the following error. The site is running on LocalWP with WP version 6.1.1, Apache, PHP8, and MySQL 8.0.16. Version 1.2.5 had no issues.

    Fatal error: Uncaught ArgumentCountError: _() expects exactly 1 argument, 2 given in /siteroot/wp-content/plugins/allaccessible/allaccessible.php:167 Stack trace: #0 /siteroot/wp-content/plugins/allaccessible/allaccessible.php(167): _(‘Are you enjoyin…’, ‘allaccessible’) #1 /siteroot/wp-includes/class-wp-hook.php(308): aacb_feedback_notification(‘plugins.php’) #2 /siteroot/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #3 /siteroot/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #4 /siteroot/wp-admin/admin-header.php(118): do_action(‘admin_enqueue_s…’, ‘plugins.php’) #5 /siteroot/wp-admin/plugins.php(605): require_once(‘/siteroot/…’) #6 {main} thrown in /siteroot/wp-content/plugins/allaccessible/allaccessible.php on line 167

    The public version of the site works, but the admin side throws the above error. I initially updated from 1.2.5, then tried removing the plugin and installing 1.2.6 from scratch. Same problem.

    • This topic was modified 2 years ago by rbrunskill.
    • This topic was modified 2 years ago by rbrunskill.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author AllAccessible

    (@allaccessible)

    We’ve made some adjustments to the code and pushed out 1.2.7. Can you please try that version of the plug in line and let us know if that resolve the issues?

    Thread Starter rbrunskill

    (@rbrunskill)

    It looks like 1.2.7 fixes the issue. I ran an update on the same dev host and 1.2.7 works fine. Thanks!

    • This reply was modified 2 years ago by rbrunskill.
    Plugin Author AllAccessible

    (@allaccessible)

    That’s great to hear, thanks for the update!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘New version (1.2.6) immediately throws an Uncaught ArtumentCountError’ is closed to new replies.