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 | Moscow sets conditions to revive Black Sea agreement, urges justice on earlier broken promises | Get Latest NRI News & Updates. Latest News & Updates for NRIs Worldwide - NRI Page
Edit

Moscow sets conditions to revive Black Sea agreement, urges justice on earlier broken promises

Moscow sets conditions to revive Black Sea agreement, urges justice on earlier broken promises

The Kremlin stated on Wednesday that it would not activate the recently negotiated Black Sea maritime security agreement until a series of longstanding conditions—most of them tied to earlier unmet commitments—are fulfilled. This development comes in the wake of a US-led effort to bring about a ceasefire between Russia and Ukraine in the Black Sea and halt attacks on critical energy infrastructure. On Tuesday, the United States announced that it had reached separate agreements with both Ukraine and Russia aimed at reducing hostilities in the Black Sea. These include pausing strikes on maritime and energy targets, a critical area of contention given the importance of Black Sea ports in the export of grain, oil, and other goods.
 

However, while the diplomatic breakthrough was hailed by some as a positive step, Moscow has made it clear that it expects a more equitable approach this time. Kremlin spokesperson Dmitry Peskov told reporters that the Black Sea initiative would not be reactivated until several long-pending conditions are met—conditions Russia says were ignored under the original 2022 deal brokered by the United Nations and Turkey. “As for the Black Sea grain initiative, it can be activated after a number of conditions are implemented,” said Peskov. “These are the same conditions that were included in the original Black Sea Initiative... all the conditions of which were fulfilled except for those concerning the Russian side. So, of course, this time round justice must prevail and we will continue our work with the Americans.”
 

Focus on sanctions and SWIFT reconnection

At the heart of Moscow’s concerns lies the continued economic pressure placed on its exports, despite official exemptions. While Russian food and fertiliser exports are not directly targeted by Western sanctions, Moscow argues that restrictions on financial transactions, shipping logistics, and insurance services have made it virtually impossible to carry out international trade effectively. A critical Russian demand involves the reconnection of its state-owned agricultural bank, Rosselkhozbank, to the SWIFT global payments network. The bank had been excluded from SWIFT as part of European and US sanctions imposed following the invasion of Ukraine. Moscow views the exclusion of Rosselkhozbank as a key barrier to facilitating global sales of food and fertilisers.
 

The Kremlin also seeks additional measures, including easing restrictions on transport and cargo insurance, and reopening logistics channels for Russian exports. These requirements could necessitate cooperation from multiple European countries, making the task diplomatically and logistically complex. Despite Moscow’s withdrawal from the original Black Sea Grain Initiative in 2023, which had been designed to ensure the safe export of Ukrainian and Russian agricultural products, the Kremlin insists that it had remained committed to fair trade. Russia claimed that, under that earlier deal, Western nations failed to uphold their end of the agreement when it came to facilitating Russian exports. The 2022 Black Sea Grain Initiative was a landmark agreement in a time of escalating conflict. Brokered by the United Nations and Turkey, it allowed for the safe passage of grain ships from Ukrainian ports, helping to stabilize global food markets. However, Moscow’s withdrawal in 2023 citing unmet promises caused widespread concern about rising global food insecurity and inflation, especially in developing nations that rely on grain imports from Eastern Europe.
 

US promises, but implementation remains unclear

According to diplomatic sources, as part of the new understanding, Washington has pledged to advocate for the easing of some sanctions related to Russian agriculture and logistics. However, no detailed timeline or formal commitments have been made public. Implementation will likely depend on the willingness of the European Union and other G7 nations to accommodate Russian demands, particularly in the context of ongoing conflict and broader sanctions regimes. While Russia’s insistence on fulfilling earlier conditions may delay the activation of the new deal, analysts suggest the firm stance could be part of a broader negotiation tactic. Moscow’s leadership appears to be using the leverage of cooperation in the Black Sea—vital for food security and energy stability—as a bargaining chip to ease broader economic restrictions.
 

The Biden administration has not yet commented in detail on the Kremlin’s latest remarks but has emphasized the importance of reducing tension in the Black Sea and protecting global supply chains. The State Department’s initial announcement portrayed the parallel agreements with Ukraine and Russia as a cautious diplomatic win, though it stopped short of promising direct concessions. As tensions remain high and trust fragile, the future of the Black Sea maritime deal hinges on whether the United States and its allies can address Russia’s concerns without undermining their broader strategic objectives. In the meantime, the Black Sea region continues to be both a geopolitical flashpoint and a critical artery for global commerce, food security, and energy stability.

What is your response?

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