Severity: 8192
Message: Return type of CI_Session_files_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_files_driver.php
Line Number: 113
Backtrace:
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/index.php
Line: 292
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_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_files_driver.php
Line Number: 280
Backtrace:
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/index.php
Line: 292
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_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_files_driver.php
Line Number: 145
Backtrace:
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/index.php
Line: 292
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_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_files_driver.php
Line Number: 223
Backtrace:
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/index.php
Line: 292
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_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_files_driver.php
Line Number: 303
Backtrace:
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/index.php
Line: 292
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_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_files_driver.php
Line Number: 344
Backtrace:
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/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: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/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: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/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: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/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: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/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: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/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: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/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: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/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: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/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: /home1/hashimui/public_html/SubDomains/iasmoksha/application/models/Readpaper_model.php
Line: 7
Function: library
File: /home1/hashimui/public_html/SubDomains/iasmoksha/application/controllers/Pages.php
Line: 10
Function: model
File: /home1/hashimui/public_html/SubDomains/iasmoksha/index.php
Line: 292
Function: require_once
For years, the two National Highways, NH 181 (linking Karnataka with Tamil Nadu) and NH 766 (linking Karnataka with Kerala), cutting through the tiger reserve had turned into a deathtrap for the wildlife, with more than 40 different species of animals getting killed every year on the road. It was then that the Karnataka High Court, hearing a writ petition in 2009, ordered closure of the NHs for night traffic, thus upholding the animals’ right to live.
However, the ban on night traffic, even though hailed by Tamil Nadu, has not gone well with the neighbouring Kerala, which has based its argument on the reason that its mountain district’s economy, predominantly supported by tourism, has gone for a toss. Even as the case is pending before the Supreme Court, Kerala has systematically failed to convince the judicial bodies, ranging from lower courts to the apex court, that the losses are indeed due to the ban on night traffic.
Karnataka, on the other hand, has been complying with all the orders of the courts, like laying out an alternative road (Hunsur to Kutta), deployment of additional staff and infrastructure development.
June 2009: Chamarajanagara DC issues night closure order, withdraws the order within a week.
August 2009: High Court of Karnataka stays the withdrawal order.
March 2010: Karnataka High Court upholds the night closure.
May 2010: Supreme Court orders exploring possibility of a convoy system.
May 2010: Tamil Nadu closes NH67 passing through Mudumalai Tiger Reserve.
February 2011: National Tiger Conservation Authority (NTCA) submits an affidavit in the Supreme Court supporting the night closure.
June 2010: In a meeting with senior officers of Karnataka and Kerala, it was decided that convoy system was not feasible.
August 2011, December 2011, October 2013 & January 2013: Meeting between chief ministers of Karnataka and Kerala. Karnataka does not change the stand.
March 2013: Work on the alternative road completed.
November 2014: Kerala Forest Research Institute publishes a report claiming night closure does not help wildlife. But the study didn’t have requisite permission. Claims in the report criticised as fictitious by conservationists.
April 2015: Meeting between chief ministers of Karnataka and Kerala. It was decided to form an expert committee.
August 2015: Expert committee comprising Sukumar, AJT Johnsingh, Sanjay Gubbi, Ajay Desai, M D Madhusudan, Ravi Ralph and Ajai Misra recommends maintaining status quo, and if possible to advance night closure to 6 pm.
January 2018: Supreme Court appoints another committee under the chairmanship of Union Ministry of Road Transport and Highways (MoRTH).
March 2018: NTCA submits report after meeting with stakeholders and field visit. April 2018: Meeting under the chairmanship of secretary, MoRTH asks Karnataka to give its stand in writing. Karnataka does not change stand.
July 2018: Secretary of MoRT writes to Chief Secretary, Karnataka claiming Chief Minister Kumaraswamy has agreed to lift the night ban and to construct elevated highway through Bandipur. Asks Chief Secretary to send a report to be submitted to the Supreme Court. Chief Minister Kumaraswamy refutes the claim.
August 2018: Chief Secretary, Karnataka writes to Secretary of Ministry of Road Transport that lifting of night closure is not possible and elevated highways through Bandipur Tiger Reserve is not feasible.
Concerns and demands of Kerala
Karnataka’s responses
Why Kerala is hell-bent on revoking night traffic ban
Eight years after night traffic on the NH 766 stretch through the Bandipur Tiger Reserve in Karnataka was banned, Kerala’s opposition continues to be pegged to one broad argument — that it inconveniences people who travel between its northern districts and the Mysuru-Bengaluru region.
Businesses in the district were severely hit because the movement of goods was restricted during crucial night hours.
Trade enquiries have continued to drop. The business of black pepper, ginger and other produce from the district has suffered.
For someone packing fruits and vegetables from the Karnataka side, losing the night hours is crucial. For traders who then supply these products to other parts of Kerala and outside, it becomes even more difficult. Delayed delivery affects quality of items like bananas and papayas.
Are traders lobbying to revoke the ban?
Volunteers working in Bandipur reveal that more than any trade body it is the powerful timber, sand and cattle smugglers’ mafia which is lobbying at various levels to revoke the ban. “Illegal transportation of timber was rampant previously. Subsequently, illegal sand sale across borders had also reached its ebb with trucks crisscrossing the boundaries. Cattle was illegally transported to Kerala which had often triggered fights in the region. The night ban has clearly put an end to such illegal activities and the same cannot be done during day light.
Karnataka Forest Department has also stepped up vigil on the alternative road by implementing ‘Gastu’ software which records movement of every vehicle within Nagarahole Tiger Reserve, and timings clocked by the vehicles to cross the forest patch