Jump to:
| Project: | Smartqueue Per User |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
so this seems like an outstanding tool for content rich sites where the emphasis may be on a large contributing user base - but i'm a bit unclear about when i'd use this versus these other options:
views (to create a custom tracker of any kind visible to any/each user, automatically created/vanishes with user creation/deletion)
tracker (the default in core, which also shows everything a 'user' has done in his/her profile, automatically prepopulates and vanishes with new/dead user accounts)
activity (which can be assigned to specific actions, including those beyond this module - like 'favorite nodes' and 'user relationships' - and displayed in profiles, blocks etc - also automatically appears/vanishes with user account creation/deletion)
others (not sure what they are)
when you designed this module, were you looking at tracker as a point of reference, or were you looking at how a user manages the content that he creates within a site? it's a bit unclear and it would be great to see or read an example of where this makes a lot of sense, or what prompted you to design this ...
Comments
#1
Here's a use case example: I'm building an apartment listing website for a client. Real estate brokers who buy the right level of access are allowed to mark 5 of their properties as "featured" (using this module). When the homepage is loaded, the entire list of properties that are featured is sorted randomly and the first x (haven't decided quite how many yet) are put on display (using views).
The reason this specific module works so well, is that it builds in the 5 property limit without needing to implement any kind of quota system. When a 6th property is added to a user's feature list, the oldest simply falls off automatically.