Possible bug in CE 10.0.3 (Linux hosted)
Posted: Thu Dec 29, 2016 3:33 pm
First of all, greetings everyone! First post, I didn't see a clear place for bug reports, so please help me find the right place if this isn't it.
My company has been using Timetrex CE for a few months, but starting last night my employees lost the ability to edit their punches. I did some digging and I see that my version of TimeTrex was updated recently (2:59 AM this morning) to 10.0.3 automatically (I didn't even know it was doing that, I'm assuming it is part of the maintenance cron).
The behavior of this has been odd. We used the default security groups, and most of the employees are lvl 2, meaning they have always been able to edit/delete their own timecards. I am a level 10, so I can do that, as well as supervise my employees. Beginning this morning neither of us could edit the timecards, just add new punches. I restarted apache and the entire security group 10, including me, regained the ability to edit. Security group 2 still is unable to do so.
Any ideas? Because of the mixed success of the apache restart I plan on a full server restart after hours tonight.
I have a backup of my timetrex directory from Tuesday. If I rolled back to that and commented out the portion of the cron that auto-updates, would the old files work and interface with my updated 10.0.3 MySQL DB?
Thanks for your help!
My company has been using Timetrex CE for a few months, but starting last night my employees lost the ability to edit their punches. I did some digging and I see that my version of TimeTrex was updated recently (2:59 AM this morning) to 10.0.3 automatically (I didn't even know it was doing that, I'm assuming it is part of the maintenance cron).
The behavior of this has been odd. We used the default security groups, and most of the employees are lvl 2, meaning they have always been able to edit/delete their own timecards. I am a level 10, so I can do that, as well as supervise my employees. Beginning this morning neither of us could edit the timecards, just add new punches. I restarted apache and the entire security group 10, including me, regained the ability to edit. Security group 2 still is unable to do so.
Any ideas? Because of the mixed success of the apache restart I plan on a full server restart after hours tonight.
I have a backup of my timetrex directory from Tuesday. If I rolled back to that and commented out the portion of the cron that auto-updates, would the old files work and interface with my updated 10.0.3 MySQL DB?
Thanks for your help!