Problem/Motivation

During testing we have set the timeout to be 60 seconds. It seems that we are unable to get a consistently shown modal. Currently it seems to show about 50% of the time, using version 1.4. I will test using the current dev version and report back if there are any changes.

Secondary to this, it seems that if the modal does show and the user decides to extend their session, a second modal does not prompt them to allow for a further extension.

Proposed resolution

Investigate the cause of inconsistent modal behaviour and create a patch.

Potentially related, which I'll also test: https://www.drupal.org/project/autologout/issues/3339695

Remaining tasks

- test against latest dev version tested, no change
- test above patch - it appears that this does help with the inconsistent nature of the modal displaying, however does not solve the issue with the modal not appearing a second time having extended the session - updating main issue text above
- further testing of patch with QA

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Comments

kiwimind created an issue. See original summary.

kiwimind’s picture

kiwimind commented
Issue summary: View changes
kiwimind’s picture

kiwimind commented
Issue summary: View changes
markwittens’s picture

markwittens commented

I have the same problem and the patch in the related issue doesn't seem to fix the problem for me. I'm always getting a Javascript error the second time the dialog should load:

jquery.min.js?v=3.7.0:2 Uncaught Error: cannot call methods on dialog prior to initialization; attempted to call method 'destroy'
at Function.error (jquery.min.js?v=3.7.0:2:2741)
at HTMLDivElement. (widget.js:234:16)
at Function.each (jquery.min.js?v=3.7.0:2:3129)
at ce.fn.init.each (jquery.min.js?v=3.7.0:2:1594)
at t.fn. [as dialog] (widget.js:224:10)
at confirmLogout (autologout.js?v=10.1.0:192:22)

admirlju’s picture

admirlju commented
Status: Active » Needs review

So it looks like #3348394: Automated logout functionality not working, due to ajaxing property return true and ajaxStop event not triggering even though ajax req completed. fixed this, at least in my testing. I'll set this issue to needs review so maintainers can credit you two.

the_g_bomb’s picture

the_g_bomb commented
Version: 8.x-1.x-dev » 2.x-dev
Status: Needs review » Closed (cannot reproduce)

I have tested this with the latest dev branch and suspect the other work done has solved this. Please feel free to reopen and update the steps to reproduce if you are still having problems.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

the_g_bomb’s picture

the_g_bomb commented
Status: Closed (cannot reproduce) » Fixed

Changing the status to represent the actual status

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.