You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
System:
Magento: 2.4.5-p1 and we updated PHP to version 8.1.
PHP: 8.1
gigya/magento2-im: 6.0.0
Issue description
When we try to save Gigya's new settings in Magento Admin Panel, we got the following error:
We discovered that in the following class vendor/gigya/magento2-im/Helper/CmsStarterKit/GigyaApiHelper.php in line 388, Gigya provides null as a parameter:
PHP 8.1 requires integer (0) for this case:
Possible solution:
When we temporary set 0 instead of null for enc method, it works correctly and we were able to save configuration in Magento Admin Panel, but it is file in vendor, so we should not modify any files there
Question:
Please, let me know, if it is issue on Gigya side or something is incorrect with our configuration/setup.
If issue is on Gigya side, please let me what is recommended solution, or do you plan any fix for this case?
The text was updated successfully, but these errors were encountered:
Hi, as far as I remember, the idea was indeed to use the default value that openssl_encrypt provides. We will verify this and modify it in the next version, assuming it works.
Hi @mtwegrzycki , I have verified that it works, but we haven't released a new version yet because we'd like to fully support the latest versions of PHP and Magento 2. I can confirm though that this modification in openssl_encrypt works.
System:
Magento: 2.4.5-p1 and we updated PHP to version 8.1.
PHP: 8.1
gigya/magento2-im: 6.0.0
Issue description
When we try to save Gigya's new settings in Magento Admin Panel, we got the following error:
We discovered that in the following class vendor/gigya/magento2-im/Helper/CmsStarterKit/GigyaApiHelper.php in line 388, Gigya provides null as a parameter:
PHP 8.1 requires integer (0) for this case:
Possible solution:
When we temporary set 0 instead of null for enc method, it works correctly and we were able to save configuration in Magento Admin Panel, but it is file in vendor, so we should not modify any files there
Question:
Please, let me know, if it is issue on Gigya side or something is incorrect with our configuration/setup.
If issue is on Gigya side, please let me what is recommended solution, or do you plan any fix for this case?
The text was updated successfully, but these errors were encountered: