#foswiki 2016-09-28,Wed

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
GithubBot[distro] vrurg pushed 4 new commits to Item14152: https://git.io/vPvuJ
distro/Item14152 29fb139 Vadim Belman: Item14152: Merge commit 'bf1f07a46d32264cb4adbbc792b71c0d00ab94cc' into Item14152...
distro/Item14152 706e34c Vadim Belman: Item14152: Merge commit '24826b5cdd1a3d4710f8d386d675db13e62c7734' into Item14152...
distro/Item14152 6eefe98 Vadim Belman: Item14152: Merge commit 'a517114a8d0f0cb5338f37268dd86ca9e36e5253'...
[00:14]
***GithubBot has left [00:14]
FoswikiBothttps://foswiki.org/Tasks/Item14152 [ Item14152: Implement OONewPluginModel proposal ] [00:14]
........................................................................ (idle for 5h57mn)
***ChanServ sets mode: +o MichaelDaum [06:11]
..... (idle for 24mn)
ChanServ sets mode: +o CDot [06:35]
........................................................... (idle for 4h52mn)
ChanServ sets mode: +o Lynnwood [11:27]
............. (idle for 1h4mn)
fsfs has quit IRC (Ping timeout: 250 seconds) [12:31]
....... (idle for 31mn)
ChanServ sets mode: +o gac410 [13:02]
.................................. (idle for 2h48mn)
LynnwoodAnyone worked with MoreFormfieldsPlugin and in particular the "date2" field type? I've having odd behavior whereby it's displaying the stored value a day off.
I know it reformats the time based on DefaultDateFormat... but I'm not sure why it should be changing the value. It seems to be related to whether I have DisplayTimeValues set to gmtime versus servertime.
If i set it to server, then it changes the display of the stored value, but if I set it to gmtime, then it changes the date of a value submitted from html form.
frustrating...
being as i'm working on a time clock applications, it's a real problem.
[15:50]
The only thing i can figure is that in translating the display of the values using DefaultDateFormat, it's changing it to epoch format and back... and that's triggering outset between server time and gmtime... or some such.
Can't see a way to over-ride it... guess i may have to fall back to the old date field.
[16:02]
MichaelDaumLynnwood, this is a browser issue [16:13]
LynnwoodHey MichaelDaum - interesting...
how so?
[16:13]
MichaelDaumbrowsers apply their own timezone logic to days in YYY-MM-DD format
only way to work around this is to use dates in YYYY/MM/DD format ... silly as it is
only then will dates stay as they are supposed to be
[16:14]
Lynnwoodi have as display format DD MMM YYYY [16:15]
MichaelDaumfound out the hard way
yea but MMM is object to i18n
[16:15]
LynnwoodAnd date2 indicates that it always _stores_ in format YYYY-MM-DD [16:15]
MichaelDaumright. [16:16]
Lynnwoodok. i'll go try it out. [16:16]
MichaelDaumnext version of MoreFormfieldsPlugin fixes this to YYYY/MM/DD [16:16]
Lynnwoodthanks so much. just so i can get it to work consistently. [16:16]
MichaelDaumas far as I've found out YYYY/MM/DD is the _only_ date format that is (a) not subject to localization and (b) not botched by browsers interpreting iso dates in some odd way [16:17]
Lynnwoodand so your recommending to use YYYY/MM/DD for DefaultDateFormat [16:17]
MichaelDaumyes
we need to differentiate store from display format
it should be stored locale independent in YYYY/MM/DD format and the displayed according to a users locale settings
[16:17]
Lynnwoodthe current docs for MoreFormfieldsPlugin indicates that it's storing it in YYYY-MM-DD format
drats.. still not working for me. I changed DefaultDateFormat to YYYY/MM/DD but when I edit a topic with date2 field, it's displaying the date in the field as YYYY-MM-DD and it's a day off...
off of the stored value.
which is also stored as YYYY-MM-DD
[16:20]
MichaelDaum - so i'm still stuck for now.
I'm wondering if I can modify line 31 of Date2.pm to say:
$value = Foswiki::Time::formatTime($epoch, $Foswiki::cfg{DefaultDateFormat} || '$year/$mo/$day')
[16:29]
FoswikiBothttps://trunk.foswiki.org/System/PerlDoc?module=Foswiki::Time [16:30]
Lynnwoodmight as well give it a try... [16:31]
............ (idle for 59mn)
gac410Lynnwood: what client browser are you using. I'm really skeptical about browsers changing formfields ... but, I guess there are some browsers that will "localize" type=date formfields. But firefox isn't one of them.
A trace of the traffic would probably tell you if it's the browser.
[17:30]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)