And the sub sites work fine?
Hey,
check_is_admin() is using Group ID as second variable, $activity->item_id IS actually Group ID if $activity->component is ‘groups’, its the way BuddyPress store activity in database.
I’m using custom theme aswell, but I haven’t overrided ajax file.
Could you try to switch back to default theme for a moment and check if you will be able to delete activity from groups?
Also, to check if changes applied took place and are working you could add some echo before that access check in ajax files like
`echo ‘AJAX WORKING’`
and then use browser debug tool, for instance select “Inspect Element” in Chrome, select “Network” and after you press “Delete” link – there should be new request in “Network” to the file which actually is trying to delete activity. Select it and check repsonse body – if you see ‘AJAX WORKING’ there it will mean that the file you’ve modified is working.
For those still looking for a solution to this, you can add the following code to the functions.php file of your active theme. The username gets replaced with the username you wish to hide. Alternatively, you could substitute the stuff in the parens of the conditional with a properly done current_user_can() statement to hide all the administrators.
`
global $current_user;
get_currentuserinfo();
if( $current_user->user_login == ‘username’ ) {
remove_action(“wp_head”,”bp_core_record_activity”);
}
`
I’m having the same issue! My index.php was overwritten with what I’ve found is the buddypress forums/index.php page… so I’ve tried reverting to my original index.php (by deleting the BP code and pasting my original template code in)… and it’s not reflecting changes I’m making to the code on the front end. So, I figure it’s still referring to that original index file… somewhere! And it’s displaying something else within the WP Theme Editor.
I also installed the BP and BP template pack plugins to try and integrate them with an existing theme that I’ve already done a lot of work on, it’s not a specific BP theme.
Eeeek! If anyone can help, that’d be much appreciated. And I promise to be indebted to you forever and extoll your virtues to anyone who’ll listen. 
It sounds like you want to strip the default theme of all traces of the original developers “branding” and thus really remove all credit for the original piece of work. In relation to funtionality does it matter if function prefixes and other coding is marked bp_ ?
It seems a great deal of work (find & replace) for very little effect or reason? Is it really necessary or are you trying to create a whole new theme to perhapse “sell on”?
Did you enable multisite? Yes or no.
Thank you for your response, mrpavlikov, but unfortunately it doesn’t appear to have done the trick for me.
After closer inspection of your code, is it possible that the check_is_admin() function should use the Group ID as the second variable instead of the Activity ID? And if so, how do I reference the Group ID?
In case it makes a difference, I’m using a different theme than the bp-default theme that is contained within the plugins/buddypress directory, so I made the change that you suggested to the ajax.php file within both my child theme directory as well as within the plugins/buddypress/bp-themes/bp-default directory. I also made the change to buddypress/bp-activity.php, but it doesn’t seem to have done the trick.
Thanks again for your assistance, and to anybody else who might have some insight on the issue.
Our in-development version of BuddyPress has had its theme updated for this and many other issues. If you’re familiar with SVN, you can grab a copy from https://svn.buddypress.org/trunk/ — if not, check out a live demo site at http://testbp.org
@shanebp I tried that code, but I couldn’t get it working yet. Could you help me with it?
On my functions.php I added bp_send_private_bzzt, bp_send_private_bzzt_link and bp_get_send_private_bzzt_link.
I also added the buzzt link on my theme, but this new link gets me to a 404 page. I’m using the twentyten theme and bp-themplate-pack plugin.
a little more information:
the way I have it setup is I have a drop down category called “topics” which is a “subcategory” for “community”. So the file I use is “category-topics.php” which of course is in the “themes” folder.
All this file does is call the index.php file in the “forums” folder (not “groups”/”single”/”forum”). So I use this line
“
As I mentioned, this worked at first. It pulled the forums created by groups into a table. But when I changed the “main” url, it gave me the error.
you can visit the url here if you’d like: http://sociallyaffluent.com/sexyafter30/ (this is the main url…it’s a subfolder that holds the site…the “old” url was “sociallyaffluent.com/21andolder”…)
Ah knew there was a reason grr
Personally speaking I’ll generally be talking about trunk as I’m concentrating on working with =>1.3
The trick would be to find an action that happens after functions.php is loaded but before wp_print_style() happens. But, I’ve just remembered, as you’re talking about trunk, the bp_dtheme_enqueue_styles() is a pluggable function.
`function bp_dtheme_enqueue_styles() {}`
should stop it
I would love to know the answer to this as well if anyone is still watching this… Loved Theme my login…
Thanks guys! Will await this with anticipation! Any ETA?
@djpaul
Where are you calling it? from my desk, calling loudly towards the monitor but it doesn’t work.
Can’t be removing it before it’s been called can it? calling it in functions.php child theme and cycled through various priorities from your ’11’ down and up as it’s simply a remove_action() I expected it to work without issue, what am I missing then about functions.php loading order? However I prefer the approach to de-registering rather than leaving registered but simply not adding.
It should. Where are you calling it? Probably you are removing before it’s being added.
Creating a duplicate theme isn’t a problem. Like any other non-child theme, if any new features are added to BP or WP in the theme, you’ll need to add manually to your theme if you want to have them.
I havent run into this problem as of yet. How ever I will keep a look out. Currently – Like I said All I did was take the entire default theme, place its contents into a folder named after my new theme, changed ALOT of things – still trying to get rid of things like ‘buddypress’ and bp_ with out it breaking – and uploaded it to my site, the default theme is still there – it has not been moved, changed, deleted – just copied. the new theme is what I am currently using (which sits in my core wordpress theme directory). So I dont think anything will break in terms of buddyPress or WordPress
based on this information is there still a chance of breakage? even with a buddypress upgrade?
nav_row is after the content tag so look in index.php Should be there. Functions.php relates to custom functions for your theme, not to your nav.
Somewhere in your code there is the info that creates that navigation that’s under your logo. Put the code pcwriter mentioned there, it will generate the BP related menu items. My guess is its either in the Header.php(should be) or is called in the index.php file. If you are using a tool like dreamweaver or notepad++ you can just select your template folder and run the find comand, search “nav_row” and there it is!
Not using a child theme will create the chance for theme mistakes to break the site. That is why they are there. So if you create a new theme thats great, but BP-default has pretty much every case loaded into it, so if your child theme messes up its there to cover you. Thats the only issue I see. Also, there are situations where BP adds classes and style to elements in the DOM such as “accepted” to buttons, this is something to consider when creating a theme.
Your theme may be hiding it, but on mine, I see a line
“Foobar posted an update in the group [GROUP]: 3 hours ago · updated 1 hour, 17 minutes ago · View · Delete”
If you’re using a theme framework, there may be a hook you need to take advantage of. So yeah – talk to the theme author.
@jonobradley
Looks like you’ll have to contact the theme developer then to find out where the nav is, sorry can’t help more 
@jonobradley
Open your theme’s header.php (or equivalent) and find the code for your main navigation. In your theme, you’ll find it in div id="nav_row". There’s probably a call to wp_nav_menus there. Add the following before the closing ul tag (should work 😉 )
<li></li>
See the codex for more: https://codex.buddypress.org/theme-development/modifying-the-buddypress-admin-bar/
Hope this helps 🙂
