I've wanted to allow management of add-on preferences through the interface but not really thought of a cunning way to do it yet. It's definitely on the cards though.I don't really get what you mean by the API suggestion.
Allow add-ons more power for creating administration pages. One way (although not very secure) might be to practically allow the add-ons to embed some sort of scripts that render the config pages, which the RTB website then styles. That, however, would be quite hard to secure down (both on the server side, and on the client side to prevent cookie highjacking and such).
Just registering controls such as input and select box and mapping them to settings within the addon would be a much neater way of doing this, could have a page with collapsible sections for each addon.
For those, just pull in the RTB prefs. I'm talking about add-ons where it isn't practical to administrate them through a set-up like that.
"Whoops. You won't be able to use this page until the server is online.""server is outdated"it say my TWO servers are down. The two are up and running.wtf
usually, whet's its outdated, all still work fine and i just need to save my build, update and restart. Mhmhmhm.
Yeah sorry about that. It should be the last time it happens since I've changed how we do the deployments now and it's a lot more effective and seamless.I feel like that'd be something which would be used by maybe one or two people but would take a fairly long time to put together. I think everything anyone would need to do could be done using the RTB prefs. I think I added the ability to do callbacks based on pref changes as well so it's pretty easy for people to make something out of that.
have fun trying to implement the administrator management page or Permissions using it.
If you can add more prefs while the site is open that could work