Title: Undefined index and array key errors
Last modified: April 20, 2021

---

# Undefined index and array key errors

 *  Resolved [spiros](https://wordpress.org/support/users/spiros/)
 * (@spiros)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/undefined-index-and-array-key-errors/)
 * I get the errors below (php 8) so I had to deactivate:
 *     ```
       Notice: Undefined index: allowed_click in /home/mysite/public_html/wp-content/plugins/quick-adsense-reloaded/includes/conditions.php on line 290
       Notice: Undefined index: ban_duration in /home/mysite/public_html/wp-content/plugins/quick-adsense-reloaded/includes/conditions.php on line 292
       Warning: Undefined array key "allowed_click" in /home/mysite/public_html/wp-content/plugins/quick-adsense-reloaded/includes/conditions.php on line 290
       ```
   
    -  This topic was modified 5 years, 1 month ago by [spiros](https://wordpress.org/support/users/spiros/).
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fundefined-index-and-array-key-errors%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Support [WPQuads Support](https://wordpress.org/support/users/wpquadssupport/)
 * (@wpquadssupport)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/undefined-index-and-array-key-errors/#post-14341829)
 * Can you please check it once by disabling click fraud detection and let us know
   back?
 *  Thread Starter [spiros](https://wordpress.org/support/users/spiros/)
 * (@spiros)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/undefined-index-and-array-key-errors/#post-14341860)
 * Yes, that is the culprit.
 *  Plugin Support [WPQuads Support](https://wordpress.org/support/users/wpquadssupport/)
 * (@wpquadssupport)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/undefined-index-and-array-key-errors/#post-14342639)
 * Now that resolved the issue? If YES – mark it as resolved and you have any other
   queries or the issue, please create a new topic.
 *  Plugin Support [WPQuads Support](https://wordpress.org/support/users/wpquadssupport/)
 * (@wpquadssupport)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/undefined-index-and-array-key-errors/#post-14343146)
 * Extremely Apologies for the previous reply, We have raised a GitHub ticket regarding
   these errors. Our developers will work on this and will fix it ASAP!
 * Please track the below ticket for reference:
    [https://github.com/wpquads/quick-adsense-reloaded/issues/350](https://github.com/wpquads/quick-adsense-reloaded/issues/350)
 *  Plugin Support [WPQuads Support](https://wordpress.org/support/users/wpquadssupport/)
 * (@wpquadssupport)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/undefined-index-and-array-key-errors/#post-14379644)
 * The issue regarding Undefined index and array key errors has been fixed in our
   latest update(2.0.26). Can you please check it once by updating the plugin and
   let us know back?

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

The topic ‘Undefined index and array key errors’ is closed to new replies.

 * ![](https://ps.w.org/quick-adsense-reloaded/assets/icon-256x256.png?rev=2369641)
 * [Quads Ads Manager for Google AdSense](https://wordpress.org/plugins/quick-adsense-reloaded/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/quick-adsense-reloaded/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/quick-adsense-reloaded/)
 * [Active Topics](https://wordpress.org/support/plugin/quick-adsense-reloaded/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/quick-adsense-reloaded/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/quick-adsense-reloaded/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [WPQuads Support](https://wordpress.org/support/users/wpquadssupport/)
 * Last activity: [5 years, 1 month ago](https://wordpress.org/support/topic/undefined-index-and-array-key-errors/#post-14379644)
 * Status: resolved