🇧🇪Belgium @siemen_hermans

Account created on 13 July 2021, over 3 years ago
#

Recent comments

🇧🇪Belgium siemen_hermans

We encountered the exact same issue today on one of our websites that's currently running on Drupal core 10.3.1.
Clearing the cache however did resolve the issue.

Sadly enough this does mean that the changes present in Drupal 10.3.1 do not resolve the issue.

🇧🇪Belgium siemen_hermans

Sorry for the late response, but it seems my colleagues forgot to reply in my absence. The issue fork you've provided seemed to have resolved our issues. The plugin now works flawlessly on our multilingual setup.

🇧🇪Belgium siemen_hermans

We too experience this issue in one of our multilingual projects. It only happens when editing content in a non-default site language. When editing a node in the default language the plugin works like a charm.
So it isn't just a local environment issue.

🇧🇪Belgium siemen_hermans

Providing an updated patch for the 4.x-dev version

🇧🇪Belgium siemen_hermans

Created a new tag for the view based on the previous patch and the existing administerusersbyrole_edit_access tag logic.

🇧🇪Belgium siemen_hermans

The changes introduced by this fix can lead to a TypeError in the array_diff function.
In our specific situation the user can only have 1 role. As a result $form['account']['roles']['#default_value'] returns a string.
This causes a TypeError in the array_diff function.

A simple check of the value returned by $form['account']['roles']['#default_value'] could resolve the issue.

🇧🇪Belgium siemen_hermans

We had a customer who created node named "Administratie en boekhouden". The auto generated path resulted in "administratie-en-boekhouden" and as such the "/admin*" path was triggered. I can see a similar issue being caused by the "/batch*" path, however that one seems less likely.

Production build 0.71.5 2024