nextcloud / nextcloud/richdocuments

[Bug]: templates folder needs explicit permission to allow templates to be opened.

Open
#2,139 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug feature: templates
Dominant language
JavaScript
Stars
453
Forks
147
Avg merge
14h 54m
Merged PRs (30d)
83

Description

⚠️ This issue respects the following points: ⚠️
  • This is a bug, not a question or a configuration/webserver/proxy issue.
  • This issue is not already reported on Github (I've searched it).
  • Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
  • I agree to follow Nextcloud's Code of Conduct.
Bug description

users can not open the template flies added in Settings / Office

Steps to reproduce
  1. Create a template folder in the root directory of nextcloud
  2. create a writer and calc template there
  3. add the template ins settings/office
  4. other users can not open the template - missing permission
Expected behavior

if the admin adds a template file in Settings/Office it should be readable by anyone without granting special rights to the file

Installation method

Other

Operating system

Other

PHP engine version

Other

Web server

Other

Database engine version

Other

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

No response

Are you using the Nextcloud Server Encryption module?

No response

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report
I am using a SAAS NC installation - can not access the server and can not answer the questions
List of activated Apps
can not access the SAAS server
Nextcloud Signing status

No response

Nextcloud Logs

No response

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

Reproduce the issue using the listed steps: create templates in the root template folder, add them in Settings/Office, and try opening them as another user. Trace how the template file's permissions are handled and ensure an admin-added template is readable by other users without granting special file rights.

Written by the indexing model from the issue text.

Assessment

Domain
authorization
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.