-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Added parameter to disable web UI integration with local client #50280
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
base: master
Are you sure you want to change the base?
Conversation
|
Wouldn't this make more sense in the... Web UI itself ? |
It's meant for admin to be able to disable such options globally using config file not per user. |
jancborchardt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
Adding @juliusknorr as he mentioned we might already have a config for this in richdocuments, and should make sure both are 1 setting only. (But possibly using this server-wide setting.) |
|
This makes sense for instances that do not make use of the desktop client at all. For that reason we have a setting in richdocuments, but having a global one seems more reasonable, we should adapt to respect that in richdocuments once this PR is merged (https://github.com/nextcloud/richdocuments/blob/920cf96886400abafffbc82ad414145408fd6d6d/lib/Service/InitialStateService.php#L112) |
|
/backport! to master EDIT: #54191 |
… client Signed-off-by: skjnldsv <[email protected]>
Signed-off-by: nextcloud-command <[email protected]>
Signed-off-by: John Molakvoæ <[email protected]> Signed-off-by: nextcloud-command <[email protected]>
27f49d6 to
17d7c7e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw, thinking about this again:
when local Nextcloud clients are not used
Is this not something we know, or can detect? That is, if the desktop client was never used, then "Edit locally" never needs to show. It should only show if the desktop client was used at all in the past, or even e.g. if it was used in the last x days (if it should be more intelligent).
Then we don’t need a setting for something that can be handled automatically.
Cons:
|
Sure, but that’s fine, the big pro is that nothing needs to be done manually. Also, we already do have that info via the devices list, don’t we?
Yeah, but if it’s automatic I would wager that this topic would never come up.
Which is why I said
Don’t we use the desktop client to do the handover in this case too? @juliusknorr could you comment on the automatic approach I proposed? |
Summary
Added system config parameter
web_ui_integration_local_client.enabledto allow disabling integration with local client from web UI (i.e. when local Nextcloud clients are not used).Use
to enable (default if not set) and
to disable integration.
Use added parameter to show/hide
Edit locallyoption in Nextcloud Files.Related: https://help.nextcloud.com/t/how-remove-hide-edit-locally-option-in-web-interface/171999/5
Author-Change-Id: IB#1156402
Checklist