Member
I just upgraded from 1.2.7 to 1.3 and it seems that there's something wrong with the subdomain configuration. I had this set up:
http://gallery.domain.com
which redirected to
http://www.domain.com/gallery
Both ways worked pretty much fine, so if I entered http://gallery.domain.com/sessions/album1 it would work, the same way http://www.domain.com/gallery/sessions/album1 worked.
At the setup for the upgrade, if I recall correctly, it told me that .htaccess didn't exist, and if I wanted to use mod_rewrite I needed to turn it on before completing the setup. I clicked there (since I was using it before) and the page reloaded saying "RewriteBase is /gallery (fixed)".
From then on the subdomain stopped working, giving me a 500 error. I read in an old post here that I should set the RewriteBase to '/' if I wanted the subdomain to work, but the regular directory way would stop working. That's really weird because I am 100% sure that both ways worked. My browser history shows that I used to access albums both ways...
Anyway, I tried to turn off mod_rewrite on the "options" tab from my administration page, but it doesn't really do anything. I manually renamed the .htaccess file but then all redirects stopped working. I guess this is what happens when I turn off mod_rewrite right?
Does anybody have a clue why it stopped working the way it was before?
Thanks in advance.
http://gallery.domain.com
which redirected to
http://www.domain.com/gallery
Both ways worked pretty much fine, so if I entered http://gallery.domain.com/sessions/album1 it would work, the same way http://www.domain.com/gallery/sessions/album1 worked.
At the setup for the upgrade, if I recall correctly, it told me that .htaccess didn't exist, and if I wanted to use mod_rewrite I needed to turn it on before completing the setup. I clicked there (since I was using it before) and the page reloaded saying "RewriteBase is /gallery (fixed)".
From then on the subdomain stopped working, giving me a 500 error. I read in an old post here that I should set the RewriteBase to '/' if I wanted the subdomain to work, but the regular directory way would stop working. That's really weird because I am 100% sure that both ways worked. My browser history shows that I used to access albums both ways...
Anyway, I tried to turn off mod_rewrite on the "options" tab from my administration page, but it doesn't really do anything. I manually renamed the .htaccess file but then all redirects stopped working. I guess this is what happens when I turn off mod_rewrite right?
Does anybody have a clue why it stopped working the way it was before?
Thanks in advance.
Administrator
I am sure that boths ways do not work as htaccess needs one rewrite base. The subdomain is "/" while the actual path with /gallery is obviously not. You have to decide. What will probably work is accessing the index page /gallery but none of the links or pages onwards will work.
Zenphoto works also without modrewrite.
Zenphoto works also without modrewrite.
Member
Hi acrylian, thanks for answering. I guess I'll stick with the subdomain then. For a matter of fact I've been only using the subdomain for a while, but in my web history it shows that I used the non-subdomain version as well - and I recall creating the subdomain as soon as I created the folder. But that's OK.
Just to clarify, if I turn off mod_rewrite, people will have to key in the full address for the album, i.e.: http://gallery.domain.com/index.php?album=sessions%2Falbum1 instead of the current http://gallery.domain.com/sessions/album1, am I correct?
Again, thank you for helping.
Just to clarify, if I turn off mod_rewrite, people will have to key in the full address for the album, i.e.: http://gallery.domain.com/index.php?album=sessions%2Falbum1 instead of the current http://gallery.domain.com/sessions/album1, am I correct?
Again, thank you for helping.