🇺🇸United States @bradhawkins

Here's the patch

I too can confirm this error. It appears that the issue is with the way the module stores the config settings in the user.mail and user.settings rather than creating a unique config entry for the module. Thus, to fix the error, we have to create a new method for storing the settings.

This patch requires that you uninstall and reinstall the module, so proceed with proper caution.

Before applying this patch:

1. Back up your DB
2. Backup the email message (if you have customized it)
3. Make note of your permissions settings (RESTful Web Services)

Preventing Permissions Errors:

To Prevent permissions errors, we have to either uncheck all permissions related to this module or apply patch #11 from this thread: https://www.drupal.org/project/drupal/issues/3358586 🐛 RuntimeException: Adding non-existent permissions to a role is not allowed Active

Without doing either of these you will get an error when attempting to uninstall.

Uninstall the Module:

Uninstall via the UI or Drush

Clean up old settings:

Now we need to remove the old settings via Drush:
drush config:delete user.mail email_verify_register_rest
drush config:delete user.settings notify.email_verify_register_rest

Apply the Patch and Reinstall

Now we can apply the patch and reinstall the module. Reapply your permissions, re-activate the REST endpoints, and update the email message as needed.

bradhawkins → created an issue.

This seems to be related to the SDK (v7.4) and its compatibility with PHP 8. On a Drupal 10 install, I was able to manually update the SDK via composer, and the error message did not appear:

composer require sendinblue/api-v3-sdk:^8.4

However, when working with Drupal 9.5 it's not possible to update the SDK to 8.0 or above because of a conflict with guzzlehttp/guzzle which is locked by Drupal core to v6.5.8.

Because of this, it seems like it might be necessary to create a 2.0 branch of the module which is only compatible with D10+ and then update the composer.json to include the SDK 8.4+.

bradhawkins → created an issue.

I ran into some issues with patches 30-34. The patches caused an "InvalidQueryException" error whenever a non-store owner (i.e. a regular user) tried to access their orders via JSON API.

Here's an example of the error produced:
Drupal\Core\Database\InvalidQueryException: Query condition 'commerce_order_2.store_id IN ()' cannot be empty. in Drupal\Core\Database\Query\Condition->condition() (line 117 of /app/web/core/lib/Drupal/Core/Database/Query/Condition.php).

I've updated patch 34 to include some if statements to check if $store_ids is empty before continuing.

Here is a patch for anyone else that needs it.