Hi,
there is a pending feature request, and a message in the forum, about the problem for the persons that are using an Apache configured to recognize only .php extensions.
I guess we could make the extension variable, depending on a variable in the config file.
And maybe a symlink index.php for index.php3.
If there is concensus about this, I am volunteer to do the job :)
Marc (Lem9)
On Wed, May 09, 2001 at 04:18:41PM -0400, Marc Delisle wrote:
there is a pending feature request, and a message in the forum, about the problem for the persons that are using an Apache configured to recognize only .php extensions. I guess we could make the extension variable, depending on a variable in the config file.
and then, how would it help ? Every file would have to be twice in the tar.gz: as .php and as .php4...
And maybe a symlink index.php for index.php3.
wouldn't work under windows...
I think the best is to continue the same way as before: for releases, put 2 zip files: one only with .php3 extensions, and one with .php. The unix gurus will know how to use the extchg.sh script, and good configured servers can read both .php and .php3 and .phtml files :)
If there is concensus about this, I am volunteer to do the job :)
would be interested to know what you would do / whould have done :)
Greetings, Olivier
I would like to propose a different solution to this problem.
Apache CAN be configured to handle the file extensions from an .htaccess file, so that may make our life a lot easier, by just putting the required lines in an htaccess file.
I would be adding a line to it as well, to solve the problem for the '<?xml' tags that PHP tries to run. My line to add: php_value asp_tags=Off
I'm just a bit swamped with exams this week, but after the weekend and next week I'm really free.
Robin Johnson a écrit :
I would like to propose a different solution to this problem.
Apache CAN be configured to handle the file extensions from an .htaccess file, so that may make our life a lot easier, by just putting the required lines in an htaccess file.
Interesting... but
1. phpMyAdmin can be run on non-Apache servers ... are those supporting the .htaccess convention?
2. even on Apache, the webmaster can configure it to ignore .htaccess, see http://httpd.apache.org/docs/mod/core.html#allowoverride
On Wed, May 09, 2001 at 04:27:32PM -0700, Robin Johnson wrote:
I would like to propose a different solution to this problem.
Apache CAN be configured to handle the file extensions from an .htaccess file, so that may make our life a lot easier, by just putting the required lines in an htaccess file.
yes, *but* : the users and webservers customers sometimes (or even most of time) don't have the right to setup an .htaccess file...
Olivier
"Olivier M." a écrit :
On Wed, May 09, 2001 at 04:18:41PM -0400, Marc Delisle wrote:
there is a pending feature request, and a message in the forum, about the problem for the persons that are using an Apache configured to recognize only .php extensions. I guess we could make the extension variable, depending on a variable in the config file.
and then, how would it help ? Every file would have to be twice in the tar.gz: as .php and as .php4...
Oops, sorry, I did not think long enough about the problem :)
-
Armel FAUVEAU -
Marc Delisle -
Marc Delisle -
Olivier M. -
Robin Johnson