Just ran into another one of the translation-errors mentioned in https://www.drupal.org/project/admin_toolbar/issues/3527462

Problem:

[error] Import of string "Text eingeben, um schnell nach Menü-Links in der Admin-Symbolleiste zu suchen!
" was skipped because of disallowed or malformed HTML.
[error] Import of string "Das Admin-Toolbar-Suchmodul fügt einen benutzerfreundlichen JS-Autocomplete-Filter für die Links im Administrationsmenü hinzu.
Es ist sehr praktisch, um schnell eine Administrationskonfigurationsseite zu finden, ohne zu wissen, wo sich deren Menü-Link im Administrations-Dropdown-Menü oder in der Organisation der Website befinden könnte." was skipped because of disallowed or malformed HTML.

The source of the problem seem to be the new lines on the help page of the submodule admin_toolbar_search

      $output .= '<p>' . t('Type text to quickly search for menu links in the Admin Toolbar!<br/>') . '</p>';
      $output .= '<p>' . t('The Admin Toolbar Search module adds an easy-to-use JS autocomplete filter of the links in the Administration menu.<br/>It is very convenient for finding quickly an administration configuration page without knowing where its menu link could be in the Administration dropdown menu or the organization of the site.') . '</p>';

I guess the fix should be the same as it was in the other ticket: Replace <br/> with <br>

Issue fork admin_toolbar-3566416

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

styx1983 created an issue. See original summary.

styx1983 opened merge request !197

dydave’s picture

dydave commented
Related issues: +#3527462: Import of strings skipped due to malformed HTML tag <br/>

raaaaaa ....
Good catch Adrian (@styx1983)!!! 😅

Not the first time we've got this issue .... I need to pay more attention to this in the future 😅
#3527462: Import of strings skipped due to malformed HTML tag <br/>
When I saw this issue in the tracker, I thought it was created by @ressa 😅
who caught this type of issue for us several times before....

Thanks a lot for the MR, I'll take a closer look a bit later... but it's most likely going to get merged as-is 👌

Adrian (@styx1983), did you check if there were any other problematic strings?
Or is it just these ones?!

Thanks again very much for your help raising this issue and contributing a patch! 🙏

dydave’s picture

dydave commented
Status: Active » Needs review

Forgot to move to Needs review.

Thanks!

styx1983’s picture

styx1983 commented

These were the only ones i could find.

I guess they were added after @ressa made his discoveries in May 2025 :)

hosterholz’s picture

hosterholz
he/him
Primary language German
commented
Status: Needs review » Reviewed & tested by the community

Looks good to me.

  • dydave committed f82ffd65 on 3.x authored by styx1983 
    Issue #3566416 by styx1983: Fixed import of module's translated strings...
dydave’s picture

dydave commented
Status: Reviewed & tested by the community » Fixed

Thanks everyone for the great help and feedback!

After getting your positive confirmation and doing a quick round of testing manually, I went ahead and merged the changes above at #7.
All tests and jobs on the 3.x branch still seem to be passing 🟢

This should hopefully get released with the next patch release for the 3.6.x branch.

Marking issue as Fixed, for now.

Thanks again!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.