-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New release builds, please? #97
Comments
Sorry I have not seen this message. I can look into this in the coming days and do a release. Anything I need to take special attention to ? PS : In case I miss again, please ping me. |
Nothing special. Just having a tag I can use in my |
ok, I will do it tomorrow early morning. |
Hi @cxj , I looked into this, and noticed my comment on #84 (comment) . The default What I would suggest is to override the values passed to Timer Lines 101 to 106 in 955ef97
For the current time I don't think I can make a release and I believe the patch #84 need to be reverted. |
I have already changed the values in my copy of The default value used by |
@cxj I agree with you, but I think it is up to the users to modify his / her |
I agree it's up to users how long |
I agree it's up to users how long session.gc_maxlifetime should be. It's
quite annoying now to deal with this low limit.
Why not override the default config.
I would really appreciate to see a new release which fixed this issue.
I will look what I can do.
|
Well, I didn't want to touch the source, so in case of an update, I do not lose my "fixes". I didn't expect there will be no updates at all for a long time ;). Anyway, I've tried hard to manage the behaviour of how long the sessions are and how to manipulate the timer. Probably my knowledge is not good enough to get it, or the script itself does not allow to extend the time of being logged in.
|
You don't want to change source. You can add another config . Ie what I
meant by override. I think I have commented about it on this thread. So you
don't want to rely on the changes happening on config of package.
…On Sun 18 Nov, 2018, 7:27 PM Qrzysio, ***@***.***> wrote:
Well, I didn't want to touch the source, so in case of an update, I do not
lose my "fixes". I didn't expect there will be no updates at all for a long
time ;).
Anyway, I've tried hard to manage the behaviour of how long the sessions
are and how to manipulate the timer. Probably my knowledge is not good
enough to get it, or the script itself does not allow to extend the time of
being logged in.
@ini_set("session.gc_maxlifetime", 3600*24);
@ini_set("session.cookie_lifetime", 3600*24);
$aura = new \Aura\Auth\Session\Timer(3600*48, 3600*24, 0, 0);
$aura->setIdleTtl(7200);
$aura->setExpireTtl(3600*24);
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#97 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHWhpxqs66p4_JhXjk5XCOtl_He4lt1ks5uwWc4gaJpZM4U4vZo>
.
|
Oh, I thought he already had been added. Thanks @harikt ! |
@pmjones I have added him to Aura.Auth for now. I don't see a way to add him to the team. Oh and you are fast to reply 👍 . |
Obviated by having a 4.x branch with the needed changes. |
Could we get some up to date releases tagged? I've been using 2.x-dev for a long time. ;-)
The text was updated successfully, but these errors were encountered: