[Bug]: A lot of app config keys are not defined
Open
Nobody has claimed this yet.
1. to develop
33-feedback
bug
feature: dav
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
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 OR Nextcloud Community Forum (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
After upgrading from 32.0.11 to 33.0.5 I am flood with a lot of warnings about not defined app config keys for DAV.
Steps to reproduce
The notifications:
[no app in context] Info: The app config key dav/hide_absence_settings is not defined in the config lexicon
GET /index.php/settings/admin/logging
[no app in context] Info: The app config key dav/sendInvitations is not defined in the config lexicon
REPORT /remote.php/dav/addressbooks/users/admin/contacts/
[no app in context] Info: The app config key dav/enableCalendarFederation is not defined in the config lexicon
REPORT /remote.php/dav/addressbooks/users/admin/contacts/
[no app in context] Info: The app config key dav/allow_calendar_link_subscriptions is not defined in the config lexicon
PROPFIND /remote.php/dav/principals/users/admin/
Expected behavior
In my opinion these warnings should not appear.
Nextcloud Server version
33
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 31 to 32)
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
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
Start by inspecting the DAV app's config lexicon declarations and the usages of hide_absence_settings, sendInvitations, enableCalendarFederation, and allow_calendar_link_subscriptions. Reproduce the upgrade-related warnings and verify that each reported key is defined in the lexicon and no longer logged as undefined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100