I started a thread with my specific problem which was a error while activating Beta 1.2 installed on standard WP 2.9.1,
“The plugin does not have a valid header.”
This thread was started in a effort to find more general information about installing for people new to buddypress.
The delete function is not working but don’t do this 
If you use the above logic and insert buddypress in the url called on delete, it deletes the whole page of comments. So be careful with that. It is obvious to me that the delete function is disabled by a call to the wrong virtual url. I will try to figure that out based on what I have learned.
Steve
I modified the define in Bp-activity.php and while it made the RSS function work on the sitewide activity it also made the other rss links fail. I suggest a patch in the code to allow immediate functionality while I look further for the complete solution.
Here is my suggestion. find: yourdomainsetup/wp-content/plugins/buddypress/bp-activity/bp-activity-widgets.php and download the file as a backup or keep a copy in the folder on your server with a slightly modified name so you can change it back if you have issues after this patch.
type this line into a web browser and see if it gives you your feed, change your domain and install folder to the values for your site;
http://yourdomain/installfolder/buddypress/activity/feed
if it does, tell the PHP code to call it as follows
go to the same file; yourdomainsetup/wp-content/plugins/buddypress/bp-activity/bp-activity-widgets.php
edit the statement line (should be line 23) in bp-activity-widgets.php
that reads;
href=”‘ . bp_get_sitewide_activity_feed_link() . ‘”
to; href=”http://yourdomain/installfolder/buddypress/activity/feed”
Please report back the success or failure of this procedure. It seems possible that the inability to delete entries on the activity widget could be related to this. I will keep looking.
If you see a mistake in my instructions please correct them.
document this edit for yourself in case you need to change it back at a later date
Steve
6 hours and yusoof hasn’t responded yet? Is he even reading his own topic to know we’re trying to help him? 
Akismet can sometimes be a little over sensitive, so taking the bad with the good means some false positives from time to time.
If you’re having issues on BuddyPress.org with your posts or topics going rogue, send myself or another moderator a PM and I’ll make them appear again. If it’s an urgent topic let me know on Twitter: @johnjamesjacoby
Also, do this too.
The virtual url call is incorrect. the main page calls http://yourdomain/installfolder/activity/feed and does not work. On my site the feeds work on the profile page and any member page but not the site feed.
If you call this url directly and get the feed; http://yourdomain/installfolder/buddypress/activity/feed
then changing the call will fix it. I will be back with that solution as soon as I have it.
1. Which version of WP/MU are you running?
Wp 2.9.1 single user
2. Did you install WP/MU as a directory or subdomain install?
subdomain
3. If a directory install, is it in root or in a subdirectory?
yes root
4. Did you upgraded from a previous version of WP/MU? If so, from which version?
New install
5. Was WP/MU functioning properly before installing/upgrading BuddyPress (BP)? e.g. permalinks, creating a new post, commenting.
yes
6. Which version of BP are you running?
bp 1.2beta
7. Did you upgraded from a previous version of BP? If so, from which version?
no
8. Do you have any plugins other than BuddyPress installed and activated?
no
9. Are you using the standard BuddyPress themes or customized themes?
default
10. Have you modified the core files in any way?
no
11. Do you have any custom functions in bp-custom.php?
no
12. If running bbPress, which version? Or did your BuddyPress install come with a copy of bbPress built-in?
bp 1.0.2
13. Please provide a list of any errors in your server’s log files.
which log file?
14. Which company provides your hosting?
hostgator
When you upgrade to BP 1.2, you can use the BP backwards compatibility plugin:
https://wordpress.org/extend/plugins/buddypress-backwards-compatibility/
That will probably be the easiest way to keep your template tags.
Read this blog post:
https://buddypress.org/blog/news/buddypress-1-2-beta/
Also what are these “errors” you speak of? Is it theme-related? Is it plugin-related?
Are you installing BP 1.2 beta on WPMU or standard WordPress?
If you grabbed a zip of the trunk, then it’s in a folder called “trunk” when you unzip it.
rename the folder to buddypress.
Your error logs woudl definitely have given you this clue.
It’s possible the wizzes behind BP haven’t responded because you haven’t given enough information to determine if this is user error, bug or random glitch. There should be instructions for posting questions and they should include what you need to let us know to help you.
9 hours and no simple answer? Is anyone even reading this forum that knows whats going on?
@Andy
Thanks! I’ve had that one bookmarked for a while.
I’ve been learning what (I think) I need to about the web for a couple of years, building sites, dabbling with this and with that. Just when I’m ready to begin developing the project I’ve had in mind for years – a community support network for recovering alcoholics & addicts – I stumble upon Buddypress. That’s serendipity.
Thanks to you and the gang for all the work you guys have put into this.
Thanks – I didn’t know that. I updated to trunk now and it seems to work. I think there are some issues, still (at least in my install):
1. Twitter: The latest tweet showing is 4 days old… (many more tweets in the time between
2. Twitter & External-Group-Blog: In other languages – in my case german – the “Umlaute” like äöü are showing strange like ü (I guess this is an easy one )
3. External-Group-Blog: The latest rss-entry showing is about 3 days old – there were many others in between
4. The “view” of an item from those plugins does not show in the “normal” narrow-way, but is just in the group (but mybe that’s on purpose…)
A further suggestion:
Wouldn’t it be nice, when tweets with a @somebody wouldn’t be fetched/showed… It could be pretty confusing with ¨@somebodys from twitter and other ¨@username from buddypress…
But besides that: Thanks for the update. Great additions!!!
I’m up for it ~ https://codex.buddypress.org/how-to-guides/install-buddypress-on-a-secondary-blog/
~ although it’s my first codex edit (w00t).. so ya’ll may want to review it! *and note that the ‘home’ in the secondary nav is pointing to MEMBERS_SLUG in the codex.
If fact, this is a problem with your theme, please follow the instructions on this post for upgrading:
https://buddypress.org/blog/news/buddypress-1-2-beta/
In the theme that you are running look for the file called screen.css
in it you can find the header section something that looks like:
/*** Header ************************************************************/
#header {
overflow: auto;
width: 100%;
background: #fff url(../images/LogoBanner.png) top left no-repeat;
}
it is a background image that points to a file in the images folder.
I am sure you can take it from there.
henrybaum, you might want to try using gettext filter instead of hacking core file. Went through this a week ago when I wanted to cut down big chunks of code and DJ Paul pointed me to the right and much easier direction,
Okay – so new problem.
To test further, I deactivated the BuddyPress plugin – and still, it’s adding an extra “wmpu/” into the URL, for some reason. i seriously, have *no* idea what’s happening now.
I’ve checked wildcards with zoneedit.com – set to *.bp-tech.net > http://www.bp-tech.net/wpmu – which is the address. sooooo lost.
***UPDATE**
okay – fixed that. changed wildcard to just http://www.bp-tech.net and it stopped the addition of the second “wpmu/”
but still – same problem. back to all of the BP links returning 404s. i dont understand?
More troubleshooting – something is wrong with whatever/however buddypress sets the virtual directories, i think. not an expert (obviously 
) but thats what its pointing to for me.
added a blog through the admin dashboard, assigned it to the user i created. when i log in as that user, and attempt to view my dashboard/add/edit/view/manage posts, i get the address:
http://www.bp-tech.net/wpmu/wpmu/wp-admin/?c=1
which has one extra root DIR. i tried removing the extra “wpmu/” in the URL and loading again, it reverted back to the above and showed 404.
I can’t find any directory related settings/information. But something is clearly wrong with the way mu and bp work together in regards to directory/url locations on my install, i think.
Hi there!
I’m actually running a trunk version of Buddypress not on MU, but on a single user WP platform. Could this have something to do with it? Everything else is working fine as intended though? I followed instructions from here:
http://wpmu.org/buddypress-now-supports-wordpress-single-user-no-wpmu-required/
And the theme I’ve yet to design, I’m using the pre-packaged standard one for now.
Cheers
