Error-500 accessing the backend after upgrade to PS v8.1.1

[Obsidrian Drama]

Hi all!
I trust you're well.
After the last automatic upgrade to what I believe it's PS v8.1.1, accessing the backend throws an error-500.
The frontend seems to work fine, as long as I don't set the PHP version to something newer than 7.4...

The error:
 

Quote

 

ServiceNotFoundException

HTTP 500 Internal Server Error

The service "prestashop.adapter.news.circuit_breaker.settings" has a dependency on a non-existent service "prestashop.core.circuit_breaker.guzzle.cache_subscriber".

 

Stack trace can be found here: https://dpaste.org/ZX765 

Any ideas how to fix this and resume access to the backend?

Thanks a lot in advance!
 

[todocabello]

I have the same error since upgrading to 8.1.1.

[Obsidrian Drama]

"We are not alone..." :-) 

Here https://github.com/PrestaShop/PrestaShop/issues/30761 there's an active discussion on the same issue that seems to be occurring since some time ago with the 8.x versions ...

In this PR (https://github.com/PrestaShop/autoupgrade/pull/609) they propose to remove the file  

src/PrestaShopBundle/Resources/config/services/adapter/news.yml

When I do it and refresh the backend link, another error shows up:

Quote

 

Oops... looks like an unexpected error occurred.

An exception occurred while executing 'SELECT t0.id_feature_flag AS id_feature_flag_1, t0.name AS name_2, t0.state AS state_3, t0.label_wording AS label_wording_4, t0.label_domain AS label_domain_5, t0.description_wording AS description_wording_6, t0.description_domain AS description_domain_7, t0.stability AS stability_8 FROM luol_feature_flag t0 WHERE t0.name = ? LIMIT 1' with params ["catalog_price_rule"]: SQLSTATE[42S22]: Column not found: 1054 Unknown column 't0.stability' in 'field list'

[Doctrine\DBAL\Exception\InvalidFieldNameException 0]

 

It continues even after restoring the copy of the news.yml file... 

Suggestions? 

TIA!

[musicmaster]

The "stability" field was added to this table in Prestashop 8.0. 

That you get this error suggests that your update didn't finish correctly but crashed due to some bug. You need to go back to your old version.

As the Github post that Obsidrian Drama mentioned mentions the ps_accounts module as involved I suggest you try upgrading with the Github version of Prestashop as that doesn't contain this module.