BuddyPress.org

@David Lewis, It’s a page template in your standard theme directory. You just need to select it in your page edit screen as template for the site where you want the calendar or event list to be displayed.
Look in your theme for a file: page-events-list.php
If you can’t see the template, check the page-events-list.php and add the missing Template name.
`
/*
Template Name: Events Calendar List
*/
`
@kunalb, first of all, thanks for the nice powerful plugin. Brilliant work!
I have a question. how can I display the event categories?
I like to display The event categories in the sidebar. But with the eventspress templates for the entry. Not as a normal entry.
I couldn’t find anything in your files. Will this function be developed soon? It’s an important part for me.

The markup for the edit profile page is in the theme directory, members/single/profile/edit.php. The change avatar page is right next to it, members/single/profile/change-avatar.php. The markup for the settings screens is created in bp_core_screen_general_settings(), located in buddypress/bp-core/bp-core-settings.php. It’s possible in theory to move all of this markup to the same file – say, edit.php.

Then you’ll have to combine the form data handlers, which might be more tricky. When you save your settings panels, they are run through bp_core_screen_general_settings; you can find the code you need there. When you save the Edit Profile screen, it gets run through xprofile_screen_edit_profile() in buddypress/bp-xprofile.php. And the first stop for the Change Avatar page is xprofile_screen_change_avatar(), also in bp-xprofile.php. You’d have to merge all of these handlers somehow in order to get them to process data from the same HTML form.

Good luck.

@fillsee226, the delete button is not in the admin dashboard, it’s in the front-end.

Assuming you’re the Site/Super Admin –
Go to home page,
select on groups tab in main navigation bar,
select group you want to delete,
in group page under group avatar, select on “Admin” link in bar, then select “Delete Group”

Hi!
I’m using WP 3.0.1 multi-site with Buddypress 1.2.5.2.
First of all, the plugin have a minor bug to be fixed: at line 594 of bp-maps.php must be closed the comments adding a / at the end of the line.

Then, I’ve other bugs that, maybe, went fixed yet on the plugin support forum (http://dev.benoitgreant.be/bbpress/forum/buddypress-maps). But that forum no more exist

1. reported at https://buddypress.org/community/groups/creating-extending/forum/topic/buddypress-maps/?topic_page=1&num=15#post-39374
Everytime I edit the profile the link send me to the top of the page and do nothing. May be a javascript problem?

2. reported at https://buddypress.org/community/groups/creating-extending/forum/topic/buddypress-maps/?topic_page=3&num=15#post-53565
Sometimes i’ve Warning: Invalid argument supplied for foreach() in /wp-content/plugins/buddypress-maps/bp-maps-templatetags.php on line 210 in the profile page.

3. reported at https://buddypress.org/community/groups/creating-extending/forum/topic/buddypress-maps/?topic_page=3&num=15#post-55594
Basically the plugin try to search the location with the xprofile-fields provided, but it don’t find anything so suggest to use the markers. Due to the 1. problem i cannot create a new marker. Also i cannot edit the map pointing a marker on it.

@grosbouff Can you re-establish the old support forum?

I think this plugin is really useful, so any help would be really appreciated

@dorothysulzmann
Not sure I understand your statement ” can’t find anything to help”? what is you other thread about then? and if the help that you are getting in that thread isn’t working why haven’t you posted back to that thread.

We can’t magic up code for you we can help you in the right direction, we all have things like this we are trying to solve or work out sometimes it does take a bit of time to get there.
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/listing-members/

@katemgilbert

field_5 cannot be the field ID they are numeric so not sure where you have got that idea, did you simply copy an example from the codex loop page/

Read the thread I linked to, not necessarily the solution you are all after but should help. As for simply displaying a particular field it’s a relatively trivial matter and should be clear how in that thread.

https://trac.buddypress.org/browser/tags/1.2.5.2/bp-themes/bp-default/members/single/profile.php where you can see calls to different parts of profile page lines 13, 16, 19
Line#19 – https://trac.buddypress.org/browser/tags/1.2.5.2/bp-themes/bp-default/members/single/profile/profile-loop.php

You can change style in either 3 ways: a) tweak css only; b) customize BP files; and c) tweak css and customize files. Tweaking CSS is the easiest way. Customizing php file is more intensive. Install Firebug add-on for Firefox to help you find hooks to change layout/colours via CSS.

I think €100 is well worth it for a good plugin. If the plugin means I can save a lot of time and get the results I need immediately, then yeah I’ll happily pay. My time and frustration are worth money too. If he spends 20 hours developing a plugin and I buy it for €100, I think I just got a great deal!

I find this JobBoardr plugin particularly interesting because we had a similar plugin written for our site, easyoutsource.com. It’s a job hiring site for Americans to hire people in the Philippines as online workers. The big issue, as you’ve already discovered I’m sure, is how to separate the roles. We set up a custom field for workers and one for employers and made you pick your role on signup. The role is just a profile field you select on signup. Then on the site every function is dependent on which role you picked. Groups have been turned into jobs entirely. Employers can create groups and workers can apply to them. Another big issue we had was that employers always showed up in the search results. We wanted to display workers (members) and jobs (groups). No employers. So we had to get a custom plugin written (by the ever so talented R-a-y) to hide employers from search results.

It’s interesting that you’ve set it up so that employers ARE groups and workers are members. Are your employers not also members? Do they have their own profile pages? How did you get this to work correctly?

@TedMann

This is what I’ve added to .htaccess to block bots:

# IF THE UA STARTS WITH THESE
RewriteCond %{HTTP_USER_AGENT} ^(aesop_com_spiderman|alexibot|backweb|bandit|batchftp|bigfoot) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(black.?hole|blackwidow|blowfish|botalot|buddy|builtbottough|bullseye) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(cheesebot|cherrypicker|chinaclaw|collector|copier|copyrightcheck) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(cosmos|crescent|curl|custo|da|diibot|disco|dittospyder|dragonfly) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(drip|easydl|ebingbong|ecatch|eirgrabber|emailcollector|emailsiphon) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(emailwolf|erocrawler|exabot|eyenetie|filehound|flashget|flunky) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(frontpage|getright|getweb|go.?zilla|go-ahead-got-it|gotit|grabnet) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(grafula|harvest|hloader|hmview|httplib|httrack|humanlinks|ilsebot) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(infonavirobot|infotekies|intelliseek|interget|iria|jennybot|jetcar) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(joc|justview|jyxobot|kenjin|keyword|larbin|leechftp|lexibot|lftp|libweb) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(likse|linkscan|linkwalker|lnspiderguy|lwp|magnet|mag-net|markwatch) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(mata.?hari|memo|microsoft.?url|midown.?tool|miixpc|mirror|missigua) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(mister.?pix|moget|mozilla.?newt|nameprotect|navroad|backdoorbot|nearsite) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(net.?vampire|netants|netcraft|netmechanic|netspider|nextgensearchbot) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(attach|nicerspro|nimblecrawler|npbot|octopus|offline.?explorer) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(offline.?navigator|openfind|outfoxbot|pagegrabber|papa|pavuk) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(pcbrowser|php.?version.?tracker|pockey|propowerbot|prowebwalker) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(psbot|pump|queryn|recorder|realdownload|reaper|reget|true_robot) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(repomonkey|rma|internetseer|sitesnagger|siphon|slysearch|smartdownload) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(snake|snapbot|snoopy|sogou|spacebison|spankbot|spanner|sqworm|superbot) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(superhttp|surfbot|asterias|suzuran|szukacz|takeout|teleport) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(telesoft|the.?intraformant|thenomad|tighttwatbot|titan|urldispatcher) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(turingos|turnitinbot|urly.?warning|vacuum|vci|voideye|whacker) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(libwww-perl|widow|wisenutbot|wwwoffle|xaldon|xenu|zeus|zyborg|anonymouse) [NC,OR]
# STARTS WITH WEB
RewriteCond %{HTTP_USER_AGENT} ^web(zip|emaile|enhancer|fetch|go.?is|auto|bandit|clip|copier|master|reaper|sauger|site.?quester|whack) [NC,OR]
# ANYWHERE IN UA — GREEDY REGEX
RewriteCond %{HTTP_USER_AGENT} ^.*(craftbot|download|extract|stripper|sucker|ninja|clshttp|webspider|leacher|collector|grabber|webpictures).*$ [NC]
# ISSUE 403 / SERVE ERRORDOCUMENT
RewriteRule . – [F,L]

To help block spam registrations, add the following to .htaccess, then create a simple GOAWAY type html page and upload to your root directory:

# BEGIN ANTISPAMBLOG REGISTRATION
RewriteEngine On
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .wp-signup.php*
RewriteCond %{HTTP_REFERER} !.yoursitehere.com. [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) http://yoursitehere.com/yourgoawaypage.html [R=301,L]

Add the following to .htaccess to deny access to wp-config.php to anyone who doesn’t have your ftp details:

order allow,deny
deny from all

Instead of example.com/register or example.com/sign-up, use something like example.com/unb2x-2010 for your register page. If you were a spammer, would that look like an inviting url to hack?

Hope this helps

Wouldn’t call it hijacking. I have the exact same problem as cristina.
-permalink structure, done without any result (just like cristina)
-putting index.php infront of pages, members, groups and other functions finds the pages but all links are broken (as above)
I can’t get the permalinks to work and I don’t understand how I give localhost (there is no ftp involved) access to the htaccess file. Maybe I should post a different thread. “Can’t make sense from thread “The requested URL /groups/ was not found on this server.” Sry. but you do sound harsh.

.htacess

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

wp-config:

<?php
/**
* The base configurations of the WordPress.
*
* This file has the following configurations: MySQL settings, Table Prefix,
* Secret Keys, WordPress Language, and ABSPATH. You can find more information by
* visiting { @link https://codex.wordpress.org/Editing_wp-config.php Editing
* wp-config.php} Codex page. You can get the MySQL settings from your web host.
*
* This file is used by the wp-config.php creation script during the
* installation. You don’t have to use the web site, you can just copy this file
* to “wp-config.php” and fill in the values.
*
* @package WordPress
*/

// ** MySQL settings – You can get this info from your web host ** //
/** The name of the database for WordPress */
define(‘DB_NAME’, ‘***’);

/** MySQL database username */
define(‘DB_USER’, ‘***’);

/** MySQL database password */
define(‘DB_PASSWORD’, ”);

/** MySQL hostname */
define(‘DB_HOST’, ‘localhost’);

/** Database Charset to use in creating database tables. */
define(‘DB_CHARSET’, ‘utf8’);

/** The Database Collate type. Don’t change this if in doubt. */
define(‘DB_COLLATE’, ”);

/**#@+
* Authentication Unique Keys.
*
* Change these to different unique phrases!
* You can generate these using the { @link https://api.wordpress.org/secret-key/1.1/ WordPress.org secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define(‘AUTH_KEY’, ‘put your unique phrase here’);
define(‘SECURE_AUTH_KEY’, ‘put your unique phrase here’);
define(‘LOGGED_IN_KEY’, ‘put your unique phrase here’);
define(‘NONCE_KEY’, ‘put your unique phrase here’);
/**#@-*/

/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each a unique
* prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = ‘wp_’;

/**
* WordPress Localized Language, defaults to English.
*
* Change this to localize WordPress. A corresponding MO file for the chosen
* language must be installed to wp-content/languages. For example, install
* de.mo to wp-content/languages and set WPLANG to ‘de’ to enable German
* language support.
*/
define (‘WPLANG’, ”);

/* That’s all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined(‘ABSPATH’) )
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . ‘wp-settings.php’);

@bpuser44 : Thanks for the positive feedback. I hit the support forums a little hard over the weekend.

You can find stuff on bp-custom.php and / or functions.php (which can be used for similar things in your theme folder) by searching the forums. BuddyPress development is not as simple as WordPress theming – you are looking at hooks, filters, and reworking core functions a lot more in BP. This should lessen as the API develops in future releases.

BP would benefit no end from a great set of developer tutorials; finding the resource (right people) and time to write them is the big challenge in the Open Source world.

There was a short lived job board forum on the site – that would be a great place to advertise and for you to find BuddyPress consultants, plugin developers, and website designers. Unfortunately, the board was taken down – I don’t know why. We have a current freelance opportunity for a skilled BuddyPress developer, but nowhere effective to advertise it – which is really frustrating.

Most of our work is on commercial BuddyPress developments – so feel free to give me a shout if you want to explore the consultancy route (http://21inspired.com).

You should have signed up for the 24 hour priority support plan – drop @apeatling a line and ask him to upgrade you.

You can change the structure of the page title by implementing your own version of the function: bp_page_title(), or by implementing a filter on bp_page_title. ( You’ll find these functions in bp-core-templatetags.php)

Put your modified function (or filter) in your bp_custom.php file

If you go the modified function route, remember to update your header.php in your bespoke theme to call the modified function instead of the core bp_page_title().

You might also want to suggest a change request for a future version of BuddyPress to output title in a more SEO friendly way by default.

If you have any problems with filters, bp_custom.php, or writing your own bespoke theme, you will find plenty of support threads in these forums

“nice plugin, only issue I see is that it tweets the URL of the page you are on rather than the item.”

@modemlooper This would work nice for a tweeting a group though ( and adding “facebook Recommend” ) so that all the ‘feed things/social stuff pertaining to the group’ are in a similar place.

Im trying to get the tweet button to be between the rss feed class and the activity-filter-select div, as in the image ( using add_action('bp_before_group_body', 'bp_tweet_button_activity_filter'); ) its inserting it above the subnav div, ( needs to be inside subnav.. ) but I can figure out how to get it between the two. Once I can position it correctly I’ll add the Facebook one too. Maybe can be a seperate, spin-off of your plug-in?

Maybe if someone knows where to find the subnav ( for groups ) code I can have a look and get it sorted.

Edit: Iv’e created a topic not to hi-jack the thread: https://buddypress.org/community/groups/creating-extending/forum/topic/inside-group-subnav/

Abit of topic but just some input.

One thing I find really useful in my current theme is indevidual sidebars for the different pages. Like sidebar-members and sidebar-members-single, on the members one you can display stuff about the entire network and when on members-single, you can display stuff related to the member, such as friend, points ( cubepoints ) and so on.

Ive done this with groups, blogs, members.. just about all my ‘sections’ have their own sidebar which shows related data.

One thing I hate though is when ppl go overboard with a themes options, trying to dig into messy code isn’t fun so I would say keep it simple and clean.

Actually, I believe this is the more relevant code:
ul#nav {
margin: 0;
padding: 0;
position: absolute;
right: 15px;
list-style: none;
bottom: 0;
max-width: 65%;
}
ul#nav li {
float: left;
margin: 0 5px 0 0;
}
ul#nav li a {
display: block;
color: #fff;
text-decoration: none;
padding: 5px 15px;
background: url( ../images/60pc_black.png );
-moz-border-radius-topleft: 3px;
-webkit-border-top-left-radius: 3px;
-moz-border-radius-topright: 3px;
-webkit-border-top-right-radius: 3px;
}
ul#nav li.selected a, ul#nav li.current_page_item a {
background: #f5f5f5;
color: #555;
}
ul#nav a:focus { outline: none; }

Are you just using the default theme?
If you’re going to mod very much at all, you should technically create a child theme and work from there, although it’s easy enough to save your CSS as you go.
(Hey, smart forum members, is there already a skeleton theme somewhere? I could probably post one, if not.)

Anyway, assuming you’re working from the default theme, find the folder “bp-default” in the “bp-themes” folder in the buddypress plugin folder. Then open style.css and, working from the above, after the existing lines in the style.css file, add only the parts that pertain to color (e.g., ul#nav li:hover > a{background-color:#330033; color:#9900FF;}
). That way, as long as you remember to backup this file regularly, you’ll know exactly what you’ve modified from the original.

If you want a menu with dropdowns, we’ll need to add some other code. Can pretty easily modify it to use WP3’s new custom menus. You can also remove (some or all of) the buddypress bits from that top menu if you want less clutter.

I had two users apparently never get the activation email. (One is me, so I know it didn’t go through, but the other attempt belongs to someone I don’t know. They MIGHT have simply never opened the email.) My first attempt used a hotmail (live.com) address. The other person’s is a personal domain.

I thought I was having a problem with ALL activation emails, but when I tried a new user registration with a gmail address, it worked. I suppose I should test new user creation with some more email addresses and providers.

In any case, if you don’t have tons & tons of new users, one thing you can do while “we” figure this out is to check the Users list under the WordPress settings (from wp-admin), as even unactivated users will show up there. Then visit any problem user in buddypress by manually typing in the address for their profile page (you know, something like http://www.example.com/members/USERNAME/). Then in the admin bar, you’ll find an option along the lines of “Admin Options->Mark user as not a spammer”. That’s probably not the exact text.

@hnla

Thanks for the update for WP3.0! I’m still trying to find my way with basic php and am just now getting my head around functions, actions, hooks, et al.

To whit, I discovered my code is causing the Community dropdown (contains all BP links) to appear in the adminbar in member sub-blogs. The WP pages do not appear in member blogs though.

If I turn this code into a plugin (and I want to try my hand at that) I think would be good to include the option for super-admins to include/exclude BP and WP dropdowns in member blogs. I can’t figure out how to code that though. Any suggestions?

When you refer to a child theme it refers to the ability to create a new blank folder within the ‘theme’ folder this would be considered a ‘Child theme’ if it simply had a stylesheet residing in it’s root /top level that stated it was using the files from a particular parent theme, what then happens is having selected this theme – which now would appear in your dashboard themes page, – WP examines the stylesheet information at the top of the file and finds that it instructs WP to look for files in a particular theme as being the main theme files to use; however the clever trick is that WP first knows that it must look in your child theme for necessary files FIRST! and if they are not found THEN look for the necessary file in the stated parent theme, thus you do not have to have any files in your child theme as WP will use the parent files, but you can add new CSS rulesets to the stylesheet living in the child theme and these will be read and acted on (that stylesheet references the parent CSS stylesheet files through the @import rule first and then reads on for any additional rules you have added below the @import calls)

If you do not want to make any changes to BP-Default theme then you simply activate that theme as seen in the theme page in the dashboard. When members create a blog then those blogs should use the twentyten theme or whatever other themes you choose to download and make available (Note that you decide what themes are available to members via the ‘Super Admin >Themes’ page only the themes that you select ‘yes’ to are available to member blogs so to avoid them attempting to use the BP-Default on user blogs you ensure BP themes are not selected)

If you decide that you do need to make changes to BP-Default theme then you would create a folder under ‘Themes’ name it ? ‘my-bp-default’
to the folder you add the requisite stylesheet and now you can move files as required from bp-Default original folder to your new folder and edit them as you wish, or simply create new rulesets to style elements which you place in the new stylesheet file. BP/WP now looks at your new child theme for any files that it must use in preference to the same versions that might reside in the original theme folder.

Apologies if the above covers ground you already understand.

I don’t really get what you’re trying to do with that code. Those admin pages are blocked from regular group members by default. You shouldn’t need any additional code to do that.

@r-a-y, @Travel-Junkie I replaced Ray’s original code with Travel-Junkies as it was favoured by the majority. However I´m using a lot of pages and Travel-Junkies solution is only blocking the core Bp functions. In addition Ray’s post is no longer present. What do I need to add to block all of my pages for non registered users? where can I find Rays original code?

“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.

@alanchrishughes said: “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.”

Just waking up Alan, so I hope I haven’t completely misunderstood. Personally, I’ve always been interested in how people respond to software systems. I think one of the main problems these days is that techies are so into, and used to, all things forum-ish, etc., that it’s second nature. People who get into systems like WordPress and BuddyPress quickly become techies, often without realising it, and take up the common language and perspectives of the software system they’re using. However, from the average user’s point of view, everything is very different.

We’ve done a lot of research with local people regarding using community websites. They know what a community is, and they know what a group is, at least in the real world. But mention a forum or a blog and we hear, “A what?! Oh, don’t give me all that computer-speak, and *don’t* try to make me understand all that rubbish”. This from some young people as well as older ones not so used to technology.

In building a social network as we are right now, forums are pretty much useless, and so are blogs. Why? Generally speaking, because in community organisations a forum is a face-to-face meeting of different service providers, and in business an online forum is seen as a bunch of people talking constantly about nothing on the Internet, ie., not much real use in terms of serious networking and increasing profits. Blogs are perceived as even worse: people blathering on and on about nothing of much interest to the world because they haven’t anything better to do, and love to see themselves racking up the page count and traffic day by day. This is our experience here in the UK, at least in our locality.

Groups, on the other hand, everyone can relate to. People form groups in real life, and the word ‘group’ is one everyone readily understands. Consequently, if I tell a local voluntary group that they can have their own online group, and even keep it private if they wish, they respond positively and grasp the idea of posting messages in a group. That’s all a group need be: forums and blogs don’t come into it. The response I’ve personally had to the question of whether someone would like a blog is, “Why?” and to the question of whether they’d like a very useful online forum it’s almost always, “But we already have a forum, twice a month”!

Whether the take-up on our site is good once it’s completed and advertised is dependent upon many factors. One thing I’ve learned to do over the past few years though, is switch off from the latest cool thing like forums within blogs within groups within posts related to other blogs which pull in every social network on the planet because you typed a certain key phrase. OMG yes it’s all so cool, but OMG do you end up with only users who also think it’s cool. The rest of the world don’t flaming well care, and the rest of the world IS the world.

Just my two-pence worth as they say here, but I’d look at what your users will find useful, and how what you’re building will make sense to them in terms they currently understand. In the recent past I’ve tried to enthuse people about all the cool stuff we have available, but unless it relates quickly and simply to their real world tasks it’s a waste of time and effort.

Groups are cool and useful because they reflect simple public/private real world entities.