|Version 17 (modified by rjollos, 21 months ago) (diff)|
Reddit-style voting on Trac resources
This plugin adds a context-navigation entry that lets users easily vote for a Trac resource, including Wiki pages, tickets, milestones, etc.
If a user has a valid session (created through the Preferences panel) and the VOTE_MODIFY permission, they will be able to vote.
If you have any issues, create a new ticket.
Download the zipped source from here.
Install the plugin:
If you get "error: Unexpected HTML page found at http://trac-hacks.org/svn/voteplugin/0.11", update setuptools:
sudo easy_install -U setuptools
Add the following to the [components] section of trac.ini:
[components] tracvote.* = enabled
Configure the list of URL paths to allow voting on in trac.ini. Globs are supported.
[vote] paths =
Grant users the VOTE_VIEW and VOTE_MODIFY permission where appropriate.
You may need to run:
trac-admin /path/to/projenv upgrade
You will also need to restart your webserver for the plugin to be available, appear in the list of those installed, have the perms available, etc.
The SQL for creating a report that sorts tickets based on the number of votes can be found in the repository.
-  by rjollos on 2014-02-19 12:53:46
Trimmed whitespace using reindent.py.
-  by hasienda on 2013-05-13 00:59:50
VotePlugin: Make compact and top standard wiki macro arguments, refs #4546 and #7592.
List output for all three macros is limited to a maximum of 5 items, if not
explicitely specified by top=<n>, where in turn 'n=0' means unlimited.
The previous limit of 10 items (TopVoted only) looked like too much.
And rendering of resource links respects the compact argument too, what
yields significantly reduced output for milestones and tickets.
-  by hasienda on 2013-05-13 00:37:50
VotePlugin: Re-enable voting on milestones, refs #4546, #7592 and #10942.
delete_vote obviously needed to not depend on a req object to work.
That went unnoticed, because it is called only by change listeners for now.
set_vote was not ready for unversioned resources, and a subtle insanity in
resource_from_path surfaced during early testing with milestones too.
Method name changes are done for clarity, that a single method call probably
deals with multiple vote entries.