.htaccess - gallery 1.3.4
|
pattz
Joined: 2003-06-26
Posts: 2 |
Posted: Thu, 2003-06-26 22:14
|
|
i just upgraded from gallery 1.3.3 to gallery 1.3.4. i used to have no warnings in the congiguration wizard and now i can't get rid of the .htaccess warning no matter what i do. i tried the <Directory> suggestion made by the wizard and it does nothing. any suggestions (and, i'm a newbie, so please be gentle)? pattz Gallery version: 1.3.4 |
|
Posts: 3474
FAQ C.21 should be resolved first and foremost.
Then let us know if you still have issues.
-Beckett (
)
Posts: 2
thanks beckett.
that'll teach me to upgrade to a new version for no reason. i have reverted to 1.3.3 and will try to stay there until i am a little more comfortable with everything.
Posts: 3474
Well, in theory, the Gallery version should have nothing to do with it. The problem is there are tons of strange bugs in PHP 4.2.x when it runs on Apache 2. I'm very very surprised that you get this error only with Gallery 1.3.4, but who knows.
-Beckett (
)
Posts: 5
I guess no developer tried to run gallery under apache 2.0 since there are at least 2 obvious bug in detecting access for .htaccess file and mod_rewrite.
in setup dir .htaccess looks like that:
<IfModule mod_php4.c>
php_value auto_prepend_filephp_value_ok.php
php_value magic_quotes_gpc off
</IfModule>
Options +FollowSymLinks
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule ^(index.php)$index.php?init_mod_rewrite=1&ersandbroken= [QSA]
</IfModule>
In my configuration IfModule mod_php4.c didn't detect php, but that module is loaded and is working. I don't know apache much but isn't ifmodule for detected compiled-in modules? Why extension is .c? I solved that problem by removing this checking (I know that I have php installed, running without it would be pointless
)) As for mod_rewrite, I don't know why that wasn't working (I also removed that checking, and manually supllied the address - I'm pretty sure that mod_rewrite is also working on my server)
So at the end I have correct .htaccess (I was also need modiffy it after the configuration) and everything is working correctly. Since I'm not much expert in apache I hope developers will find resaon why this isn't working, I hope my post will help in that.
Posts: 7994
Your problems are because PHP changed the way that it integrates into Apache2 (specifically, it uses the SAPI apache2 dll and that changes the way that the module is defined). This is only an issue on windows and was fixed in CVS for version 1.3.5 a few weeks back. You neglected to mention your OS so I'm assuming that you're on windows.
It would be helpful if you upgraded to the latest CVS snapshot (see the "bleeding edge" section of the download page) and see if that works out of the box. If it *doesn't* then if you can provide the output from http://your.server/server-info it will help us to sort out which type of SAPI integration you're using to get PHP into Apache2 on windows.
Posts: 5
I'm running FreeBSD; apache, mod_php and gallery is installed throug ports system, I'll try to install gallery from CVS and I'll respond when I finish it
Posts: 5
Yes, in current gallery that problem is fixed, mod_php and mod_rewrite was detected in setup. Server-info shows that mod_php has name: sapi_apache2.c
Posts: 7994
Thaks for following up, takeda. I hadn't realized that they had changed the name of the module on Unix also so it's good to hear that the PHP team at least used consistent names for the modules across platforms
Posts: 5
You're welcome, thank you for the Gallery
PS. I think that information about Gallery 1.3.4 should go to FAQ in case other people could have similar problem. (I belive that only updating .htaccess in setup dir is needed to make it work)