I'm still struggling with this problem without being able to solve it, so here I'll write more details and maybe someone will be able to help me figure out why the feature isn't working correctly and if it's a problem of my configuration or a bug in Drupal.
I use a relatively unmodified version of Drupal 4.5.2 The only "quirk" is that the engine is in a /drupal/ subdirectory. So the real address is: http://www.cesspit.net/drupal/ To redirect there I have an .htaccess directly into http://www.cesspit.net/ which just contain a line: DirectoryIndex drupal/index.php
This redirects to the subdir whenever the basic address is accessed. and it seems to work. I cannot install drupal in the main directory because the http://www.cesspit.net/admin/ shortcut is used by the provider to access the admin pages of the website, so it prevents drupal to work in the case I install it there. The other technical details are that I use PHP 4.3.8 and Apache 2.0.50
The .htaccess file in have on the /drupal subdirectory is exactly the one in default package. The only difference is that I followed the instructions, replacing <IfModule mod_php4.c> With: <IfModule sapi_apache2.c> This considering that I run the site on Apache 2.
But this didn't produce any effect. The sessions weren't saved and every time I closed the browser I had to log in my site again.
To solve this problem I had to directly edit the php.ini file in /etc/ So I searched for the session.cookie_lifetime and set it to 2000000 instead of 0 (the previous value).
From my attempts I realized that my site simply ignores what's written in
the drupal's .htaccess. I tried to set the value in php.ini to 8000000 (which should correspond to four months) and the one in the .htaccess to 6000000 (which should be three months). And looking directly at the cookie stored in my browser I saw it always behave as the php.ini value, no matter what value I put in the .htaccess file.
Anyway, setting the php.ini file solved the problem of the cookie. I use Firefox 1.0 as browser and I can see that there's a cookie expiring in May, about three months from now and exactly following the value in the php.ini.
Now the session is somewhat saved. I can shut down the browser, reopen it and I'm still logged in. But if I don't go back within an hour or so I have to relog *again*. So the cookie basically works for some time but then vanishes in the void. Absolutely ignoring the fact that it should last at least THREE MONTHS.
So, please, is someone able to figure out what is happening?
-HRose / Abalieno
To solve this problem I had to directly edit the php.ini file in /etc/ So I searched for the session.cookie_lifetime and set it to 2000000 instead of 0 (the previous value).
Your provider, or yourself, has dissalowed the use of htaccess files. It is a feature that needs to be enabled in apache's own config. See http://httpd.apache.org/docs-2.0/howto/htaccess.html
Anyway, setting the php.ini file solved the problem of the cookie. I use Firefox 1.0 as browser and I can see that there's a cookie expiring in May, about three months from now and exactly following the value in the php.ini.
yes, this sounds about right
Now the session is somewhat saved. I can shut down the browser, reopen it and I'm still logged in. But if I don't go back within an hour or so I have to relog *again*. So the cookie basically works for some time but then vanishes in the void. Absolutely ignoring the fact that it should last at least THREE MONTHS.
Have you tried this in any other browsers or operating systems? Be sure it's not a preference setting in a browser to ditch cookies at closedown. or a setting to not disk store cookies. Try it in a pretty vanilla IE on a different computer.
I created an account on your server and can confirm that it succesfully kept me logged in after closing down my browser and restarting. (You may delete the account called 'cheeky' if you like)
On Sun, 30 Jan 2005 03:50:49 +0100, Abalieno abalieno@cesspit.net wrote:
I'm still struggling with this problem without being able to solve it, so here I'll write more details and maybe someone will be able to help me figure out why the feature isn't working correctly and if it's a problem of my configuration or a bug in Drupal.
I use a relatively unmodified version of Drupal 4.5.2 The only "quirk" is that the engine is in a /drupal/ subdirectory. So the real address is: http://www.cesspit.net/drupal/ To redirect there I have an .htaccess directly into http://www.cesspit.net/ which just contain a line: DirectoryIndex drupal/index.php
This redirects to the subdir whenever the basic address is accessed. and it seems to work. I cannot install drupal in the main directory because the http://www.cesspit.net/admin/ shortcut is used by the provider to access the admin pages of the website, so it prevents drupal to work in the case I install it there. The other technical details are that I use PHP 4.3.8 and Apache 2.0.50
The .htaccess file in have on the /drupal subdirectory is exactly the one in default package. The only difference is that I followed the instructions, replacing
<IfModule mod_php4.c> With: <IfModule sapi_apache2.c> This considering that I run the site on Apache 2.
But this didn't produce any effect. The sessions weren't saved and every time I closed the browser I had to log in my site again.
To solve this problem I had to directly edit the php.ini file in /etc/ So I searched for the session.cookie_lifetime and set it to 2000000 instead of 0 (the previous value).
From my attempts I realized that my site simply ignores what's written in
the drupal's .htaccess. I tried to set the value in php.ini to 8000000 (which should correspond to four months) and the one in the .htaccess to 6000000 (which should be three months). And looking directly at the cookie stored in my browser I saw it always behave as the php.ini value, no matter what value I put in the .htaccess file.
Anyway, setting the php.ini file solved the problem of the cookie. I use Firefox 1.0 as browser and I can see that there's a cookie expiring in May, about three months from now and exactly following the value in the php.ini.
Now the session is somewhat saved. I can shut down the browser, reopen it and I'm still logged in. But if I don't go back within an hour or so I have to relog *again*. So the cookie basically works for some time but then vanishes in the void. Absolutely ignoring the fact that it should last at least THREE MONTHS.
So, please, is someone able to figure out what is happening?
-HRose / Abalieno
-- [ Drupal support list | http://lists.drupal.org/ ]
I created an account on your server and can confirm that it succesfully kept me logged in after closing down my browser and restarting. (You may delete the account called 'cheeky' if you like)
and a few hours later, i can confirm that i'm logged out :S Sounds odd, this one. Remember that Drupal does not use any cookies of its own and just repies on the inbuilt PHP session handling cookie. It seems that drupal and the browser are both behaving correctly. Is something happening in your Apache/PHP to cause it to lose PHP sessions? Server re-configs / reloads / restarts? Cleaning of temp data?
and a few hours later, i can confirm that i'm logged out :S Sounds odd, this one. Remember that Drupal does not use any cookies of its own and just repies on the inbuilt PHP session handling cookie. It seems that drupal and the browser are both behaving correctly. Is something happening in your Apache/PHP to cause it to lose PHP sessions? Server re-configs / reloads / restarts? Cleaning of temp data?
I don't know, the site is hosted at canaca.com and I obviously have just a limited access. I can just say that this behaviour isn't something recent but it has been a constant.
Also, I had another forum engine on the same site and the cookies always worked perfect. I was always logged in on that one.
Here you can read about the rest: http://www.cesspit.net/misc/phpinfo.php
-HRose / Abalieno
I was able to solve the problem with: session.gc_maxlifetime = 1440 and setting it to 2000000. Now the sessions don't vanish and the site automatically log ins the users even after various hours.
Now there are still things on my 'wish list' :)
- Better forums, with post counts considering both comments and forum posts - Possibility for the aggregator module to parse atom feeds - Possibility to create and define different types of nodes so that each uses a specific layout-template - "Read more" link also in the body of the message when showing the teaser only - Archives viewable by date - Like listing all the notes in a specific time span. Like all post in November - Layers on the search function to narrow the search using time, categories etc.. - Correcting the bug with comments count. (it doesn't get update when approving comments that were in moderation)
I created an account on your server and can confirm that it succesfully kept me logged in after closing down my browser and restarting. (You may delete the account called 'cheeky' if you like)
and a few hours later, i can confirm that i'm logged out :S Sounds odd, this one. Remember that Drupal does not use any cookies of its own and just repies on the inbuilt PHP session handling cookie. It seems that drupal and the browser are both behaving correctly. Is something happening in your Apache/PHP to cause it to lose PHP sessions? Server re-configs / reloads / restarts? Cleaning of temp data?
Abalieno wrote:
I was able to solve the problem with: session.gc_maxlifetime = 1440 and setting it to 2000000. Now the sessions don't vanish and the site automatically log ins the users even after various hours.
Now there are still things on my 'wish list' :)
- Better forums, with post counts considering both comments and forum
posts
- Possibility for the aggregator module to parse atom feeds
- Possibility to create and define different types of nodes so that
each uses a specific layout-template
- "Read more" link also in the body of the message when showing the
teaser only
- Archives viewable by date - Like listing all the notes in a specific
time span. Like all post in November
- Layers on the search function to narrow the search using time,
categories etc..
- Correcting the bug with comments count. (it doesn't get update when
approving comments that were in moderation)
Posting wishlist items here will not help at all. Check for feature requests, and make some if there aren't any.
Steven Wittens