I could now reproduce the WSOD error with Drupal 10.3.10 and doctrine/deprecations 1.1.4, it was shown after clearing the cache and editing a field of a content type. The error went away with doctrine/deprecations 1.1.3.
Can confirm the memory error when visiting URL /%5C on Drupal 10.3.10 and symfony/http-foundation v6.4.16.
I received similar warnings with drupal/core 10.3.10 and doctrine/deprecations 1.1.4 when visiting pages under /admin:
Warning: include(): Failed opening '/var/www/html/vendor/composer/../doctrine/deprecations/lib/Doctrine/Deprecations/Deprecation.php' for inclusion (include_path='/var/www/html/vendor/pear/archive_tar:/var/www/html/vendor/pear/console_getopt:/var/www/html/vendor/pear/pear-core-minimal/src:/var/www/html/vendor/pear/pear_exception:.:/usr/local/lib/php') in include() (Line 576 in /var/www/html/vendor/composer/ClassLoader.php)
#0 /var/www/html/docroot/core/includes/bootstrap.inc(166): _drupal_error_handler_real()
#1 /var/www/html/vendor/composer/ClassLoader.php(576): _drupal_error_handler()
#2 /var/www/html/vendor/composer/ClassLoader.php(576): include('...')
#3 /var/www/html/vendor/composer/ClassLoader.php(427): Composer\Autoload\{closure}()
#4 /var/www/html/vendor/doctrine/lexer/src/Token.php(104): Composer\Autoload\ClassLoader->loadClass()
#5 /var/www/html/docroot/core/lib/Drupal/Component/Annotation/Doctrine/DocParser.php(619): Doctrine\Common\Lexer\Token->offsetGet()
...
Warnings went away after downgrading to doctrine/deprecations 1.1.3.
I encountered the issue https://www.drupal.org/project/drupal/issues/3398734#comment-15876225 π TypeError: Cannot access offset of type string on string in core/modules/views/src/Plugin/views/area/Text.php) Postponed: needs info when visiting /admin/workbench on Workbench 1.6. It might be related to this issue.
I just encountered this issue with Drupal 10.3.10 and Workbench 1.6 and can confirm that the error is resolved after changing the content structure in the relevant configuration to:
content:
value: '<h3>Example</h3>'
format: 'basic_html'
I noticed that the following warning was issued during the configuration import with the structured content:
[warning] Array to string conversion StatementWrapperIterator.php:113
alex.n β changed the visibility of the branch 3198881-dependency-calculation-needs to active.
alex.n β changed the visibility of the branch 3198881-dependency-calculation-needs to hidden.
alex.n β made their first commit to this issueβs fork.
alex.n β created an issue.
Those optons are missing because there are not configurable on form display of the base fields.
I can confirm that drush locale:check deletes module translation files in the translations folder. Subsequently running drush locale:update then leads to the error [error] TypeError: fgets(): Argument #1 ($stream) must be of type resource, bool given in fgets() (line 248 of /var/www/html/docroot/core/lib/Drupal/Component/Gettext/PoStreamReader.php), apparently because a translation file could not be read.
Drupal version : 10.2.7
PHP version : 8.1.27
Drush version : 12.5.3.0
I can confirm this fixes the error [error] array_key_exists(): Argument #2 ($array) must be of type array, null given
when upgrading drupal/ldap 4.7.0 to 4.8.0, thanks!
Thanks for the fixes so far in v4.8, but now in my case an error occurred when upgrading from 4.7 to 4.8 with empty user defined "drupal mappings".
...
- Upgrading drupal/ldap (4.7.0 => 4.8.0): Extracting archive
- Upgrading drupal/ldap_servers (4.7.0 => 4.8.0)
...
Generating autoload files
55 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
----------- ----------- --------------- -------------------------------------
Module Update ID Type Description
----------- ----------- --------------- -------------------------------------
ldap_user 8408 hook_update_n 8408 - Fix account creation setting
spelling and Drupal mappings.
----------- ----------- --------------- -------------------------------------
// Do you wish to run the specified pending updates?: yes.
> [notice] Update started: ldap_user_update_8408
> [error] array_key_exists(): Argument #2 ($array) must be of type array, null given
> [error] Update failed: ldap_user_update_8408
[error] Update aborted by: ldap_user_update_8408
[error] Finished performing updates.
It might also help to warn if now excluded properties are found in ldap_user.settings config.
We faced an issue with ldap 4.7 where the following old (ldap v4.6) field mappings (field-name, field-mail) from ldap_user.settings config where not visible in the UI under /admin/config/people/ldap/user/drupal
Excerpt from ldap_user.settings
ldapUserSyncMappings:
drupal:
field-name:
ldap_attr: '[samaccountname]'
user_attr: '[field.name]'
convert: false
user_tokens: ''
config_module: ldap_user
prov_module: ldap_user
prov_events:
- create_drupal_user
- sync_to_drupal_user
field-mail:
ldap_attr: '[mail]'
user_attr: '[field.mail]'
convert: false
user_tokens: ''
config_module: ldap_user
prov_module: ldap_user
prov_events:
- create_drupal_user
- sync_to_drupal_user
After saving the form under /admin/config/people/ldap/user/drupal these entries field-name, field-mail were removed from ldap_user.settings config and ultimately the mapping for ldap attribute "mail" was missing, because the "mail_attr" was not set in ldap_servers.server.xyz config. For us the fix was to set the mail_attr in the ldap_servers.server.xyz config.