Title: [Plugin: Bogo] Fatal error when using trunk version
Last modified: August 20, 2016

---

# [Plugin: Bogo] Fatal error when using trunk version

 *  Resolved [raymer](https://wordpress.org/support/users/raymer/)
 * (@raymer)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-bogo-fatal-error-when-using-trunk-version/)
 * Is any active development happening on this plugin? I really like it but anytime
   I update to the trunk version in svn I get:
    “Fatal error: Call to a member function
   get() on a non-object in /usr/home/myuser/mywebsite/wp-includes/query.php on 
   line 27”
 * I have to roll-back to ver. tag 1.1 to get rid of the error.
 * I am about to update some sites to WP version 3.4 and I want to make sure this
   plugin will still work before I do…
 * -Ray
 * [http://wordpress.org/extend/plugins/bogo/](http://wordpress.org/extend/plugins/bogo/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Takayuki Miyoshi](https://wordpress.org/support/users/takayukister/)
 * (@takayukister)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-bogo-fatal-error-when-using-trunk-version/#post-2846584)
 * Yes, active development is happening. Trunk is a place for the purpose. Please
   use stable version 1.1.

Viewing 1 replies (of 1 total)

The topic ‘[Plugin: Bogo] Fatal error when using trunk version’ is closed to new
replies.

 * ![](https://ps.w.org/bogo/assets/icon-256x256.png?rev=1047282)
 * [Bogo](https://wordpress.org/plugins/bogo/)
 * [Support Threads](https://wordpress.org/support/plugin/bogo/)
 * [Active Topics](https://wordpress.org/support/plugin/bogo/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bogo/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bogo/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Takayuki Miyoshi](https://wordpress.org/support/users/takayukister/)
 * Last activity: [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-bogo-fatal-error-when-using-trunk-version/#post-2846584)
 * Status: resolved