Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

404 while trying to resume the time tracking #470

Closed
gnimor opened this issue Dec 6, 2018 · 5 comments
Closed

404 while trying to resume the time tracking #470

gnimor opened this issue Dec 6, 2018 · 5 comments
Labels

Comments

@gnimor
Copy link

gnimor commented Dec 6, 2018

I am able to create a new time tracking record by clicking the play button. After that I am stoping the time tracking for this new entry. Now when I try to resume the time tracking I get a 404 page.

Moving the mouse pointer over the resume button shows the following link:

http://XXXXX/en/timesheet/start/1

I have tried this for several entries and it seems that all resume buttons point to this link which doesn't work. Moving the mouse pointer over the delete button for the corresponding row shows the following:

http://XXXXX/en/timesheet/8/delete

So it seems something with the routing is messed up?

Any idea what's wrong here?

By the way the installed version is 0.6.1.

@kevinpapst
Copy link
Member

This bug has already been fixed with 0.6.1 - so I guess you upgraded from a previous version?
Did you already try flush your cache with bin/console cache:clear?

@gnimor
Copy link
Author

gnimor commented Dec 7, 2018

Hmm, this was a fresh installation.

@kevinpapst
Copy link
Member

Please compare the file templates/timesheet/index.html.twig in your installation with this:
https://github.com/kevinpapst/kimai2/blob/master/templates/timesheet/index.html.twig#L93

This part is most important {'id' : entry.id} - does it look the same?

@kevinpapst
Copy link
Member

Closing, due to missing feedback

@lock
Copy link

lock bot commented Mar 22, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai.

@lock lock bot locked and limited conversation to collaborators Mar 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants