Opened 15 years ago
Closed 8 years ago
#6603 closed task (wontfix)
Add administrative overwrite for user preferences
Reported by: | Ryan J Ollos | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | AnnouncerPlugin |
Severity: | normal | Keywords: | preferences |
Cc: | Steffen Hoffmann, Jan Beilicke | Trac Release: | 0.11 |
Description
The main page is a bit detailed and intimidating with all of the configuration parameters. Would you have any objection to moving the detailed info to a Configuration page, and providing a default configuration on the main page that should work for most users?
Attachments (0)
Change History (8)
comment:1 Changed 15 years ago by
comment:2 follow-up: 4 Changed 15 years ago by
def classification(): """Should return "simple", or "advanced". """
Then we could sort advanced to the bottom and hide the panels with javascript. We could then add a checkbox or something to the bottom for advanced settings. That would be ok with me. I don't want to create a second page though.
comment:3 Changed 15 years ago by
Sorry, I should have been more precise about what I meant. I was referring to the wiki page: AnnouncerPlugin, and trying to make the documentation a little bit cleaner.
I think the preferences panel is pretty good, and we haven't experienced any issues with users not understanding the parameters.
comment:4 Changed 15 years ago by
Replying to doki_pen:
We could then add a checkbox or something to the bottom for advanced settings. That would be ok with me.
Though, giving some thought to the feature you suggested, I do think that this could add some value in cases were an admin does not want to give users control over certain preferences. For instance, I'd really rather prefer to set the Always notify preferences via trac.ini, and not allow users to change them. Currently, I don't see a way I can over-ride the ability of a user not change some of these settings.
So perhaps a good feature would be to allow the admin to specify which of the 5 panels should be visible to users: E-Mail Format, Ticket Subscriptions, Ticket Component Subscriptions, Watch Users, General Wiki Announcements.
comment:5 Changed 14 years ago by
Cc: | Steffen Hoffmann added; anonymous removed |
---|---|
Keywords: | preferences added |
Summary: | Configuration page → Add administrative overwrite for user preferences |
Think I hit the same point (administrative overwrite for user preferences, i.e. for corporate applications) when discussing an improved preferences system with doki_pen some time ago.
Care should be taken, that any solution isn't easily exploitable as suggested in #6798. Just another +1 for an rework of the preferences system.
comment:6 Changed 14 years ago by
Cc: | Jan Beilicke added |
---|
comment:7 Changed 10 years ago by
Owner: | Robert Corsaro deleted |
---|
comment:8 Changed 8 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Please upgrade to Trac 1.2, which has integrated the core of AnnouncerPlugin. Please raise the issue on the trac:MailingList if you encounter the issue with Trac 1.2.
Right now, there is a preferenceprovider interface. Any components can implement the interface to get a panel on the Announcer Preferences page. I wouldn't object to classifying these panels, maybe by adding a method to the interface. Perhaps