Title: bot-detect.php problem with WP super cache preloading
Last modified: July 27, 2023

---

# bot-detect.php problem with WP super cache preloading

 *  [Bobosom](https://wordpress.org/support/users/bobosom/)
 * (@bobosom)
 * [2 years, 10 months ago](https://wordpress.org/support/topic/bot-detect-php-problem-with-wp-super-cache-preloading/)
 * Plugin uses something called Cookie_Notice_Bot_Detect. If Cookie Notice detect
   crawler in list of UserAgents, then do not show cookie baner. Between this crawlers
   is also WordPress. And that was a problem, because WordPress as UserAgent makes
   preloading of WP super cache. Maybe also in others caching plugins it working
   similary.
 * When I erased ‘WordPress\/’, then preloading worked.
 * Can you please fix it? Because Wordfence now detects modified file.
 * Thank you in advance.

Viewing 1 replies (of 1 total)

 *  Plugin Author [dFactory](https://wordpress.org/support/users/dfactory/)
 * (@dfactory)
 * [2 years, 10 months ago](https://wordpress.org/support/topic/bot-detect-php-problem-with-wp-super-cache-preloading/#post-16941032)
 * Thanks – we’ll look into that.

Viewing 1 replies (of 1 total)

The topic ‘bot-detect.php problem with WP super cache preloading’ is closed to new
replies.

 * ![](https://ps.w.org/cookie-notice/assets/icon-256x256.png?rev=3549327)
 * [Compliance by Hu-manity.co](https://wordpress.org/plugins/cookie-notice/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cookie-notice/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cookie-notice/)
 * [Active Topics](https://wordpress.org/support/plugin/cookie-notice/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cookie-notice/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cookie-notice/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [dFactory](https://wordpress.org/support/users/dfactory/)
 * Last activity: [2 years, 10 months ago](https://wordpress.org/support/topic/bot-detect-php-problem-with-wp-super-cache-preloading/#post-16941032)
 * Status: not resolved