Create an componet confìg like this: config.xml
fill in Date with time in Repeat able table (before_save.jpg)
save the form, then the shown time is changed (after_save.jpg)
Show the save Time after saving!
The saved time leave the timezone
systeminfo-2019-01-28T14_21_30+01_00.json.txt
This issue take on both sites (Frontent and Backend(Config))
BeforeSave
After Save
Config:
config.xml.txt
Priority | Urgent | ⇒ | Medium |
Status | New | ⇒ | Information Required |
@thuebschmann you should not use filter="user_utc"
in your config.xml
for the calendar in the subform field. Because it not applied to subform field while saving, but applied by the calendar field while displaying.
At current point of time the fields in the subform field does not support filtering/validation.
@Fedik I have try this option too. but this is no different.
At current point of time the fields in the subform field does not support filtering/validation.
--> thats the reason of this issue report
I have try this option too. but this is no different.
@thuebschmann I meant, you should remove that attribute
@thuebschmann any Comment?
if I remove the attribute i have the problem too.
In normal field i can User filter="user_utc", but in Repeatable subform isn't work.
if i use UTC as Konfig-Time-Zone there is no problem. But I need the Berlin Timezone.
if I remove the attribute i have the problem too.
Are you sure? because I cannot reproduce it.
if you do not use filter attribute, the time will NOT be modified after save as you asked in your first comment,
The problem remain that the default value in UTC, but after save it stay what was selected.
But again, this is because 'subform' do not support filter/validation at current time.
This is known issue.
There even was a pull request #14189
@HLeithner should #14189 reopened and merged?
@franz-wohlkoenig no, this PR will not be merged, UTC should work and hopefully we get #14189 rewritten for 4.0 @Harmageddon
Indeed, #14189 sadly didn't have very high priority, because surprisingly few people noticed / reported that filters and validations don't work in subforms. Right now, it is too late to introduce it to 3.x because of our version roadmap.
I hope I manage to get a new PR for 4.0 ready for testing within the next two weeks. Will inform you then.
Category | ⇒ | com_config |
Labels |
Added:
J3 Issue
|
Status | Information Required | ⇒ | Confirmed |
@Harmageddon are you still looking at getting a PR set for this?
Status | Confirmed | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-03-11 17:05:33 |
Closed_By | ⇒ | jwaisner |
Status | Fixed in Code Base | ⇒ | Closed |
Closed_By | jwaisner | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @jwaisner by The JTracker Application at issues.joomla.org/joomla-cms/23703
Closing as #14189has confirmed that previous merges have corrected this.
@HLeithner can you please comment?
@thuebschmann changed Status "Urgent" to "Medium" according to https://docs.joomla.org/Bug_and_Issue_Tracker_Priority