User list view showing total nodes created for each user I have a view which displays a list of particular users. For each user displayed I would like to also display the total number of nodes that user has created.

I was wondering if there was an easy and/or efficient way of doing this, or if there is a module available that can? Obviously you would not want to calculate each total on the fly, but rather have the totals cached and updated whenever a user creates/deletes a node.

It would be nice if a module existed that could take care of this aggregate accumulation, and not just for node creation/deletion but for any desired aggregate (per user, or per node, etc).

Any help is greatly appre
If I understand the question this can be done in Views using aggregation.


Set up a View to list All Content (not users). Select Unsorted. Show fields rather than teasers. 
Double check you really don't have any sorting in the Sort criteria section. If you do, it'll mess up the aggregation settings. If you forgot, remove it now. I know I'm repeating here, but if you don't do this you run the risk of driving yourself crazy wondering why aggregation doesn't seem to be doing what it's supposed to.
Add the Content: author relationship (in the Advanced section). This is so you can gain access to the the name field for the user.
Add the 'User: name' field (in the Fields section).
Turn on the Use aggregation option (in the Advanced section under Other).
Change the Aggregation settings for the Content: Title field. Set aggregation to COUNT. This will count up all titles authored by the same user.
If you need sorting, e.g. in descending number of posts, you can add that. But make sure under sorts you set the aggregation settings correctly, e.g. to COUNT. Alternatively, leave the Sort criteria section empty and sort via the Table format.


That's the tricky bit. If that's all working you can refine the output with Global: Custom Text fields or use of tables.

Your view configuration will look at bit like this:





Note: if you user entity has extra fields, e.g. for a richer user profile or for name variants etc. you may be able to access these through the 'Content: author' relationship. Or you may need to add another relationship.