You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
I hope this is the correct place to report this issue.
I'm using the https://github.com/hofff/contao-calendarfield which uses the multicolumnwizard to manage disabled Dates for a calendar form input.
When I create 2+ entries (e.g. 08.09.2023, 09.09.2023 and 10.09.2023) and save it, it gets correctly serialized like this: a:3:{i:0;a:2:{s:4:"date";i:1694124000;s:6:"active";s:1:"1";}i:1;a:2:{s:4:"date";i:1694210400;s:6:"active";s:0:"";}i:2;a:2:{s:4:"date";i:1694296800;s:6:"active";s:0:"";}}
note the timestamps.
When I remove an entry which is not the last one (e.g. 08.09.2023) it gets serialized like this: a:2:{i:0;a:2:{s:4:"date";i:1694210400;s:6:"active";s:0:"";}i:1;a:2:{s:4:"date";s:10:"10.09.2023";s:6:"active";s:0:"";}}
Only the last date of the list gets serialized as string while the rest gets serialized as integer.
Kind regards,
Thomas
The text was updated successfully, but these errors were encountered:
Hi!
I hope this is the correct place to report this issue.
I'm using the https://github.com/hofff/contao-calendarfield which uses the multicolumnwizard to manage disabled Dates for a calendar form input.
The multicolumnwizard is configured like this:
When I create 2+ entries (e.g. 08.09.2023, 09.09.2023 and 10.09.2023) and save it, it gets correctly serialized like this:
a:3:{i:0;a:2:{s:4:"date";i:1694124000;s:6:"active";s:1:"1";}i:1;a:2:{s:4:"date";i:1694210400;s:6:"active";s:0:"";}i:2;a:2:{s:4:"date";i:1694296800;s:6:"active";s:0:"";}}
note the timestamps.
When I remove an entry which is not the last one (e.g. 08.09.2023) it gets serialized like this:
a:2:{i:0;a:2:{s:4:"date";i:1694210400;s:6:"active";s:0:"";}i:1;a:2:{s:4:"date";s:10:"10.09.2023";s:6:"active";s:0:"";}}
Only the last date of the list gets serialized as string while the rest gets serialized as integer.
Kind regards,
Thomas
The text was updated successfully, but these errors were encountered: