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 | Rishabh Pant Faces Heat After LSG's Second Defeat; Rs 27 Crore Tag Sparks Social Media Backlash | Get Indian Desi Latest Sports News & Updates in USA. Stay Ahead in Sports & Gaming Action - NRI Page
Edit

Rishabh Pant Faces Heat After LSG's Second Defeat; Rs 27 Crore Tag Sparks Social Media Backlash

Rishabh Pant Faces Heat After LSG's Second Defeat; Rs 27 Crore Tag Sparks Social Media Backlash

The Rs 27 crore investment made by Lucknow Super Giants (LSG) in acquiring Rishabh Pant for the IPL 2025 season is rapidly becoming one of the most talked-about decisions in the tournament. After three matches, Pant's underwhelming performances with the bat and some debatable captaincy calls have drawn strong reactions from fans and cricket analysts alike. The narrative online has already labeled the dynamic wicketkeeper-batter as a “Rs 27 crore flop,” highlighting the immense expectations and scrutiny he now faces. LSG suffered their second defeat of the season on Tuesday night, going down to Punjab Kings in a match that exposed some of the team’s weaknesses. Following the loss, a now-familiar scene played out at the stadium as franchise owner Sanjiv Goenka was seen engaging in a seemingly serious discussion with Pant on the field. The conversation, which included finger-pointing gestures and intense expressions, quickly went viral, igniting a fresh social media storm.
 

This is not the first time Goenka has been seen confronting his captain after a poor performance. In LSG’s opening match of the season, which ended in defeat to Delhi Capitals, Goenka had a similar on-field conversation with Pant. Previously, former captain KL Rahul had also faced on-field questioning from the owner after underwhelming team displays. The recurrence of such interactions has led to wider discussions about Goenka’s management style and its potential impact on team morale. Against Punjab Kings, LSG once again fell short, especially with the bat. The team’s total was well below par, and Punjab chased it down comfortably. In the post-match presentation, Pant admitted that the team had fallen 20-25 runs short and that early wickets had derailed their momentum.
 

“It wasn’t enough, we were 20-25 runs short, but that’s part and parcel of the game,” Pant said. “Still assessing the conditions at our home ground. It’s always going to be difficult to get a big total when you lose early wickets, but each and every player is trying hard to take the game forward. The idea was to get a slow wicket. I think the slower balls were sticking in. We got to learn from this game and move forward. There are a lot of positives, can’t say much.” Pant’s words, though measured, did little to calm fans who had expected fireworks from the star player. With just three matches into the season, Pant’s batting returns have been minimal and unconvincing. While the team did manage a win against Sunrisers Hyderabad in between their losses, consistency remains an issue. What’s drawing even more attention is the price tag attached to Pant. Acquired for a massive Rs 27 crore, he is one of the most expensive players in IPL history. Such a figure naturally invites heavy expectations, both in terms of leadership and personal performance. So far, neither has lived up to the billing.
 

Critics have also pointed to some questionable captaincy decisions during the matches, including field placements and bowling changes at crucial times. These tactical choices, coupled with Goenka's very visible dissatisfaction, have raised questions about the pressure Pant might be facing behind the scenes. While Goenka and Pant were seen smiling briefly during their latest on-field conversation, the images of pointed fingers and body language suggested tension. Reactions on social media ranged from sympathetic to critical, with hashtags like #PantUnderPressure and #Rs27CroreFlop trending within hours after the game. Despite the rocky start, the IPL season is long, and fortunes can change quickly. Pant, known for his aggressive batting and fearless spirit, has the potential to bounce back. LSG, too, will look to regroup and get their campaign back on track with improved performances and stability in leadership. For now, however, the focus remains firmly on Rishabh Pant — his price, his form, and how he handles the growing pressure both on and off the field.

What is your response?

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