Loading Profile...
Dates on badge being reported as "January 1, 1970"
When I use TreoTwit (http://www.mitreo.com/motwit_twitter_...) to report a book finished, the date isn't getting captured from my Treo device.
This might not be a problem with *your* application, I agree. But there's also this odd discrepancy between the books being attributed as "finished" in the JSON and those on the Bkkeepr Web site:
My badge seems to be updating o.k.
So I wonder why:
1) the contents of the JSON differ from the Bkkeepr user page;
2) the dates on certain of the JSON entries are using a default. Is it the application I'm using? Timezone? Time format?
This might not be a problem with *your* application, I agree. But there's also this odd discrepancy between the books being attributed as "finished" in the JSON and those on the Bkkeepr Web site:
My badge seems to be updating o.k.
So I wonder why:
1) the contents of the JSON differ from the Bkkeepr user page;
2) the dates on certain of the JSON entries are using a default. Is it the application I'm using? Timezone? Time format?
I’m persuaded I can live with it.
4
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
![James [bkkeepr]](http://3.static.getsatisfaction.com/uploaded_images/0224/8647/bkkeepr-200_small.jpg)
Hey all - huge apologies for the delay, but I think this is now fixed... Do you want to check your badges and let me know if it's still buggy?
I’m slow, but eventually useful.
The company and 1 other person say
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I have a similar thing on my badge - it lists my latest unfinished book as finished in 1970. As soon as I send the message to mark it as finished, the date goes all sensible. Hope that helps!
I’m fuddled
-
Inappropriate?Hi Melanie et al.,
Thanks for reporting this. I'm aware of the problem and I'm working on it.
Initially I thought it was due to the server switching over to British Summer Time, but I've changed that over and the problem's still there in part, so I'm pursuing other solutions.
Apologies for the inconvenience, and hope to have it fixed soon...
James
I’m annoyed but on it...
1 Comment Add a comment
This solves the problem
-
Great! Sorry to have caused an international incident. -
1 Comment Add a comment
This solves the problem
-
I'm still getting this today. It's still only a problem with the JSON, not on my user page hosted by bkkeepr.
-
Inappropriate?Hey all - huge apologies for the delay, but I think this is now fixed... Do you want to check your badges and let me know if it's still buggy?
I’m slow, but eventually useful.
The company and 1 other person say
this solves the problem
-
-
Inappropriate?Fantastic, it's working exactly how I wanted it to. :):):) Thanks!
I’m thrilled and exhuberant
![James [bkkeepr]](http://2.static.getsatisfaction.com/uploaded_images/0224/8647/bkkeepr-200_medium.jpg)
EMPLOYEE
