Skip to content

Conversation

@pboguslawski
Copy link
Contributor

Summary

Added system config parameter web_ui_integration_local_client.enabled to allow disabling integration with local client from web UI (i.e. when local Nextcloud clients are not used).

Use

occ config:system:set web_ui_integration_local_client.enabled --value='true' --type=boolean

to enable (default if not set) and

occ config:system:set web_ui_integration_local_client.enabled --value='false' --type=boolean

to disable integration.

Use added parameter to show/hide Edit locally option 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

@solracsf
Copy link
Member

Wouldn't this make more sense in the... Web UI itself ?

@pboguslawski
Copy link
Contributor Author

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.

Copy link
Member

@jancborchardt jancborchardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it’s still enabled by default (as it seems to be) and not too much of a maintenance load (@sorbaugh @skjnldsv) I’m fine with it.

@skjnldsv skjnldsv added the 3. to review Waiting for reviews label Jan 28, 2025
@skjnldsv skjnldsv added this to the Nextcloud 32 milestone Jan 28, 2025
@jancborchardt
Copy link
Member

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.)

@juliusknorr
Copy link
Member

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)

@skjnldsv
Copy link
Member

skjnldsv commented Aug 1, 2025

/backport! to master

EDIT: #54191

@nextcloud nextcloud deleted a comment from backportbot bot Aug 1, 2025
@skjnldsv skjnldsv added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Aug 1, 2025
pboguslawski and others added 3 commits August 1, 2025 08:47
This was referenced Aug 22, 2025
@nextcloud-bot nextcloud-bot mentioned this pull request Sep 2, 2025
This was referenced Sep 4, 2025
This was referenced Sep 25, 2025
@skjnldsv skjnldsv modified the milestones: Nextcloud 32, Nextcloud 33 Sep 28, 2025
@pboguslawski pboguslawski requested review from a team as code owners December 1, 2025 17:08
@pboguslawski pboguslawski requested review from ArtificialOwl, leftybournes, szaimen and yemkareems and removed request for a team December 1, 2025 17:08
@szaimen szaimen requested review from artonge, nickvergessen and susnux and removed request for szaimen December 1, 2025 17:12
Copy link
Member

@jancborchardt jancborchardt left a 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.

@pboguslawski
Copy link
Contributor Author

That is, if the desktop client was never used, then "Edit locally" never needs to show.

Cons:

  • extra data to store/maintain per user,
  • cannot disable integration globally by admin for whatever reason,
  • user cannot disable it after used in the past,
  • won't help in other places (like richdocuments above).

@jancborchardt
Copy link
Member

That is, if the desktop client was never used, then "Edit locally" never needs to show.

Cons:
* extra data to store/maintain per user,

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?

* cannot disable integration globally by admin for whatever reason,

Yeah, but if it’s automatic I would wager that this topic would never come up.

* user cannot disable it after used in the past,

Which is why I said or even e.g. if it was used in the last x days (if it should be more intelligent) – then if the server notices that you haven’t used the desktop client in a week or a month (whatever length we decide), the menu item can vanish.

* won't help in other places (like richdocuments [above](#issuecomment-2620107898)).

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants