TimeTrex Time and Attendance

Well, I ran sed over the file and replaced the \' with ''. That got me pretty far. But now \r\n is causing problems.

I'll wait to hear back. Maybe you have a more convenient solution than what I am doing.

I'm using mysql 5.7.22 and psql 9.5.13.

I just grepped the sql file and found: SET standard_conforming_strings = 'off';SET backslash_quote = 'on';SET escape_string_warning = 'off';

So technically this should work. But again...it ain't.

I verified that standard_conforming_strings is on. So it would seem that this should not be happening. But it is.

So close: psql:timetrex_mysql.sql:1089984: invalid command \'t brian@bxp(bxp):12:41:/var/www/time2/db/timetrex $ sed -n 1089984p timetrex_mysql.sql INSERT INTO message (id, parent_id, object_type_id, object_id, priority_id, status_id, status_date, subject, body, require_ack, ack, ack_date, ack_by, c...

Gah! Brain fart. I knew that! Thanks.

This is what is on that line: 766876:INSERT INTO remittance_source_account (id, legal_entity_id, status_id, type_id, country, name, description, data_format_id, currency_id, last_transaction_number, value1, value2, value3, value4, value5, value6, value7, value8, value9, value10, value11, value12, va...

Sigh, ok. Starting to really loath MySQL. It took 1hr and 12min to complete But at least it completed.

This was a TRUNCATE. I simply removed it and moved on. Before that line was: TRUNCATE recurring_schedule_template_control; TRUNCATE recurring_schedule_user; TRUNCATE regular_time_policy; TRUNCATE remittance_destination_account; TRUNCATE remittance_source_account; --- But now I get: psql:timetrex_mys...

Upgrading from mysql to postgres. The upgrade to the last mysql capable version appeared to go without a hitch (although it took a really long time - but no errors in the log). I've done everything listed at https://forums.timetrex.com/viewtopic.php?t=7519 up to the last step: putting the data back ...

I'm converting our mysql install to postgres. As part of the process we are upgrading from 10.6.2 to 11.0.2. The upgrade is taking a looooong time (like working on forty minutes now). The longest part is the upgrade of the system_log table. It has over 2.5 million records. Can we truncate this to sp...

nm, found it: EST5EDT Not EDT.

Same issue I think. I am on 11.0.2 using php 5.6. Timezone is correct on the server, but all of the dates for pay periods is set to GMT and are thus four hours off. I tried setting the ssytem_timezone in the timetrex.ini, but the only option it appears to accept is EST. Which is only right for half ...

I set it manually in the timetrex.ini.php and that fixed it.

system_timezone = EST

Not sure if that is what I was supposed to do or not. I didn't see this option in the linux example config.

I upgraded our system (a test system with 10.6.x installed) to 11.0.2 in preparation for moving to postgresql. But all of our pay periods have jumped into the future four hours. I've checked the server and it is set to the correct timezone, so is PHP. I am not sure where to look next.

Sorry. The above post relates to the installation checks. This is an upgrade.

I realize this has been asked before, but after reading a few posts I still can't see the problem. /var/ww/timetrex/logs not writable. My logs directory is set to the owner and group of the webserver (nginx). Permissions are set to 755 and 644 for the dir and files. This is the way my current instal...

You are right. I am the IT manager for our systems and I get regular reports and notices about the state of my servers. I guess most people installing this aren't in the same position I am. But then again...if it is really mission critical you would think that having qualified people managing their ...

Wow! Six whole years since I mentioned this. What...is...the...point? if ( $free_space > $min_free_space AND $free_space_percent > $min_free_percent ) { return 0; } I've been commenting this out for six years because even though I had plenty of free space, the percentage always failed even when I ha...

So we upgraded to 10.0.4 (local install) today. And our supervisor noticed that when she went to approve requests there were a lot more fields then before. I see reference to this here: http://help.timetrex.com/v10.0/enterprise/#Modules/Requests.htm#kanchor100 She is seeing what is listed under the ...

One more thing (is this written down somewhere? I looked in the manual but didn't see it):

Does the password policy expire passwords? I don't want to be surprised by this one either.

Thanks

Concerning your passwords that would or would not be accepted. I went back and checked that out. You are right (of course), but it seems that maybe some tuning would be a good thing. Like why in the world would abc123 be accepted but Paumiu6w or Deis7iLi not? Sequential numbers and letters are typic...

Thanks for the feedback. I guess the problem I'm running into is that you and I have different ideas of what is needed for the environment I work in. Besides, passwords that are so difficult that they cannot be memorized with a certain amount of ease just get written down and stored out in the open ...

Our passwords are secure and frankly screwing with the password policy sucks when we already have a company wide one that isn't in sync with yours. So now I have to change our policy to fit yours? If you are going to do that then please enable the password policy editor for the community edition. Wh...

Ok, so suddenly the passwords I use to use aren't working. I'm told they are too weak and need a special char or number? My passwords eight characters and contain upper and lower case and a number and are never based off of regular english words. So they are strong enough for an inhouse system. I tr...