Updater function reports issue with data directory—should mention update directory
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Install older version of Nextcloud
- Configure config.php file with datadirectory
- Configure updatedirectory as '' (empty)
- Attempt update (web or command line)
Expected behaviour
Update progresses with understandable error messages.
Actual behaviour
Update fails with incorrect error (Error message: Could not read updater or data directory from config.php.)
Server configuration
Web server: Nginx
Database: Maria
PHP version: 8.3
Nextcloud version: 31.0.12
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the update through the web or command line with an empty updatedirectory in config.php, then trace where the updater builds the reported configuration error. Done means the failure identifies the update directory accurately instead of calling it the data directory, while retaining an understandable error message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100