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 YLR 1777 KARACHI-HIGH-COURT-SINDH
Side Appellant : MUHAMMAD SARWAR
Side Opponent : State
Ss. 365-A, 148 & 149---Kidnapping or ABDUCTION for extorting property, valuable security etc., rioting armed with deadly weapon, unlawful assembly---Appreciation of evidence---Benefit of doubt---Prosecution case was that the accused and co-accused armed with Kalashnikov and gun kidnapped two persons for ransom---Name of accused did not appear in the FIR---No evidence was available to show that accused had kidnapped abductees for ransom but only allegation against him was that he had received ransom amount but time and place of payment had not been established---Accused was not put to identification through witnesses after his arrest---No ransom amount was recovered from him during investigation--Both abductees did not implicate accused that he kidnapped them for ransom and received amount---Only piece of evidence collected against accused was that he was identified by prosecution witnesses before the Trial Court after five years of the incident---Identification of accused before the Trial Court was not safe for conviction---Evidence showed that 30-bore pistol was recovered from accused during investigation---Accused had faced trial under the Arms Ordinance before the Judicial Magistrate but had been acquitted in that case--- Admittedly, four co-accused were acquitted on the same set of evidence---Conviction of the accused on same set of evidence without independent corroboration was unwarranted in law---Evidence showed that there were material contradictions in the prosecution case with regard to the place of incident, place of payment of ransom and other particulars of the case---Allegedly, during the captivity of the abductees in jungle there was a police encounter but none received injury from either sides which clearly showed that prosecution story was unbelievable and unnatural---After release from accused, abductees did not go to the police station for fifteen days for recording their statements, which created serious dent in the prosecution case---In the present case, identification parade was held by Magistrate while ignoring the legal formalities---Record showed that before holding of identification parade, accused were shown to the abductees---Statements of abductees showed that they failed to individually identify either of them with reference to role allegedly played by them in the incident---Manner in which identification proceedings were conducted raised serious doubt on the credibility of the process---Circumstances established that prosecution had failed to bring on record the antecedents of the abductees who were kidnapped for ransom which was paid to the accused for their release---Appeal was allowed and accused were acquitted, in circumstances, by setting aside conviction and sentences recorded by the Trial Court.
Difference between courts and tribunals (PLD 2020 SINDH 284)
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
CHANGE IN DATE OF BIRTH
Social and economic rights of underprivileged segments of society
Sentence on an offender already sentenced for another offence
Inheritance
Mutation Proceedings
The exercise of jurisdiction by the Revenue Courts