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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: 292
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: 166
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: 235
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: 315
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: 356
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: drivers/Session_files_driver.php
Line Number: 108
Backtrace:
File: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
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: /home/k35euu4ok03e/public_html/iacademy/application/controllers/Home.php
Line: 6
Function: __construct
File: /home/k35euu4ok03e/public_html/iacademy/index.php
Line: 293
Function: require_once
All businesses, even those that rely mostly on online or digital support, would still have to deal with employees. And sometimes, managing their daily issues and concerns could be time-consuming and exhausting.
We asked our resource person, Alvin Alburo, who specializes in business law and labor law, for some practical advice on how to handle employee matters effectively.
• Clearly defined rules and regulations
In order to make sure that the employees would comply with the company’s Code of Conduct, it is important the rules are clearly written. The kind of behavior and character that the company expects from its employees must be provided clearly.
Of course, the rules must not be unreasonable, say bathroom breaks are allowed only once in the morning and once in the afternoon. It must be grounded on the laws of the land and must not violate basic human rights. After all, your employees are supposed to be working for you, not against you.
The rules must have no room for ambiguity, otherwise, some employees will use whatever excuse they can come up with just so they can get away from disciplinary actions. The Code must specify the violations, the gravity or severity of this violation, and the consequences of its commission.
• Discuss the Employee Code of Conduct with the employees
Fostering good communication with employees is very important because it ensures productivity and allows the company to operate effectively. The company must not just distribute it without telling the employees its relevance in the workplace.
Employees must understand well that any violation would merit a disciplinary action. They need to know that the company is serious and expects employees to abide by it.
• Uniform implementation
In order to ensure compliance with the Code of Conduct, there must be a uniform implementation. The same rules would apply regardless of the length of stay in the company, academic achievement, or worse, closeness or friendship with the superior.
In fact, there are no grounds that should excuse noncompliance. If the superiors are too friendly with their subordinates, there are chances they might start taking undue advantage of the friendship. This might be taken as an excuse not to comply with the rules and not to respect the superior. The effect? It would affect the morale of the rest of the employees and would encourage them not to follow the Code of Coduct. Why would they follow it if a certain someone gets away with it just because he/she is close with the supervisor?