Hi,
Adding this setting in user preferences will not work correctly, as all overrides to config.inc.php's values are loaded after auth is done, when database is available. The only solution for this to work, is to try loading user overrides from session cache ($_SESSION['cache']['server_?']['userprefs']) just after config.inc.php is read.
Hi
Dne Thu, 16 Sep 2010 20:46:10 +0200 Piotr Przybylski piotr.prz@gmail.com napsal(a):
Adding this setting in user preferences will not work correctly, as all overrides to config.inc.php's values are loaded after auth is done, when database is available. The only solution for this to work, is to try loading user overrides from session cache ($_SESSION['cache']['server_?']['userprefs']) just after config.inc.php is read.
I think getting cookie validity from the cache should do the right thing.
2010/9/21 Michal Čihař michal@cihar.com:
Hi
Dne Thu, 16 Sep 2010 20:46:10 +0200 Piotr Przybylski piotr.prz@gmail.com napsal(a):
Adding this setting in user preferences will not work correctly, as all overrides to config.inc.php's values are loaded after auth is done, when database is available. The only solution for this to work, is to try loading user overrides from session cache ($_SESSION['cache']['server_?']['userprefs']) just after config.inc.php is read.
I think getting cookie validity from the cache should do the right thing.
Done, changes pushed to master.
Shouldn't we warn in main.php when LoginCookieValidity may be limited by LoginCookieStore?
Hi
Dne Tue, 21 Sep 2010 14:11:02 +0200 Piotr Przybylski piotr.prz@gmail.com napsal(a):
Done, changes pushed to master.
Thanks.
Shouldn't we warn in main.php when LoginCookieValidity may be limited by LoginCookieStore?
Yes, that would make sense.
-
Michal Čihař -
Piotr Przybylski