BuddyPress.org

yes and no. It’s not updated yet to work with current BP

https://wordpress.org/extend/plugins/achievements/

Iis doesn’t usually support php. Web.config is a file that’s used for an asp.net application/website. You should switch your plan to a Linux based hosting plan if you want to use buddypress and wordpress as those are usually best run on Linux plans. I’m not even sure how you got them running on IIS as you need mysql database and I wouldn’t think you could get one with a windows plan.

This looks like a great Widget. Unfortunately I see an error in my Home page after it has been activated:

Fatal error: Call to undefined function bp_blogs_get_latest_posts() in C:\xampp\htdocs\enterprise\wp-content\plugins\ahjira-recent-sitewide-articles\ahjira-recent-sitewide-articles.php on line 41

Sorry if this is a newbie mistake. I am using WordPress MU 2.9.2. Any idea why it thinks the function is missing?

Thank You for posting the Widget – the options looked really good.

-Gary.

Which version of WordPress and BuddyPress are you running?

To post a new topic to a thread using the Group Forums Directory, you must be a member of that group and the group must be public. So, you will not have the option of selecting groups that are private or those of which you are not a member.

I’ve been playing with Mystique as a likely candidate for a blog I’m working on, but I’d lo be able to play with BuddyPress without giving it up! So I’ll just add in another voice that’s excited for this development

@MrMaz Yeah… I’m not having any luck getting avatars resized and uploaded on a single wordpress install. BP Links (Version 0.3.2) is just embedding the URL of the original image. I’m guessing the plugin currently has no folder structure for a single install like it does for MU, which you stated earlier places avatar images in: /wp-content/blogs.dir/files/link-avatars/ — I’m keeping my fingers crossed the next release will have a fix for this

Out of curiosity, anyone know how I can alter the user link (will be editing: link-header.php)?

Currently using bp_link_userlink() but I’d like to change the output from mysite.com/user/ to mysite.com/user/links/ so people can see other links posted by the link owner.

BuddyPress nor WordPress doesn’t have such files called web.config

Every file should be named as something.php. In WordPress, for example, wp-config.php

I think it’s the smtp plugin you installed, which is causing the problem. Make sure the plugin is compatible with current versions of WordPress and BuddyPress.

This thread is going around in circles; I’m closing it. In a nutshell:

If you want to offer your members their own blog, then you will need to use WPMU. The fact that each of your members has their own blog does not mean they have their own site. All the blogs are located on and served from your site.

If you only want to have one blog but offer a social networking layer on top of that using BuddyPress, then single-version (solo-blog) WordPress is all that you need.

You can use single WP and assign users a WP role of contributor or editor if you want users to post on the same blog.

It’s not a HTML file, but rather a function that is located in /buddypress/bp-core/bp-core-adminbar.php.

What are you specifically trying to do?

If you’re trying to modify the BuddyBar, read this:

https://codex.buddypress.org/how-to-guides/modifying-the-buddypress-admin-bar/

Requires a bit of manual coding.

Or you can also try this plugin:

https://wordpress.org/extend/plugins/buddypress-admin-bar-mods/

Here’s a guide by Adam Wulf:

http://welcome.totheinter.net/2009/05/06/changing-wordpress-mu-from-subdomains-to-subdirectories/

What’s the character encoding for your WP install? See http://radoff.com/blog/2009/12/03/chinese-characters-in-wordpress/

@Brajesh Singh: Thanks. I made changes directly into the database to fix this problem. The users where are from my old WordPress installation and they registred before installing BP. Maybe it should be possible to have usernames with space, dots and whatever as WordPress do think it is ok???

Hi there,

I have just tried to install the plugin with a woo theme and cannot get it to work.

1. I have modififes my .htaccess to:

# BEGIN WordPress

<IfModule mod_rewrite.c>

RewriteEngine On

RewriteBase /

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule . /index.php [L]

</IfModule>

# END WordPress

I have my permalink settings to: /%postname%

The site is not showing an BP pages at all.

I have tried the following links:

http://leistungsakademie.com/blogs

This gives me a 404

also:

http://leistungsakademie.com/wp-content/themes/coffeebreak/blogs/index.php

The latter shows nothing…

It´s not a server issue!

Any idea?

Thanks for your help!!!

You should probably look at the “Auto Join Groups” plugin:

http://brentandmary.net/2009/10/24/bn-auto-join-group-plugin/

It does what you want it to do, but automatically from the admin area.

Haven’t tested this in BP 1.2 though.

Might want to contact the dev of that plugin if it doesn’t work.

—

Also it is quite easy to modify DJPaul’s Welcome Pack plugin to auto-join groups as well.

See my post here:

https://buddypress.org/forums/topic/bbpress-and-buddypress-1#post-43925

—

Update:

Just came across a plugin called “BP Registration Groups”:

http://hardlyneutral.com/wordpress-plugins/

Purports to do exactly what you want, Bowe.

You could create one group that all people join when they register.

Use DJPaul’s Welcome Pack plugin for that:

https://wordpress.org/extend/plugins/welcome-pack/

Otherwise go the external bbPress route, and yes, you’ll need to theme it.

[EDIT]

Forgot that Paul changed his plugin so it sends out group invites, instead of auto joining groups.

If you want to make Paul’s plugin automatically join groups.

Change the following lines in the Welcome Pack plugin from:

groups_invite_user( array( 'user_id' => $new_user_id, 'group_id' => $group_id, 'inviter_id' => $group->creator_id ) );

groups_send_invites( $group->creator_id, $group_id );

to:

groups_join_group( $group_id, $new_user_id );

I should say I haven’t tried this, but it should work.

The change from @gian-ava to the bp-core-avatars.php file on line 389 corrects the problem when running a single installation of wordpress.

Thanks @gian-ava

Yeah ok looks like it might be his theme. https://wordpress.org/extend/themes/buddypress-widget-theme

Right now the theme is more important than the plugin so I will deactivate it. That being said who it gets sorted out so I can use the attachments in the forum.

Thanks for the help

Both Andy and I have recommended several times not to use his test version; he just submitted it to me as an example of how to make correct BuddyPress usernames. There’s only one version available on the wordpress plugins repository. The advantage? That everyone else will be using the real version, that if you don’t use the real version you’ll be running unsupported code along with all the bugs that I’ve fixed since it was produced, and that obviously the documentation on my site will reflect the real plugin, not unreleased debug versions.

Yeah it is kind of a hack, isn’t it? :p

Might want to post this in Trac:

https://trac.buddypress.org/newticket

Put something about using the blog URL vs. the WordPress URL for standard WP:

https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

I think the second method will do exactly what you want.

More info here:

https://codex.wordpress.org/Changing_The_Site_URL

I would do a backup of everything just to be extra cautious!

Hi kb,

The problem you are experiencing is a different issue than rossagrant was referring to. However, I think I’ve fixed your issue in the most recent (pre-release) version. Please visit this link:

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

And click on the “Development Version” link. After you install this newer version of the plugin (the version number is still 0.3.1) please let me know if your problem continues.

Also, Are you able to upload and view avatars? I’ve found most of the time this is caused by shared code between Group Documents and Avatars.

Thanks for giving the plugin a whirl, and letting me know.