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
Recently began testing out Sparkpost and this extension. It's mostly great, but have one issue to look at. On the settings page (/civicrm/admin/setting/sparkpost) this PHP error appears dozens of times:
Notice: Array to string conversion in Civi\Core\SettingsMetadata::_filterSettingsSpecification() (line 149 of /home/cividemo/public_html/sites/all/modules/civicrm/Civi/Core/SettingsMetadata.php).
Anything I've tried still works despite the error, but best case it is disconcerting.
PHP 7.2.20
CiviCRM 5.15.1
Sparkpost extension 1.3, initially tried with the version in the extension directory, then tried with the latest version here
The text was updated successfully, but these errors were encountered:
I get the same error. I think it's related to the webhook throwing errors on the settings page. But I'm not sure if that's happening for everyone. When we upgraded to PHP 7.2 the callback URL got lost. Not sure it's related but I suspect that something in the extension has a bug in how settings metadata is set up.
Guys - I will let you debug this one as I do not have any customer instance on PHP 7.2 and/or CiviCRM 5.15. Please submit a PR, making sure you keep backwards compatibility with previous versions of CiviCRM and PHP. Thanks.
Recently began testing out Sparkpost and this extension. It's mostly great, but have one issue to look at. On the settings page (/civicrm/admin/setting/sparkpost) this PHP error appears dozens of times:
Notice: Array to string conversion in Civi\Core\SettingsMetadata::_filterSettingsSpecification() (line 149 of /home/cividemo/public_html/sites/all/modules/civicrm/Civi/Core/SettingsMetadata.php).
Anything I've tried still works despite the error, but best case it is disconcerting.
PHP 7.2.20
CiviCRM 5.15.1
Sparkpost extension 1.3, initially tried with the version in the extension directory, then tried with the latest version here
The text was updated successfully, but these errors were encountered: