idea: move settings from conf/settings.php into the database

ithcy

seems like permissions issues are a big stumbling block for new users, and they can be really difficult to correct. also developers all use their own unique methods to configure their extensions and this can be pretty confusing. to kill these two birds, why don't we get together and write up some standards for extension development, and make vanilla and all the extensions store settings in the database? wait, is this what that meta-extension does? well, maybe we should standardize that.

Mark

Storing all of the conf/settings.php stuff in the database will cause the entire app to slow down a great deal. It's why I put them in conf/settings.php in the first place. I'm all for writing documentation, though. Coming up with a clear and standard method for people to get things done. Let's do it!

Minisweeper

One thing i'd love to be standard in extensions is for the panel->add method to be single line!

k4zzy

"One thing i'd love to be standard in extensions is for the panel->add method to be single line! "
Haha, I take it you haven't found a solution yet? :P

Minisweeper

Well...no. not that i've looked. But I think it'd be more work than just coaching extension developers to use a single line :P Mark's the main culprit :P

Mark

When searching the file for the add line, parse the string until you hit the next semi-colon. When you hit it, that's the whole line. Remove \r\n and you're done.

Minisweeper

hmmm. I'll think about it.

Bergamot

"Storing all of the conf/settings.php stuff in the database will cause the entire app to slow down a great deal. It's why I put them in conf/settings.php in the first place."

Was this the result of testing, or a hunch? Seems to me that it would be a quick query to a relatively small table, and would be possible to cache. File IO isn't free either.