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 : 2018 PLC(CS)N 3 HIGH-COURT-AZAD-KASHMIR
Side Appellant : MUHAMMAD SALEEM
Side Opponent : AZAD GOVERNMENT OF THE STATE OF JAMMU AND KASHMIR
R. 33---Temporary appointment---Scope---Appointments of certain officials were made on temporary basis against their lien---Temporary appointment did not create right for permanent induction---Such employees could not claim confirmation on the basis of said appointment---Petitioners who were regular employees of the department and were promoted on officiating basis, had right that their cases for regular promotion be presented before the Selection Committee for consideration---Selection Committee was to examine as to whether petitioners (regular employees) were entitled to confirmation on the basis of their seniority and fitness or not---Department was directed by High Court to advertise the posts held by the said officials (appointed on temporary basis) against the quota reserved for initial recruitment within specified period---Writ petition was allowed in circumstances.
Citation Name : 2018 PLC(CS)N 137 Gilgit-Baltistan Chief Court
Side Appellant : RASHID AHMED
Side Opponent : PROVINCIAL GOVERNMENT through Chief Secretary
Promotion---Scope---Petitioner-employee had been exonerated from all the inquiries---Cases were being re-opened on some false pretext---Mala fide of department was on record---Petitioner-employee remained suspended for two years---No Annual Confidential Report was required during the period of suspension---Question of promotion rested within the power of competent authority---When authorities competent to award promotion acted in violation of law, in excess of jurisdiction, without jurisdiction and in colourable exercise of powers, Chief Court could exercise writ jurisdiction to redress the wrong---Department had deprived the employee from his legitimate right of promotion in violation of rules and regulations---Some inquiries had been illegally ordered from which petitioner had been exonerated even after issuance of restraining order from the Chief Court---Executive authorities were bound to follow the orders/judgments of Chief Court in letter and spirit---Orders for holding inquiries in circumstances were struck down---Authorities were directed to promote the employee from the date of holding post with all back benefits and seniority admissible under law---Writ petition was allowed in circumstances.
Citation Name : 2017 PLC(CS) 1457 SUPREME-COURT-AZAD-KASHMIR
Side Appellant : MUHAMMAD TUFAIL MIR
Side Opponent : SECRETARY ELECTRICITY DEPARTMENT, AZAD GOVERNMENT OF THE STATE OF JAMMU AND KASHMIR
S. 7---Azad Jammu and Kashmir Civil Servants (Appointment and Conditions of Service) Rules, 1977, Rr.10-B & 13---seniority ---Determination of---Officiating promotion---Scope---Service Tribunal ordered for determination of seniority of the relevant cadres diploma holder Sub-Engineer and B. Tech. (Hons) employees of the department according to departmental rules on the basis of their first appointment/induction into service--Validity---Authority could cause seniority list from time to time of the members of service, cadre or grade---seniority would take place from the date of regular appointment to a post in that grade---Civil servants who were selected for promotion to higher grade in one batch should on their promotion retain their inter se-seniority ---Promotion of Sub-Engineer on creation of vacancy of Assistant Engineer should be made while considering the respective dates of obtaining qualification along with the prescribed experience after such qualification---All qualified persons while passing acting/current charge promotion orders should have been considered and if the posts were available then promotion order for regular induction should have been made---Officiating promotion order could be made when post fell vacant as a result of deputation, leave or on current charge basis of the regular incumbent---Qualified civil servant having relevant experience and qualification prescribed for the post might be appointed/promoted but such promotion would not confer any right for regular promotion---All eligible persons were not considered while issuing the promotion orders on current charge basis and officiating basis, only the appellants were considered for such promotion---Judgment passed by the Service Tribunal was legal---Appeal was dismissed in circumstances.
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