@xxxxx Stop notification spamming. Consider this your third (and final?) warning.
The email issues are a common topic with bluehost sites, check this thread and the plugins mentioned by mercime – they should get around an issue which frankly should be tackled at the server level.
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/problem-after-installing-buddypress/
Also you might want to add an SPF record to your zone file and ask bluehost to add a PTR RDNS record for your IP/Domain name as these two items – or the lack of them – can be the cause of email server rejecting sent emails from a server they can’t verify.
=== but other than my main blog, brand new install? ===
It all depends on a variety of factors which include what your realistic expectations about adding BuddyPress are. I don’t know what your current site/blog is all about so only you can determine if social networking will enhance your current site’s branding or if it would be better if the social networking feature was a separate entity/site altogether.
Well, I definitely had PHP 4.3 or better, MySQL 4.1.2 or better, and Apache Module mod_rewrite enabled for “pretty permalinks”. I had installed it a couple of times over before that, but I can’t remember whether I tested the clickthrough to the single hello world post for that (just saw the home page and that the dashboard worked), so I wouldn’t know whether I had a fully stable WordPress install to begin with.
I’ll give the reinstall a try and report the results for posterity in this thread.
PJParticipant
This may be a temporary option for your site: https://buddypress.org/community/groups/registered-users-only-2/
I’m not sure how to specifically limit widgets for those who are logged in.
@xxxxx Please dont @mention quite so many people it’s not going to get you any faster attention and likely to just annoy 
you say: stay single WP installation,
but other than my main blog, brand new install? hence my main blog if for it purpose…
I do not want users create a blog/site of their own.
@MrMaz – just wanted to give you a heads-up about this issue…
=== … relocating my .htaccess file to various locations throughout the /var/www/html hierarchy … I thought the BuddyPress installation instructions were pretty straightforward, but it seems to actually work in a whole different way from what is documented. ===
BuddyPress installation is pretty straightforward when server configuration is stable and meets standard requirements https://codex.buddypress.org/getting-started/before-installing/
which includes WordPress install already working with pretty permalinks at the very least https://codex.wordpress.org/Using_Permalinks#Using_.22Pretty.22_permalinks You should read this as it addresses the .htaccess file which is at the crux of the matter
The .htaccess file for your WordPress installation should be where WP is installed.
If WP in root, http://yoursite.com/ then .htaccess should be at http://yoursite.com/.htaccess.
if WP in subdirectory, then .htaccess should be at http://yoursite.com/subdirectory/.htaccess.
Strongly recommend you restart from scratch by deactivating BuddyPress and BP plugins, change theme to default twentyten theme, deleting .htaccess file wherever you placed it and dropping tables in DB. Reinstall WordPress and resolve pretty permalinks issues at https://wordpress.org/support/forum/how-to-and-troubleshooting before installing BuddyPress.
Good luck.
@Virtuali Cheers. I’m fine with 3.1 – love that only file in my child show in edit:-) My concern is with using non-buddypress themes such as twentyten and adding BP to them. I initially used the Template Pack but it seems this is not being supported. I wanted to know if all I need to do in future – when I do this for another website – is to copy the folders from bp-default to my theme. Is it that straightforward?
After almost 8 hours of looking into every possible theme file and googling around, I found the markup responsible for activity comments – I thought I would share the info in case someone else will be looking for it in the future.
Turns out it’s nowhere in the theme files, but in BuddyPress files in buddypress/bp-activity/bp-activity-templatetags.php file. The function `bp_activity_comments` is defined around line 633 and it has a comment that this solution is temporary:
`/* TODO: The HTML in this function is temporary and will be moved to the template in a future version. */`
It can be edited there, but I’m assuming it will be possible to do this in theme files in some future version.
Phew.
7693536Inactive
@apeatling, @johnjamesjacoby, @djpaul, @MrMaz, @jeffsayre, @boonebgorges, @r-a-y, @nuprn1, @hnla, @modemlooper, @andrea_r, @gunju2221, @mercime, @crashutah, @StevieG, @pollyplummer, @dwenaus, @erich73, @slaFFik, @xberserker, @ewebber, @Aces
It’s not working for me either… any solutions??
7693536Inactive
@apeatling, @johnjamesjacoby, @djpaul, @MrMaz, @jeffsayre, @boonebgorges, @r-a-y, @nuprn1, @hnla, @modemlooper, @andrea_r, @gunju2221, @mercime, @crashutah, @StevieG, @pollyplummer, @dwenaus, @erich73, @slaFFik, @xberserker, @ewebber, @Aces
Ok thanks for the tip, i’ll try to upgrade
There are a few rules you will probably want to follow if you want help on these forums:
– Please don’t call out every notable user by name. Use the @-mention system for drawing someone’s attention to an item when it’s relevant to them. To flag everyone down every time you have a problem has the potential to be quite annoying.
– Make your forum post titles descriptive. Almost everyone in this forum is looking for help; naming your topic ‘HELP’ does not help anyone else to know what your problem is. Also, no need for all the exclamation points.
– Please give as much information as you can about your installation. You are apparently not running the latest stable version of BP (1.2.
, as line 432 of bp-core-signup.php in BP 1.2.8 does not have a reference to bp_core_signup_user(): https://trac.buddypress.org/browser/tags/1.2.8/bp-core/bp-core-signup.php#L432 Try upgrading to the most recent version of the software, or at least providing more details about your installation: WP/BP versions, other plugins you are running, etc.
Go multisite (create a network) and install BuddyPress if you want to allow your users to create a blog/site of their own in your installation. Otherwise, do not create a network, stay single WP installation.
I was right about to launch a BuddyPress powered site at work when I upgraded to 3.1, and now I’m not sure whether to downgrade back to 3.0.5 for now or not.
Currently I have the same issue as the original poster, only way I can activate the plugins that deliver the core featureset the site is designed for is as a “Network Activate”, but I don’t want them enabled on the additional blogs we’ll be providing to some users.
Would you recommend downgrading to 3.0.5 in order to keep the functionality we had during the whole design and testing phase? Am I misunderstanding what Network Activate will do?
@mojoshaun, @oriste I have not figured this out yet, actually I stopped trying for a long time, I am about to begin my search again, I think there are some solutions now.
@jivany, a wpmu question indeed, but now that its all wp3-in-one, I’ll pose the question again here. Also, it’s not for the option of having a “blog” — remember everyone doesn’t use the multisite “blog” as a traditional blog in a blog network. I have other uses for the “site” for each user. My users aren’t necessarily aware that they are on a “blog network” so they don’t think in terms of blogging or having a blog etc. Each user “blog” is just a posting tool that is integrated into their profiles, much like FB notes. So I’m not too worried about anyone being annoyed because they could care less about what we call it in the forums or in the backend.
@mrwweb Sorry I did, I had this set to yes “Disable global forum directory?:” turning it to no fixed it.
Under BuddyPress > General Settings
Here’s a different way to do it. It’s not exactly what I want, but it’s a step forward.
For more info, you can see this: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/move-registration-form-to-home-page
From research, you have to edit slugs to get it to work.
I would be nice to find some examples of editing slugs for bbpress registration form.
Noting that it wants to go to `wp/members` rather than where the buddypress install and BP Compatibility configuration directions had me put that and its other folders (which was in `/wp/wp-content/themes/bp-default`), I copied all the bp-themes directories to where WordPress and the web server are looking for them… `/wp/members`.
The URL that appears in the browser is http://098.765.43.210/members/admin/activity/
That’s not exactly right, though, as the structure “admin/activity” isn’t even part of “members”. The error log reflects this (correctly) as:
`[Tue Mar 08 14:48:36 2011] [error] [client 123.456.789.0] File does not exist: /data01/home/username/production/wp/members/admin`
And so does the access log:
`123.456.789.0 – – [08/Mar/2011:14:48:36 +0000] “GET /members/admin/activity/ HTTP/1.1” 404 301`
So I truncate the URL in the address bar to be http://098.765.43.210/members and now I get a blank page. No source.
The access log now says:
`123.456.789.0 – – [08/Mar/2011:14:53:01 +0000] “GET /members/ HTTP/1.1” 200 -`
But the error log now says:
`[Tue Mar 08 14:53:01 2011] [error] [client 123.456.789.0] PHP Fatal error: Call to undefined function get_header() in /data01/home/username/production/wp/members/index.php on line 1`
I’m soooo totally baffled by all of this. I thought the BuddyPress installation instructions were pretty straightforward, but it seems to actually work in a whole different way from what is documented.
maybe it has something to do with the membor count starting out as zero or no members atall or something Im lost, should I turn WP_ERROR off and that might bypass this?
Here are example lines from my error log and access log (IP numbers obfuscated for security):
Error log:
`[Tue Mar 08 14:25:49 2011] [error] [client 123.456.789.0] File does not exist: /data01/home/username/production/wp/members, referer: http://098.765.43.210/`
Access log:
`123.456.789.0 – – [08/Mar/2011:14:25:49 +0000] “GET /members/admin/profile/ HTTP/1.1” 404 300`
With Permalinks set to “Month and Name”, a hit to the hello world blog post for this install generates the following error and access log entries:
Error log:
`[Tue Mar 08 14:38:48 2011] [error] [client 123.456.789.0] File does not exist: /data01/home/username/production/wp/2011, referer: http://098.765.43.210/`
Access log:
`123.456.789.0 – – [08/Mar/2011:14:38:48 +0000] “GET /2011/03/hello-world/ HTTP/1.1” 404 298`
Setting the Permalinks to “Day and Name” gives this:
Error log:
`[Tue Mar 08 14:35:02 2011] [error] [client 123.456.789.0] File does not exist: /data01/home/username/production/wp/2011, referer: http://098.765.43.210/`
Access log:
`123.456.789.0 – – [08/Mar/2011:14:35:02 +0000] “GET /2011/03/05/hello-world/ HTTP/1.1” 404 301`
