Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Wrong davis version on diagnostics page

Open Beginner friendly
#319 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, php, symfony
Domain
backend

Research direction

Start by tracing the /dashboard/diagnostics page to find where it reads and displays the Davis version, then check how the Docker image supplies that version. Reproduce with the v5.6.2 image and compare the displayed value with the image version; done means the diagnostics page reports the correct Davis version.

Written by the indexing model from the issue text.

Description

bug
Davis version

v5.6.2

Installation method

Docker – (Davis + MariaDB + nginx)

PHP version (bare metal only)

No response

Database

MariaDB

Reverse proxy

Nginx

Authentication method

Internal (ADMIN_LOGIN / ADMIN_PASSWORD)

Affected protocol(s)
  • CalDAV
  • CardDAV
  • WebDAV
  • Admin dashboard
  • API
Client(s) exhibiting the issue

I think diagnostics page sows wrong davis version. Running latest davis docker image for v5.6.2 the diagnostics page still shows version 5.5.0

Image
Relevant environment variables
APP_ENV=prod
...
Steps to reproduce

Open /dashboard/diagnostics of your davis instance

Expected behaviour

Diagnostics page should show correct versions of davis etc.

Actual behaviour

wrong software version

Logs

Additional context

Running davis together with nginx reverse proxy, I also cleared nginx www cache, but diagnostics page still shows wrong davis version.

Dominant language
PHP
Stars
760
Forks
45
Avg merge
1d 14h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from tchapi/davis

All issues in tchapi/davis

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.