You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If richdocuments detects onlyoffice app, it completely disables handling of any documents which are also compatible with onlyoffice. This shouldn't be the correct approach, since it effectively allows only a few extensions to be handled by richdocuments and the user has no way of opening file with those disabled extension with Collabora.
Furtermore, onlyoffice allows to open any documents from the context menu so the correct approach would be to have richdocuments handle all office documents by default and if user want's to open a document with onlyoffice, he can do so by opening the context menu and selecting the option to open onlyoffice.
The code which handles this is in file:
./lib/Service/CapabilitiesService.php
Deleting/commenting out this section fixes the issue
if ($this->appManager->isEnabledForUser('onlyoffice')) {
return true;
}
To Reproduce
Steps to reproduce the behavior:
install onlyoffice app (no need to configure it)
Click on any document which is supported by onlyoffice (docx, xlsx etc.)
Documents either open with onlyoffice (if correctly configured), or a download dialog appears
Expected behavior
If the document is supported by richdocuments it should open Collabora. If user wants to open it with onlyoffice, he can do so by selecting the appropriate option in the context menu.
**Web server: Apache/2.4.57 (Debian) / within docker
**Database: Mariadb, docker image version latest (11.2.2)
**PHP version: php 8.2.15
**Nextcloud version: 8.0.2
**Version of the richdocuments app: 8.3.1
**Version of Collabora Online: 23.05.8.4
The text was updated successfully, but these errors were encountered:
gchatthes
changed the title
richdocuments effectively disable Collabora if onlyoffice plugin is installed
richdocuments effectively disables ability to open files with Collabora if onlyoffice plugin is installed
Feb 3, 2024
gchatthes
changed the title
richdocuments effectively disables ability to open files with Collabora if onlyoffice plugin is installed
richdocuments effectively disables ability to open files with Collabora if onlyoffice app is installed
Feb 3, 2024
confirm the behaviour which is new after upgrade from 26 to 28.0.4
One could prefer onlyoffice for some use case and keep richdocument for all other documents !
could we just exclude document type explicitly selected in onlyoffice configuration, letting also option to "open with collabora using contextual menu"
Describe the bug
If richdocuments detects onlyoffice app, it completely disables handling of any documents which are also compatible with onlyoffice. This shouldn't be the correct approach, since it effectively allows only a few extensions to be handled by richdocuments and the user has no way of opening file with those disabled extension with Collabora.
Furtermore, onlyoffice allows to open any documents from the context menu so the correct approach would be to have richdocuments handle all office documents by default and if user want's to open a document with onlyoffice, he can do so by opening the context menu and selecting the option to open onlyoffice.
The code which handles this is in file:
./lib/Service/CapabilitiesService.php
Deleting/commenting out this section fixes the issue
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If the document is supported by richdocuments it should open Collabora. If user wants to open it with onlyoffice, he can do so by selecting the appropriate option in the context menu.
Client details:
Server details
Operating system: Debian 12 Bookworm / Docker install (latest)
**Web server: Apache/2.4.57 (Debian) / within docker
**Database: Mariadb, docker image version latest (11.2.2)
**PHP version: php 8.2.15
**Nextcloud version: 8.0.2
**Version of the richdocuments app: 8.3.1
**Version of Collabora Online: 23.05.8.4
The text was updated successfully, but these errors were encountered: