Severity: 8192
Message: Return type of CI_Session_database_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_database_driver.php
Line Number: 126
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
Function: require_once
Severity: 8192
Message: Return type of CI_Session_database_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_database_driver.php
Line Number: 261
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
Function: require_once
Severity: 8192
Message: Return type of CI_Session_database_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_database_driver.php
Line Number: 143
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
Function: require_once
Severity: 8192
Message: Return type of CI_Session_database_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_database_driver.php
Line Number: 193
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
Function: require_once
Severity: 8192
Message: Return type of CI_Session_database_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_database_driver.php
Line Number: 278
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
Function: require_once
Severity: 8192
Message: Return type of CI_Session_database_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_database_driver.php
Line Number: 306
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
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: 281
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
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: 293
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
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: 303
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
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: 313
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
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/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
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/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
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/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
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: 107
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 140
Backtrace:
File: /home/lawyrspk02/public_html/application/controllers/Blog.php
Line: 24
Function: __construct
File: /home/lawyrspk02/public_html/index.php
Line: 292
Function: require_once
Mobile: +92 321 3261348
Citation Name : 2019 PLC(CS) 126 SUPREME-COURT
Side Appellant : MUHAMMAD RASHID BHATTI
Side Opponent : The DIRECTOR GENERAL FIA, HEADQUARTERS, ISLAMABAD
R. 3(c)---Fundamental Rules, Pt. II, R. 17(1), proviso---Inter-se seniority ---Grant for seniority in case of supersession and subsequent promotion---Petitioner, who was working as sub-Inspector in BPS-14 in the Federal Investigation Agency, was superseded by several sub-Inspectors of BPS-14 on two separate occasions---Such supersession was not challenged by the petitioner at that time---Subsequently the petitioner was promoted as Inspector (BPS-16) and on assumption of such promoted office, he made representation to the department for inter-se seniority as Inspector (BPS-16)---Service Tribunal declined request of petitioner for inter-se seniority by observing that he was considered twice for promotion by the Department Promotion Committee, but superseded on each occasion by the Committee on account of many factors; that such supersession was approved by the Department Promotion Committee in its successive meetings and resultantly the petitioner could not regain his inter se seniority ---Plea of petitioner that proviso to R. 17(1) of Fundamental Rules made express provision for granting of seniority in case of supersession and subsequent promotion---Validity---Proviso to R. 17(1) provided for a situation where the civil servant who was entitled to be promoted from a particular date but for no fault of his own was wrongfully prevented from rendering services in the higher post was to be paid the arrears of pay and allowances of such higher post through proforma promotion or upgradation by ante-dated fixation of seniority ---Present case, however, was neither of a tenure post nor a deferment case nor that of petitioner being not promoted from a particular date for no fault of his own---Petitioner was deliberately superseded and such supersession was also endorsed by the Departmental Promotion Committee---Rule 17(1) of Fundamental Rules as relied upon by the petitioner therefore, was not applicable to the facts and circumstances of the present case---Petition for leave to appeal was dismissed and leave was refused accordingly.
Citation Name : 2019 PLC(CS) 83 SERVICE-TRIBUNAL-PUNJAB
Side Appellant : PARVEEN SHAD
Side Opponent : CHIEF SECRETARY, GOVERNMENT OF THE PUNJAB
Regularization of service---Scope---Regularization of service is not to be construed as initial recruitment rather it is to be construed as confirmation of existing employment---On confirmation of existing employment, period already served by employees would entitle them to benefit of pay in form of increments, seniority and upgradation etc., as normally available to civil servants.
Defence Saving Certificates Rules, 1966
2019 PLC(CS) 83
2019 PLC(CS) 333
Whether ad hoc employee, who was switched to contract employee and then finally regularized in service…
Neither any seniority nor any promotion could be claimed or granted without actual length of service…
Residential Accommodation at Peshawar (Procedure for Allotment) Rules, 2018
Civil Servants (Appointment, Promotion and Transfer) Rules, 1973
Maxim: Audi alteram partem
-Civil servant transferred to another department after making a request for mutual transfer with another…
Superintendent in the subordinate judiciary
Appointment of employees appointed on current charge basis was to come to an end on the appointment…
specific time constraint was set out in S.25 in which the power to issues notification by the Federal…