Difference between revisions of "Extensions:Design Update Voting"

From Lorekeeper Wiki
Jump to navigation Jump to search
Tag: 2017 source edit
Tag: 2017 source edit
Line 1: Line 1:
{{Extensioninfobox|title=Design Update Voting|desc=Adds the ability for staff with masterlist permissions to vote on pending design updates.|auth=Mercury|status=Testing|github={{Github|user=itinerare|branch=design-update-voting}}|migration=yes|package=no}}
+
{{Extensioninfobox|title=Design Update Voting|desc=Adds the ability for staff with masterlist permissions to vote on pending design updates.|auth=Mercury|status=Testing|github={{Github|user=itinerare|repo=lorekeeper-ext-archive|branch=design-update-voting}}|migration=yes|package=no|modified-main=yes}}
 
<!-- Put a short summary of your extension here! -->
 
<!-- Put a short summary of your extension here! -->
 +
'''This extension is now incorporated into {{Github|user=corowne|branch=modified-main}}.''' The information here is maintained as documentation, and further support is via that branch.
 +
 
Note that this incorporates the changes in {{Github|user=preimpression|branch=bootstrapTables}}!
 
Note that this incorporates the changes in {{Github|user=preimpression|branch=bootstrapTables}}!
  

Revision as of 09:41, 15 November 2020

Design Update Voting
Description Adds the ability for staff with masterlist permissions to vote on pending design updates.
Author(s) Mercury
Status Testing
Github itinerare/lorekeeper-ext-archive/design-update-voting
LK Version Unspecified
Contains a Migration
Is part of LK v2 (modified-main)






This extension is now incorporated into modified-main . The information here is maintained as documentation, and further support is via that branch.

Note that this incorporates the changes in bootstrapTables !

Adds the ability for staff with the Manage Masterlist permission to vote on pending design updates and MYO submissions. Note that this doesn't actually process submissions either way, it is just intended to serve as a communication tool (since sometimes a drive-by "looks good" button press is more manageable for folk). The number of votes "required" is provided via an added site setting; the default is 3.

Specifically, it adds a card to the header of pending and approved design updates. Staff can only vote on pending updates, but the information remains displayed on approved design updates for the sake of archival. In the top right are buttons to vote to approve or reject, above which are displayed the current number out of the total required number of votes. The bottom half is given over to the lists of each sides' votes/voters, with usernames for the sake of record keeping. It also adds a display of the current votes in the admin queue/index displays.

Installation

Pull the branch; run

php artisan migrate

and

php artisan add-site-settings

Configuration

If desired, change the number of votes requested in the "site settings" admin panel.

Usage

The voting panel will appear on pending design updates/MYO submissions. Staff can then click the voting buttons in the top right of it to cast their vote.

Troubleshooting

Find me in the Lorekeeper discord!

See Also