A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_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_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_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_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_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_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_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_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_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_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_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_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

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: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

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/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

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: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | Yuzvendra Chahal Divorce Case Expedited: Bombay High Court Waives Cooling-Off Period | Get General Articles. Stay Informed on a World of Topics - NRI Page
Edit

Yuzvendra Chahal Divorce Case Expedited: Bombay High Court Waives Cooling-Off Period

Yuzvendra Chahal Divorce Case Expedited: Bombay High Court Waives Cooling-Off Period

The Bombay High Court has directed the Bandra Magistrate Court to decide the divorce case of Indian cricketer Yuzvendra Chahal and his estranged wife, Dhanashree Verma, by March 20. The decision comes as Chahal’s Indian Premier League (IPL) 2025 commitments draw closer, with the Punjab Kings set to play their opening match on March 25 against the Gujarat Titans in Hyderabad. Justice Madhav Jamdar presided over the case and emphasized the urgency of resolving the matter promptly. The court considered Chahal's professional obligations and waived the mandatory six-month cooling-off period, enabling the divorce proceedings to conclude sooner.
 

Legal Battle and Alimony Details

Chahal and Dhanashree had filed for divorce by mutual consent on February 5 before the family court. However, the court had initially refused to waive the six-month cooling-off period on February 20. The couple had been living separately since June 2022, roughly 18 months after their marriage. A crucial aspect of the case revolved around alimony payments. As part of the agreed consent terms, Chahal was required to pay Rs 4.75 crore as alimony to Dhanashree. The family court had previously noted that Chahal had only partially complied with the payment terms, having paid Rs 2.37 crore. The court's decision to delay the divorce initially stemmed from incomplete financial compliance and a report from a marriage counsellor indicating only partial mediation success.
 

Following the family court's refusal to expedite the divorce, Chahal and Dhanashree jointly appealed to the Bombay High Court, seeking a waiver of the cooling-off period under Section 13B of the Hindu Marriage Act. This clause permits the waiver if there is no possibility of reconciliation between the two parties. Considering that the couple had already been separated for over two and a half years and had complied with most of the agreed financial terms, Justice Jamdar approved the waiver and ordered the Bandra Magistrate Court to conclude the divorce proceedings by March 20. The court noted that the remaining balance of the alimony payment would be settled after the divorce decree was granted.
 

Chahal's IPL 2025 Commitments

Yuzvendra Chahal has been actively preparing for IPL 2025 with Punjab Kings, having joined their pre-season camp in Chandigarh in the second week of March. Punjab Kings are set to face Gujarat Titans on March 25 in Hyderabad. Given his commitments with Punjab Kings, the court prioritized Chahal’s professional schedule in its expedited ruling. Chahal was also recently seen supporting the Indian cricket team during the Champions Trophy final in Dubai on March 9. He was spotted in the stands at the Dubai International Cricket Stadium, sitting alongside social media influencer RJ Mahvash.
 

Speculations and Clarifications

Speculation about Chahal and Dhanashree’s relationship had been circulating since the couple stopped posting pictures together on social media. Earlier this year, rumors emerged that Dhanashree had demanded Rs 60 crore as alimony. However, her family strongly denied these claims. "We are deeply outraged by the baseless claims being circulated about the alimony figure. Let me be absolutely clear — no such amount has ever been asked, demanded, or even offered. There is no truth to these rumours whatsoever," a family member of Dhanashree clarified. The Bombay High Court’s decision has now paved the way for the divorce proceedings to conclude swiftly, ensuring both parties can move forward amicably. With Chahal’s IPL 2025 commitments fast approaching, the court's decision aligns with his professional priorities, while ensuring that the legal and financial conditions are respected.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD