All add-ons currently require PHP 7.4 or greater.
On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.
Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Datagrab is erroring out when upgraded server to php 8.3
| Status | Resolved |
| Add-on / Version | DataGrab 5.2.1 |
| Severity | |
| EE Version | 7.4.9 |
Kevin Chatel
May 09, 2024Hi, We’ve upgraded one of our testing server to php 8.3.6 and now when trying to create a datagrab import it throws this error
Error Caught
Call to a member function getErrors() on null
user/addons/datagrab/mcp.datagrab.php:383
Stack Trace: Please include when reporting this error
#0 [internal function]: Datagrab_mcp->check_settings()
#1 ee/ExpressionEngine/Controller/Addons/Addons.php(1592): call_user_func_array()
#2 ee/ExpressionEngine/Controller/Addons/Addons.php(868): ExpressionEngine\Controller\Addons\Addons->getModuleSettings()
#3 [internal function]: ExpressionEngine\Controller\Addons\Addons->settings()
#4 ee/ExpressionEngine/Core/Core.php(268): call_user_func_array()
#5 ee/ExpressionEngine/Core/Core.php(124): ExpressionEngine\Core\Core->runController()
#6 ee/ExpressionEngine/Boot/boot.php(184): ExpressionEngine\Core\Core->run()
#7 index.php(143): require_once('...')
#7 index.php(143): require_once('...')I’m using the latest version of Datagrab you provided my April 25th “datagrab-5.2.1-develop-2e103a45”
Let me know if I need to downgrade or if it’s a quick fix. Thanks
BoldMinded (Brian)
Looks like you resolved this before I had a chance to take a look at it. What was the issue and resolution?
Kevin Chatel
Comment has been marked private.
BoldMinded (Brian)
I don’t think those lines of code have anything that would change behavior between 8.2 and 8.3. Do you have different versions of PHP locally vs a remote server? If so then based on where this error is occurring it sounds like the settings are messed up on the remote server. Have you tried re-creating the import configuration?
Kevin Chatel
We figured it out, we needed to change the php session directory permission in nginx. Thanks Brian