🇹🇳Tunisia @adel-by

adel-by → created an issue.

Added a minor fix : When creating a new user we get the assertion error : Cannot load the "user" entity with NULL ID.
This is because the $account object is initialized with and empty uid

adel-by → created an issue.

adel-by → made their first commit to this issue’s fork.

I'm running into a similar problem but with mariadb and Drupal 11.
When adding an existing subgroup, i hit the assertion error :
Fetch mode 65543 is not supported. Use supported modes only.
This happens on D11 because of : https://git.drupalcode.org/project/drupal/-/blob/11.1.x/core/lib/Drupal/...
I guess this is related to this change : https://www.drupal.org/node/3377999 →
The patch in #3 ( issue3268971-fix.patch → ) helped me bypass the problem.
Not sure about the correct fix for this though.

In my case the error was originated from a call to "Drupal::moduleHandler()->loadInclude()" in a custom module.

The solution provided here helped : https://www.drupal.org/project/drupal/issues/3420704 🐛 container not initialized yet Active

Please ignore patches from #41
here's a patch that's against 10.4.x (added same changes to ComponentNodeVisitor)

Patch for Drupal Core 10.4.x (added same changes to ComponentNodeVisitor)

adel-by → made their first commit to this issue’s fork.

adel-by → made their first commit to this issue’s fork.

adel-by → made their first commit to this issue’s fork.

adel-by → made their first commit to this issue’s fork.

Tested this MR, works as expected.
Thank you!

Tested and working as expected. Marking as RTBC.

Tested and working as expected. Marking as RTBC
Thank you.

Works as expected. Marking as RTBC.

Tested the MR, works as expected. Marking RTBC.
Thank you

Tested and works as expected.

This is looking good, i've been testing this MR alongside with frontend_editing and everything is working as expected.
Thank you.

The new plugin Bluesky was not discovered because it was not in the right directory
I moved it from src/Plugin/SocialMediaLinks/ to src/Plugin/SocialMediaLinks/Platform/

adel-by → made their first commit to this issue’s fork.

The patch in #14 no longer applies, here is a re-roll.
BTW we are using this patch on a production site for several months now and no issues were reported.

Hello,

It should be

$settings = $custom_options + $default_settings;

not

$settings = $default_settings + $custom_options;

or else all fields get added to the "hidden" region (the default value) even if explicitly set to "content"

Hi,
Following the suggestion in #10, here's another MR that adds support to search_api views.
It also makes sure that the sets feature work properly and introduces a hook that allows other modules to alter the possible contextual filter ids.
I'm using this module on media entities BTW and it works just fine.

adel-by → made their first commit to this issue’s fork.