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 PCrLJ 131 ISLAMABAD
Side Appellant : MUHAMMAD SHARIF
Side Opponent : MUHAMMAD SADIQ
Ss. 3 & 4---Criminal Procedure Code (V of 1898), Ss. 265-K, 145(7) & 431---Illegally and forcibly occupying land---Accused died pending revision---abatement of revision---Scope---Dismissal of complaint---Accused, who died during pendency of revision, during his life time interfered into land of the petitioners and took over the possession of land illegally and petitioners filed complaint under Ss.3 & 4 of Illegal Dispossession Act, 2005---Two reports were obtained by the Trial Court---First one was submitted by the Investigating Officer and the other was submitted by Naib Tehsildar, which reports had clearly revealed that deceased/accused was in illegal occupation of land belonging to the petitioners---Contention of the petitioners, was that due to death of deceased accused, proceedings would not abate, but would continue against his legal heirs to the extent of illegal possession of disputed land---Material available on record had established that deceased accused, without any lawful authority, had illegally encroached upon the property in question---Trial Court was only required and prompted to form prima facie opinion of the title for the purpose of Illegal Dispossession Act, 2005, without prejudice to the final and authoritative adjudication on the matter of civil dispute, but there was no civil suit pending at that stage---Trial Court accepted application of accused filed under S.265-K, Cr.P.C., acquitted the deceased accused; whereas, law required that when the court had issued the process on being satisfied that prima facie case was made out and as such cognizance taken, could not be recalled or reversed, especially when charge had been framed by the Trial Court---Only course to be left in such eventuality to accused side was to assail such process before the appellate or revisional court as the law did not provide any power of review to the same court---Claim of the petitioners in such situation would survive despite the fact that accused was no more active and legal heirs of the deceased could be proceeded for the restoration of possession of the disputed land to the petitioners---Revision was allowed, impugned order passed by the Trial Court was set aside---Station House Officer concerned and Tehsildar, were directed to restore the possession of the disputed property of the petitioners within 30 days in accordance with the reports after demarcation on spot and would enter the same in revenue record for the future reference under the law.
Citation Name : 2018 PLD 178 SUPREME-COURT
Side Appellant : PROVINCE OF PUNJAB through Secretary Punjab Public Prosecution Department
Side Opponent : MUHAMMAD RAFIQUE
Ss. 6 & 23---Transfer of case from Anti-Terrorism Court to court of ordinary jurisdiction---Scope---Personal enmity over property---Admittedly there was a dispute of a plot where the occurrence took place---Prosecution's own case was that the complainant had filed a civil suit and on his application for initiation of contempt proceedings against the accused persons, a bailiff of the Court was appointed---Application of contempt of court and appointment of bailiff triggered the enmity which resulted in the present occurrence---Allegedly five persons fired specifically at complainant's wife (deceased) hitting on her legs, but till that time there was no allegation of creating terror and insecurity in the general public---Subsequently, it was alleged that 26 persons, in order to create terror and insecurity in the general public, made indiscriminate firing, but, such allegation was not supported from any source as neither any crime empty was recovered from the place of occurrence nor anybody else received even a scratch on his person due to said indiscriminate firing---Due to the alleged indiscriminate firing not a single bullet hit on the walls of the plot in question which were 2.3 feet high---Furthermore, according to the complainant party, two police constables, who were guarding the complainant, were present at the place of occurrence, but it was not alleged by the prosecution that they were restrained by the accused persons to discharge their duties or anybody fired upon them or threatened them---Bailiff of the court and police constables, never claimed that they were fired at or they were threatened by the accused persons, instead they were subsequently introduced as accused persons in the case for abatement ---Perusal of the allegations levelled in the FIR, the material so collected by the investigating officer and other surrounding circumstances of the case, showed that the present case was not triable under the provisions of the Anti-Terrorism Act, 1997---Appeal was dismissed accordingly.
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…