Bump. This is an issue related to recent changes on the wordpress.org site, and is still being looked into.
You need to change mid_size (I think) on all the calls to paginate_links(). There may or may not be a filter in WordPress core to let you do this without changing core, I haven’t looked
I don’t know if it will set this particular case, but have you set SSL in WordPress?. https://codex.wordpress.org/Administration_Over_SSL
No, no; don’t start hacking WordPress or BuddyPress core files. You will cause yourself problems with upgrades in the future. This thread was 1.5 years old before ivanoats replied to it; ivanoats, I’m going to close this thread, but could you please make a new post with fuller details of what you’re trying to do, what you’ve done so far, the error you’ve got, the theme you’re trying to use, and the version numbers of BP and WP. Thanks.
This has been fixed in our dev version; take a look at https://buddypress.trac.wordpress.org/changeset/4169 for the fix
PDX came on IRC. For the benefit of Google, PDX is running on a server with the Confixx panel installed. It appears to do something funny with the Apache rules for .htaccess files, causing a 403 error on the entire domain (NOT just the WordPress specific files). http://wp.uberdose.com/2004/03/05/confixx-and-htaccess-and-mod_rewrite-403/ seemed to help
== project management tool (with a budget tracker would also be cool) that has the ability to be integrated with wordpress and BB. ==
If by BB. you mean BuddyPress (BP), then try out https://wordpress.org/extend/plugins/bp-gtm-system/
I also had this problem and went through a deep analysis.
The issue stems from the fact that Bluehost requires that the email be sent from an account that exists on the system. They do this as an anti-spam technique and they require this even if the mail is originating from within the system.
Enter WordPress. PHP uses a mail function mail(). WordPress maps this to wp_mail() and pretty much everyone uses the wp_mail for the plugins within WordPress. This makes sense as it allows customization of WordPress mail at a relatively low cost of performance.
Enter Buddypress. Buddypress places a filter upon wp_mail() such that all email originate from the user ‘noreply’ on the domain such that end users don’t reply to the notifications. Sounds cool.
But remember that Bluehost does not allow email to be sent from non-accounts and that’s the catch.
Using a foreign SMTP does not work for Bluehost blocks those ports. Using local SMTP will work but you need to provide the right setup and credentials. Finally, using mail-from plugin works since it filter’s the Buddyhost filter changing the email from address back to a valid Bluehost email account.
Hopefully, this explains what is happening and you can choose which strategy you want to use to fix the problem.
@dubsel
Try Advertising Manager. I’ve had no problems at all with it. It works like a charm and automatically recognizes most ad networks.
https://wordpress.org/extend/plugins/advertising-manager/
Oh well, found this:
https://wordpress.org/extend/plugins/hts-display-active-members/
It displays for ALL visitors, and I kinda like the concept a bit better than the original widget anyway 
Ok so for the person that googles this later, it appears to be working network wide even though I activated it only in the root site. This should activate all of the options.
So it appears to work if not activated network wide, although I do want this active across the network…
@eventfulsd
I just tried creating an account on your site and believe I’ve found the cause of the discrepancy between subscribers and members: no activation email is received so folks simply cannot activate their accounts.
Check with your hosting provider to ensure that your email accounts are set up correctly for WordPress (Buddypress uses the same email routines as WP).
Perhaps my question should have been more basic. I am new with buddypress and wordpress, so please forgive my painful learning curve. I have 130 subscribers yet I only show 2 “members.” How do I set up buddypress to make each subscriber a member. My site is at eventfulsandiego.com. Thank you so much for your help. And by the way, I did see a send friend request to my other member.
@dinoraptor101 so you use the plugin https://wordpress.org/extend/plugins/cloudflare/ or did you test without it? If you did use it, maybe a bug report post on https://wordpress.org/tags/cloudflare?forum_id=10#postform about it would help get it solved
Yes, it does help, pcwriter, thanks. I already have S2Member installed and activated – I use it for overall privilege control, but it still uses only the WordPress basic priv levels – subscriber, contributor, author (which in my WP, does nothing), editor and admin. What I need is more granularity – to be able, for example, to allow a single subscriber or contributor member to access two specific pages for write, and read the rest. Role Scoper says it does this, but Role Scoper crashes my website. Can you tell me how to use S2Member (a very fine plugin!) to add more privs by page capability to my website?
Thank you @djpaul for explaining this was php4 v. 5 issue. As you knew, I was guessing global would fix 
And what message if any did you see when setting permalinks? If you saw a lot of code that is suggestive that WP wasn’t able to update your .htaccess file and is showing you what needs to go in the file. You’ll need to confirm that you actually have mod_rewrite working correctly, perhaps first disable BP and ensure that WP works correctly with permalink structure for posts.
Edit// I note that you have a url structure with that dreaded index.php in, ‘Almost pretty permalinks’ ? I think that you perhaps ought to read the WP codex page on permalinks to arm yourself with a little further understanding of this area and how to deal with it, you may have to add a custom link structure adding in the index.php/year/month/etc
https://codex.wordpress.org/Using_Permalinks
Of course we’ll make sure that whatever the current version of WordPress happens to be, BuddyPress will work with it.
I think people want to know if BuddyPress 1.3 will work with WordPress 3.2, or will there ever be a time when all three versions of software are up to date, completed and compatible with each other, since they rely on each other to run?
People may be concerned about “security updates” and other issues that would make their buddy press site vulnerable to attacks.
Also, will future releases of buddypress have more of the newer social networking features built into it? (Share buttons, sort by popularity, events, pages, recommended users, etc.)
You need to enable user registration: https://wordpress.org/support/topic/how-to-enable-user-registration-log-in
And make sure you’ve set custom permalinks. Otherwise, we’ll need more details to help
