I have…
- [X ] Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
- [X ] Used code blocks with ``` to format my code examples like JSON or logs properly.
I’m submitting a…
- [ X] Regression (a behavior that stopped working in a new release)
- Bug report
- Performance issue
- Documentation issue or request
Current behavior
After upgrading Squidex to version 7.23, the DateTime editor no longer allows users to enter seconds.
The editor only displays fields for hours and minutes. When a future date and time are selected or an existing value is edited through the Squidex user interface, the seconds are removed and the value is saved with seconds set to 00 .
For example, a value containing seconds:
2026-08-10T15:30:45
is changed to:
2026-08-10T15:30:00
This behavior was not present before the upgrade.
Expected behavior
The DateTime editor should allow users to enter and edit hours, minutes and seconds.
Existing timestamps containing seconds should retain their original value when the field is opened or edited.
For example, the HTML datetime-local input could support second-level precision by using:
step="1"
Minimal reproduction of the problem
- Create or open a schema containing a DateTime field.
- Create or edit a content item.
- Select a future date and time using the DateTime editor.
- Try to enter a value including seconds.
- Save the content.
The editor does not provide a field for seconds, and the saved timestamp contains 00 seconds.
The same issue occurs when an existing timestamp containing seconds is edited through the user interface: the original seconds are lost.
Environment
App Name:
- [X ] Self hosted with docker
- Self hosted with IIS
- Self hosted with other version
- Cloud version
Version: 7.23
Browser:
- [X ] Chrome (desktop)
- Chrome (Android)
- Chrome (iOS)
- Firefox
- Safari (desktop)
- Safari (iOS)
- IE
- Edge
Others:
The DateTime field is used to manage deadlines for public notices and procurement procedures. Second-level precision is required to ensure that expiration dates and times are recorded accurately and handled consistently by the system.