Opened 16 years ago

Closed 16 years ago

Last modified 15 years ago

#7633 closed (wontfix)

Feature request: Admin-configurable settings interface

Reported by: Leaf <LeafStormRush@…> Owned by: nobody
Component: Contrib apps Version: dev
Severity: Keywords: db, settings
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


I have a suggestion for Django's included admin framework. Essentially, it's the ability to create app settings pages that could be editable from the admin. The essential idea behind it is that there's one record per site. It can be used to configure global app settings - for example, if you're sharing your code with someone else, writing an app specifically for distribution to other users, or just want to make it easier to change things without editing your templates directly.

It would be pretty simple - you just create a Model like you would normally, but in the Admin section of the Model definition, you would do something along the lines of setting a "Mode" parameter to "Settings". It would then show up under your app heading in the admin, but when you click on it, it will immediately call up the editor. After changing the settings, you'd then be able to retrieve the data somehow - maybe by using the existing Model systems, or maybe by using some sort of "Settings.<model-name>.<field-name>" setup.

I would greatly appreciate it if this setting was implemented.


Change History (4)

comment:1 by Alex Gaynor, 16 years ago

Component: Admin interfaceContrib apps
Keywords: db settings added
milestone: post-1.0

This is something that has often been discussed and can be seen in apps like db-settings, and Satchmo's configuration app. It may eventually become a contrib app, but for now it isn't on the roadmap due to the push for 1.0.

comment:2 by James Bennett, 16 years ago

Resolution: wontfix
Status: newclosed

This should actually be closed; the idea's come up before and, I'm pretty sure, been rejected.

comment:3 by Marty Alchin, 16 years ago

You're more than welcome to check out dbsettings, which sounds like it will do much of what this ticket is asking for, but it's not something that needs to be in Django itself. It (or something like it) might someday make it into the django.contrib package, but there's no sense having a ticket out there for it until it's ready for prime time.

comment:4 by (none), 15 years ago

milestone: post-1.0

Milestone post-1.0 deleted

Note: See TracTickets for help on using tickets.
Back to Top