[Paul Wong-Gibbs]

Take a look at https://buddypress.org/forums/topic/path-conflict-with-user-blogs-using-buddypress-theme-wpmubp, same issue

[Paul Wong-Gibbs]

Ok people, step back from your keyboards and take a deep breath.

1) The ‘ideas’ forum collects any ideas that people want to see in future BP version.

2) After some period of time, I am going to make a list of all the ideas. I am going to take it to a http://bpdevel.wordpress.com/ BuddyPress dev chat, and those present (everyone is welcome) will help decide which of those ideas to go into a poll on this website.

3) Everyone can then go to the poll on this website and vote what they would like to see in BP version 1.3, 1.4, and so on. Results will be announced by Andy Peatling and the Roadmap updated.

This is very similar to what happened around the 1.0 release.

Like what 21cdb said:

Humans always looking out for their own interests, thats natural behaviour, but we should always keep in mind to respect interests of the public and of the parties concerned as well.

A poll is a great way to determine what the public needs are. I believe it will give the main developers good impressions in which directions they should focus in the future.

[Paul Wong-Gibbs]

Yes it should work OK.

[Oliver @ WebMatros.com]

Thanks for your fast answer Xevo.

Will that later on give me the same possibilities (integrating with groups for example, should I want that at some point in the future)?

[andrew_s1]

For anyone following the thread to date: Armand Morin’s question (how to add the BuddyPress Nav to the theme) gets answered here: https://buddypress.org/forums/topic/creating-nav-bar

[Xevo]

Just install bbpress the old fashion way and do a wordpress intergration.

[r-a-y]

Read this post in the FAQ thread:

https://buddypress.org/forums/topic/faq-how-to-code-snippets-and-solutions#post-37123

[r-a-y]

The forums on GoFastBargains.com is using the internal forums component in BuddyPress. No integration is needed with anything else.

This is how it’s done:

1) Install WordPress

2) Install BuddyPress

3) Enable forums component in BuddyPress

4) Smile! You’re done!

[r-a-y]

@summerchilde – as stated above and in the readme.txt, the array_map() warning is a BP issue. It’s fixed in BP-trunk. The next release of BP 1.2.1, coming this week, will address this issue. If you can’t wait until then, you can patch the issue yourself (check out the “Known issues” section in the readme.txt).

@modemlooper – Sorry about the folder renaming! I know it’s a pain! The good news is oEmbed for BP v0.6 will fix the “rename folder” issue and will feature some performance enhancements (courtesy Andy P). Stay tuned for the next release which will come out when BP 1.2.1 drops.

[gofastbargains]

I went ahead and created a new forum. I actually like the forum inside buddypress a lot better than just bbpress.

[abcde666]

Advanced Search for X-Profile-Fields was on the BP-Roadmap for 1.2, same as “Privacy-Features” and “User-Blogs-Posts from Front-end”. However those 3 features did not make it into BP1.2

I think most of the requested and discussed features on this Forum are Plugin-territory, but the mentioned 3 features should definitely be within Core and are essential to run a Social-Network-website:

– Privacy Features

– Advanced Search & X-Profile Fields

– User-Blogs-Posts from Front-end

I would even say:

STOP any further feature-polls for BP 1.3 and focus on above mentioned 3 features ONLY.

[snark]

Thanks for the links, @r-a-y — those discussions were helpful, and I can see that this has been an ongoing discussion for at least the last couple months.

For now I’ve disabled Forum replies in the activity stream, to avoid the “forked conversation” issue of having some topic relies in the Forum and some in the AS. I’m still wrestling with the whole Groups thing and the Groups comment box at the top of each Groups page — I know for a fact that when I open this up to 10k+ members of my current forum, many, many of them will just start posting their topics in the Group page, rather than creating a Topic in a Group Forum. Maybe I should just open it all up and let it be chaotic, and let the user community figure out how to self-regulate?

The other thing I’m still looking for is a sitewide Favorites option, so users can mark Forum Topics, Group AS posts, or blog posts as Favorites — currently you can only do that with Group AS posts. It looks like @JohnJamesJacoby is working on such a plugin — see https://buddypress.org/forums/topic/favorite-button-available-on-singlephp — which hopefully will be ready soon and solve this particular issue.

[danbpfr]

Working

WP single, WPMU 2.9.1 & BP 1.2

wp-ban

invisible defender

wp-spamfree

bp-links

bp-group-documents

On BP 1.2

Group Forum Subscripton for BuddyPress

SyntaxHighlighter Plus

Quanrantine (awaiting for soon? update)

bp-events

bp-groupblog

[quaker-oats]

this is exactly the same problem i am having and I put a post also describing my situation (https://buddypress.org/forums/topic/upgrading-bp-getting-white-screen).

it seems like this problem may be common.

[Jeff Sayre]

Since this forum is meant to discuss possible enhancements for future BuddyPress versions in 2010, the idea of forking the project is beyond scope. You of course are free to continue discussing this topic but it might be better to start a new thread in the Miscellaneous Forums.

As to this example:

Lets say if i want to use Buddypress to set up an organic farming community for example I am going to have many of my users getting confused with having a backend and a front end and all of the options and admin stuff in the backend.

The only reason users would need access to the backend is if the Site Admin has set up their BuddyPress community to allow users to have their own blogs. If the mulitblog feature is not enabled, then users only have access to the frontend menus to set options and navigate the network. Also, the Site Admin could choose to build their community on the single-user version of WordPress. Then offering blogs to users is not even an option.

Whereas your assertion that

…stripping out the WP centric features surely won’t be an issue in the context of running a social network.

might be the case from a user’s perspective, it is a huge issue with regards to the amount of programming and code refactoring that would be required.

I can state with a high-degree of certainty that Andy nor Automattic will not be forking their own creations. The only way I could see that happening is if a few Automattic employees break off and form their own shop.

Why wait for someone else to do it? As I said in my first post in this thread, forking any OS project is a lot of work, but you are free to do so as long as you follow the GPL. If you think you have a unique, under-served vision for the platform, form a team and do it.

[Avi M]

I think improved privacy is must for things like member profiles, so I looking forward to seeing the updated plugin and possible improvements to 1.3.

In the mean time I thought I would offer up the following.

A while back asked a question on this very question over at premium.wpmudev.org and here is the response/ solution I was given. No idea if it can applied to other theme or BP 1.2 but for what it’s worth here it is.

ok, back to your question..

i see the member directory still viewable after turn on privacy...yeap

it is a glitch in theme...no worry here's an easy fix



open profile/index.php

and copy the top code



<?php $privacy_enable = get_option('tn_buddysocial_privacy_status'); if($privacy_enable == 'enable') { ?>

<?php if (!is_user_logged_in() ) { ?>

<?php wp_redirect(get_option('siteurl') . '/wp-login.php'); ?>

<?php } ?>

<?php } //off ?>



to directories\members\index.php before get_header();

actually you can apply this to any page you do not want unlogged user to view like group, forum etc..

Hope this helps.

Here is a link to the actual thread.

http://premium.wpmudev.org/forums/topic/social-theme-privacy-options-not-working-1

[PJ]

Jehy suggested the plugin Register Users Only 2. It has worked well in my install. Hope this helps.

https://buddypress.org/forums/topic/limiting-access-to-registered-users#post-38303

[intimez]

Glad it worked out for you siayuneh.

[peterverkooijen]

@raoulduke, I did get Posthaste working. I had the tag in the wrong place. It really needs to be right before the loop.

P2, Posthaste, the TDO Mini Forms plugin all work fine on regular blog index pages, but I can’t get any of them to work on the Group Blog. There is a referral check problem or the form can’t find the right blog ID.

[podictionary]

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.

[Tore]

There’s no water proof way of securing all components (without some sacrificice at least).

But check this for example:

https://buddypress.org/forums/topic/plugin-force-login-for-member-pages

[Jeff Sayre]

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)

[David Lewis]

I was the first to post about this issue actually (in that other thread). I’ve tried to reliably reproduce it and I’m afraid I cannot. Blogs are set to public. It always seems to happen when a new user registers and/or is promoted to a blog admin. I’m not sure if this is a BP bug or a WPMU bug… but I couldn’t find anything about this issue on the WPMU forums. At one point even my original admin user (username “admin”) couldn’t see any blogs listed. And I went into Site Admin > Options and switched the order of the admin usernames listed (on a lark) and that fixed it?! Very random… and bizarre. I wish I could outline steps to reproduce it.

p.s. unlike zageek… everything else is working perfectly. The only issue is no blogs being listed under “My Blogs” in the admin bar and in the users profile. So it’s not really all that critical. Everything still works. But it’s confusing to see a “Blogs (3)” tab in the profile with no results… and it’s a pain to have to type “wp-admin” in the address bar of your browser rather than being able to use the shortcuts in the admin bar.

[takuya]

This is not a problem of BuddyPress, please use WPMU support forum for general questions. Please only post questions regarding functions provided by BuddyPress plugin to this forum. In fact, you get faster response if you post this to WPMU support forum.

[zgreen]

Ray,

Thanks for the reply. I was afraid that a standalone bbpress is the only option, but was hoping for an easier way to avoid the complexity. All the talks about bbpress eventually evolving into a plugin anyway makes me hesitant too. I might end up keeping the /blog/forum/ setup.