TimeTrex Time and Attendance

If we stopped updating completely then security fixes and tax table updates wouldn't get rolled out and as you can imagine that would be a major problem for anyone using TimeTrex for payroll. Which is worse? Not getting updated tax tables which is relevant for some, or breaking the install which is...

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....

PHP 5.3.10-1ubuntu3.26 with Suhosin-Patch appears to be the most recent version available to me. Still 5.3.10-1, but a build or two more recent.

Per the screenshot, the PHP version is 5.3.10-1ubuntu3.25. Note that we have PHP 7.0.15-1+deb.sury.org~precise+1 in /usr/bin. Timetrex does not appear to be using this. This system is pretty much locked from most upgrades because of other dependencies. See my discussion that Timetrex should check fo...

The automatic update from about 90 minutes ago that bumped us to 11.5.1 (2019-04-17 21:12) [screenshot attached] is generating the following error when trying to add shifts: PHP Fatal error: Using $this when not in object context in [home]/TimeTrex/timetrex/classes/modules/api/schedule/APISchedule.c...

Ok, that's fine. If I'm stuck at this version for awhile, I can live with that.

Thanks,

-G

Yes, I understand how system entropy works. In our case, we use Timetrex for schedule, timeclock, and timesheets only. Payroll is not a concern for updates for us. The Chrome example is off-point. In the case we are discussing, Timetrex auto-updated such that it was incompatible with existing system...

This particular server might not be able to be upgrade past 12.04 for some time, as newer versions break some other critical software due to hard linking to specific versions of libicu. But that isn't a timetrex issue. So, if I cannot run PHP 5.4 on this server, how do I A) downgrade timetrex to whe...

Timetrex just auto-updated to 10.1.0, and now I'm seeing this message in red: WARNING: System stack components (PHP/POSTGRES) are out-of-date and not supported with this version of TimeTrex! Please upgrade them immediately! Local install on Ubuntu 12.0.4 LTS. Just updated PHP and Postgres, warning r...

Running on Linux (Ubuntu 12.04), I receive this error when running the upgrade: % php ~gbl/TimeTrex/timetrex/tools/unattended_upgrade.php -f Force Mode enabled... ERROR: Current system requirements check failed... Failed Requirements: Require,WFilePermissions Looks like a bunch of files had their ow...

Yes, this is v9.0.10. Posting to the other thread. Thanks.

This problem happened again today. Pay period ended on Sunday, new pay period was not created on Monday. When I looked at timesheets for the new week, there was a big red error banner. I followed the same steps: - manually created a new pay period for the new Monday-Sunday week so there was an open ...

Strange, I see them just fine here. Grab.app saves them as tiffs, which seemed portable enough. Here they are as pdf's.

Here you are.

My auto-update to 9.07 Community Edition went through this past week. We have one pay period schedule that begins at 00:00 Monday. All employees are assigned to it. Today, it did not automatically create a new pay period, and I am now seeing this same error message on all timesheets. I manually crea...

I have not changed the code to re-enable the interface, it was already enabled. I just changed the code to not pop-up the warning message. The legacy interface is far easier for some people to work with when viewing schedules and the like.

-G

Sure, of course. Setting installer_enabled = TRUE and re-running the web installer says that TimeTrex/timetrex/templates/Login.tpl has an invalid checksum. Because I modified that file to remove the floating "this old interface will be disabled" warning that was generally annoying when usi...

We started seeing this note in red just the other day: WARNING: TimeTrex automatic upgrade has failed due to a system error! Please contact your TimeTrex administrator immediately to re-run the TimeTrex installer to correct the issue. Finally had time to investigate, and it appears that this command...

Version: 7.1.3 Created a Recurring Template with 2 identical shifts. Note: this is either with 2 lines on the same Template that are identical, or 1 line on two different Templates that happen to be identical when applied to the same week. Two identical shifts are correctly listed as Open. One shift...

How can I change the designations of a "work" and "alternate" email to "primary" and "secondary"? Similarly, how can I change phone numbers to be "primary" and "secondary"? The goal is that the employee will put the appropriate email and ph...

It seems that hand-entering individual shifts has gotten more fiddly in version 7 (admittedly, I am upgrading from 2.2, so this might have occurred awhile back). We're retail with lots of different start and stop times to achieve the sales floor coverage we need based on the shifting availability of...

Alas. I have been running TimeTrex for some time now, but am looking seriously at dropping it because my situation, similar to that of the original poster, is just getting too cumbersome to manage. Has anyone found a solution for this type of availability-based scheduling? I would love to find somet...

The Admin->Pay Period Schedules->View Pay Period->Import Punches did fix the problem. Thanks a ton!

I have only one pay period, and have never modified it since the original install. Any idea what creates the discrepancy, requiring the need to import punches?

Thanks again,

-G

Click on the day-of: Pay Period: Sun, Nov 23 2008 to Sat, Nov 29 2008 Click on the day-after: Pay Period: Sun, Nov 23 2008 to Sat, Nov 29 2008 Click on the day-before: Pay Period: Sun, Nov 16 2008 to Sat, Nov 22 2008 What is interesting is that the total time does change when clicking on a Sunday to...

I have one employee where their Total Time ignores any shifts on Sundays. Delete the punches, alter times on the punches.. add punches to a future Sunday. The Total Time for that day displays properly, but is not included in the Accumulated Time Total Time does not include Sundays for this employee....