-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Allow additional personal settings via normal registration #22589
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
Allow additional personal settings via normal registration #22589
Conversation
Signed-off-by: Joas Schilling <[email protected]>
this is because there is no an personal addtional section in the please check my pull request #22144 |
While I agree in general, the one liner is much easier to be backported. So let's make it properly (like in the admin section?) with your PR, and only do the minimal impact PR for the backporting |
|
/backport to stable19 |
|
/backport to stable18 |
already closed my PR, this much simpler |
Currently the
Additional settingsfor personal settings only shows when there are legacy panel registered via\OCP\App::registerPersonal('ransomware_protection', 'personal');When this is transformed into a "normal" setting, it works and shows up in the additional section, as long as there is one "old" setting registered, otherwise the menu entry will not show up (but the page will work and show the setting).
So we now check if there is a legacy setting or any other setting registered for additional to determine whether the panel should display, or was this a conscious decision to get rid of the
additionalsection for personal settings but keep it in administration settings?