Open ablears opened 2 years ago
This has been a common issue around different plugins that have been moving to the PHP >= 7.4 supported Psr Container ^2.0.x.
I have run into this issue in a few of my personal packages too. The only resolution is to have SatisPress bump it's depemdency to support PHP >= 7.4 and then update psr/container to ^2.0.2.
See changes: https://github.com/php-fig/container/compare/1.1.2...2.0.2
Funny, I ended up running into this issue again today with a project, and was able to resolve it via Composers use as feature. In my projects composer require I included: "psr/container": "dev-master as 1.1.2"
. This pulls in latest 2.0.x but tells your project it's version 1. Just be careful about strict type comparisons.
Using Satispress on a regular wp site and getting this error... How exactly can I implement the suggested solution inside within the plugin files..? Currently have this error showing up: Fatal error: Declaration of Pimple\Psr11\ServiceLocator::get(string $id) must be compatible with Psr\Container\ContainerInterface::get($id) in /home/443710.cloudwaysapps.com/wxbfkrannf/public_html/wp-content/plugins/satispress/vendor/pimple/pimple/src/Pimple/Psr11/ServiceLocator.php on line 38
The only way to get the website back up is to disable the plugin... But... I kinda need it :-) Will appreciate any idea anyone might have for me :)
Anyone? Anything..??
I'm also having this issue after downloading the latest release and uploading it as a standard plugin.
composer require cedaro/satispress:1.0.3
results in the following:composer require cedaro/satispress:1.0.3 -W
:This then results in a fatal error: