Hi,
Thank you for your reply.
> Did you test tomcat alone after the upgrade? Was it working as expected
or was it just showing weirdness? I would start from there :)
>
I didn't try tomcat only. But we use a lot of rewrite rules with httpd, so
that we cannot test easily...
Moreover, the errors som
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:
s
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
