Skip to content
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

[BUG]Enabling 'Only for Editor' on the settings page has not taken effect #1505

Open
yzkqq345 opened this issue Nov 20, 2024 · 5 comments
Open
Labels

Comments

@yzkqq345
Copy link

image
I found that the '/api/settings' interface did not set 'secureOnlyEditor' to 'runtime.settings.secureOnlyEditor';

I don't understand Node.js, please forgive me if I'm wrong

@mauroalexandre
Copy link
Contributor

Your token are expiring with this option enabled?

@yzkqq345
Copy link
Author

Your token are expiring with this option enabled?

No, token is valid
'post /api/settings' did not handle the parameter 'secureOnlyEditor'
image
image
image

@yzkqq345
Copy link
Author

Your token are expiring with this option enabled?

The parameter 'secureOnlyEditor' is only written to the 'mysettings. json' file, so it needs to be restarted in the Docker container to take effect

@unocelli
Copy link
Member

Hi, some settings require a restart of the backend and this is one of them

@yzkqq345
Copy link
Author

Hi, some settings require a restart of the backend and this is one of them

So why not add a prompt on the settings page?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants