#3260 closed defect (bug) (wontfix)
Non-object error tossed by WP 3.2 beta 2 + BP 1.3 bleeding
Reported by: | zamoose | Owned by: | |
---|---|---|---|
Milestone: | 1.5 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Core | Keywords: | |
Cc: |
Description
All pages see the following using the latest WP and BP trunks:
[Notice: Trying to get property of non-object in /Applications/MAMP/htdocs/wp-content/plugins/buddypress/bp-members/bp-members-template.php on line 847
]
Change History (10)
#2
@
14 years ago
Sorry, I neglected to mention this is with WP_DEBUG enabled. Do you have it in place?
#3
@
14 years ago
This occurs with WP trunk + BP 1.2 as well. See, e.g., http://lblg.zamoose.org
#4
@
14 years ago
I did. Still can't recreate it, especially if you can on "any page." What theme and do you have any other plugins enabled?
#5
@
14 years ago
I can recreate that on any BuddyPress page. Normal pages render fine, though the BP PHP error strings still spew.
Theme is my own custom, with templates taken from the BP Template Pack for BP support.
I have, on my local install, the following plugins active:
- BuddyPress (obviously)
- Log Deprecated Notices
- Markdown On Save
- Theme Check
- WordPress Importer
None of those, by my light, should affect BP in the slightest. The live sight has the same plugins active, minus Markdown On Save.
I've deactivated all plugins but have not deactivated BuddyPress itself on the live site -- same issue.
#6
@
14 years ago
The net effect is that no BP-specific loops seem to get rendered and page rendering dies.
#7
@
14 years ago
- Version changed from 1.3 to 1.2.8
Okay, must've gotten some wires crossed. This definitely occurs with 1.2.8 but *not* with trunk.
#8
@
14 years ago
- Resolution set to wontfix
- Status changed from new to closed
We aren't patching the 1.2 branch for this sort of issue. Great to hear it is okay in trunk though, thanks for checking.
#9
@
14 years ago
We aren't patching the 1.2 branch for this sort of issue. Great to hear it is okay in trunk though, thanks for checking.
We should talk about this policy at the next dev chat. If 1.3 is going to continue to be delayed, it might be worth relaxing this policy so that we can release a point release that cleans up some of the more egregious errors.
I can't recreate.