Private Message crash after upgrade to Drupal 11.2.0

Attached is a copy of what was filed in the web site logs (recent entries).

vinodhini.e → made their first commit to this issue’s fork.

Do you have a patch to fix the critical issue while waiting for a module update? I've currently updated Drupal to 10.1, and the module versions 3 and 4 are unusable.

Hi, I encountered this issue identified the cause. I've implemented a fix and provided a merge request. I also tested the fix on a Drupal 11 site, and it's working as expected.

Please review the MR and let me know if any further changes are needed.

Hi, thanks @vinodhini.e for your patch. I tested it on 3.0.7 (for some reason I can't get the "Create private message" to show using version 4 so can't test that version right now) and Drupal 11.2.2 :

Your patch does solve the original crash so you're on to something but unfortunately there is a follow up bug (see: message_bug_after_applying_patch.txt) that seems to be originating from the "message" module. It happens when I actually try sending a private message to a user who has never received one before. There is indeed a similar bug in the "message" module's issue queue which I added as a related issue.
I tried also applying the proposed "message" patch and that results in another error (see:
remaining_bug_after_applying_both_patches.txt).
I tried removing your patch to see if just the message patch would suffice but the original issue came back identical.

I just tested on version 4.0.0-alpha4 (by going directly to /private-message/create?recipient=3) and Drupal 11.2.2.

Again after applying the first patch I get the same error coming from the "message" module.
After applying the linked issue's patch then issues seems to be resolved. I will do more testing and report back.

@vinodhini.e

Thank you. I applied the patch but there are still bugs and the logs are very strange.

I also have errors in the browser console

@zenimagine, please try installing this patch: https://www.drupal.org/project/message/issues/3531949#comment-16168319 🐛 render() of renderer service can only accept array now, passing null lead to final error Needs review

You have the same error "Copie d'écran_20250719_055107-1.png" from the "message" module that I got on "message_bug_after_applying_patch.txt".

Please let us know if you still encounter bugs after these two patches.

@zatox I was unable to apply the patch, I am on version 3.07

@zenimagine, sorry I was unclear.
Please try re-applying the patch but to the "message" module and not "private_message".

This issue needs one patch for each module to resolve I believe.

@zatox Thank you, yes that fixes the problem with the Message module and I no longer have any errors in the logs and the console.

With the 2 wall patch it seems to work normally. But if user we send messages (new contact), they have an access to refuse to conversion, if it was created before the application of the 2 patch .

If I create a view to try to delete the conpromitated conversation

@zenimagine, maybe I've not looked close enough (it's hard to) but I can't see an error in there. It seems to be a .json with views configuration data. If you can spot the error message in there please point it out.
Otherwise maybe you can get an error message from the logs or something?

Also I don't understand quite what the issue here is, especially this part: "they have an access to refuse to conversion".
Could you please expand? Especially on how it relates to private_message and this issue?

@zatox Before the fix:
When a user created a conversation, the message was sent but not received by the recipient.

After the two fixes:
If the user accesses a previously created discussion thread, an access denied message is displayed.

Current solution:
The administrator must manually delete all new discussion threads created during the bug period.

Deletion works correctly with the Olivero theme.
However, in a view using the Admin theme, an error message is displayed (see screenshot).

@zenimagine, I can't see an error in your last screenshot. Please try posting a log of the error from the watchdog or something else, preferably in text form.

Also as a workaround for your issue with thread deletion:
You could make a view with a path outside of /admin ( and restrict the view access to the admin role) so it uses the Olivero theme.
This way you can delete the content without having to fix this view error you are talking about.

If that doesn't work I suggest creating another issue for the edge case you are in.
Seems to me that your issue should be a child issue of this one.
This thread should focus on fixing the bug and making sure it doesn't have side effects, like the one you are experiencing, before people can go to production with it.

I tested the patch in this issue, and that resolved the problem for me, after upgrading to 11.2.

I'm going to take the liberty of marking this issue RTBC, because I think the patch is ready to be merged.