Title: Undefined array key “triggerIcon”
Last modified: April 7, 2025

---

# Undefined array key “triggerIcon”

 *  Resolved [acgm2023](https://wordpress.org/support/users/acgm2023/)
 * (@acgm2023)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/undefined-array-key-triggericon/)
 * 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 1 year, 1 month ago by [acgm2023](https://wordpress.org/support/users/acgm2023/).
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fundefined-array-key-triggericon%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  Thread Starter [acgm2023](https://wordpress.org/support/users/acgm2023/)
 * (@acgm2023)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/undefined-array-key-triggericon/#post-18403999)
 * 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](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.

 * ![](https://ps.w.org/accessibe/assets/icon.svg?rev=3375045)
 * [Web Accessibility by accessiBe](https://wordpress.org/plugins/accessibe/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/accessibe/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/accessibe/)
 * [Active Topics](https://wordpress.org/support/plugin/accessibe/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/accessibe/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/accessibe/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [acgm2023](https://wordpress.org/support/users/acgm2023/)
 * Last activity: [1 year, 1 month ago](https://wordpress.org/support/topic/undefined-array-key-triggericon/#post-18403999)
 * Status: resolved