BuddyPress.org

Keep it quiet from JJJ as it just might be the straw that breaks the camels back… hmm camels don’t have stripes do they?

sorry finding this subject hard to take seriously now, striping, should be the simplest thing!

Has anyone made any progress with this? Will we have buddypress checking for banned email domains soon?
Will we have buddypress checking for banned domains upon registration and perhaps even again upon activation?
Can someone please add the possibility to add *.info in a way that works
I know this won’t stop all spam and splogs – but I am getting tired of deleting a dozen spammers every day that are mostly from the same dozen domain names that I have added to the block list. This would save lots of people hlaf the splog deletions, and that adds up to a lot of time saved.
BTW – has anyone tested buddypress with TTC Spam Bot Registration plugin (https://wordpress.org/extend/plugins/ttc-user-registration-bot-detector/ )to see if there are any issues? I am guessing it may still be bypassed by buddypress even if it worked in WP?

I just replied to a similar topic with how to fix it:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/fatal-error-when-trying-to-delete-user/

I’m removing the alternating highlighting from the Privacy Component for the time being. The “fix” still has issues. It still selects for the entire form and not per table. If you add another row to the outputted settings tables in the Activity, Messages, or Friends form coding, you will see the issue when navigating to “Settings > Notifications” in your user profile menu.

It is an issue of odd versus even rows in a given table. Right now, since all the outputted tables (a total of four tables are outputted to make up the aforementioned screen) each have an even number of rows, it appears that all works fine. But by doing what I suggest–adding a test odd row–you will see the problem.

@retroriff – in your second post, you mentioned you followed the BP codex where you placed define bp site via “Specifically, you can do this by creating a file called “bp-custom.php” in your “/wp-content/plugins/” directory (if you haven’t already).”

I would suggest that you delete the code you placed in bp-custom.php and add the code in wp-config.php per my post (ref: https://codex.buddypress.org/how-to-guides/changing-internal-configuration-settings/) – it works.

@alanchrishughes They are EXACTLY like facebook fan pages. You have an activity stream on both. You have forum/discussions on both. Not sure why you think otherwise. You can also add apps to facebook fan pages and buddypress groups. They look different and the wording on each is different but they really are the same thing.

Ice-cream sundaes! Oh yes! Actually, that’s one direction Drupal has been going (not the ice-cream, sadly), which is the eventual simplification of data storage. The biggest problem now, I think, is that developers map their views to data, and vice-versa. Drupal stores everything and anything as a ‘node’. So a node can contain one word, a site link, a story, a page, images, files, or any combination of all by having nodes within nodes. Its Views module then allows you to say how nodes are displayed; as blocks (widgets), pages, in tables, rows, any kind of custom layout.

What I’m visualising at present is a way of doing things like BP’s activity stream, where data is any kind of node you like, and you decide whether nodes can overflow or are cut (eg., large images), displayed all at once or shown as a bite (eg., stories/pages and small excerpts with ‘read more…’) etc. You then just decide whether each site page appears as a single page, a list of related nodes kinda bloggish, a list of related nodes a-la activity stream, etc. A couple of clicks could create a stream, a shopping page, or whatever you wish. Users then have BP style filtering links, so they can view everything the view shows, just friend’s contributions, just their groups, etc. Off-site information can be pulled in via links as well, and displayed as the same kind of node (similar data, just a different source). Wrap all that around an individual member with a profile and roles/permissions, and you have the most powerful and adaptable social network there is.

As I say, you can do that with Drupal, but gawd is it time consuming for a large project. I like the way WordPress is going, and if BuddyPress follows suit in the simple and easy to use stakes, the two combined will be amazing.

@peterverkooijen; Good points about the focus of a social network being on the member, while a forum is focussed more around the information. I think @alanchrishughes has a point too though, about non-techies being put off by having to register.many people are still terrified that if they enter their name and email address then you’ll have access to their bank account – seriously!

I’ve built a number of sites in Drupal, which is very powerful indeed, and doesn’t suffer so much from update issues. It gives such fine control of everything that it’s amazing, and for those who haven’t tried it, you can basically build your own custom CMS with it. It takes so long to do though. We tried Elgg, which is kinda cool out of the box, and does a lot of social network things really well. However, its interface is naff (in my opinion) and theming is not easy. Worse still, adding extra pages to build a custom site means lots of coding, instead of WP’s simple click-to-add. We’re going to need that for custom background (paying) advert pages, and hopefully a lot of them as time goes on. Also, Elgg has almost no member control, roles, etc., and wile the Elgg team feel that’s not important, we strongly disagree. People do not behave nicely just because they signed up to a social network!

Personally, I see nothing wrong with a social network which allows unregistered users to comment with CAPTCHA, along with well defined and easy to use groups for members to join, and good role management and strong privacy for those who require it. That way, just as in the real world, you can have private places and high streets, with members themselves controlling who does what. For me, at least, that’s all a social network need be.

I utterly refuse to use the phrase ‘Zebra Striping’ again; from now on I have decided it’s ‘Tiger Striping’ yeah and lets leave the poor giraffes alone.

I also just upgraded to 1.2.5 BuddyPress this morning and have this same problem.

Using normal wordpress dashboard I cannot delete user… results in error message:

Fatal error: Using $this when not in object context in /###/wp-content/plugins/buddypress/bp-groups/bp-groups-classes.php on line 1053

*Note: I am not using “SuperAdmin”.
*Note: I am using “Fluency Admin” however. Shouldn’t be the issue.

When trying to delete user from front-end members page it simply does not delete the user at all. No error message or anything, it just doesn’t delete the user.

I just activate Buddypress 1.2.5 on Wodrdpress 3.0 Multisite without any problems. Can viewed on http://teronggosong.com.

@thekmen you know there’s a trac ticket for twentyten to be included with BuddyPress?

I’d already added that patch but separate to that under 3.0 and the latest 1.2.5 the activity (in the home page of http://retrofitdiaries.org) only seems to include the top level blog activity.

Activity Streams are set to work across the whole site (just one other test blog for now).

Can anyone suggest a reason?

Thanks

Have a similar problem

Prev. installation WP 3.0 and BP 1.2.4.1
Upgraded to BP 1.2.5

In the blog comments of the blog with id 2 I got some warnings:

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/is/htdocs/my-account-name/my-domain/www/wp-content/blogs.dir/1/files//avatars/3) is not within the allowed path(s): (/is/htdocs/user_tmp/my-account-name:/tmp:/dev/null:/dev/urandom:/bin:/usr:/is/default.errors:/is/htdocs/my-account-name) in /is/htdocs/my-account-name/my-domain/www/wp-content/plugins/buddypress/bp-core/bp-core-avatars.php on line 150

The Problem is, that there is no directory /wp-content/blogs.dir/1 in my installation! Besides the main blog I created only a second one (/wp-content/blogs.dir/2).

If I copy bp-core-avatars.php from BP 1.2.4.1 in my 1.2.5 installation the waring is gone! But this does not seem to be a proper solution because there a some changes in the php file …

My solution, which I found some where else in this forum: I put the following two lines in /wp-content/plugins/bp-custom.php:

define( ‘BP_AVATAR_URL’, ‘http://’ . $_SERVER . ‘/wp-content/uploads’ );
define( ‘BP_AVATAR_UPLOAD_PATH’, $_SERVER . ‘/wp-content/uploads’ );

The warning is gone

“… but I think non-techies are thrown off by having to register for websites and checking their email, verifying, password, etc. they don’t care enough and just leave.”

You can’t have a social network without verification of identity. You should just build your site in bbpress, punbb, joomla or drupal. Or Moodle.

Yes. https://buddypress.org/support/topics/feed/ should lead to topics (?) but gives the whole activity feed.

“What is the idea even behind this “groups” concept? I have been trying to understand it and figure out a way to just work with it, but it just doesn’t make sense, it’s backwards.”

“It’s like facebook fan pages. Why do people find this concept so strange?”

This is again the clash between forum and social network. They are NOT the same thing! They are different ways to structure a community. Mixing them is a recipe for disaster. Buddypress is pulled in two directions. The old-fashioned forum structure (bbpress) is winning.

A social network is organized around members. Member profiles are the main home pages, usually including a wire or blog. Members can friend or follow eachother and form groups and share content.

A forum is organized around topics. Members are secundary and are usually identified by anonymous usernames. Topics are arranged linearly, with main topics and sub-topics.

Because member management is horribly underdeveloped in Buddypress and the old BBpress users now set the tone in the developers community, Buddypress is turning into a confused forum script.