mod rewrite problems
|
pcmike
Joined: 2002-10-12
Posts: 36 |
Posted: Thu, 2009-07-30 22:48
|
|
Original issue is now extremely mute... but when I edit permissions gallery still complains about mod_rewrite. |
|
Posts: 16503
did you go to gallery3/index.php/upgrader
____________________________________________
Like Gallery? Like the support? Donate now!!! See G2 live here
Posts: 25965
Sorry to here that. So you had beta2 that was not working and tried to do a git pull and the issue you are still experiencing is a nod_rewrite issue?
Dave
_____________________________________________
Blog & G2 || floridave - Gallery Team
Posts: 7985
I'm betting that pcmike didn't read the instructions and is having a very bad day.
Hard to tell though because the post doesn't actually indicate any errors and http://adiosairlines.org shows me a login page and no errors.
Quick fix:
php index.php upgradeLonger fix: change your life philosophy a bit. relax, this stuff isn't the end of the world. take the time to read instructions, we wrote them for a reason. look both ways before crossing the road, etc.
---
Problems? Check gallery3/var/logs
bugs/feature req's | upgrade to the latest code | use git | help! vote!
Posts: 36
Honestly, I didn't mean to be quite so dramatic. I just was looking back at how long it took me correct all the issues I had when I updated from gallery1 -> g2 -> g3. It took me forever to identify one problem and fix it and I wasn't happy at the prospect of having to do that all over again.
dave,
Yes the problem I was having was with the mod_rewrite (which is enabled) and the fact that when I goto edit permissions I get...
Oh no! Your server needs a configuration change in order for you to hide photos! Ask your server administrator to enable mod_rewrite and set AllowOverride FileInfo Options to fix this.
I did the above and double checked everything and I still get the problem. I searched on here and followed some advice I saw and still had the same problem. So I did a 'git pull' and it updated a bunch of stuff and then I went to run the updater and all I got was a bunch of errors. Nothing was logged to var/logs/. Evidently gallery3 recognized me as still being logged in and all I was seeing was the errors, but I guess bharat didn't see the errors and saw the index just fine because he wasn't logged in.
I'm not quite sure what instructions bharat is referencing that I "didn't read," but I certainly don't remember seeing anything? I've gone ahead and run 'php index.php upgrade' and now I see gallery3 again with no errors.. but the mod_rewrite problem is still there. I'm going to go ahead and try to run updater now.. since I don't think it ever successfully ran the other day.
bharat, what instructions didn't I read?
Posts: 36
..
Posts: 7985
We get a little irked when there's a lot of drama because we spend a huge amount of time trying to get this working and make it right for you. For free. So please, don't show up and start yellin' in all caps, that'll just get us annoyed. Trust me when I say that the amount of time that you've spent updating g1->g2->g3 is a drop in the bucket to the amount of time I've spent writing all three of those apps for you. If you want to edit the subject of the original post to make it a little less alarming, I'm sure we'll all appreciate it.
Ok, got that out of the way.
The document I was referring to is http://codex.gallery2.org/Gallery3:Upgrading (referenced in my signature) which should take care of all of the problems that you were seeing right after you did your update via git. I'm guessing (ok, I have some inside info so this is a little more than a guess
) that the errors you saw were from running "php index.php updater" as opposed to "php index.php upgrade". But I'm further guessing that you've already figured all that out and have gotten your G3 upgraded properly now. Actually that isn't a guess either because I can see from visiting your site that it's working and the mod_rewrite stuff seems to be working also. So I think we're all good at this point, right? No harm, no foul.
---
Problems? Check gallery3/var/logs
bugs/feature req's | upgrade to the latest code | use git | help! vote!
Posts: 36
bharat,
I've gone ahead and edited the first post + title and of course you're correct in all but one thing.... g3 is still complaining about mod_rewrite. Whenever I go to edit permissions on a album it takes like 15 seconds or more to pull up the permissions dialog and the "Oh No!" message about mod_rewrite is still up at the top. However mod_rewrite appears to be working... but at the same time I still don't see the option to hide a photo.
Thank you
Posts: 25965
You cant hide photos you can only set permissions at the album level.
Sorry can't offer any advice on mod_rewrite.
Dave
_____________________________________________
Blog & G2 || floridave - Gallery Team
Posts: 4
I had the same problem, and enabled next module in httpd.conf: LoadModule rewrite_module modules/mod_rewrite.so
Posts: 36
I fixed my own problem after encountering a "upload error: 500" everytime. Everyone needs to make sure their gallery installation directory (or probably just gallery3/var) is owned by the user apache is running as. Once I did that the upload error went away and so did the permissions error. Can someone confirm if only var needs to be owned by this user? git pull naturally made everything owned by the user I was logged in via ssh.
Thanks.
Posts: 16503
var does not necessarily need to be owned by the web server user. That all depends on your server's setup. A permission of 777 on var should be enough on most servers, but apparently some "admins" have set some other settings that even at 777 the web server cannot create files.
Doing a git pull or git clone or anything git does not create, edit, modify, delete a var directory. That's only created by you or the web server if the directory Gallery is being installed in is already owned by the web server user.
____________________________________________
Like Gallery? Like the support? Donate now!!! See G2 live here
Posts: 25965
I think we need to create some test tools that the user can download and run that does some tests that checks for unusual server configuration issues like this.
If the var direcotry is 777 and the webserver-user/php/gallery3 can't create files then there should be a way to detect this and warn the user in a admin page.
Dave
_____________________________________________
Blog & G2 || floridave - Gallery Team
Posts: 16503
I agree. However, something had to have changed in his config otherwise Gallery wouldn't have been able to create any of the directories under /var
____________________________________________
Like Gallery? Like the support? Donate now!!! See G2 live here