Hello Marco,
we tried to change the year as you suggested, but nothing is changing
because the problem is about day and month
On 22/03/17 15:26, Marco Di Sabatino Di Diodoro wrote:
Il 22/03/2017 15:14, Tech ha scritto:
You could try with YYYY-M-d or YYYY-d-M or YYYY-MM-d ... we tried
different combinations to make it working, but the result didn't change.
We save the user and when we try to edit the date field the only
correct information is the year
Please, try with yyyy-M-d
convert years to lowercase
Regards
M
On 22/03/17 14:54, Marco Di Sabatino Di Diodoro wrote:
Hi,
Il 22/03/2017 14:48, Tech ha scritto:
Dear Syncope Team,
we are using version 2.0.2 of the product.
We detected this issue both from Console and Enduser interface:
changing a custom date, the year is reported correctly, but the day
and month are wrong.
If we try to define a date like the 31-01-2017, the date that is
store is actually 02-00-2017.
To reproduce your use case I need some information:
1. the conversion pattern defined in your schema
2. steps to reproduce the problem
Regards
M
We also detected that the time is in GMT, therefore if we set as
date 01-01-2017 00:00:00, the date that is actually considered is
31-12-2016 23:00:00.
Could you please double check this?
Thanks
--
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570
Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 0859111173
http://www.tirasa.net
Apache Syncope PMC Member
http://people.apache.org/~mdisabatino/
--
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570
Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 0859111173
http://www.tirasa.net
Apache Syncope PMC Member
http://people.apache.org/~mdisabatino/
