Actually, I've already grep'ed through the code (grep -r
"configuration.php" /www/joomla3 > grep.out); found 179 occurrences
(lines of code). And as I've mentioned, there are currently 58
parameters in the configure.php file. This would be an ambitious
project. In consideration that I'm not
Why is Joomla designed this way? Seems that yet another MySQL DB
table could have been designed into the system and the configuration
extracted from the same, rather than reading the content of a
configuration.php file.
What stops you from implementing configuration.php the way you describe:
First, thanks for your quick reply. I suspected there was no “magic” in
Apache to accomplish my task. My concern is the fact that the inclusion
of configure.php is embedded in the application system, which by-the-way
is . . .Joomla. Aside from being a totally php based application (there
are
If you want client requests to http://your.site/config.php be served by
./parent/config.php , then the answer is yes -- I'd start with
mod_rewrite for instance. If config.php is invoked by PHP, not by
Apache, then you cannot fix it using Apache features -- you really need
to change that
I don’t know if and how this can be accomplished.
Scenario:
Two directories, parent and child.
parent is in a virtual host “container”.
child is a symbolic link to an application default core distribution
directory (php objects).
./parent/child contains a default config.php file.
./parent
