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) 403 ISLAMABAD
Side Appellant : WASEEM RIAZ
Side Opponent : MINISTRY OF CAPITAL ADMINISTRATION AND DEVELOPMENT (CADD)
S. 5---Civil servant s (Appointment, Promotion and Transfer) Rules, 1973, Rr. 10, 11, 12, 13, 14, 15, 16 & 17---Notification O.M. No.F.53/1/2008-SP dated 11-05-2017---Constitution of Pakistan, Art. 25---Recruitment policy---Petitioners were appointed on daily wages in various educational institutions and they sought direction to the authorities for their regularization---Validity---'Initial' appointment to a post described in S. 5 of Civil servant s Act, 1973 was covered under Part-III of Civil servant s (Appointment, Promotion and Transfer) Rules, 1973---Qualifications and other conditions relating to eligibility to a post were laid down by concerned Ministry or Division in consultation with Establishment Division---Posts were divided into 2 categories; in basic pay-scale 16 and above or equivalent and in basic pay scale 1 to 15 or equivalent---Appointment to former posts were required to be filled through tests and examinations conducted by Federal public Service Commission and in case of latter on recommendation made by Selection Committee of the relevant department after vacancies were advertised---Candidate for any post was eligible to be considered if he or she had possessed prescribed educational qualification, experience and other conditions---Age limit was also a relevant factor---All posts, whether permanent or temporary, were to be filled strictly in accordance with Civil servant s Act, 1973 and Civil servant s (Appointment, Promotion and Transfer) Rules, 1973--- New recruitment policy was not in conflict with Civil servant s (Appointment, Promotion and Transfer) Rules, 1973 while implementing new policy appointing authority was to ensure that provisions of Civil servant s Act, 1973 and Civil servant s (Appointment, Promotion and Transfer) Rules, 1973 were not violated in case of making appointments to posts described in S. 5 of Civil servant s Act, 1973--- Initial appointments of petitioners on daily wage basis were made in violation of principles of transpare ncy and were void as other similarly placed persons were regularized therefore, petitioners could not be treated alike--- Illegality could not be made ground for discrimination nor would give rise to rights being accrued in favor of petitioners---Petitioners were seeking their appointment as civil servant s under Civil servant s Act, 1973 and Civil servant s (Appointment, Promotion and Transfer) Rules, 1973---New recruitment policy approved by Federal Cabinet was not in conflict with Civil servant s Act, 1973 and Civil servant s (Appointment, Promotion and Transfer) Rules, 1973---Petitioners were in pay scale 16 and above and they were at liberty to apply directly to Federal public Service Commission in accordance with new recruitment policy, i.e. Notification OM No. F.53/1/2008-SP dated 11-05-2017---High Court while exercising Constitutional jurisdiction could not condone lack of transpare ncy and then allow illegality to perpetuate---Constitutional petition was dismissed in circumstances.
slide2
Defence Saving Certificates Rules, 1966
Sentence on an offender already sentenced for another offence
Inheritance
Mutation Proceedings
The exercise of jurisdiction by the Revenue Courts
Negotiable Instruments Act
Huma Jamil Babar
Accused indulged in arranging for employment of some persons abroad on basis of forged documents although…
2012 PCrLJ 679 KARACHI-HIGH-COURT-SINDH
2015 PLD 382 KARACHI-HIGH-COURT-SINDH
2016 PLD 70 LAHORE-HIGH-COURT-LAHORE