Title: Undefined array key Last modified: February 29, 2024 --- # Undefined array key * Resolved [Brisch](https://wordpress.org/support/users/brisch/) * (@brisch) * [2 years, 2 months ago](https://wordpress.org/support/topic/undefined-array-key-41/) * Hi, since your new update I get a Warning (see text below and the picure). I get it with different Themes and different Providers.Do you have any suggestions how to solve that? THANK YOU!!!Blessings, Brigitte**Warning**: Undefined array key “content” in **/srv/www/3/9/7/3977/www/www.kurs.wien/htdocs/brisch/wp3/wp- content/plugins/widget-options/includes/widgets/widgets.php** on line **56** * ![](https://i0.wp.com/www.kurs.wien/brisch/wp3/wp-content/uploads/2024/02/Widget- Options-Fehler.png?ssl=1) * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fundefined-array-key-41%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 4 replies - 1 through 4 (of 4 total) * Plugin Author [Mej de Castro](https://wordpress.org/support/users/mej/) * (@mej) * [2 years, 2 months ago](https://wordpress.org/support/topic/undefined-array-key-41/#post-17462959) * Hi [@brisch](https://wordpress.org/support/users/brisch/), We’ve release v4.0.1 that include fixes to Undefined array key PHP warning. Could you please update and let us know how it goes?Regards,Mej * Thread Starter [Brisch](https://wordpress.org/support/users/brisch/) * (@brisch) * [2 years, 2 months ago](https://wordpress.org/support/topic/undefined-array-key-41/#post-17463094) * Thanks for trying, unluckily the error is still there: * **Warning**: Undefined array key “content” in **/srv/www/3/9/7/3977/www/www.kurs. wien/htdocs/brisch/wp3/wp-content/plugins/widget-options/includes/widgets/widgets. php** on line **56** * Moderator [Support Moderator](https://wordpress.org/support/users/moderator/) * (@moderator) * [2 years, 2 months ago](https://wordpress.org/support/topic/undefined-array-key-41/#post-17463314) * [@brisch](https://wordpress.org/support/users/brisch/) *  Please don’t offer to send or post logon credentials on these forums: [https://wordpress.org/support/guidelines#the-bad-stuff](https://wordpress.org/support/guidelines#the-bad-stuff) * **It is not OK to offer, enter, or send site credentials on these forums.** Thanks for your cooperation. * [@mej](https://wordpress.org/support/users/mej/) * I’ve deleted your offer to login to your user’s site. I’m am 100% sure you mean well but please **never ask for credentials on these forums.** - [https://wordpress.org/support/guidelines/#the-bad-stuff](https://wordpress.org/support/guidelines/#the-bad-stuff) * Now for the why: The internet is a wonderful place full of very nice people and a few very bad ones. I’m sure everyone here is very nice however, by giving some ones keys to your house you are trusting they wont steal anything. Likewise the person who takes the keys is now responsible for the house FOREVER. * If something was to go wrong, then you the author may well legally become liable for damages, which they would not normally have been as their software is provided without warranty. * **Please be aware that repeatedly asking for credentials will result in us escalating this to the plugins team.** * It’s never necessary to do that. Here’s why. * There are many ways to get information you need and accessing the user’s site is not one of them. That’s going too far. - Ask for a link to the [https://pastebin.com/](https://pastebin.com/) or [https://gist.github.com](https://gist.github.com) log of the user’s web server error log. - Ask the user to create and post a link to their `phpinfo();` output. - Ask the user to install the [Health Check plugin](https://wordpress.org/support/plugin/health-check/) and get the data that way. - Walk the user through[ enabling WP_DEBUG](https://codex.wordpress.org/WP_DEBUG#WP_DEBUG_LOG_and_WP_DEBUG_DISPLAY) and how to log that output to a file and how to share that file. - Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again. - Ask the user for the step-by-step on how they can reproduce the problem. * You get the idea. * Volunteer support is not easy. But these forums need to a safe place for all users, experienced or new. Accessing their system that way is a short cut that will get you into real trouble in these forums. * Plugin Author [Mej de Castro](https://wordpress.org/support/users/mej/) * (@mej) * [2 years, 2 months ago](https://wordpress.org/support/topic/undefined-array-key-41/#post-17464759) * Hi [@brisch](https://wordpress.org/support/users/brisch/), Can you please try deactivating and deleting Widget Options, clear your website and hosting cache and then reinstall the latest version of the plugin.If the warning is still there, please open a support ticket [here](https://widget-options.com/contact/).Thanks- Mej - This reply was modified 2 years, 2 months ago by [Mej de Castro](https://wordpress.org/support/users/mej/). Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘Undefined array key’ is closed to new replies. * ![](https://ps.w.org/widget-options/assets/icon-256x256.gif?rev=2513739) * [Widget Options – Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets](https://wordpress.org/plugins/widget-options/) * [Frequently Asked Questions](https://wordpress.org/plugins/widget-options/#faq) * [Support Threads](https://wordpress.org/support/plugin/widget-options/) * [Active Topics](https://wordpress.org/support/plugin/widget-options/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/widget-options/unresolved/) * [Reviews](https://wordpress.org/support/plugin/widget-options/reviews/) ## Tags * [array key](https://wordpress.org/support/topic-tag/array-key/) * [warning](https://wordpress.org/support/topic-tag/warning/) * 7 replies * 3 participants * Last reply from: [Mej de Castro](https://wordpress.org/support/users/mej/) * Last activity: [2 years, 2 months ago](https://wordpress.org/support/topic/undefined-array-key-41/#post-17464759) * Status: resolved