Incorrect translatable string in FileTransferAuthorizeForm

Hi @chi
Yes translatable strings doesn't allow html tags inside, I provided patch for this if any changes require i will work.

I suggest we quote the message with double quotes and use %message placeholder to highlight the received message.

Tried to address pointer in #4.

provided patch changes suggest in #4 comment patch #5 does not highlight the "Message" in double quotes.

Hi, I tried to reproduce the error by importing a .po file but got no error.
How can I test the issue and the fix?

@stephencamilo Check out if you po file has the following string

msgid ""
"Failed to connect to the server. The server reports the following "
"message: <p class=\"error\">@message</p> For more help adding or "
"updating code on your server, see the <a "
"href=\":handbook_url\">handbook</a>."

@chi Yes there is.

audrey.brockhaus → made their first commit to this issue’s fork.

I am working on this issue at Drupalcon Atlanta 2025 with the help of Randy Fay

I added the Needs issue summary update because it would be nice to have a clear problem/motivation and proposed resolution section on the issue.

I have been talking with Audrey and Robb about this bug, and the only reason we could think of to merge the MR is that there may be some project out there that is using this form.

I reviewed the issue summary and it is correct.

Reviewed the fix at DrupalCon Atlanta. Looks good!

Thank you everyone for reviewing the code. I was talking with Gábor who knows a bit more about multilingual and translatable strings. He pointed out that the paragraph tag is allowed in translatable strings. He went to locale.drupal.org to search for use of <p in translatable strings.

So this may not be as straight-forward as we thought.

I am going to add the Needs issue summary update and Needs steps to reproduce tags and set this to Needs work as there is something else that is causing the error.

I talked with Jason and postponing the issue seems like a good idea after updating the issue summary about why this is postponed / should be closed eventually.

https://localize.drupal.org/translate/languages/uk/translate?project=dru... is places where a p tag is used in core.

https://api.drupal.org/api/drupal/core%21modules%21locale%21locale.modul... shows the p tag is allowed in core. So I don't think this is about the p tag?

Thanks for working on this. However, since it's entirely dead code at this point, and there's no explanation for what the actual problem is, I'm going to mark this "won't fix". I hate to see anyone spending more time on a dying / dead system.