BuddyPress.org

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.

Anyone can sell BuddyPress or WordPress themes. License must be GPL.

if you want to allow your members to create blogs and go multisite, then yeah the members will have access to the backends of respective blogs. For site where BP is installed, members cannot access Add New Post unless you elevate their roles from anything other than Suscriber level which is default set in Super Admin Options.

For front end posting compatible with BP, https://wordpress.org/extend/plugins/one-quick-post/

This isn’t BP specific. Google is your friend. There a ton of tutorials about WordPress plugin creation.

Welp, too late for the OP but in case anyone else gets this error when trying to get the BP Compatibility Pack working, here’s what fixed it for me.
1. Multisite enabled on your WP installation. You need to add a line to your wpconfig.php file to do so (unless there’s an admin menu I’ve missed). Here’s the directions: https://codex.wordpress.org/Create_A_Network.
2. Buddypress installed and activated. However, if you’re using the BP Compatibility Pack, it’s because you want to use your WP theme, so do not enable the Buddysite-specific theme.
3. BP Compatibility Pack installed and enabled, then you can do the walkthrough to set up BPCP and you won’t get the error.

Is there an update for this fix? 1.2.7 broke this solution on our site and I can’t find an alternative so far.

Really, it’s extremely annoying that BuddyPress keeps making changes to the themes in minor updates. Every update (1.2.7 also saw us gain an unwanted admin bar menu item with links to the WordPress backend) sees us having to chase down the little changes they made which break our layout.

Regarding the ‘export’/’import’ of WordPress. At some point in the future when BuddyPress (may) use custom post types for (some of) its components, I hope that those components can also be exported without any extra work on our part. “For free.”

As and when we get closer to doing this work, we’ll see best what the situation is.

@andrea_r

I think there should be an option to have an export of some type similar to wordpress to avoid backing up old or junk databases. This will allow to get a clean install. I think @DJPaul has this on his to-do.

Wonderful solution, but it only partially import comments and blog posts. When I try to hit the button again I did import a few more, but the third time I ended up with just this message and no import:

Blog name: WordPress Dimensie

Blog name: WordPress Dimensie
Importing: ""
Importing: ""
Importing: ""


Any clue as to what’s going on here? Because I’m stumped and I would appreciate any and all help
Working with 3.1beta2 and BP 1.2.7 btw..

You do not answer my question …
It is possible manually resend the message? It can be validated by the admin manually?
The subjective responses of the merits of wordpress is not useful …
Management accounts BuddyPress if you can not do that is not terrible in this case … There is a plugin to do what I want?

“specifically designed for wpmu or buddypress”

There doesn’t need to be – just pick one of the many that grabs *all* the database tables.

https://wordpress.org/extend/plugins/search.php?q=backup

Note for future searchers, there’s also a free ebook on setup for multisite:

http://wpebooks.com/2010/09/how-to-enable-multisite-in-wordpress/

Hi @boonebgorges, that sounds so great! It disappointed me, that it is so difficult to give group members the possibility to just write articles in a group. WordPress started as a Bloggingsystem, and the missing possibility to write articles in groups is for me like something is really missing there.

Of course there is the groupblog plugin, but I think it’s a bit overloaded, to create a blog for every group, just to have some articles in this place.

There is another plugin from Brajesh Singh http://buddydev.com/buddypress/blog-categories-for-groups-plugin/. But nothing like a framework, to build your own component on it.

At the moment, the only easy starting point is on quick post plugin, but this plugin turned of buddypress support in the latest versions.

To have a framework for custom post type support in BP (front end editing, integration into nav menus, etc) to build custom post type components for buddypress with the possibility, to write articles from the frontend with the same functionality like the backend offers, would make buddypress application field much more powerful. Groups could be such a beautifully bloging tool.

Thanks for that news, and Happy Christmas

@hnla Ahhh yes. Will keep in mind … didn’t realize there was a distinction when on the BP homepage one of the specific features mentioned says “Even allow each of your users to start their own full powered WordPress blog.” It doesn’t say anything about Multi-site, so I thought this was a feature of BP. Maybe there needs to be some clarification on that feature description to avoid confusing folks.

Now, due to a problem with a photogallery, I had to change everyone from “Member” to Contributor which then allows members to post on on the site – just not on “their own full powered WordPress blog.” This may suffice for now.

@mercime I was aware of the difference between a real and a wildcard/virtual subdomain but not having had to create the wildcard functionality didn’t have a clue on how to implement. Suffice it to say I went to my hosting guys and got “Oh that’s easy. We’ll take care of that for you.” I’m about to dive in to the remaining instructions.

Thanks to all of you for your input and guidance!