Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editing a newly created Oplog entry clears Start/End Dates #308

Open
er4z0r opened this issue Apr 28, 2023 · 2 comments
Open

Editing a newly created Oplog entry clears Start/End Dates #308

er4z0r opened this issue Apr 28, 2023 · 2 comments
Assignees
Labels
bug Something isn't working stale

Comments

@er4z0r
Copy link

er4z0r commented Apr 28, 2023

Describe the bug
When I manually create new oplog entry using the "create" button, it is added to the log with start and end date pre-filled. As soon as I double click a field like "source" and the editing dialogue comes up, the start and end fields are blanked out

To Reproduce
Steps to reproduce the behavior:

  1. Create oplog entry using "create" button -> entry added to the log with start/end prefilled
  2. Double-Click a field e.g. "source" --> dialoge w/ start/end display as empty

As you can see from the screenshots my date format is d.m.Y when looking at the field in the edit entry dialogue using "Inspect Element" in Firefox I get:

<input type="datetime-local" name="start_date" value="28.04.2023 17:17:53" autocomplete="off" step="1" class="datetimeinput form-control" required="" id="id_start_date">

Expected Behavior
Start and End fields should display the pre-filled values.

Screenshots
gw-oplog-bug

gw-oplog-bug2

Server Specs:

  • Ghostwriter v3.2.6, released 10 April 2023

Additional context

  • Firefox 102.9.0esr , German Locale
@er4z0r er4z0r added the bug Something isn't working label Apr 28, 2023
@chrismaddalena
Copy link
Collaborator

To acknowledge this for anyone looking at it here: this was discussed over Slack, and I expect it has to do with an issue between the datetime-local field type and the locale. I'll look into this.

Copy link

This issue has been labeled as stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

2 participants