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) 333 SUPREME-COURT
Side Appellant : MAQBOOL AHMAD QURESHI
Side Opponent : GOVERNMENT OF PAKISTAN through Secretary Law and Justice
S. 17, Proviso II---Sindh Civil Servants Act (XIV of 1973), S. 18, Proviso II---Khyber Pakhtunkhwa Civil Servants Act (XVIII of 1973), S. 17, Proviso II---Punjab Civil Servants Act (VIII of 1974), S. 16, Proviso II---Balochistan Civil Servants Act (IX of 1974), S.17, Proviso II---Constitution of Pakistan, Art. 203-F---Repugnancy to Injunctions of Islam---Order of dismissal, removal from service or reduction in rank set aside---Entitlement to back benefits/ arrears on reinstatement---Plea of appellant before the Federal Shariat Court was that civil servants who were dismissed and or removed from service did not render any service during the intervening period till their restoration and or reinstatement; that Proviso II to S.17 of Civil Servants Act, 1973, Proviso II to S.18 of Sindh Civil Servants Act, 1973), Proviso II to S.17 of Khyber Pakhtunkhwa Civil Servants Act, 1973), Proviso II to S.16 of Punjab Civil Servants Act, 1974), and Proviso II to S.17 of Balochistan Civil Servants Act, 1974, which provided the concerned authority with the discretion to grant back benefits on reinstatement, were misused and abused by the reinstated civil servants, therefore such provisions, were repugnant to the Injunctions of Islam and should not be allowed to remain on the statute book---Federal Shariat Court dismissed the petition by holding that the impugned provisions did not provide for automatic grant of arrears of the intervening period between dismissal/removal/reduction in rank and restoration to the original position; that the authority vested under the law to make such an order, depending upon law, facts and circumstances, may determine, inter alia, question relating to reinstatement, etc., including restoration to original position, in seniority , cadre, and post, treatment of intervening period as duty or on leave and its kind---Held, that appellant did not cite any Nass of the Holy Quran and Sunnah of Holy Prophet (PBUH), which was sine qua non to seek declaration of the kind sought by the appellant---No exception could be taken to the view formed by the Federal Shariat Court in the impugned judgment---Ayah 188 of Surah Baqrah [2-188: Holy Quran] relied upon by the appellant, was not relevant to the point in issue nor the appellant was able to explain the same---Shariat Appeal was dismissed in circumstances with costs of Rs.10,000.
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…