Integration FAQ
ONLYOFFICE Docs uses Office Open XML format when opening and editing files. If the file format is different from OOXML, it will still be converted to the corresponding OOXML for the Document Server proper work and faster performance. After that, you can edit the file, make any changes available for the base OOXML format, and save the file to this base OOXML format.
If the source file format is different from the base one, and you still want to save it to the original format, the file will be converted to this format from OOXML. As the formats are fundamentally different, some data (such as charts, tables, autoshapes or images) and formatting can be lost due to the simple reason that some formats (csv, txt, etc.) do not support them or treat them differently than OOXML standard does. That is why all the non-OOXML files by default are opened for viewing only, although there is an option to convert the file in the context menu. If you realize the data/formatting loss risks after the conversion but still want to open non-OOXML files for editing, you can check them in the list in the settings. Editing for .csv and .txt files is available by default.
If the document is shared using the Federated Cloud Sharing app, the co-editing among the servers will not be available. The users from the same server can edit the document in the co-editing mode, but the users from two (or more) different servers will not be able to collaborate on the same document in real-time.
Adding the storage using the External storages app has issues with the co-editing in some cases. If the connection is made using the same authorization keys (the Username and password or Global credentials authentication type is selected), then the co-editing is available for the users.
If different authorization keys are used (Log-in credentials, save in database or User entered, store in database authentication options), the co-editing is not available. When the Log-in credentials, save in session authentication type is used, the files cannot be opened in the editor.
If you are using a self-signed certificate for your Document Server, Nextcloud will not validate such a certificate and will not allow connection to/from Document Server. This issue can be solved the following way: locate the Nextcloud config file (/nextcloud/config/config.php) and open it.
Insert the following section to it:
'onlyoffice' => array
('verify_peer_off' => true
)This will disable the certificate verification and allow Nextcloud to establish a connection with Document Server, but you must remember that this is a temporary insecure solution and we strongly recommend that you replace the certificate with the one issued by some CA. Once you do that, do not forget to remove the above section from the Nextcloud config file.
Nextcloud Hub is a new solution from the Nextcloud team with the built-in MS Office compatibility, which is provided with the help of ONLYOFFICE editors.
Specifically created ONLYOFFICE Document Server this solution is called Community Document Server. Community Document Server uses the client-side code of our Document Server, but the server-side code was partially rewritten by the Nextcloud team using PHP to fit the whole platform.
Here are some technical details:
- The new version was created to facilitate the installation and avoid using Docker. However, you still need it in the installation stage.
- It supports x86-64 Linux servers.
- You still need our connector. Just get it from the App Store, everything else is pre-configured. Refer to this How-to to install ONLYOFFICE in Nextcloud Hub.
If the document is shared using the Federated Cloud Sharing app, the co-editing among the servers will not be available. The users from the same server can edit the document in the co-editing mode, but the users from two (or more) different servers will not be able to collaborate on the same document in real real-timetime.
Adding the storage using the External storages app has issues with the co-editing in some cases. If the connection is made using the same authorization keys (the Username and password or Global credentials authentication type is selected), then the co-editing is available for the users.
If different authorization keys are used (Log-in credentials, save in database or User entered, store in database authentication options), the co-editing is not available. When the Log-in credentials, save in session authentication type is used, the files cannot be opened in the editor.
If you are using a self-signed certificate for your Document Server, ownCloud will not validate such a certificate and will not allow connection to/from Document Server. This issue can be solved the following way: locate the ownCloud config file (/ownCloud/config/config.php) and open it.
Insert the following section to it:
'onlyoffice' => array
('verify_peer_off' => true
)This will disable the certificate verification and allow ownCloud to establish a connection with Document Server, but you must remember that this is a temporary insecure solution and we strongly recommend that you replace the certificate with the one issued by some CA. Once you do that, do not forget to remove the above section from the ownCloud config file.