• Resolved acgm2023

    (@acgm2023)


    Hi,

    What could be causing this error? The AccessiBe support chat could not help me.

    Warning: Undefined array key “triggerIcon” in /home/www/wp-content/plugins/accessibe/class.accessibeforwp.php on line 212

    and

    Warning: Undefined array key “triggerIcon” in /home/www/wp-content/plugins/accessibe/class.accessibeforwp.php on line 213

    I googled this error and found it in other websites, but no solution anywhere, so please respond.

    • This topic was modified 11 months ago by acgm2023.

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

Viewing 1 replies (of 1 total)
  • Thread Starter acgm2023

    (@acgm2023)

    I have found a solution with the help of Grok 3 and Google Inspect. I had to remove the configuration object from acsbJS.init() to fix the Google Inspect warning: “The dashboard is providing the widget’s configuration, so this local acsbJS.init call with its own settings is redundant and ignored, triggering the warning.”

    Find this section : /** * Render js in footer */ in class.accessibeforwp.php, starting on line 185 (footer for me, maybe it show differently for you, if you chose position top or center) and substitute the code including line 221, with the following code:

    /** * Render js in footer */ public static function accessibe_render_js_in_footer() { $accessibe_options = self::accessibe_get_options(); $current_domain = self::sanitizeDomain(wp_parse_url(site_url())[‘host’]); // $current_domain = ‘9cc3-2405-201-5c0f-d070-14fd-b303-b02-1999.ngrok-free.app’; if ((!isset($accessibe_options[‘accessibe’]) && (!isset($accessibe_options[‘script’]) || !isset($accessibe_options[‘script’][$current_domain]))) || (isset($accessibe_options[‘accessibe’]) && ‘enabled’ != $accessibe_options[‘accessibe’] && (!isset($accessibe_options[‘script’]) || !isset($accessibe_options[‘script’][$current_domain]))) || (isset($accessibe_options[“script”][$current_domain]) && $accessibe_options[“script”][$current_domain][‘widgetStatus’] != true)) { echo “<script>console.log(“.wp_json_encode($accessibe_options).”)</script>”; } if (isset($accessibe_options[“script”][$current_domain]) && $accessibe_options[“script”][$current_domain][‘widgetStatus’] != true) { return false; } echo “<script>(function(){var s=document.createElement(‘script’);var e = !document.body ? document.querySelector(‘head’):document.body;s.src=’https://acsbapp.com/apps/app/dist/js/app.js&#8217;;s.setAttribute(‘data-source’, ‘WordPress’);s.setAttribute(‘data-plugin-version’, ‘”.esc_js(self::accessibe_get_plugin_version()).”‘);s.defer=true;s.onload=function(){acsbJS.init();};e.appendChild(s);}());</script>”; } // accessibe_render_js_in_footer /** * Reset accessibe_pointers */ public static function accessibe_reset_pointers() { $accessibe_pointers = array(); $accessibe_pointers[‘welcome’] = array(‘target’ => ‘#menu-settings’, ‘edge’ => ‘left’, ‘align’ => ‘right’, ‘content’ => ‘Thank you for installing the <b>Web Accessibility by accessiBe</b> plugin. Please open <a href=”‘ . admin_url(‘admin.php?page=accessibe’) . ‘”>Web Accessibility by accessiBe</a> to configure it.’); update_option(ACCESSIBE_WP_POINTERS_KEY, $accessibe_pointers); } // reset_accessibe_pointers

    It worked perfectly. I hope you guys from AccessiBe take some action on this in a near future.

Viewing 1 replies (of 1 total)

The topic ‘Undefined array key “triggerIcon”’ is closed to new replies.