Dashboard error due to localized (default) date about bugloghq HOT 6 CLOSED

Hi mz83, I am not able to reproduce this error. Do you know what locale is being used in this case? also is this a Linux or Windows OS?
Thanks!

from bugloghq.

The system in question is a German (locale "de-DE") Windows 7 with all the latest updates, same goes for Java 7 and CF updates. The CF server itself is English (in case the L10N features make a difference), but running with a German locale.
I'll have to dig deeper into the code once I have time again, but a lsParseDateTime() in the right spot will probably take care of it.

from bugloghq.

Still not much closer to the target, but apparently the appService.searchEntries() gets called twice in quick succession, first with the correct now() (ODBC format) and then with the localized date (tick count difference of 1461).

Dumping the "criteria" at the top of the general.dashboardContent() results in the following struct:

{
    "SEARCHTERM": "",
    "GROUPBYAPP": true,
    "SEVERITYID": "1,2",
    "SORTDIR": "asc",
    "SEARCHHTMLREPORT": false,
    "GROUPBYHOST": true,
    "SEARCH_CFID": "",
    "USER": { },
    "ROWS": 5,
    "RSSURL": "index.cfm?event=rss&GROUPBYAPP=YES&SEVERITYID=1,2&SORTDIR=asc&GROUPBYHOST=YES&NUMDAYS=0.25",
    "NUMDAYS": 0.25,
    "SEARCH_CFTOKEN": "",
    "STARTDATE": "Mai, 17 2013 01:31:06",
    "HOSTID": 0,
    "SORTBY": "",
    "URL": "index.cfm?event=dashboard&GROUPBYAPP=YES&SEVERITYID=1,2&SORTDIR=asc&GROUPBYHOST=YES&NUMDAYS=0.25",
    "ENDDATE": "1/1/3000",
    "APPLICATIONID": 0
}

As you can see, the date is in that localized format again.

from bugloghq.

Ok i think i know what is the problem. The second call to searchEntries() is originated from the dashboardContent event; which is loaded via ajax on the dashboard page. This is what actually shows you the graph and the recent bug reports. dashboardContent loads the criteria from a json-serialized cookie, deserializes it and then gives it "as-is" to the searchEntries() method as arguments. So I'm thinking that the problem lies on the json deserialization process not handling the date/time value correctly (assuming it's a string).

I'm not sure if this is going to work, but try adding

criteria = normalizeCriteria(criteria);

in the loadFilter() method of /hq/handlers/general.cfc. Add it right after the call to deserializeJSON() and before the line that starts with criteria.user = getValue...

Clear your cookies, reload and see what happens.

from bugloghq.

Thank you!
I'll try it as soon as I get back from this 3 day weekend trip (next Monday is a holiday over here).

from bugloghq.

Just managed to get remote access for a few minutes.
You're correct. That function fixes the dashboard.
I've sent a pull request to save you some time (see issue #32).

from bugloghq.