TimeTrex Time and Attendance

I'm not seeing any errors in your log file, please check your Apache or PHP error logs, its possible Apache or PHP may be crashing or timing out.

The currency format is controlled by your operating system locale. What operating system/version do you have TimeTrex installed on, and what country is the employee in?

You don't have things setup properly to pay the employee then. Can you please post a screenshot of the employees wage records in their employee profile?

When you click the "Wage" icon on the timesheet and you don't see any wages appear, it means that you added the employees wage record after you entered time on their timesheet. Therefore its considered a retro-active wage change and you must recalculate the employees timesheet (using the R...

Nope.

Please upgrade to the latest version (v11.5.1) and try again.

Can you please confirm the exact version of TimeTrex that you are using?

Ok - why does TimeTrex auto-update itself to a point where it fails? In our deployment, this Ubuntu 12.04 system cannot be upgraded because it supports what has become critical legacy software. I don't need any new features from TimeTrex - I just need it to keep working with the old legacy software...

Your PHP version is the problem then, PHP v5.4 has been the oldest supported version for a while now, and as of TimeTrex v11.5.0 it switched to PHP v7.0 as the minimum required version. PHP v5.3 end-of-life was 5 years ago, and PHP v7.0 end-of-life was back at the beginning of January. So your PHP v...

The error at the top of the screen says your system stack components are out of date. What version of PHP are you using?

The PostgreSQL log doesn't seem to match the TimeTrex log, are you sure thats the entire timetrex log file? If so please do the following: In your TimeTrex.ini.php file, set the following under the [debug] section: enable = TRUE enable_display = FALSE buffer_output = TRUE enable_log = TRUE verbosity...

There should be more information in your TimeTrex log file, can you try to re-run the last step that failed and attach the entire log file here please?

The reason is because the "N/A" absence shifts that you have on Apr 16th and Apr 18th are likely entered incorrectly, they span two days, Apr 16th @ 8PM to Apr 17th @ 6PM for a total of 22hrs and therefore conflict with the shift that you are trying to add on Apr 17th from 9AM to 12PM. If ...

Just so you are aware Recurring Schedules (gray font) in the future never conflict with manually created schedules (black font). So if you are getting an error message about conflicting start/end times, its not conflicting with a recurring schedule, but already committed shift. Can you please post s...

When viewing the schedule under Attendance -> Schedule, please click the "Basic Search" tab, then click the "Clear Search" button, does the employees Wed. shifts appear then?

If you remove all lines from your crontab regarding TimeTrex, then in the TimeTrex directory run: That should automatically add the proper cron command for you.

There is still a "$" at the end, if that actually is in your crontab, then the command would fail as it shouldn't be there.

The command you pasted here is cut-off at the end (notice the $), can you please paste the full and complete command that you are using?

If that is the full command, then that is likely your problem as its cut-off and missing the last part.

Here is a direct link to the downloads: https://www.timetrex.com/onsite-community?step=download

Once upgraded to the latest version let us know if the problem persists or not.

What version of TimeTrex are you using?

TimeTrex doesn't have any policies that would deduct time exactly how you mentioned. However rounding policies may get your fairly close to what you want by rounding the In punch to something like 9:30AM, or rounding the out punch to 5:00PM.

I'm not sure I understand what you are looking for. What you described seems to be exactly what our undertime schedule policy functionality currently does. Can you please provide more detailed examples of what you are looking for?

Out-of-the-box CentOS7 uses stack components that are well past their end-of-life, so you will need to upgrade them to meet at least the minimum requirements of TimeTrex specified here: viewtopic.php?f=6&t=6

You've likely changed permissions to remove that functionality then, if you revert those permission changes or revert your permissions back to the defaults it should restore it.

TimeTrex doesn't block employees from punching in/out as the end result is typically just a missing punch as employees will just continue on with their day and get distracted and forget to punch again in 5 minutes. Paid editions of TimeTrex can show messages to employees if they try to punch outside...