puthre
puthre
@bwie starting and stopping a timer should happen instantly. I suspect there is a configuration issue (like maybe the nextcloud server tries to resolve the mariadb server by name and...
Are you still experiencing this issue?
Might be fixed by 6bd1e5af4ffc7a0364a521036443c5520538b1b5
@smatthie What is your client specs? Does Chrome show the same issue?
@smatthie How long does it take for your server to respond to the work-intervals ajax call in these circumstances?
The issue seems to be a combination of a dated cpu with the instancing of hundreds (or maybe thousands) of select2 controls for tags and project editing. As a comparison...
> So I don't think it is acceptable that rendering a simple web table will take so long. The issue here is that what you get it's not a "simple...
@smatthie if you can access and build your code you can simply uncomment lines 420,473,474, 479, 519 and 520 in /js/src/timer.js. You will have to recompile your js files in...
@adnoh I think you'll need separate routes for API so you can start, stop and add timers for different users as just disabling CSRF is a hack that would require...
Yes, all the reporting done server side is in UTC. Individual times are converted in local timezone by the clients depending on their individual location (or timezone settings).