Hey @prattarazzi@thibautdavoult@daviducolo@marcuscoh and everybody else, I just fixed a small bug that might have fixed the issues you guys reported. At least I'm not ever getting the bug you describe. You mind checking it out? That would be great!
@karlludwigweise Hey Karl. Unfortunately, still getting the problem. I tried the following: 1) Deleted existing logs & projects. 2) Deleted all cookies (6 I think). 3) Closed browser tab. 4) Opened new browser tab & created a new timer. Tried to stop timer. Got the 'Someone ate your cookies on the way; or you deleted them.' message.
@karlludwigweise Fixed it for me after I cleared my cookies and cache/cached images (because why not do that as well). Excited to try this out as I start a new work day. One quick feedback: when logging a timed sequence, I don't expect to be instantly directed to a new timer upon saving it. Rather, I'd expect to get to the list of past timed sequences that I logged. Not a huge deal and I'll get used to the flow, but just wanted to let you know it felt counterintuitive in the first try.
@thibautdavoult glad to hear that. Maybe @prattarazzi can try the same approach ;)
We actually thought a lot about what you do, when you're done with a log. We decided to go with starting a new log, because we think that during your day you just return to the site to stop the running timer and start logging a new task. I think you probably get used to it :D
Happy logging!
Hey everybody and especially @marcuscoh@thibautdavoult@prattarazzi and @daviducolo
I just solved the "Cookie Error" your guys got. Would you mind checking it out? A simple reload of the page should be enough to solve it on your machine.
@karlludwigweise Hey, I'm still getting it! Sorry. I deleted all the cookies. Logged into my simple account. Deleted all existing logs. Refreshed browser (Chrome). Started a timer. On stopping the timer I get the error. [I'm now going to delete my account and try recreating it to see if that helps... OK, I deleted the account and created a new account, but I'm still getting the problem. I can start a timer, but I get the error when I try to stop the timer (Chrome browser)]
Hey @prattarazzi , that's weird. Because I don't get the error no matter how hard I try. Did you clear your cache? It actually is a javascript error, so you would need to load the new JS file. Let me know if you have any insights. You can reach me more directly at ludwig@timelog-app.com
brilliant. i need this in my life, sadly.
on one of my browsers, the countdown clock either does not move or starts with a negative value. on another, the cookie monster keeps telling me it ate my cookies -- only happened after i created an account and logged in.
:o)
@marcuscoh Thanks, Marcus! Which browser causes which behavior? Does cleaning-up your cookies might help?
Report
@herbigt using chrome in both cases. on the negative countdown, if i refresh the page, it seems to work. however, the calculation remains in error on summary -- such as Total: -16598d 11h 19min 38sec ...
are you not seeing this issue in chrome or is using chrome the issue?
Hey @marcuscoh thanks for the input. I'm looking into it right now. The error occurs, when you are logged out, right? What platform are you on? Windows? I'm trying to find the root of the error ;)
Product Hunters, we'd also love to get your feedback on our ideas for future iterations of Timelog:
- Editing of log descriptions
- Editing of log projects
- Export project logs as .csv
- Export project logs as .pdf
- Collaborative logging on projects
- Invoicing directly from projects
- API for integration with further services
What else are you missing to make Timelog your default solution to track efforts on projects or clients?
Hey! Nice job. I really like the colour scheme. It wakes me up and makes me feel happy :-) The simplicity is great too. Really clear how to use it. [fyi... I've been getting a few 'Ooops! Someone ate your cookie errors...' when I click 'stop timer'. Using Chrome and Safari browsers on Mac.]
@herbigt@prattarazzi I've had them in both versions. I'm not sure if it's related to multiple browser windows. I wanted to keep one window open to time things whilst using the other window to look at other parts of your website. The additional information is: -Stop Action Error total:-
Edit: I closed my browser windows with Timelog. I reopened 1 window. The timer was still running. I click stop. I get the error message. No event is logged. I refresh and the timer continues to run.
love the user on-boarding technique where you allow users to start timing items without being logged in.
this comment is a year later, Hows the project going now?
@thibautdavoult Hey Thibaut, thanks a lot! Appreciate your feedback. Do you constantly get this message or only when you try to log something? A quick clean-up of your cookies should help at last. Hope you can enjoy Timelog anyways!
Timelog
Product Snacks
Timelog
Livestorm
Timelog
Timelog
Product Snacks
Timelog
SearQ
Timelog
Git2Go
Timelog
Timelog
Git2Go
Product Snacks
Git2Go
Product Snacks
Git2Go
Product Snacks
Paste A Date
Livestorm
Git2Go