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 | Digvesh Rathi’s IPL Celebrations Spark Controversy Despite Stellar Bowling for LSG | Get Indian Desi Latest Sports News & Updates in USA. Stay Ahead in Sports & Gaming Action - NRI Page
Edit

Digvesh Rathi’s IPL Celebrations Spark Controversy Despite Stellar Bowling for LSG

Digvesh Rathi’s IPL Celebrations Spark Controversy Despite Stellar Bowling for LSG

Lucknow Super Giants (LSG) spinner Digvesh Rathi has emerged as one of the most exciting new talents in the ongoing Indian Premier League (IPL) 2025 season. While his bowling has consistently delivered crucial wickets for LSG, it’s his post-wicket celebrations that have unexpectedly become a talking point—and not always for the right reasons. Rathi, who was acquired for a modest INR 30 lakh at the IPL 2025 mega auction, has proved to be a valuable asset for the Lucknow franchise. Despite being relatively unknown before the season began, the left-arm spinner has repeatedly shown composure and effectiveness on the field. However, his celebrations after dismissing batsmen have reportedly drawn the ire of the Board of Control for Cricket in India (BCCI), resulting in multiple fines. According to insiders, the cost of these fines may have already exceeded Rathi’s signing amount, prompting criticism from former cricketers and fans alike.

Simon Doull: “He’s Being Made an Example”

Former New Zealand pacer and current IPL commentator Simon Doull has publicly expressed his disappointment with the BCCI’s handling of the situation. Speaking on Cricbuzz, Doull called the punishments “unfair,” especially when similar or more intense actions by senior Indian players have gone unpunished. "The team have got to be paying that (the fines). I don't like it. I love the celebrations, I don't think he has done anything at all wrong," said Doull. "I've seen senior Indian players do way worse, be in your face, and not get a fine. They are making an example out of a young man who is what, making a note in his notebook?" Rathi’s celebratory act first drew attention during a game against Punjab Kings, where he dismissed batter Priyansh Arya and mimicked a “note-taking” gesture. It was later revealed that Rathi and Arya are good friends, and the act was intended as light-hearted banter.

Banter or Breach? BCCI Unimpressed

Despite the harmless context, the BCCI was quick to act, issuing a fine and a warning. The backlash raised questions about double standards in enforcement, with some pointing to inconsistencies in how player behavior is policed across different teams and players. Shahbaz Ahmed, Rathi’s teammate and fellow spinner at LSG, came to his defense, stating, “Priyansh Arya is his very good friend. He did it on a friendly note, but since he is on the verge of suspension, I hope he doesn't repeat it.” In an attempt to comply with the board's expectations while still maintaining his identity, Rathi tweaked his celebration in a match against Kolkata Knight Riders. This time, he performed the gesture subtly on the ground, away from opposing players, in the hope that it would avoid further penalties.

While the fines have drawn attention, what remains unquestioned is Rathi’s impact on the field. With consistent performances and the ability to strike at key moments, he is fast becoming one of the breakout stars of IPL 2025. His economy rate and wicket tally speak volumes of his cricketing potential, even as his celebrations continue to stir debate. Fans and experts alike hope that the young spinner won't lose his flair and confidence amid the controversy. As LSG progresses in the tournament, all eyes will remain on Digvesh Rathi—not just for his bowling skills, but for how he chooses to celebrate them. With the IPL spotlight now firmly fixed on him, the coming matches may define both his reputation and his career trajectory in Indian cricket.

What is your response?

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