πŸ‡³πŸ‡±Netherlands @K3vin_nl

Account created on 29 November 2007, over 16 years ago
  • Designer / front-end developer at FRMWRKΒ  …
#

Recent comments

πŸ‡³πŸ‡±Netherlands K3vin_nl

Just want to confirm that #2 3375025-2.patch fixed the issue for us.

πŸ‡³πŸ‡±Netherlands K3vin_nl

BTW when I change line 219 to
'#default_value' => implode(PHP_EOL, $config->get('config_import_ignore.list') ?? []),
The form displays correctly.

πŸ‡³πŸ‡±Netherlands K3vin_nl

I just did a new install on a Drupal 10 site and ran into the same problem.
I did some debugging and found that
$this->config('mix.settings')->get('config_import_ignore.list'); results in null
which causes the implode on line 219 of modules\contrib\mix\src\Form\SettingsForm.php to fail

πŸ‡³πŸ‡±Netherlands K3vin_nl

Previous patch could not be applied.

πŸ‡³πŸ‡±Netherlands K3vin_nl

First version of patch for D10 compatibility

πŸ‡³πŸ‡±Netherlands K3vin_nl

BTW, I am working on a basic patch / MR to get the module working again.

πŸ‡³πŸ‡±Netherlands K3vin_nl

The module in the current state is not working (on Drupal 10).
The latest version relies on `drupal/google_api_client:^4.0` which in it's turn requires `google/apiclient-services:~0.200`

However, in this version of google/apiclient-services the Photos Library Service is no longer available, it seems to have moved to a separate package.

See
https://github.com/googleapis/google-api-php-client-services/issues/2664
for more details.

πŸ‡³πŸ‡±Netherlands K3vin_nl

@waldomero, might be worth mentioning this on the modules frontpage?

πŸ‡³πŸ‡±Netherlands K3vin_nl

FYI, we are using a work-around for this issue.

In the `Mapping of webform fields to Pardot fields` settings, we map the multi-select fields to individual fields:

multiselect_.option1|multiselect_option1
multiselect_.option2|multiselect_option2
multiselect_.option3|multiselect_option3
etc...

Not the most elegant solution, but it does work.

πŸ‡³πŸ‡±Netherlands K3vin_nl

Yes, I thought it might come in handy, if somebody finds this issue again.
I tried manually emptying all the cache tables in the database first, but that too didn’t fix it?

πŸ‡³πŸ‡±Netherlands K3vin_nl

Confirming the latest patch #19 works for us.

πŸ‡³πŸ‡±Netherlands K3vin_nl

Strangely enough clearing the cache didn't fix this for me.
Only after I disabled and re-enabled the module (via drush) the error disappeared.

πŸ‡³πŸ‡±Netherlands K3vin_nl

I saw Niels created a new release for Purge β†’ , so I assume he is still active. Probably just busy :-)

πŸ‡³πŸ‡±Netherlands K3vin_nl

Any plans to do a Drupal 10 compatible release?

Production build 0.69.0 2024