nextcloud / nextcloud/server

[Bug]: Document templates broken

Open
#52,560 8 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 31-feedback bug feature: templates
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

Create a new office document or text document in Nextcloud. The document creation dialog only ask for the filename but doesn't let me chose one of the Templates from the "Templates" folder

Happens to me on c.nc.com. On a fresh setup LTD it seems to work but this is also a older version (30.0.10) while c.cn.com runs on 31.0.4

Steps to reproduce
  1. Make sure to have a "Templates" folder with some templates
  2. Create a new document
  3. You get only asked for a filename:

Image

Expected behavior

I can chose a Template for the new document

Nextcloud Server version

31

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the problem from the document creation dialog with a Templates folder containing templates, using the reported Nextcloud 31 setup. Inspect the dialog and template-selection entry point; done means creating a new office or text document offers the available templates. No files or tests are named in the issue, so identifying the relevant code and adding coverage will require repository research.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.