Posted by xjs on February 24, 2008 at 9:00pm
Jump to:
| Project: | User Points Contributed modules |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
What the main usage of user point categories besides setting all points to the default category?
I though with this feature, I could assign points earned from different channels into different categories, such as blogging points, user2user points, etc. However, it seems that I couldn't do this. Am I missing anything? Thanks!
Comments
#1
You are right about the purpose of storing points in different categories.
The way to use it is at the API level. You write a module to store the points in the categories you want for the actions/conditions you want.
If you are using an existing module, you can modify it to have settings for that feature and submit patches for it.
#2
It would be nice if this could be set for the basic events included in the User Points module.
For example, on admin/settings/userpoints under "Points for basic events" it would be nice to change not only the number of points awarded, but also the point category. I don't know if that's hard to program or not... but it would be nice.
#3
Makes sense for an quick start +1
#4
Am supporting this feature request.
There could be default categories like
1. Node creartion
2. Registration
4. Commenting
#5
Totally agree! Actually, I logically thought that was how the system was setup. For example, I have different points for example when a user invites members to my site I give them one point and when they add a listing to my online site (which is a online directory) they get 5 points.
These points go to a category called site-contribution. These points never expire.
But then I would like to award points to people that write reviews of the listings on my site and have these as monthly contests. So each user that writes a review will get say 5 points and these points should be put in a category called monthly-review-contest. And these points are only valid for one month. Then at the end of that month the person with the most points wins a prize or something.
So it would be nice to set the categories to content types.
I would definitely love to see this feature added!
#6
Reopen as I think a general higher level implementation could be done and this seems to be the biggest contrib to userpoint.
Instead of selecting category on each submodule, and each submodule has to implement/provide the selection. It makes more sense to have let's say categories as tabs, and every submodule to be under each category, which you can enable/disable per category.
e.g.
submodule userpoints_badges, referral_points are enabled
Under every category, by default enabled submodule appears by category
Point A | Point B | Point C
In Point A tab, we've userpoints_badges, referral_points which apply to Point A, similarly for Point B & C.
This way, we can really have the flexibility to assign e.g. 10 referral_points point A and 1 referral_points point B at the same time. This does not break 'old way' of working.
Or maybe this can be implemented at userpoint module itself by requiring all submodules to take in category by default.
Thoughts?
#7
After giving this more thoughts, this does not apply to submodule only.
Even userpoint settings such as moderation, point branding, expiration, messages, category to display on the user profile page, should be resided as settings per category.
Example, these are currently not possible from the UI, but the API could easily support it.
- some categories of points may need moderation, some not
- different categories of points could have different expiration, some not
- select multiple categories of points to display on user profile page
- branding for each category of point, instead of the default only
- some categories of points need message notification, some not
The only userpoint setting that does not fall under this is Default Category.
Should we move this to Userpoint issue queue for further discussion?
#8
After going through the Userpoints Core and submodules, having a generic category control at Userpoints Core maybe hard as submodules are doing a lot of different things. Besides a lot of logic are local to submodules, hence adding the multiple categories support is more logical implemented by submodules.
I'm making some preliminary progress on the multiple categories support, but I'm a bit confuse on the default tid for the uncategorized points. The is no consistency as NULL and 0 are used through out, both in core and submodules. There are sporadic comments on backward compability for NULL, but no actual description.
Would like to know what is the convention/tid for uncategorized points?
To use categories as checkboxes, the #options array can not have a 0 key (ref. http://api.drupal.org/api/file/developer/topics/forms_api_reference.html...), which may require changes to the uncategorized points tid. I would suggest -1 which is a safer number. I suppose NULL would work also but could possibly conflict with no choices made.
#9
Closing this issue, any module needs to implement settings to choose the category themself. If some modules are missing that, please open separate feature requests.