BuddyPress.org

Hi. This should work:

https://wordpress.org/extend/plugins/registered-users-only-2/

Now works. Welcome to testing:

https://wordpress.org/extend/plugins/registered-users-only-2/

Hello. I just corrected registered-users-only, and it sould work fine with buddypress

Your tests and feedback are welcome:

https://wordpress.org/extend/plugins/registered-users-only-2/

Accoring to https://wordpress.org/extend/plugins/bp-member-map/changelog/

yes and no

JJJ?

Great question. Jeff Sayre had the privacy plugin of 1.1.x but won’t release a version for 1.2 just yet.

http://jeffsayre.com/2009/12/05/buddypress-privacy-component-released/comment-page-1/#comment-531

I’m confident, when released, it will provide some much needed privacy to BP.

I’ve heard that the following plugins may help bring some privacy to BP, but I haven’t heard which one users find the most effective or are compatible with BP 1.2:

https://wordpress.org/extend/plugins/registered-users-only-2/

https://wordpress.org/extend/plugins/registered-users-only/

https://wordpress.org/extend/plugins/members-only/

Grosbouff, are you aware of the Geo Mashup plugin. Couldn’t you leverage that?

I installed and activated Geo Mashup site-wide, but then it asks all the member blogs for their own Google API code in the wp-admin, which is annoying and will confuse many users.

Haven’t had time to test your plugin yet, but if it does the same as Geo Mashup, I’d rather have a cleaned up BP-ready version of Geo Mashup.

Thanks Tore !

https://wordpress.org/extend/plugins/registered-users-only-2/

Hi!

Thanks for the suggestion. I’ve been using a header-hack to ensure that no non-registrees are allowed into the website. I’ve only found https://wordpress.org/extend/plugins/registered-users-only-2/ that’s secure enough for me (all parts of the website). But it isn’t supporting BP 1.2. right now. I’m hoping for a release soon enough although.

https://codex.buddypress.org/how-to-guides/wordpress-to-buddypress-theme/

wordpress and buddypress are not proprietary scripts, you do not have to pay to delete the copyright or the product name, there is no license related to the product name.

the reason why you see the names and links to the original projects is what we call respect and credits… nothing more. you can still respect the authors and give credits to them if someone ask… so yes, you can delete everything you need to.

that is the answer to the OP.

Hi, I just installed buddypress on my wordpress blog that is currently running bbpress. I guess I am missing something. I thought buddy press could run along side my blog and not take it over. I was hoping to create a community with buddypress and keep the template and look of my current blog. Is that possible? I installed it as a plugin through wp.

Index and search are important related issues. A few points:

1) Database content search throughout needs serious thinking. How to include (and how to distinguish in results) blogposts, comments, activity updates, forums…

2) Indexing for search engines needs thought. What serious website doesn’t want to show up in Google?

3) A Google custom search is an option but shows up the problems of appearing in Google results; namely that scrolling activity lists result in indexes pointing to pages that no longer hold that content.

@nexia I see that at wordpress.com there is “search wordpress.com blogs” so MU can and does somehow allow for this.

As Open Source projects, anyone is free to fork any of the WordPress family of products as long as they adhere to the GPL licensing. In fact, WordPress itself started as a fork of another blogging platform.

However, Automattic will not fork its own products. With Andy as the only full-time Automattic employee working on BuddyPress, there is already too much for him to do with the current BuddyPress product, not to mention that forking your own product is basically creating a competitor.

Forking is not a task that should be taken lightly. Successful Open Source projects require a lot of supporting infrastructure: from a project repository; to an up-to-date and maintained project website; to a core team of developers; to a community that springs up and supports the project fork; to a support forum to offer help to users. These are just a few of the many requirements of creating and growing a healthy OS project.

But that should not stop you or anyone else who feels they have a different vision for the future of the platform to fork it and take it in a different direction.

http://en.wikipedia.org/wiki/Fork_(software_development)

Get the New Blog Defaults plugin.

https://wordpress.org/extend/plugins/wpmu-new-blog-defaults/

That will set whatever theme you pick as the default for new blogs.

To change the theme that’s already on exisiting blogs, it depends on what theme they have selected already.

for that, you need to suggest this in a ticket to the WordPress.org system…

Does anyone know if a child theme of bp-default placed in the themes folder and called default can replace an original default theme by mu.wordpress. I tried it and all blogs are broken. The only thing that shows is a white page.

There is potentially a way of doing this without having to get your hands wet in code.

If the posts are in different categories, then you could grab the “WP Post Columns” plugin (http://www.samburdge.co.uk/plugins/wp-post-columns-plugin-2) and the “Show Post Shortcode” plugin (on the WordPress.org plugin repository). You can then add shortcodes for three columns within a page (through the backend editor for the page) and, within each column, use the shortcode for showing posts in each of the relevant three categories. I’ve tried this for testing purposes, in a test BP1.2 install, and have had it working perfectly. The column code widths are expressed as percentages so they expand and contract along with the flexible theme.

Cheers

Richard

You can have a look at a theme called Feed me, Seymour, https://wordpress.org/extend/themes/feed-me-seymour

It is not for BuddyPress, but maybe you can find some code to copy and paste…