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 : 2017 PLC(CS) 738 PESHAWAR-HIGH-COURT
Side Appellant : SAEED MUHAMMAD ZAI
Side Opponent : The SECRETARY, GOVERNMENT OF KHYBER PAKHTUNKHWA, LABOUR DEPARTMENT
Employee-petitioner being Social Security Officer---Promotion---Supersession of employee-petitioner due to average grading/ performance---Scope---Fitness---Determination of---Contention of employee-petitioner was that he was eligible for promotion but he had not been promoted---Validity---Respondent had been promoted to the post of Deputy Director (Administration) by superseding the petitioner---Rule and method for promotion for the said post was seniority -cum-fitness from amongst the Social Security Officers having at least five years service---Both the petitioner and respondent were performing their duties as Social Security Officers having five years service at their credit---Employee-petitioner was senior to respondent---Average grading could not be considered as adverse report unless so treated and conveyed to the civil servant---Fitness could not be determined on mathematical formula---Fitness was though an important element in consideration of promotion but it would precede with seniority ---Senior officer should be considered for promotion on priority basis---Nothing was on record as to why junior officer was promoted by superseding the petitioner---Competent authority should give reasons while superseding the employee---Impugned action of the department was not based on sound principles of reasonableness, Openness, justice and fair play which was struck down by High Court---Mater was remitted to the Departmental Selection Board to re-consider the promotion case of the parties afresh and decide the same in accordance with law and rules with speaking order giving reasons---Department was directed to decide the matter within a period of two months---Constitutional petition was disposed of accordingly.
Citation Name : 2017 PLC(CS)N 17 PESHAWAR-HIGH-COURT
Side Appellant : HUMAYUN KHAN
Side Opponent : GOVERNMENT OF KHYBER PAKHTUNKHWA
Appointment of Patwaris---Contention of petitioners was that authorities were intending to make appointments of their favorites and blue-eyed candidates in violation of rules---Validity---Appointment of persons for Patwari posts should be on seniority basis according to list given in register "G" of Land Record Manual and policy formulated by the Government---Any test and interview for the said appointment would be in violation of settled law---Constitutional petition being premature was disposed of accordingly.
Defence Saving Certificates Rules, 1966
Emigration Ordinance (XVII of 1979)
2019 PLD 133 SUPREME-COURT
2019 PLD 133 SUPREME-COURT
Back benefits, allowance
Rule and method for promotion for the said post was seniority -cum-fitness from amongst the Social Security…
Naib-tehsildar, appointment
Respondents and appellant, were selected by Federal Public Service Commission as Veterinary Officers…
Promotion as Naib Tehsildar against reserved quota for ministerial staff
Appointments of certain officials were made on temporary basis against their lien
Promotion to the post of Sub-Inspectors
Repeating CSS competitive examination