You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently user settings must match a setting value set in globals to be included in the $GLOBAL super. If a module wants to set a needed setting that is user specific and does not want a default from global setting then the setting is never set in globals.php. E.g. Module wants have a global admin value for one reason but doesn't want that value to be valid for a specific user.
I propose to remove the limitation
The text was updated successfully, but these errors were encountered:
Describe the problem
Currently user settings must match a setting value set in globals to be included in the $GLOBAL super. If a module wants to set a needed setting that is user specific and does not want a default from global setting then the setting is never set in globals.php. E.g. Module wants have a global admin value for one reason but doesn't want that value to be valid for a specific user.
I propose to remove the limitation
The text was updated successfully, but these errors were encountered: