Ticket #131 (new enhancement)

Opened 2 years ago

Last modified 4 weeks ago

Break Admin Options Out of a Single Table Row

Reported by: derek Owned by: derek+mike
Priority: low Milestone: 1.1
Component: Administration Version: 1.0b3
Severity: major Keywords:
Cc: derek@…, mike@…, stefan@…, johan@…, ryan@…, anti@…

Description

  • presently, plog-config is a table with a single row
    • imo, this setup isn't particularly extensible and is hampering admin panel development
  • I would like to see plog-config become 2-dimensioned, mainly to allow greater options metadata, particularly:
    • default (e.g. '0')
    • label (e.g. "Thumbnail Size")
    • option "section" (thumbnails, interface, etc)
    • option "subsection" (sort order, comments, etc)
    • datatype ("yn", "text", "enum", "int")
    • privledges (int, 3 tiers?)
  • this allows for iterability in the control panel, and SQL queries via "GROUP BY section,subsection"
    • iterate via foreach() to generate options table
  • it would also be a good chance to break out the login settings from plog-config and put them into their own table, to begin some semblance of a user system

Thoughts? This is a big leap, so I'm starting this ticket discussion-style and going from there. Does anybody else believe this would be a positive step for dev? This would definitely affect the admin panel, as well as _upgrade and _install.

Change History

Changed 2 years ago by mike

Derek, I think you are on the right track. Modularizing the admin panel would open up an avenue for plugin development, and also make it much easier for us to add new admin options, perhaps with a single function call.

This is definitely an ambitious undertaking though, you need to really think through the upgrade process for existing installations. I think the most complex part of this is that _upgrade.php is designed to upgrade from any previous Plogger configuration, including ones that would have been already converted to this two-dimensional model.

Maybe this could be for next release? I think we should clean up the existing features and make a release before all these new developments push our release schedule (do we have one? lol) back another few months.

Changed 2 years ago by anti

- label (e.g. "Thumbnail Size")

Storing labels like this in DB will cause problems as soon as we are going to have localization, so please don't do that. Otherwise .. go on :)

Changed 2 months ago by sidtheduck

  • type changed from defect to enhancement

Changed 4 weeks ago by sidtheduck

  • milestone set to 1.1

This definitely needs to happen soon to keep development of the admin section going. I'll add to 1.1 in order to kick start development of the other features for 2.0

Note: See TracTickets for help on using tickets.