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 CLD 318 LAHORE-HIGH-COURT-LAHORE
Side Appellant : MUSHTAQ AHMED
Side Opponent : JUDGE, BANKING OFFENCES COURT NO.2, LAHORE
Ss. 9 & 20---Offences in Respect of Banks (Special Courts) Ordinance (IX of 1984), Ss. 4 & 5---Offences triable under Offences in Respect of Banks (Special Courts) Ordinance, 1984---Jurisdiction of Banking Court---Offence of preparing fraudulent land record documents for obtaining finance facility---Question before the High Court was whether offence of preparing a forged "fard" for obtaining a finance facility/loan from a Financial Institution/Bank, fell within the exclusive jurisdiction of Financial Institutions (Recovery of Finances) Ordinance, 2001, or could the same be tried under provisions of Offences in Respect of Banks (Special Courts) Ordinance, 1984---Held, that in the present case, allegations of making ABETMENT had also been made against Bank Manger and Revenue Officials, which were examined by the Special Court under Offences in Respect of Banks (Special Courts) Ordinance, 1984 and the same ordered the accused to stand trial for said offences---Suit filed before Banking Court under Financial Institutions (Recovery of Finances) Ordinance, 2001 was different in nature as the issue in the same was default by petitioner/customer and recovery of the same---Complaints before the Special Court, in the present case, were against different parties on different grounds which could not be tried by the Banking Court since it could only try matters covered in S. 9 of the Financial Institutions (Recovery of Finances) Ordinance, 2001---Offences which fell under purview of Financial Institutions (Recovery of Finances) Ordinance, 2001 were to be tried by Banking Court while other offences not covered by the said Ordinance would be triable under Offences in Respect of Banks (Special Courts) Ordinance, 1984---High Court observed that S. 20 of the Financial Institutions (Recovery of Finances) Ordinance, 2001 did not cover allegations made in the present case which fell squarely within jurisdiction of Ss. 4 & 5 of the Offences in Respect of Banks (Special Courts) Ordinance, 1984---Constitutional petition was dismissed, in circumstances.
Citation Name : 2019 YLR 2576 LAHORE-HIGH-COURT-LAHORE
Side Appellant : NOOR AHMAD
Side Opponent : State
Ss. 302(b), 324, 109, 148 & 149---Qanun-e-Shahadat (10 of 1984), Art.22---Qatl-i-amd, attempt to commit qatl-i-amd, ABETMENT , rioting armed with deadly weapon, unlawful assembly---Test identification parade---Scope---In the present case, complainants had also relied upon test identification parade conducted with respect to co-accused---Facts remained that neither the name of said co-accused was mentioned in the written application nor any descriptive features through which he could be identified---Test identification parade had lost its authenticity and evidentiary value, in circumstances.
slide1
Difference between courts and tribunals (PLD 2020 SINDH 284)
P L D 2020 Peshawar 52 (a) Khyber Pakhtunkhwa Continuation of Laws in the Erstwhile Provincially Administered…
Defence Saving Certificates Rules, 1966
Defence Saving Certificates Rules, 1966
Suit for declaration seeking change in date of birth
-International Covenant on Civil and Political Rights
Offences in Respect of Banks (Special Courts) Ordinance (IX of 1984)
Abatement of revision
Interim/interlocutory orders of the Appellate Tribunal---Constitutional jurisdiction of High Court-
specific time constraint was set out in S.25 in which the power to issues notification by the Federal…
Protesters who claimed to espouse their cause often forgot that their right to protest ended when other…