BuddyPress.org

I am now learning that this isn’t the only BuddyPress delete hook that is placed in this way. I’d also like to hook into groups_remove_data_for_user(), but same deal – the action is triggered only *after* the user’s group membership data has occurred (and that’s the data I need access to for Google Docs). I’m going […]

Thanks for the quick reply, Paul. I did what you said, and the errors disappeared so long as BP was disabled. They came back as soon as I re-enabled it. But at least now I have super-admin access again. I had to disable all the plugins to get that to happen. I did a mysqlcheck […]

There’s no reason we should suddenly be exceeding 256 MB of memory on every wp-admin dashboard request. I think this must be related to the MySQL-Link errors.

Also noticed this error on the Dashboard under the QuickPress section:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 64 bytes) in /home/wmaster/yexpress.net/wp-includes/wp-db.php on line 1315

No worries – we decided not to take this route after all. Instead we’ll add a new function “Request to close topic”, which will message the group admin/moderator, who does have the power to accomplish this.

Since I’m trying to meet a deadline I’m just going to leave this for now, and make do with accessing the page from the member domain (i.e., /members//groupdir). But if anyone has any inkling as to why accessing /groupsdir as a root component is redirecting me to the home page, I’d be most appreciative! I […]

Thanks, @jeffsayre. I must have missed that page when I was browsing the Codex. I was following the Skeleton Component because my coworkers had recommended it to me. However, apparently none of them tried writing a BP plugin that provided a root component! Now my problem isn’t that I’m getting a 404 error anymore. Instead, now […]

Thanks, you two. This sort of info would be fantastic to include in the Codex and as revisions to the Skeleton Component so more of us don’t spend days scratching our heads. 🙂

Well I couldn’t resist investigating further, and it turns out that the code that BuddyPress runs to compare the URL to the $bp->root_components array happens during the bp_loaded action, which happens during the WP plugins_loaded action, which seems to happen *before* the bp_init action – which is the action I’m supposed to use to cause […]

Tried changing the priority of add_action( 'wp', 'bp_gdatree_setup_root_component' ) – still no difference. Can’t seem to scrap the 404 no matter what I try. I’m out of ideas.

Could it have to do with the order that bp_gdatree_setup_globals, bp_gdatree_setup_nav, and bp_gdatree_setup_root_component are run in…? I’m not sure what the correct order is.

(Oops – make that /members//groupsdir)

Well, still no luck. I added this to my code: function bp_gdatree_setup_root_component() { /* Register 'groupsdir' as a root component */ bp_core_add_root_component( BP_GDATREE_SLUG ); } add_action( 'wp', 'bp_gdatree_setup_root_component' ); add_action( 'admin_menu', 'bp_gdatree_setup_root_component' ); Again, I used an echo statement to verify…[Read more]

Wow, well I had no idea. Where in the skeleton component do you see this mentioned? That’s exactly what I’ve been following to build my plugin. Then I started looking into the messages component to see if there was something I was missing, but didn’t make any headway. I guess I didn’t look at enough […]