incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Bondarenko" <jetm...@users.sf.net>
Subject [allura:tickets] #7014 Trove category editing improvements
Date Tue, 28 Jan 2014 11:46:34 GMT
> 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

Where do you want to store this option?  It should be site-wise, right?  Now it's stored in
the config file and I didn't find any site-wide model for storing configuration.  Should we
add one?

It still should be boolean option available for site admins to edit or you need something
more flexible?  Like specifying users who can edit perhaps.


---

** [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:** Fri Jan 24, 2014 09:08 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.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message