Julius Härtl

I think the main problem is that we cache the capabilities and the automatic start doesn't get triggered then for some reason. > Is there a CLI workaround on how...

Can you try the following order maybe: ``` curl https://[domain]/apps/richdocumentscode/proxy.php?status sudo -u collab php --define apc.enable_cli=1 occ config:app:set richdocuments public_wopi_url --value https://[domain]/apps/richdocumentscode/proxy.php?req= sudo -u collab php --define apc.enable_cli=1 occ config:app:set...

Can you paste the full json error from the log file?

I could reproduce this but not on the dashboard and rather just in the file list itself. It seems that removing the filesystem/dav type from app info caused that the...

Might be a regression from https://github.com/nextcloud/richdocuments/pull/1728

Another finding to be filed in server, but need to check if it is an issue actually: - Within the PreviewManager it seems that there are some places where only...

Could you maybe on the nextcloud server issue the following request towards the collabora server url curl -v https://collabora.yourserver/hosting/capabilities This should list an entry "convert-to" that tells if the conversion...

@pedropintosilva This might also one something worth to update on https://sdk.collaboraonline.com/docs/theming.html#content-of-hidden-field-css-variables

If you are installing Collabora separately form the CODE repository there is no need to have richdocumentscode installed. The recommendation would always be to have the full installation through docker...

This is an issue of the richdocuments app, I guess we should add some check on public pages if the share owner is part of the allowed groups and otherwise...