Date of an Entry changes after first Creation of an Entry
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 40/100
Research direction
The payload names no file, so start by reproducing: create an entry with the Eloquent entries driver under the Europe/Berlin timezone and compare the date saved on first save with the date entered. Find where the date is parsed or converted on save for the entry's date field. Done means a newly created entry keeps the date the user set, and the fix is confirmed by a test that saves an entry across the timezone boundary.
Written by the indexing model from the issue text.
Description
Bug description
If I create a new entrie and save it, the Date ist set to 1 day before today.
How to reproduce
Create an Entrie. Save the first time and the date is set to an day before today.
Logs
Environment
Environment
Laravel Version: 13.34.0
PHP Version: 8.5.8
Composer Version: 2.10.2
Timezone: Europe/Berlin
Locale: de
Locales
Installed: cs, da, de, en, nb, nl, nn
LaravelLang\Lang\Plugin: 15.37.3
Locales Version: 2.11.0
Protected: de, en
Publisher Version: 16.8.0
Livewire
Livewire: v4.4.7
Statamic
Version: 6.34.1 PRO
Statamic Eloquent Driver
Addon Settings: file
Asset Containers: file
Assets: file
Blueprints: file
Collection Trees: eloquent
Collections: eloquent
Entries: eloquent
Fieldsets: file
Form Submissions: eloquent
Forms: eloquent
Global Sets: eloquent
Global Variables: eloquent
Navigation Trees: eloquent
Navigations: eloquent
Revisions: eloquent
Sites: file
Taxonomies: eloquent
Terms: eloquent
Tokens: file
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
- Dominant language
- PHP
- Stars
- 4.9k
- Forks
- 647
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 100
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
- 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.
More from statamic/cms
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
There's a default crop when cropping imagesPossibly taken A pull request linked to this issue is open or already merged. Openassets
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
antlers
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
backdrop-contrib/commerce#60 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
TYPO3-Documentation/TYPO3CMS-Reference-CoreApi#7330 ·
Maintainers usually reply within 1 day
-
dependencies
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100