Feature Wiki
Tabs
WOPI: Create empty Documents
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 4 Additional Information
- 4.1 Involved Authorities
- 4.2 Technical Aspects
- 4.3 Privacy
- 4.4 Security
- 4.5 Contact
- 4.6 Funding
- 5 Discussion
- 6 Implementation
- 6.1 Description and Screenshots
- 6.2 Test Cases
- 6.3 Privacy
- 6.4 Approval
1 Initial Problem
If an online editor is configured, existing files can be opened and edited with it. This feature should make it possible to edit new, empty documents together.
2 Conceptual Summary
The options for creating a new file object have been extended to include a new option: Create empty document.
All options supported by the connected WOPI editor are offered.
3 User Interface Modifications
3.1 List of Affected Views
- Creation Dialog for new Files in Repository
3.2 User Interface Details
The existing file input is moved to a switchable group and displayed by default. In a second group (radio option), it is possible to create a blank document.
3.3 New User Interface Concepts
The feature is implemented with existing UI components and does not introduce any new UI concepts.
3.4 Accessibility Implications
The use of existing UI components does not introduce any new implications for accessibility.
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Schmid, Fabian [fschmid]
- Authority to Sign off Code Changes: Schmid, Fabian [fschmid]
If this request is related to multiple components, please list both authorities for all related components.
4.2 Technical Aspects
To create new documents, WOPI uses the `editnew` actions. These must also be taken into account by the crawler and then provide the information for which file types the editor supports the creation of new files.
Furthermore, the WOPI endpoint must now support the 'PutFile' operation: https://learn.microsoft.com/en-us/microsoft-365/cloud-storage-partner-program/rest/files/putfile
4.3 Privacy
No new personal data is collected or processed as a result of the implementation of the feature.
4.4 Security
The implementation of the feature does not introduce any new attack vectors. there are no further special security-related considerations to be made.
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: Lorenz, Katharina [klorenz]
4.6 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.
5 Discussion
Potter, Chris [ChrisPotter]: 25 SEP 2025: I would suggest the following changes to the language entries visible in the image above (based on the latest version of the English Style Guide - basic rule: to the left - title case, to the right - sentence case):
Creation Mode
Upload file
File Type
JourFixe, ILIAS [jourfixe], 29 SEP 2025: We highly appreciate this suggestion and accept the feature for trunk. The submit on the creation form should be adapted to the new options on the screen. Currently, it is labeled 'Upload File'. This doesn't fit with the creation of an empty file. Maybe a simple 'Create' would be better.
6 Implementation
Feature has been implemented by Schmid, Fabian [fschmid]
6.1 Description and Screenshots
Additional changes
To make creating empty documents work reliably with WOPI clients such as OnlyOffice, ILIAS now supports the WOPI locking operations: Lock, GetLock, RefreshLock and Unlock. Saving checks the lock as well. A lock expires after 30 minutes unless the WOPI client refreshes it. This prevents two editor sessions from overwriting each other's changes.
Besides that, the implementation was brought in line with the WOPI specification, and several robustness issues were fixed:
- Requests from the WOPI client are verified with the proof keys from the discovery.
- Saved content is stored on behalf of the stakeholder that owns the file.
- While WOPI is deactivated, requests are refused.
- The WOPI settings are protected against CSRF.
- Error responses no longer reveal internal details.
- The discovery is only fetched from web URLs, with a timeout and a size limit.
- Access to the WOPI administration is only granted with permissions on the File Services node.
Option "Create Templates"
The original request did not include this option; it was added after the acceptance meeting. The WOPI settings now have a checkbox "Create Templates", deactivated by default. When it is activated, the file type selection for empty documents also offers template formats such as .dotx, .xltx or .potx. Without the option, only regular document formats are offered.
The block "Currently supported Suffixes" in the WOPI administration always shows the template formats of the discovery in a separate row "Create (Templates)", whether the option is active or not. This way administrators can see which templates the connected WOPI client supports before they activate the option.
In the selection, each format shows the name of the WOPI app and the suffix, for example "Word (.docx)", sorted by app.
6.2 Test Cases
Test cases completed at 16 OCT 2026 by Schmid, Fabian [fschmid]
- C93941 : Verify that empty documents can be created
- C93942 : The creation form offers uploading files and creating an empty document
- C93943 : Create an empty text document and edit it
- C93944 : Create an empty spreadsheet, presentation and PDF
- C93945 : View a new document before it is published
- C93946 : Users who may only read cannot edit a created document
- C93947 : Without a suitable WOPI client, files are uploaded as before
- C93948 : Uploading files still works with WOPI activated
- C93949 : Automatic publication publishes the latest content
- C93950 : "Create Templates" offers template formats when creating an empty document
6.3 Privacy
no change required
6.4 Approval
Approved at 2026-10-26 by Stake, Sebastian [sstake].
Last edited: Today, 13:10, Kunkel, Matthias [mkunkel]