Title: WebDecoy's Replies | WordPress.org

---

# WebDecoy

  [  ](https://wordpress.org/support/users/webdecoy1/)

 *   [Profile](https://wordpress.org/support/users/webdecoy1/)
 *   [Topics Started](https://wordpress.org/support/users/webdecoy1/topics/)
 *   [Replies Created](https://wordpress.org/support/users/webdecoy1/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/webdecoy1/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/webdecoy1/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/webdecoy1/engagements/)
 *   [Favorites](https://wordpress.org/support/users/webdecoy1/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WebDecoy Bot Detection - Block AI Crawlers, Spam Bots & Card Testing] Fatals with 2.10.0](https://wordpress.org/support/topic/fatals-with-2-10-0/)
 *  Plugin Author [WebDecoy](https://wordpress.org/support/users/webdecoy1/)
 * (@webdecoy1)
 * [1 week, 3 days ago](https://wordpress.org/support/topic/fatals-with-2-10-0/#post-19030102)
 * Thanks for the report and the stack trace, and sorry about this. 2.10.0 called
   a class before the file that defines it was loaded, which caused a fatal error
   on every request, not only in WP-CLI. It’s fixed in 2.10.1, which is out now:
   wp plugin update webdecoy or update from the Plugins screen. We’ve also added
   a test that fails the build if this kind of load-order mistake comes back. Let
   me know if anything still looks off after updating.

Viewing 1 replies (of 1 total)