BuddyPress.org

Here you go:

https://trac.mu.wordpress.org/changeset/2063/tags/2.8.6?old_path=%2F&format=zip

I’m in the same boat as @do77 here.

I’m looking to add a login for all content at my buddypress instance.

I, however, am running WordPress 2.9.1 (single) and the Buddypress trunk (I update once a week)

I have the “Force User Login” plugin for WordPress currently running, but you can still navigate around it if you try via direct URL requests and the like.

Any solid solutions?

I was able to get what I wanted by using the following code. It’s a link and not a button, but it also detects whether the user is logged in and displays a different message if they are not, so you can send them to the sign up page.

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

<p>Don’t see a group you like? < href=”../register”>Login or Sign Up to create a new group.</p>

<?php else : ?>

<p>Don’t see a group that can help you? < href=”../members/<?php global $current_user; get_currentuserinfo(); echo $current_user->user_login; ?>/groups/create/step/group-details”>Create a new group.</p>

<?php endif; ?>

Apparently there’s a get_currentuserinfo() function somewhere that lets you grab info, just like in WordPress. Go figure.

https://codex.wordpress.org/Function_Reference/wp_get_current_user

(Note: I took the “a”s out of the code because this forum is making them into links and the backticks are inexplicably not working)

@Peterverkooijen

hi Peter

We understand you pointing to the issues. There is no problem with that. It is a community project and Automattic and Andy is doing the good things for us. Automattic does not get funds for supporting wp+wpmu+bp(well Now they may get as WordPress foundation has been formed).

Instead of criticizing, if we appreciate what they have done for us and politely ask for the features, I am sure, Andy is listening and will be glad to accomodate.

Buddypress is one of the great project and see how much improvement has been in recent times. Please do not take the things personal, and let us keep the community constructive, It will be better for all of us.

Hope you don’t mind my words. Yes, currently Bp is more developer friendly than the end user, but with time, It has improved so much and you may expect it to be much more end user friendly by bp 1.3(my guess)

Please let us keep it constructive.

@all, Please keep this thread free from personal attacks before DjPaul sees this thread

So what I have to say to people that are complaining about missing features in the core: Start writing code.

This is like a car maker selling a car without brakes and telling the user he should manufacture them himself. I’m just a regular WordPress user giving feedback. I don’t get paid to write code. Andy does.

Could be done with openid plugin. If you use RPX, you can use your wordpress.com account to sign on to your wordpress/wpmu.

There are no sub-…’s all is as fresh installation.

1. Which version of WPMU are you running? WordPress MU 2.9.1.

2. Did you install WPMU as a directory or subdomain install? directory

3. If a directory install, is it in root or in a subdirectory? subdirectory

4. Did you upgraded from a previous version of WPMU? If so, from which version? no

5. Was WPMU functioning properly before installing/upgrading BuddyPress? i believe so.

6. Which version of BuddyPress (BP) are you running? latest

7. Did you upgraded from a previous version of BP? If so, from which version?

8. Do you have any plugins other than BuddyPress installed and activated? no

9. Are you using the standard BuddyPress themes or customized themes? standard

10. Have you modified the core files in any way? no

11. Do you have any custom functions in bp-custom.php? no

12. If running bbPress, which version? Or did your BuddyPress install come with a copy of bbPress built-in? built in

13. Please provide a list of any errors in your server’s log files.

14. Which company provides your hosting? heart internet

Great work! I haven’t had the time for a detailed test, but i have some short feadback for the beginning:

1. Everything works fine and seems logical. Thats great. There could be some front-end twaeks, but i will come back later next week with some more detailed ideas and mockups.

2. From our experience it is great to have advanced edit functions but hide them in a second row from the avarage user (like the wordpress backend editor does). For a wiki article the user (students) should focus on the content instead of any fancy formating. Basic options could be a select-box for h1, h2, h3 (this is important and must be easy accessible, because it will build the toc and people should get used to it) bold, italic, url link, unordered list, and numberd list. Everything else could go in a second or third row which appears if you click some “advanced options” button.

3. (future release) A searchable wiki directory page with all public pages.

4. (future release) “Suggest a wiki page” button so that non admin-members could ask the admin to create a new wiki page for them.

5. (future release) non-admin wiki page creation

@dwakabayashi, where can we get your BP plugins?

“you will have a merge script to port any existing installation to the new structure,”

Just a minor correction: in 3.0 you just upgrade. That’s it.

There were tow conversations going on about needing a script, one was in regard to making wp 3 have multiple blogs. This happens now in trunk via switching on an option. (way cool btw)

The other conversation about needing a script, was referring to people who had multiple single WP installs and wanted to merge them into one wp 3 install.

So – if you start now with BP on MU or on WP, when 3.0 comes out, you upgrade as usual.

And it’s WordPress 3.0.

Enrich73, we are working with speaklike and worldwide lexicon on a plug-in that will allow WP blogs to be translated by humans and/or machines.

Of course our work is GPL

We built all of our work on it.

Hi,

have you checked the buddypress-group-documents plugin?

https://wordpress.org/extend/plugins/buddypress-group-documents/

@DCCartwright – i think it’s a winner. I think you’ll find a lot of interest in this… Folks have hacked it (mediawiki) together in various ways..and you might benefit from a team effort with some of these guys that have done so.

Just to clarify – you should not be moving any themes from the BuddyPress directory. From WordPress 2.9 onwards the themes will be automatically detected in the BuddyPress plugin folder. You can simply create a new child theme in wp-content/themes and it will automatically know that the parent is in the BuddyPress plugin folder.

Mike: Not sure why you want to remove the custom header functions? They simply provide a UI to uploading a custom header image in Appearance > Custom Header.