TypeError: Cannot access offset of type string on string

I expect PHP is issuing warnings in 7.4. Can you verify that?

Does the site have modifications in terms of patches, custom code, or contributed modules, to the user form?

The steps to reproduce describe a normal process so there must be more steps to reproduce.

While this may seem like none related, I have updated the core drupal 9.5.9
with these tickets and I still cant find the root cause of my errors. They are as follows:

https://www.drupal.org/files/issues/2021-12-27/2991986-16.patch →
/core/lib/Drupal/Core/Field/WidgetBase.php
//modified line 388ish will find comments in file for the location
offset '_original_delta' error

https://www.drupal.org/files/issues/2023-01-25/date-view-filter-core_0.p... →
/core/modules/views/src/Plugin/views/filter/Date.php

https://www.drupal.org/files/issues/2023-03-28/2719553-50.patch →

/core/lib/Drupal/Core/StringTranslation/TranslatableMarkup.php
/core/modules/locale/src/LocaleConfigManager.php

https://www.drupal.org/files/issues/2022-12-24/3328962-5.patch →
core/modules/user/src/AccountForm.php -- user password reset

Drupal 9.5.9
Php 7.4.11

https://example.com/user/register is location and the below shows

InvalidArgumentException: $string ("Create new account") must be a string. in Drupal\Core\StringTranslation\TranslatableMarkup->__construct() (line 133 of /home/jk7exiton6ol/public_html/core/lib/Drupal/Core/StringTranslation/TranslatableMarkup.php)

I appologize if I am going in circles with bug fixes. My Drupal is limited. :)

This i also see an error for all admin pages with
The website encountered an unexpected error. Please try again later. related to the above.

I will keep digging for warnings in the reports

When user is logged in with php 7.1.11

https://example.com/user/34493/edit?check_logged_in=1&pass-reset-token=v...

Warning: Illegal string offset '_original_delta' in Drupal\Core\Field\WidgetBase->extractFormValues() (line 391 of /home/jk7exiton6ol/public_html/core/lib/Drupal/Core/Field/WidgetBase.php)
#0 /home/jk7exiton6ol/public_html/core/includes/bootstrap.inc(347): _drupal_error_handler_real(2, 'Illegal string ...', '/home/jk7exiton...', 391)

however the bug fix for this i have implemented

// https://www.drupal.org/files/issues/2021-12-27/2991986-16.patch →
if (is_array($value)) {
$value['_original_delta'] = $delta;
}
I hope this helps. :)

@cilefen I will test any of the modules for that impact. It has taken a while to figure out the php production environment so i could try to create a drupal core install with the proper php to continue forward but if anyone has ideas on where to look googling has not been as forthcoming for me. :)

It's difficult to understand what is going on here. Can you experiment by layering on patches, etc, on to a clean Drupal install to determine the cause?

Hi @cilefen,

Yes, I agree there is a lot of strange logging making it hard to dissect. This site i believe has been upgraded from drupal 7 -> 8.9 -> 9, on Apache running a legacy-project upgrade and Ive been having issues with since I think 9.3.

I also created a clean legacy 9.5.9 on the server to create a development environment. I copied the database from production. This environment has the same bugs. :(

That being said I am now trying to created a development drupal with 9.5.9 and php 8.1.17 to test which module may be the one interfering with the user.module

I will report back when i get any farther ahead. Thank you!!

Hi cilefen,

I found the problem is with the bootstrap barrio theme upgrade to 5.5.12. I created a subtheme from it previously. I have another version of the site working fine with 5.5.9 so i did incremental upgrades of the theme and found 5.5.12 breaks the login for some reason. I rolled the theme so we can close this issue. At least it has some information in it. :D

Thank you so much for your help advising me. :)

I see the same problem if I combine content moderation and Gin theme. After latest update and using PHP 8.1 I can't save any existing content anymore. Using patch from #9 solves the issue for me.
Using Claro instead of Gin works without any problems
Using Gin without content moderation also works

So, it seems to be the combination.