Fatal PHP error thrown in versions 2.2.0, 2.2.1, 2.2.2.

[simondeeley]

I get the following error when activating your plugin in WordPress 3.4.2 running BuddyPress 1.6.1.

"Fatal error: Call to a member function get() on a non-object in /Users/username/Sites/hawthorn/wp-includes/query.php on line 27"

It seems that whatever code your plugin is calling it is throwing the error with a low-level WordPress function, which as of yet I've not been able to track back higher up the chain to which part of your plugin causes the error. For information, versions of your plugin prior to 2.2.0 were working perfectly fine without error and I'm running on PHP 5.4.1 on MacOS X/Apache.

The plugin in its current versions (2.2.0, 2.2.1, 2.2.2) does not cause the error whilst sitting in the plugins directory but deactivated, only when activated does it throw the error and on every page following that I try to access.

[truphat]

Having the same fatal error issue when installing upgrade 2.2.2.

[gagan0123]

Sorry for the trouble caused, and thanks for reporting the issue, we'll look into it and try to give a fix ASAP.

@donottumbledry : can you please mention which BuddyPress theme you are using and what other plugins you've installed with their versions?

[rahul286]

@donottumbledry & @truphat

Some more users reported same error:

Fatal error: Call to a member function get() on a non-object in /home/XXXXX/public_html/wp-includes/query.php on line 27

But we are not able to replicate it. We tried hard but its simply not coming on our sites. :|

Can we get access to error logs on your site where it is breaking? It will help us debug and find out any issue if exists in our code.

[simondeeley]

Which error logs would you like? The install I'm currently running is on my home machine so no publicly accessible logs but I can post snippets up.

[rahul286]

I will need access to Wordpress dashboard and FTP to enable/inspect logging.

If u can recreate issue on a public server, please send details to admin@rtcamp.com

---

By the way, have u tried running upgrade when other plugins are deactivated?

Also when buddypress default theme is active?

Sent from my iPhone

On 07-Nov-2012, at 12:14 AM, donottumbledry notifications@github.com wrote:

Which error logs would you like? The install I'm currently running is on my home machine so no publicly accessible logs but I can post snippets up.

—
Reply to this email directly or view it on GitHub.

[rahul286]

Also have u checked latest version 2.2.3?

Sent from my iPhone

On 07-Nov-2012, at 12:14 AM, donottumbledry notifications@github.com wrote:

Which error logs would you like? The install I'm currently running is on my home machine so no publicly accessible logs but I can post snippets up.

—
Reply to this email directly or view it on GitHub.

[simondeeley]

Interestingly, in 2.2.3 I no longer get the errors on the website itself, but I do get the error thrown when trying to view any admin pages/dashboard etc.

[rahul286]

We found few notices on front-end so it was fixed in 2.2.3 (ref: 9883a19)

We still couldn't reproduce admin-side issue.

Have u tried using BuddyPress-media with all other plugins disabled (except BuddyPress itself) AND with default BuddyPress theme?

[rahul286]

BuddyPress-Media v 2.2.5 fixes above issue. Tested here.

Please upgrade and let us know if you still encounter this issue after that.

[simondeeley]

Many many thanks for persevering with this!

You'll be happy to know that the issues experienced before have now gone. 👍

I ran through a complete "dry test" with the default theme and no plugins and slowly added each one back, one by one and finally added my custom theme. With version 2.2.3 your plugin worked with no issues. I've just upgraded to 2.2.5 with the plugin still active and everything worked fine. Once again, many thanks for your time and effort in pushing out incremental fixes! Out of curiosity - what did you do?

[rahul286]

You can check commit history. ;-)

Will send some details once I log back from my mac in morning.

It's 3AM here. On my way back to home.

Thanks a lot for your feedback. I can sleep peacefully tonight. :-)

Sent from my iPhone

On 08-Nov-2012, at 2:57 AM, donottumbledry notifications@github.com wrote:

Many many thanks for persevering with this!

You'll be happy to know that the issues experienced before have now gone.

I ran through a complete "dry test" with the default theme and no plugins and slowly added each one back, one by one and finally added my custom theme. With version 2.2.3 your plugin worked with no issues. I've just upgraded to 2.2.5 with the plugin still active and everything worked fine. Once again, many thanks for your time and effort in pushing out incremental fixes! Out of curiosity - what did you do?

—
Reply to this email directly or view it on GitHub.

[rahul286]

@donottumbledry & @truphat

Can u please confirm if version 2.2.5 worked for you?

If there any no further errors, then I will close this issue.

@donottumbledry

There was some code in bbPress which were conflicting with few other plugins. We can not fix other code but we restructured few things to avoid conflict with bbPress.