- Issue created by @Selvam J
Hi @apadero/Team, Is any update for this issue?
Please, kindly share your thoughts.
Thanks!- 🇮🇳India pravat231
Instead of calling the ajax.success directly, we should call with Promise which would solve the problem. This patch will solve your problem. patch created from this version 8.x-1.x
- last update
over 1 year ago 18 pass, 4 fail - last update
over 1 year ago 18 pass, 4 fail - 🇸🇪Sweden andersmosshall
Also noted this issue. There is a change record for ajax.js in core here.
https://www.drupal.org/node/3293812 →
Effectivly the suggested solution is to store the original success callback, do your processing and then call the original callback again.
I created a patch doing just that.
- last update
about 1 year ago 18 pass, 4 fail - last update
about 1 year ago 18 pass, 4 fail - Status changed to Needs work
about 1 year ago 8:10am 24 August 2023 - First commit to issue fork.
- last update
about 1 year ago 18 pass, 4 fail - @deaom opened merge request.
- Status changed to Needs review
about 1 year ago 2:06pm 19 September 2023 - 🇸🇮Slovenia DeaOm
Applied the patch from comment #8 🐛 Automated logout functionality not working, due to ajaxing property return true and ajaxStop event not triggering even though ajax req completed. Needs review and created a MR (so it easier to maintain). Tested the functionality which seems to work as expected. The tests are expected to fail because of a core migration issue 🌱 [META] Serialization issues in Migration tests Active , so see no reason this can be merged, but changing status to needs review, so somebody else can also test.
- Status changed to Needs work
about 1 year ago 10:40am 20 September 2023 This fix causes a bug for me.
Specs:
- Drupal 10.1.2
- PHP 8.1.21
- Modules is the issue fork
- Timeout: 80
- Timeout padding: 20
After the 80s the dialog opens, and I click to extend the logged-in time. The dialog closes, and about 10-20s later the dialog shows up and immediately logs me out.
I'm checking out what is going on and for now, setting the status to needs work.
- Status changed to Needs review
about 1 year ago 11:37am 20 September 2023 So it looks like my problem is not related to the fix in this issue. But is caused by 🐛 getRemainingTime treats logout_regardless_of_activity as always active RTBC . I'm moving this issue back to needs review.
- last update
about 1 year ago 18 pass, 4 fail - Status changed to Needs work
about 1 year ago 7:32am 21 September 2023 Ok for some reason I'm still getting the bug mentioned in #13 and the fix from #14 was merged and the issue fork was rebased with that fix in it. So I have no clue why it's not working correctly again.
- Status changed to RTBC
about 1 year ago 9:05am 22 September 2023 - 🇸🇮Slovenia DeaOm
I re-tested again to see the behaviour and on D9.5 works fine (except for multiple dialogs adding on when you interact and extend the session by click on yes). But that issue should be resolved with 🐛 Autologout triggered in background tab, no indication in other open tabs Fixed . For things to move forward, I think this needs to be merged and then new issues can be opened and solved, so marking it as RTBC.
-
boshtian →
committed 9de48ebb on 8.x-1.x authored by
DeaOm →
Issue #3348394: Automated logout functionality not working, due to...
-
boshtian →
committed 9de48ebb on 8.x-1.x authored by
DeaOm →
- Status changed to Fixed
about 1 year ago 1:46pm 28 September 2023 Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
12 months ago 10:41am 29 November 2023