Title: Shows warning errors
Last modified: March 7, 2019

---

# Shows warning errors

 *  Resolved [anjanphukan](https://wordpress.org/support/users/anjanphukan/)
 * (@anjanphukan)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/shows-warning-errors/)
 * Please check the screenshot [here](https://www.awesomescreenshot.com/image/3903921/5dfeaabf387937f837d564e39679d00a).
   It shows some warning saying:
 * `Warning: key() expects parameter 1 to be array, null given in SERVER_PATH/wp-
   content/plugins/content-control/classes/Is.php on line 36`

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Thread Starter [anjanphukan](https://wordpress.org/support/users/anjanphukan/)
 * (@anjanphukan)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/shows-warning-errors/#post-11285260)
 * On enabling WP_DEBUG got the following messages:
 *     ```
       Notice: Undefined index: which_users in SERVER_PATH/wp-content/plugins/content-control/classes/Site/Widgets.php on line 47
   
       Notice: Undefined index: roles in SERVER_PATH/wp-content/plugins/content-control/classes/Site/Widgets.php on line 47
   
       Warning: key() expects parameter 1 to be array, null given in SERVER_PATH/wp-content/plugins/content-control/classes/Is.php on line 36
       ```
   
 *  [moisb](https://wordpress.org/support/users/moisb/)
 * (@moisb)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/shows-warning-errors/#post-11312991)
 * I also see several PHP warnings like this:
    Notice: Undefined index: selected
   in wp-content\plugins\content-control\classes\Condition_Callbacks.php on line
   162
 * the plugin has not been updated for more than 1 year, and is probably obsolete
   for PHP 7+
 * it seems that the author has abandoned development, so at this point it is wise
   to look for another plugin
 *  Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/)
 * (@danieliser)
 * [7 years, 1 month ago](https://wordpress.org/support/topic/shows-warning-errors/#post-11479686)
 * [@anjanphukan](https://wordpress.org/support/users/anjanphukan/) – These errors
   indicate missing data in your plugin settings for some reason. I can add sanity
   checks to prevent errors from showing.
 * [@moisb](https://wordpress.org/support/users/moisb/) – No offense, but bad assumptions
   all around, only thing you got right was time since update. I will admit I missed
   a few tickets here the past couple months, but this plugin is so sporatic in 
   terms of support requests.
 * And if you check I have plenty of other plugins that don’t get updated often,
   most simply don’t require it, others have everything they need and no feature
   requests. Not gonna push updates just to push them, that is wasteful of my time
   and yours.
 * As for PHP 7 support, it was origianlly developed on PHP 7.1 well before most
   people were even getting access to 7.0. I typically develop on the latest stable
   at all times.
 * Now specifically your error indicates you chose a specific condition that has
   a `selected` field, something like Page Selected etc, and the field data was 
   somehow lost, not saved, or corrupted, try adjusting your settings for each one
   specificaly the conditions.
 * Hope that helps, but be aware, lack up pushed updates !== lack of dev support.
   If you check my other plugins you will see why this one is low priority, I manage
   support for all of those users (~400k) by myself currently ;).
    -  This reply was modified 7 years, 1 month ago by [Daniel Iser](https://wordpress.org/support/users/danieliser/).
 *  Thread Starter [anjanphukan](https://wordpress.org/support/users/anjanphukan/)
 * (@anjanphukan)
 * [7 years, 1 month ago](https://wordpress.org/support/topic/shows-warning-errors/#post-11481178)
 * Hi [@danieliser](https://wordpress.org/support/users/danieliser/), I used this
   plugin mainly for conditional redirection of pages. I already checked the plugin
   settings, disabled and deleted the plugin and reinstalled it and deleted the 
   Content Control settings and created them again, but without any luck. So I ended
   up using a different plugin for redirection. Sorry for that. Regards.
 *  Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/)
 * (@danieliser)
 * [7 years, 1 month ago](https://wordpress.org/support/topic/shows-warning-errors/#post-11483168)
 * [@anjanphukan](https://wordpress.org/support/users/anjanphukan/) – Not a problem,
   I have added some checks in the lines you mentioned before to ensure that warnings
   don’t show up for users. Was that the only issue you had with it was they appeared
   on your site, or was it not functioning like you needed as well?
 *  Thread Starter [anjanphukan](https://wordpress.org/support/users/anjanphukan/)
 * (@anjanphukan)
 * [7 years, 1 month ago](https://wordpress.org/support/topic/shows-warning-errors/#post-11483188)
 * Hi [@danieliser](https://wordpress.org/support/users/danieliser/), I think that’s
   the only issue I had.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Shows warning errors’ is closed to new replies.

 * ![](https://ps.w.org/content-control/assets/icon-256x256.gif?rev=2968535)
 * [Content Control - The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks & More](https://wordpress.org/plugins/content-control/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/content-control/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/content-control/)
 * [Active Topics](https://wordpress.org/support/plugin/content-control/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/content-control/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/content-control/reviews/)

## Tags

 * [notice](https://wordpress.org/support/topic-tag/notice/)
 * [warning](https://wordpress.org/support/topic-tag/warning/)

 * 6 replies
 * 3 participants
 * Last reply from: [anjanphukan](https://wordpress.org/support/users/anjanphukan/)
 * Last activity: [7 years, 1 month ago](https://wordpress.org/support/topic/shows-warning-errors/#post-11483188)
 * Status: resolved