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

Can't change the date format of the daily note

Open Beginner friendly
#1,405 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Domain
desktop

Research direction

Start by locating the code that generates daily note titles and applies the user's date format setting. The issue appears for years before 2026, suggesting a conditional based on the year. Verify the fix by creating or updating a daily note for a year before 2026 and confirming the title reflects the chosen date format.

Written by the indexing model from the issue text.

Description

Search first
  • I searched and no similar issues were found
What Happened?

In the latest version, I've noticed that my daily notes for 2025 and 2024 only have the year in their titles, without the month or day. When I change the date format in settings, nothing happens.

Reproduce the Bug

After updating to the latest version, this issue appears when open any year before 2026.

Expected Behavior

No response

Screenshots
Image
Files

No response

Browser, Desktop or Mobile Platform Information

platform: macOS 27.2
version: https://github.com/logseq/logseq/releases/download/nightly/Logseq-darwin-arm64-2.0.2-alpha+nightly.20261003.dmg

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.
  • I'm willing to submit a PR (Thank you!)
Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

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 logseq/db-test

All issues in logseq/db-test

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.