Add admin setting to disable user-specific logout thresholds#37
Open
alexellison wants to merge 1 commit intoajitdev:8.x-1.xfrom
alexellison:8.x-1.x
Open
Add admin setting to disable user-specific logout thresholds#37alexellison wants to merge 1 commit intoajitdev:8.x-1.xfrom alexellison:8.x-1.x
alexellison wants to merge 1 commit intoajitdev:8.x-1.xfrom
alexellison:8.x-1.x
Conversation
TRUE, hides the autologout threshold text field from the user edit form and does not set a autologout.user.uid configuration item on form submit.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If setting is TRUE, autologout threshold text field is hidden from the user edit form
and the form does not set a autologout.user.uid configuration item on submit.
Motivation
Currently when an admin saves a user with autologout enabled configuration is written for each user's individual logout threshold.
This not only reduces the module's footprint, but allows for workflows where configuration changes should not be made on the production environment; only on staging or local environments.
Certain hosting providers (e.g. Pantheon) don't allow config to be written unless the site is flipped from (default) git mode into sftp mode, which means with autologout enabled users wouldn't be able to be saved.
Related drupal.org issue: https://www.drupal.org/node/2730737