@DJPaul – I understand. However, having tested in dev installs to WP 3.0 RC2 and not getting the smooth experience I have on WPMU 2.9.2 with BP 1.2.4.1 and with all preferred BP plugins working; I can only recommend using WP 3.0 with BP 1.2.4.1 in test/dev installs and not in production/live installs.
There are 5 ways to test BuddyPress with WordPress 3.0 and I’ve tested four of those configs:
1) WP 3.0 single (new install) – “Page Not Found” for BP components. Preferred BP plugins not working as they have not been upgraded to work with WP 3.0.
2) WP 3.0 multisite subdomain (new install) – “Page Not Found” for BP components. Enable MULTIBLOG renders BP links in subsites to go to home page. preferred BP plugins not working as they have not been upgraded to work with WP 3.0
3) WP 3.0 multisite subdirectory – did not test – I’ve heard that this set up is working for some friends and per posting in WP.org forums
4) WPMU 2.9.2 subdirectory upgraded to WP 3.0 – same as #2 above
5) WPMU 2.9.2 subdomain upgraded to WP 3.0 – same as #2 above
Maybe I’ll try to test the 4 configs I have for WP RC3 and see what happens this weekend or next.
@nuprn1 Hmm… maybe I have done something wrong but I have pasted the code in and yet I can’t see a widget?
@nuprn1 Thanks so much.
So I have pasted that code into my bp-custom.php file.
So should the widget show up or do I need to activate the sub plugin. Will that not activate the forum index with it? I just need the widget. We’re nearly there!
@prerna I recommend you a wordpress redirection plugin – it also counts redirects etc.
@nuprn1 Sorry for having to ask such simple questions but I am exactly that… Simple!
Wen you say ,’place this class BP_Forum_Extras_Index_Latest_Topics_Widget extends WP_Widget into the bp-custom.php file’
What am I actually placing in the custom php file?
I’m not sure how much of the code I am cutting and pasting?
So sorry, I’m just learning!
Thanks so much!
@r-a-y
Thanks for your help, I have seen this page before and the solution in, but it cause error on the admin profile cause it stay in the old /members/ URL
I asked it here before:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/bp_enable_root_profiles-on-mu-problem-admin-profile-link-is-broken/
Isn’t there any other solution like hataccess rules or so on?
Thanks again.
Similar issue as Tom…
On my local MAMP environment, I set up WP 3.0 RC3 and BP1.4.2.1 (running on MySQL Server version: 5.1.37 and PHP Version 4). Smooth sailing – I can access /wp-admin and site administration works properly.
When I attempted to set up the same configuration (WP 3.0 RC3 and BP1.4.2.1) on my remote hosted environment (running on MySQL Server version: 5.0.77 and PHP Version 5.2.13), as soon as I click the ‘activate’ link for the BuddyPress plugin from the Site Administration area, the browser attempts to load the following URL:
/wp-admin/plugins.php?activate=true&plugin_status=all&paged=1
but only displays a blank page.
All further attempts to access the /wp-admin pages results in the blank page.
If I navigate to the site front end, I’ll see the default theme and then at the bottom of the page, the un-styled textual content of the BP installation. See here: http://linchpinhq.org
If I manually delete the BuddyPress directory from my server, I’m able to access the site administration area again.
I’ve tried a few variations:
– WP 2.9.2 + BP 1.4.2.1 – same issue on remote server
– WP 3.0 RC3 nightly build + BP 1.4.2.1 – same issue on remote server
Is this an issue with the version of PHP/MySQL running on my remote hosted environment?
@nuprn1 Great stuff! This is exactly what I need but I only need the widget and not the index. The index is a great idea but I have 2000 groups so isn’t really suitable.
I’m a bit of a numpty when it comes to extracting code but would really like to hear how I can use just the widget without the index! I’d even pay for this to be made into a standalone widget.
Cheers
Ross 
@slaffik – Hmm… make sure you’re using the latest code as the older ones I posted on Pastebin did not hook into the right action.
Also double check the wp_bp_activity table and make sure for the “new_blog_post” type that the item_id is the blog ID and the secondary_item_id is the post ID on the blog.
One thing that you pointed out to me is I need to add some type of check to see if the activity ID exists for the blog post in question, if it does, then output the favorite button, if doesn’t, it should output nothing.
There is no real guideline apart from making sure your plugin is BP-aware.
You can check out how BP’s internal code is structured as well some of the most popular BP plugins.
A BP plugin is basically a WP plugin so you can also read up on WP’s general guidelines.
Also check out:
https://codex.wordpress.org/Developer_Documentation#Plugin_Development
BuddyPress Codex
@walid3 – Add the following line to wp-config.php:
define ( 'BP_ENABLE_ROOT_PROFILES', true );
For more nifty internal config settings, check out this page:
https://codex.buddypress.org/how-to-guides/changing-internal-configuration-settings/
No, no.
BuddyPress 1.2.4 onwards should/is meant to work fine with WordPress 3.0. If it doesn’t, it’s a bug we need you to report at https://trac.buddypress.org/ so that we can fix it for the next build. BuddyPress 1.3 will require WordPress 3.0, and won’t work with any previous version of WordPress.
@blacktattoo – You could try the BP Usernames Only plugin if you want to replace the display name with the username:
https://wordpress.org/extend/plugins/buddypress-usernames-only/
If you want to add it to the activity content, you could apply a filter to “bp_get_activity_content”.
Full support for WP 3.0 will be in BP 1.3 – https://buddypress.org/about/roadmap/
In the meantime, BP 1.2.4.1 working well in WP/MU 2.9.2
Full support for WP 3.0 will be in BP 1.3 – https://buddypress.org/about/roadmap/
In the meantime, BP 1.2.4.1 working well in WP/MU 2.9.2
Hi Martin
As per our regular procedure, I’m closing this topic. If anyone’s interested, please get in contact with @marto.
Here’s a good as place as any for BuddyPress developers. I’m closing this topic, as per our usual procedure, but if anyone’s interested, please contact @thatmtnman.
@techguy Do you happen to know how to make the most recent avatars widget pictures the same size as it is in this sidebar? I’m not a programmer and for some reason on my site the pictures for this widget are larger than what is shown here and I can’t seem to find any setting to change the size on the dashboard. Is this something that my programmer needs to do with CSS or something?
I am pretty resigned to the fact that i am not going to be upgrading my BP sites any time soon if ever. I am really disappointed by this because until 1.2 things were going great with the platform. That would not be so bad except for the fact that the invite system on BP events never really worked so many of my users are just not using the events section at all which was a major hub of activity on my former Ning based sites. On that note I have to be honest and admit that i have told many soon to be Ex Ning folks that if Events functions are important to their site they will need to look elsewhere because at this time BuddyPress is not a good solution for them.
Yes i have looked at the “Eventpress” solution that is being worked on but unfortunately it uses the dDshboard to create and mange events which is entirely the wrong track IMHO. Unless someone is higher than a Subscriber to your site they really should never see the dashboard.
i believe @3sixty created a plugin (or posted code – have to search for it) to record the user’s last viewed post
Think I found it – at least it seems to be working now!!
To redirect to the homepage on login:
https://codex.wordpress.org/Function_Reference/wp_login_url
line 147 in wp-includes > general-template.php has to be changed from:
<a href="” title=”Login”>Login
to:
<a href="” title=”Login”>Login
after much trial & error I replaced (‘url’) not with the entire URL but with just the name of the folder that my BuddyPress protected blog is in – this is because my blog is not in the root folder – if yours is it may not be necessary to change anything.
YAY… hope you can still make this easier for other users of your GREAT script… thank you Jehy!!
It is protecting all pages and sections from prying eyes. Other scripts I tried had spotty protection – once on the registration page they let some of the tabs like members be viewable without registering or logging in…. registered-users-only2 is protecting everything.
: )
Thanx intimez and Paul. I select settings->permalinks and then a common setting like the second (date and name) or third (month and name) but when I click “Save Settings” there is a message (in greek this is the translation) on the bottom of the page that “if the .htaccess file was writable then save will be automatically be completed, but it seems that it is not. Here are the rules mod_rewrite that you must enter into the .htaccess file.
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
“
So, I cannot save settings and I cannot find .htaccess file. I have manually (I uploaded the folder with filezilla) installed buddypress, because there was a problem with automatic installation. Maybe it is the “same” problem again…
I also tried to create the “.htaccess” file as Paul suggests but since I have windows xp, it is impossible to create a file without a filename.
I tried to make the “/” folder writeable also (I give you the procedure I followed). I logged in with filezilla and I right clicked on “/” folder. Then I clicked on file properties and I ticked “write” on owner, group and public and I also selected to apply this setting to subfolders.
Unfortunately, the problem remains 
I wrorte about an issue here
https://wordpress.org/support/topic/409388?replies=2
to clarify, the ajax chat box keeps popping up in group chat in new pages created by group extension plugins eg: links, albums etc
Group pages like activity or forums it stays out of the way unless called upon.
Any ideas?
@angelntini You’ll probably have to create the file if that folder’s not writeable. I use to have to do that. Just create a blank .htaccess file. Then, paste the code in. Or make it writeable so that it can be updated from within WordPress.
