[allura:tickets] Re: #7014 Trove category editing improvements

[Dave Brondsema <br...@users.sf.net>]

Continuing to use the ini config file for this setting is fine.  I was thinking that we could support not just `trovecategories.enableediting = true|false` but also `trovecategories.enableediting = admin` which would let site admins edit.  At this point we don't have a need for more control over specific users or groups to have access.


---

** [tickets:#7014] Trove category editing improvements**

**Status:** in-progress
**Labels:** 42cc 
**Created:** Fri Dec 20, 2013 08:41 PM UTC by Dave Brondsema
**Last Updated:** Tue Jan 28, 2014 11:46 AM UTC
**Owner:** nobody

Restore the link to edit trove categories, was accidentally(?) removed in `git show b55760a -- Allura/allura/templates/user_skills.html`

Change `trovecategories.enableediting` from simply boolean to allow an option for admins only to edit.  It should be a link on the /nf/admin sidebar

Add events (via `g.post_event`) for every category add/remove/edit, so that 3rd-party code can listen for those changes (e.g. to keep another database in sync).


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.