Opened 13 years ago
Closed 13 years ago
#3873 closed defect (bug) (fixed)
XMLRPC error
Reported by: | lancehudson | Owned by: | |
---|---|---|---|
Milestone: | 1.6 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Core | Keywords: | |
Cc: |
Description
On 1.6 bleeding (5577) getting
<br /> <b>Notice</b>: Trying to get property of non-object in <b>C:\Development\www\WordPress-Dev\wp-content\plugins\buddypress\bp-core\bp-core-loader.php</b> on line <b>170</b><br />
preventing xml-rpc clients from working. In my case turning off notices isn't an option.
Attachments (3)
Change History (13)
#2
@
13 years ago
Or, since we don't expose any of our API via XMLRPC, we could just not load BuddyPress in such situations.
#5
@
13 years ago
- Milestone changed from Awaiting Review to 1.6
I think it'll be easier to keep track of the cases where BP shouldn't load (XML-RPC may not be the only one) if we do it in the constructor.
#6
@
13 years ago
- Keywords reporter-feedback added
You know, the more I think about it, the more I'm nervous about simply killing BP on XMLRPC requests. There could be folks out there who are taking advantage of it, even though it's not an official use. (Not sure how, of course, but it's possible that someone has hacked something together.
lancehudson, can you test 3873.03.patch to see if it's enough to fix your problem? It's a much less broad changed.
Added, patch, feels like a hack though. Anyone know what implications it may have?