Views integration should provide one field per statistic

Sorry for not replying to this sooner.

How does the Views integration work?

Badly! I didn't really implement this very well, it will be re-written at some point (though I'm concentrating on other modules at the moment).

You use the Statistic value as the field, then use Statistic name as a filter, so you only get the values you want.

Really there should be one Views field per-statistic, that would make a lot more sense. :)

I would like to point out that I followed the instructions above and that worked great. But when I add more users via user import they are filtered out. Additionally if I remove the statistic name filter my missing users come back and are listed only once with a zero where all other users are listed twice like described originally. Any fix for this?

I was going to open a new bug report for this but it seemed easier to describe here in this issue.

I was going to open a new bug report for this but it seemed easier to describe here in this issue.

Ah, you should have done that. This support request is only about User Stats' Views integration being really weird and whacky, your bug report is about it being broken, completely separate issues! :)

Now we're sending e-mails to Michelle on an issue she doesn't care about and I'm going to get confused about which bugs I've fixed and which I haven't.

If you wouldn't mind, please copy and paste your comment into a new issue, think up a clever title and I'll have a look at it. Thanks!

Still the same problem:

How can I show user stats value in a view without a patch? Can you correct this in dev version?

How can I show user stats value in a view without a patch?

You don't need a patch.

Can you correct this in dev version?

Strictly speaking, there's nothing to correct. The View integration sucks but does work, if you follow the instructions in #1. I know it's confusing, sorry. :)

Since I do intend to change this so it makes sense, instead of being really esoteric, am changing this to a bug report.

I never did get this to work without having duplicate entries and ended up using something else in that spot.

In that case, sorry for my previous post, I was wrong. It sucks and doesn't work! :)

Subscribe.

I set filter User Stats: Statistic name = post_count and now I get only one field returining the value of user posts.

Subscribe

subscribe

In current dev version this problem is still not solved. Why?
This is not a great thing.

How can it be solved per patch?

In current dev version this problem is still not solved. Why?

Sorry I haven't had time to fix this, I have started but am also busy with other work.

Unfortunately, bumping issues up to critical and being rude isn't going to make me less busy. And, as Michelle pointed out, I'm just a volunteer. :(

Here's a patch that might help. Instead of 'name' and 'value' view fields, you can use a kind of table alias to get the data for one type of statistic, even if it's in a single table.

Please review!

Thanks lavamind!
This patch is working well for me for displaying Post Count.

subscribing

This is similar to what I'd like to do, but for all fields. The idea is to loop through all the field names, building the Views array automatically.

The problem with the approach in this patch is it doesn't allow for dynamically added, new stats (like those gathered via our hook in user_stats_get_stats() for example).

Anyone wanting this feature OMGNOW!1!11one should use this patch though. Just don't build too many views based on it, because when I finally commit a permanent fix it may break them. :)

Drake's solution worked perfectly for me :)

> The idea is to loop through all the field names, building the Views array automatically.

Wouldn't the better fix to be to normalize the database table so you have one field per value and one row per user? I'm not sure why you need the current key/value schema, as every user statistic seems to be one-to-one with a user.

Are there actually any modules that add additional user_stats dynamically and require the schema to be the way it is?

Here's the previous patch update to apply to D7 Branch. I think this is the correct way for this to function. Filtered by seems messy and unnecessary considering what most folks will be doint.

Hi,
Thank you for your patch.
While this patch does provide the number of posts field, it doesn't display anything in the view results. i suspect this patch misses something, it should display my field title at least..... but it doesn't display anything.

could you please double check that this patch was ported to D7 correctly?

BR
Itzhak

update,
It does work for me, just the title is missing.

I had to reset the post counter, than run cron X times to gather all the information about the users, and now it is working as expected - it displaying the correct number of post.

THX!
Itzhak

Hi guys,

thanks for the awesome module, but as the original poster, I would like to get more out of the views. Has there been any progress or way to work around this?

Currently, I am able to display the user's post_count by adding that to a filter and then add the statistic value to as a field. But as mentioned above, there is no way to add another value such as login_count. I would like to have a view to display all my users in a table with columns showing their last login, their post count, their login count, etc. All in one table that I can sort on and filter.

Any idea how I can do this?

Thanks!

Oh btw, just to share, what I have done for now, is just expose the filter so that I can change the statistic name to change it on the fly to see the other values I want to check out. But again, I can only look at one at a time...which is just a bummer.