Questions About WOPI Integration with ONLYOFFICE Community Edition

Docs
,
1

I am currently evaluating the integration of our application with ONLYOFFICE Community Edition using the WOPI protocol. Our backend implements the WOPI APIs, and ONLYOFFICE communicates with our application through these endpoints.

During testing, we encountered two issues and would appreciate your guidance:

  1. PutFile / PutContent invocation timing

According to the documentation, ONLYOFFICE calls the WOPI PutFile (PutContent) endpoint when all users leave the editing session and the document is ready to be saved.

However, this behavior makes it difficult for our users to know when their changes have actually been persisted to our backend. We would like users to be able to explicitly save their changes instead of waiting until the editing session is closed.

Could you please clarify:

  • Under what conditions does ONLYOFFICE call the PutFile/PutContent endpoint?

  • Is there a way to trigger PutFile/PutContent immediately when a user clicks “Save”?

  • Is there a recommended approach for implementing manual save functionality when using WOPI with ONLYOFFICE Community Edition?

  1. View mode warning message

When opening a Word document in view mode, ONLYOFFICE always displays the following warning message:

“The file is opened in view mode. The file is locked for editing or your access rights do not allow editing.”

In our case, the document is intentionally opened in read-only mode, so this warning may confuse users because there is no actual error.

Could you please clarify:

  • Is it possible to hide or disable this warning message?

  • Is this behavior specific to Community Edition, or does it also occur in Enterprise and Developer Editions?

  • Are there any configuration options or customization methods available to suppress this notification?

We would appreciate any recommendations or best practices regarding these topics.

3

Thank you

5

Hi @duyhoa, welcome to the community!

1. Manual save (PutFile timing)

By default PutFile fires only when all users leave the session. To save sooner, enable server-side autoAssembly in local.json (the override file; defaults live in default.json, which you shouldn’t edit directly):

{ "services": { "CoAuthoring": { "autoAssembly": { "enable": true, "interval": "1m", "step": "1m" } } } }

This makes the editor push PutFile periodically instead of only at session close. For this to reliably capture in-progress edits, also make sure the document opens in fast co-editing mode (editorConfig.coEditing.mode: "fast") — in strict mode, changes aren’t assembled until the user clicks Save. On your side, you can distinguish save types from the PutFile request headers X-LOOL-WOPI-IsModifiedByUser, X-LOOL-WOPI-IsAutosave, and X-LOOL-WOPI-IsExitSave.

Docs: Saving file | ONLYOFFICE

2. View mode warning

This message is shown intentionally — it appears when the editor ends up in a forced view-mode state, either because the file is locked for editing by another client, or because the editing-permission flags weren’t granted. It isn’t suppressible via configuration, and the behavior is the same across CE/EE/DE since it’s editor-level.

To open cleanly in view mode without the message, launch via the view action URL from WOPI discovery (not edit), and set ReadOnly: true together with UserCanWrite: false in CheckFileInfo. Opened as a genuine view session, the editor doesn’t attempt edit mode, so the message doesn’t appear.

Docs: CheckFileInfo | ONLYOFFICE

Hope this helps!