magespecialist/m2-MSP_DevTools

PHP message: PHP Fatal error: Uncaught TypeError

Opened this issue · 2 comments

matejslo commented

Hi, for some reason MSP dev tools module when enabled returns HTTP ERROR 500.

I checked the NGNIX logs and I see this error:

2022/03/07 09:54:12 [error] 8929#8929: *47794 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught TypeError: Argument 1 passed to MSP\DevTools\Plugin\PhpEnvironment\ResponsePlugin::aroundSendContent() must be an instance of Zend\Http\PhpEnvironment\Response, instance of Magento\Framework\HTTP\Php$
Stack trace:
#0 /srv/web/myproject/vendor/magento/framework/Interception/Interceptor.php(135): MSP\DevTools\Plugin\PhpEnvironment\ResponsePlugin->aroundSendContent()
#1 /srv/web/myproject/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Framework\HTTP\PhpEnvironment\Response\Interceptor->Magento\Framework\Interception{closure}()
#2 /srv/web/myproject/generated/code/Magento/Framework/HTTP/PhpEnvironment/Response/Interceptor.php(184): Magento\Framework\HTTP\PhpEnvironment\Response\Interceptor->___callPlugins()
#3 /srv/web/best" while reading response header from upstream, client: 89.212.50.92, server: myproject.si, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php/php7.4-fpm.sock:", host: "myproject.si"

PHP 7.4.27
NGNIX 1.20.2
Magento ver. 2.4.3-p1

  1. Steps to reproduce
  2. Enable module MSP Devtools
  3. run setup:upgrade
  4. reload page in browser

Expected result

  • 500 ERROR PAGE
  • Error in ngnix logs

Actual result

  1. [Screenshot, logs]

Thank you.

giacmir commented

Hello @matejslo,
we can't reproduce your issue on a clean Magento 2.4.3-p1 instance. Can you provide some more elements to help us?

Is this happening on a particular page? Are you using Luma or a custom theme? Do you have any 3rd party module that could interfere with our module?

matejslo commented

We will try to get more info. I went to some old (aproox. 1 month) commit and the problem was gone so it must be related to some third party module or module update that we installed.

We have a custom theme, but the problem happens also on default luma theme.

I will get back to you when we have more info. We will try to find the source of the problem commit by commit.

Thank you for now.