Error: SeekingLimitStream::getSize() must be compatible with StreamInterface::getSize()

[Joo32]

After upgrading to whmcs v8.8, we have a problem piping emails into ticket.
When an email comes to our inbox, we do a pipe forward to create a ticket like this(as we were already using it without any problem):

/opt/cpanel/ea-php81/root/usr/bin/php -q /home/----------/public_html/my/crons/pipe.php

But instead of creating a ticket, it shows an error in ActivityLog as below:

Whoops\Exception\ErrorException: Declaration of ZBateson\StreamDecorators\SeekingLimitStream::getSize() must be compatible with Psr\Http\Message\StreamInterface::getSize(): ?int in /home/-----------/public_html/my/vendor/zbateson/stream-decorators/src/SeekingLimitStream.php:74
#0 /home/-----------/public_html/my/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\Utility\Error\Run->handleError(64, 'Declaration of ...', '/home/-----------/...', 74)
#1 [internal function]: WHMCS\Utility\Error\Run->handleShutdown()
#2 {main}

 

Any clue?

 

Thanks

 

[Jonathan Jordan]

The error message doesn't seem to reflect $fileName location (/uploads/images). Maybe $file still refers to old location of the file (which already moved)?

 

[katherine561]

The error "Error: SeekingLimitStream::getSize() must be compatible with StreamInterface::getSize()" suggests a mismatch in the getSize() method between the SeekingLimitStream class and the StreamInterface interface in the PHP code. To fix this, ensure that the getSize() method in SeekingLimitStream has the same parameters and return type as specified in StreamInterface. This alignment should resolve the compatibility issue and eliminate the error.

[twhiting9275]

Seeing this same issue randomly (4-5x daily). This is a software issue, not something that should be put on clients to resolve

Edited May 2 by twhiting9275

[websavers]

Encountered this same problem, preventing POP import to ticket from working. The issue was because of an addon that was updated with a newer version of the Guzzle Psr Library. Whomever is developing the addon would likely need to set Guzzle to version 7.0.1 only to match what WHMCS has in v8.x

For those with their own addons, here's how to do that in your addon (prior to upload to WHMCS):

Edit composer.json so that in the "require" section it has this: "guzzlehttp/guzzle": "7.0.1"

Since that needs PHP 7.2, we need to tell it to ignore the PHP requirements with --ignore-platform-reqs during 'update':

php composer.phar update --ignore-platform-reqs

Edited September 26 by websavers

[websavers]

Note: WHMCS 9 will be using Guzzle 7.4.5, so once it's released and people start using WHMCS 9, the solution above will likely need that composer.json edit to be set to guzzle version 7.4.5. Otherwise weird compatbility issues will surely arise.