5 users online. Create an account or sign in to join them.Users
Login problems as of 2.0.6
A for , submitted by Alistair on 07 August 2009
Announcement
Symphony's issue tracker has been moved to Github.
Issues are displayed here for reference only and cannot be created or edited.
Browse
Closed#95: Login problems as of 2.0.6
-
-
- Alistair
- Comment #1
- 07 Aug 09, 12:21 pm
-
-
- michael-e
- Comment #2
- 09 Aug 09, 12:12 pm
What about this line:
RewriteRule ^image/(.+.(jpg|gif|jpeg|png|bmp))$ //extensions/jit_image_manipulation/lib/image.php?param=$1 [L,NC]
I don’t think this will work if Symphony is installed in a subdirectory. Or am I wrong here?
-
-
- michael-e
- Comment #3
- 09 Aug 09, 12:22 pm
Strange: If I install Symphony in a subdirectory, I get a different image rewrite rule:
RewriteRule ^image/(.+.(jpg|gif|jpeg|png|bmp))$ ./extensions/jit_image_manipulation/lib/image.php?param=$1 [L,NC]
Shouldn’t it simply be like that:
RewriteRule ^image/(.+.(jpg|gif|jpeg|png|bmp))$ extensions/jit_image_manipulation/lib/image.php?param=$1 [L,NC]
-
-
- Alistair
- Comment #4
- 23 Aug 09, 11:17 pm
michael-e, I have posted a separate issue in the JIT issue tracker http://github.com/pointybeard/jit_image_manipulation/issues/#issue/8
-
-
- Alistair
- Comment #5
- 24 Dec 09, 11:08 am
This has been fixed.
This issue is closed.
There is a problem with the new
.htaccessrules. Here they are:### ADMIN REWRITE RewriteRule ^symphony/?$ ./index.php?mode=administration&%{QUERY_STRING} [NC,L] RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^symphony(/(.*/?))?$ ./index.php?symphony-page=$1&mode=administration&%{QUERY_STRING} [NC,L] ### FRONTEND REWRITE - Will ignore files and folders RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*/?)$ ./index.php?symphony-page=$1&%{QUERY_STRING} [L]Notice the
./before theindex.php. This is resulting in strange file path, E.G.[SCRIPT_FILENAME] => /home/path/to/domain/symphony-cms.com/public/./index.phpand that, in turn, leads to bad session paths. Specifically/., breaking the login. Solution is to remove the leading./in the.htaccessrules. Needs to be tested properly.forum thread is here