Gabor Hojtsy wrote:
Jose A. Reyero wrote:
I don't like hardcoded values at all, and I'd like *everything* to be configurable. The problem is if we make everything configurable, the admin interface would be unmanageable.
Proposed solution: Make all of these values configurable in the settings file, but not through the web pages. Ideally, we'd access all of these values throught the variable_get/variable_set interface, but then we'd need some array in the settings file to hold all of these values, and then the variable management functions to discriminate between the ones that have to be set into the database and the ones that are in the code.
The fun thing is that all this works right now (and worked before :) with Drupal. Look into the bottom of your settings.php (variable overrides).
Goba
Yes, you're right. So we just have to define the variables in settings.php and use them in the code through all Drupal :-) In addition to this, someone can make a module to configure this rarely changed values...