Severity: 8192
Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 132
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 290
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 164
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 233
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 313
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 354
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 282
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 294
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 304
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 314
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 315
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 317
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 375
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 110
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 143
Backtrace:
File: C:\xampp\htdocs\pdss\index.php
Line: 315
Function: require_once
This is a supplementary project to PayDay Software Systems (Pty) Ltd's Time and Attendance module. It serves as an alternative to using biometric devices that are dedicated to carry out tasks related to time and attendance. The main purpose of this application is to record date and time which can be categorized as IN, OUT, CAPTURE PHOTO, CALL OUT(IN) or CALL OUT(OUT) to specify whether a duty has started or ended. Furthermore a comment or proof as a form of an image can be attached to that task for generating reports. Any information collected on Mobile Terminal Application is mainly used for PayDay's software application, no data is shared with any other institution/party.
MTA only records your GPS Coordinates only when you perform a clocking task, which can be IN, OUT, CAPTURE PHOTO, CALL OUT(IN), CALL OUT(OUT) and that is the only incidence the system will know your location. The application does not automatically track your location. The GPS coordinates collected are further decoded to a human readable address for reporting purpose. The main reason behind recording your location is to highlight a site where the users have logged their times to avoid dishonest claims of reporting on duty.
MTA only uses your camera when you choose CAPTURE PHOTO on the application, this photo is attached to a log transaction saved which can later be used as a proof that work has been completed during site visits or call outs.
Versions of MTA running on ZKTeco's Mobile Data Terminal (HB510) devices have the ability to capture employees' fingerprints. Stored fingerprints are used to identify employees when any task under Clock IN/OUT activity is executed.