BuddyPress.org

It’s so funky, my emails totally fluctuate. I just installed 3.04, and activation emails are not being sent out. I will have to go into troubleshooting mode tomorrow….

I wish wordpress would really fix this, I am getting %&$% tired of email problems.

The emails at one time would appear right smack away, but I recall the emails taking a massive amount of time to appear, so I would recommend a notice on the register page about this.

You have to edit the part about the server. On mamp it will be localhost and your user name and password is usually root. This is so WP can connect to your local database.

// ** MySQL settings – You can get this info from your web host ** //
/** The name of the database for WordPress */
define(‘DB_NAME’, ‘buddypress’);

/** MySQL database username */
define(‘DB_USER’, ‘root’);

/** MySQL database password */
define(‘DB_PASSWORD’, ‘root’);

/** MySQL hostname */
define(‘DB_HOST’, ‘localhost’);

As for creating a database you go to phpmyadmin enter a name of the db in the create database input and hit create.

Then in the wp-config file you enter the name you entered here define(‘DB_NAME’, ‘ PUT YOUR DB NAME HERE’);

Yep, I just did the update, and so far so good. But if you are concerned, you should do a backup just in case.

WP upgrades, especially security and maintenance releases (ie when the version number is 3.x.x rather than 3.x), are generally very unlikely to break any plugins, including BP. I’d recommend that you upgrade to maintenance releases immediately.

Feature releases, like WP 3.0 and 3.1, are somewhat more likely to cause problems with plugins like BP. But the BP core team works closely with the WP core team to ensure that BuddyPress is ready for whatever changes come along ahead of time. If there is something in BuddyPress that absolutely cannot be fixed prior to a major WP release, we’ll do our best to warn you about it before you upgrade.

I work with local mirrors on MAMP Pro. This is what I do :

1. Copy the remote files (the whole install) to my local machine (I do this so the file creation dates are the same).
2. Backup the remote database with phpMyAdmin (be sure to select Add DROP TABLE) as a gzip file.
3. Edit the local copy of wp-config.php for my local machine’s database connection.
4. Create a new local database and import the remote backup (I personally always destroy the local db and create a new empty one to import into – then I know it’s clean).
5. Use this tool to change all absolute URLs from remote to local: http://spectacu.la/search-and-replace-for-wordpress-databases/

Then I’ll test new plugins locally before deploying. Also I update plugins locally, and then manually copy them to the server, having had a few past failures updating plugins on production servers. Once it’s running, the only files I normally have to backup from remote to local are all in wp-content (avatars etc., which can easily be sync’d).

Hope that helps.

https://wordpress.org/support/topic/need-a-cheap-reliable-hosting-for-my-buddypress-network?replies=2
https://buddypress.org/community/groups/buddypress-hosting/forum/
“Cheap” is relative.

https://wordpress.org/extend/plugins/buddypress-badge/

I also have found myself torn about using pages for BP directories. In the end, though, I think it’s a compromise that works out for the better in the short- to medium-run, and does not have awful long-term consequences.

In my view, it is a gross overstatement to say that this move ‘ruins’ BP. However, there are a few things about it that are unappealing:
1) It forces the creation of what are, essentially, dummy pages – whatever content you might add to the page through the normal WP editor is totally ignored
2) Related – It uses part of the WP page infrastructure (URLs) without using others (in particular, WP page templates)

Problem (1) is unappealing, but it is mitigated by a couple of points. First, the current system is not a whole lot better. Instead of having ‘dummy’ pages that you can see in the admin (like BP trunk has), the current version of BP has ‘phantom’ pages, so that when BP detects a URL like example.com/groups, it essentially hijacks the page load in order to do its own stuff. This is a bit jarring, and not at all transparent. So there is a trade-off, but it’s not all bad. Second, while the idea that ‘Pages in WordPress are supposed to be static content’ seems right to me in broad strokes, it doesn’t seem to me to be a hard-and-fast rule. Many plugins (gallery plugins, ecommerce plugins, etc) display their content by means of a shortcode that is manually inserted on a page or post, with pages being used for their pretty URLs.

On the other hand, there are some real benefits to directories-as-pages:
A) Easier URLs (as @driz has noted)
Integration into WP 3.0-type menus (this is the big one IMO)

How important are things like (A) and (? For sites maintained by folks with some PHP chops (and organizations with money to pay people with PHP chops), they could be fairly easily accomplished with BP_GROUPS_SLUG, etc, and with some other finagling. But – and this is just a guess – this profile does not match most of the users of BP. Nor should it, necessarily. To the extent that BP can be easy to use and install for people with little technical knowledge, without at the same time making it less flexible from a developer’s point of view, it should be. This change is good for end users, and is no more difficult for developers than the current technique, so it seems like a net win.

Another more theoretical argument for the directories-as-pages move (especially as compared to the new admin panel @driz suggests for changing slugs) is that BP shouldn’t reproduce functionality that WP could provide, unless there is a convincing reason for doing so. Using WP pages for BP directories is a step toward greater BP-WP integration. It’s not perfect (see my problem (2) above) but it is a start.

As for custom post types: It’s likely that at least some of BP’s components will be refactored to use custom post types in the future. When that happens, part of the upgrade script will probably involve removing the dummy pages at issue here. So from the user’s point of view, the transition will be seamless.

I should say that I am in agreement with a lot of the sentiment in this thread about making BP a bit more lightweight, framework-y, and disjointed than the sometimes hulking behemoth it is now. However, that kind of transition can and probably should be gradual (at least more gradual than the 1.3 release).

Sounds like you’re using an older version of WordPress.

Deactivate BuddyPress and upgrade WordPress:
https://codex.wordpress.org/Upgrading_WordPress_Extended

Well, don’t blast something for being exactly what it’s suppose to be. Since BP is a WordPress plugin and the dummies books are for absolute beginners then it makes sense to spend a great deal on the core. Is there room for more documentation? Yes!

Read the documentation on this site: http://codex.buddypress.org
Visit these:
http://etivite.com
http://bp-tricks.com
http://wpmu.org/category/buddypress

I’m sure there are more resources out there. Just search or ask.

Lol, yes, I am a troll.
I am old and smell funny and live in a cave.

Look, in today’s economic climate, the job market is pretty much empty, even in Australia. Even if you do get a job with a company, then you’re hard pressed to pay rent and bills, and you can never think of buying a house.

The only option left is web-development and small business. I’m sorry I got upset about it yesterday, but it’s really frustrating when you get to a golden package like Buddypress and you find that they documentation is really sparse. Then you find that there’s a book out there specifically about the package, and all that’s in it are the installation instructions and how to use the admin panel.

For the record, there’s a second book called ‘WordPress for Dummies’, so that’s why I thought it wasn’t right that her first half of the book is about WordPress.

Still works like a charm for me with
Version 1.2.7
WordPress 3.0.3

WordPress, not BuddyPress plugin, handles email activations. It could also be because of webhosting configuration. Deactivate BP and BP-dependent plugins, then double-check if activation emails are sent from your installation. Check for resolutions from
https://codex.buddypress.org/getting-started/faqs/specific-faqs/
WP.org forums https://wordpress.org/search/activation+emails+not+sent?forums=1.

“There is no listing and explanation of functions. There is no explanation of hooks, actions or filters.”

LOL, it’s called “dummies” meaning for people who don’t even know how to install WordPress let alone BP. The Dummies book is great for an absolute beginner. If you have moderate experience with WordPress, then no, the dummies book will not do you any good. You are better off reading this forum, going through the developer docs.

Not to mention, why are you replying to a topic that is 8 months old? Are you a troll?

Buddypress for dummies is a piece of crap.
Do not buy it. Just d/l it from isohunt.

I just read through it and my hope has turned to despair.
There is no listing and explanation of bp functions. There is no explanation of bp hooks, actions or filters.
Basically, for the first half of the book (literally) she tells you what WordPress is and how to install it.
For the 3rd quarter of the book, she tells you what the components are, what plugins are, how to use (wait for it) HTML tags, CSS, and other crap.
Also, you learn how to use the admin panel. Yay…
Do not waste your money.

Buddypress for dummies is not suitable for developers.
I don’t suggest buying it if you want to develop seriously.

I just read through it and my hope has turned to despair.
There is no listing and explanation of functions. There is no explanation of hooks, actions or filters.
Basically, for the first half of the book (literally) she tells you what WordPress is and how to install it.
For the 3rd quarter of the book, she tells you what the components are, what plugins are, how to use (wait for it) HTML tags, CSS, and other stuff.
Also, you learn how to use the admin panel. Yay…
I really didn’t like it.

Creating a child theme really isn’t that hard, and you aren’t relying on a 3rd party to maintain a plugin.

First I created a new folder in the usual WP themes location, and named it child theme.
Then I grabbed the header and footer pages from the buddypress/themes folder, and edited them for my page, saving in the new Child theme folder.
Then,I used a basic generic WP framework to get started, and added some buddypress and wordpress php as needed – just cutting and pasting the loop, and BP stuff as needed.
Once the first page was made, I just would add or subtract the items needed for individual pages, blog pages, user pages, etc.

If you know just a little php, html, and CSS it’s not hard.

Make a copy of your BP theme. Delete all folders you see here https://trac.buddypress.org/browser/tags/1.2.7/bp-themes/bp-default except _inc/ folder if you have your CSS file and images parked there. Then delete all BP references/code/templatetags you see in the remaining files – header.php, funcions.php etc.And, don’t forget to delete bp-custom.php from plugins folder if you have one.

Why not just add a website profile to the BP side, and forget about (turn off) the WP side?

Add me to that question also. I have been playing around with this for some time trying to figure out how I can integrate the two separate profile systems. Is there a reason for the redundancy? I am particularly worried that people will change their “Website” field in the WordPress profile, messing up the link which Buddypress uses. I don’t want to disable the user profile on WordPress, but it is definitely a problem.

bbPress is going to be turned into a WP plugin which would mesh well hopefully with BuddyPress as lead dev for bbPress is also one of leads for BuddyPress.
https://trac.bbpress.org/roadmap

Some have used SimplePress Forums, Mingle Forums, or BP Global Forums ($30) for what you want.