A big step for the members module

The members module went through some big changes recently. Apart from some bug fixes the following features were added:

  • Weighted fields!
  • Blocks
  • Improved menu settings
  • Page/block header and footer

I'm currently working on adding some more fields like the amount of nodes created, amount of comments, amount of [content type] nodes, ... This would make it very easy to create a customizable block that displays the Top 5 posters or Top 10 bloggers for instance. After that filters and arguments will be added. Exciting times!

Comments

What is it?

What exactly is the Members module? Is it a simple extension of the User Module, providing most useful blocks and menu's or does it do something entirely different?

I dont want to pee on your fire - but you say that you're going to work on adding more fields like "nodes created", etc... Is this for admin purposes? In any case, isn't this something that the Views module can easily do?

views for users

My understanding is that Views 2 will include support for base tables other than the node table, meaning that it will be able to do a lot of what this module currently does.

But until then...

Views 2 and users

Well, when Views 2 is out, it will support the user table just fine, and there won't be a need for usernode, and it will do all this stuff. However:

1) Views 2 isn't out
2) Views 2 will only be Drupal 6.

So it's great that I'm here saying this'll happen, but this one is here now and it works. Use what works. I'm all behind this.

At least until Views 2 is out. But even then, this may well have spiffy features Views won't have (and instead maybe it'll offer Views support =)

I want the members listing

I want the members listing to be displayed in two columns.. How it possible...

I checked with Earl

Hi Dalin, I checked with Earl (merlinofchaos) about this when I heard about Views 2 and its ability to include tables other than the node table. Although the users table can indeed be plugged, the same usability will not be attained because other tables will always be looked at from a node point-of-view. Earl suggested that to provide lists of users with views (and views 2), the usernode module is used. While this might be good for some purposes, in my opinion this will not always be the easiest or fastest way.

User listing

Hi Nicholas,

The members module does/aims to do do for user listings what views does for node listings. You can create blocks and pages containing user listings of any sort, adding the user's picture, created date, roles, organic groups, ... I will be adding the amount of nodes created so people can easily create a block that contains the Top x posters for instance. Currently people need to use a php snippet for this and not everyone is familiar with this method. With the members module people will be able to create such a block with just a few clicks. You could use it for admin purposes if you want. An extra addition will be communication with modules like mass_contact so mails can be send to specific lists of users.

The views module, and even more so for views 2 can do this partly when you use the usernode module, which is overkill for most purposes. Views will always be node-oriented while the members module is user-oriented.

thanks for the clarification

Thanks for clearing that out. If Views 2 will support this without the usernode module, then I will certainly put my time in contribution to the views_user.inc. This functionality is something a lot of people need and most people will be using the Views module already for other functionality so there's no reason to split it up between 2 modules.

Post new comment

The content of this field is kept private and will not be shown publicly.