Problem/Motivation

After installing Drupal 8 (beta-15) and choosing to automatically install it in another language (Swedish), the message "One translation string was skipped because of disallowed or malformed HTML. See the log for details." is presented to the user.

According to the "User Interface Translation" the message should have a link to the log, but the translated message doesn't print the link.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

AdamEvertsson created an issue. See original summary.

AdamEvertsson’s picture

Apparently this was reported in 2013 and the issue #2062103: Skipped translation import shows dblog link message that is not yet available in installer was closed in January 2015.

I experienced the problem in Drupal 8-beta 15 on my MacBook Pro, using MAMP to host the site. PHP 5.5.10.

(Sorry for posting a duplicate, I did search for an issue of the problem I experienced, only to find it after I posted this issue.)

unstatu’s picture

nachosalvador and I are working on it in the DrupalConEur mentored sprint.

unstatu’s picture

We were able to reproduce the bug. The steps to do it are the following:

  1. To install Drupal in a non-English language (we have reproduced it using Spanish (Español) and Sweeden (Svenska)
  2. In the configuration step (once the Drupal is installed, but before leaving the installer) the wrong message will be displayed.
unstatu’s picture

The problem was that during the installation the logs are not available yet and there wasn't any specific message to show during the installation.

So, the solution that we took is to show an specific message when installing.

unstatu’s picture

Status: Active » Needs review
nachosalvador’s picture

I did pair programming with unstatu in DrupalCon 2015 Barcelona to create the #5 patch

Status: Needs review » Needs work

The last submitted patch, 5: drupal-malformed-html-2567671-5.patch, failed testing.

marysalento’s picture

Status: Needs work » Needs review
FileSize
196.57 KB

The path work for me, but the path is not working in the test. We need defined the constant MAINTENANCE_MODE in the test

marysalento’s picture

@elchiconube and I defined the constant MAINTENANCE_MODE in two files (core/modules/locale/src/Tests/LocaleImportFunctionalTest.php and core/modules/locale/src/Tests/LocaleUpdateTest.php) because it's necesary to pass the test.
I added also the patch of @unstatu and @nachosalvador

marysalento’s picture

Status: Needs review » Needs work

The last submitted patch, 10: drupal-malformed-html-2567671-10.patch, failed testing.

The last submitted patch, 5: drupal-malformed-html-2567671-5.patch, failed testing.

nachosalvador’s picture

Fixed MAINTENANCE_MODE definition

The last submitted patch, 10: drupal-malformed-html-2567671-10.patch, failed testing.

unstatu’s picture

The tests were failing because the constant MAINTENANCE_MODE were not defined.

So, finally we have used drupal_installation_attempted() to check if Drupal is being installed.

nachosalvador’s picture

Status: Needs work » Reviewed & tested by the community

Works fine and the tests passed.

The last submitted patch, 14: drupal-malformed-html-2567671-14.patch, failed testing.

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 16: drupal-malformed-html-2567671-15.patch, failed testing.

The last submitted patch, 14: drupal-malformed-html-2567671-14.patch, failed testing.

unstatu’s picture

Version: 8.0.0-beta15 » 8.0.x-dev

Changed to 8.0.x-dev because the problem still there.

Status: Needs work » Needs review
Sutharsan’s picture

Status: Needs review » Needs work
Issue tags: +Needs tests

Thanks for the patch, well done and a deserved green test result after 1+ day work. I checked the patch and confirm that the original translated string is not changed. Only new strings added.

Back to 'needs work' to add a test. Added the tag 'Needs tests' too.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

larowlan’s picture

Adding some tags

Removing needs tests because I don't think we need them here, testing will be arduous

karishmaamin’s picture

Re-rolled patch against 9.5.x. Please review

needs-review-queue-bot’s picture

Status: Needs review » Needs work
FileSize
1.16 KB

The Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

karishmaamin’s picture

Sorry, there was Custom command failure #37. Here is the patch fixing that

Aadhar_Gupta’s picture

Status: Needs work » Needs review
FileSize
2.57 KB
590 bytes

Adding Reroll for Drupal 10

Aadhar_Gupta’s picture

I applied the #39 patch on my local and it got applied but somehow I missed that part and applied php-cs and php-cbf there was a minor change so I created an interdiff and uploaded the patch so this patch can be considered as improved code quality.

Ranjit1032002’s picture

Status: Needs review » Reviewed & tested by the community

I had Reviewed the patch and it's working as expected mentioned in comment #40

larowlan’s picture

Status: Reviewed & tested by the community » Needs work
+++ b/core/modules/locale/locale.bulk.inc
@@ -467,7 +473,7 @@ function locale_translate_file_attach_properties($file, array $options = []) {
-  // {project}-{version}.{langcode}.po, {prefix}.{langcode}.po or {langcode}.po
+  // {project}-{version}.{langcode}.po, {prefix}.{langcode}.po or {langcode}.po.

This change is out of scope

jungle’s picture

Version: 9.5.x-dev » 10.1.x-dev
Status: Needs work » Reviewed & tested by the community
Issue tags: -Needs reroll
FileSize
2.08 KB
708 bytes

Addressing #43. RTBC, unless the CI rejects. The current dev branch is 10.1.x

larowlan’s picture

Status: Reviewed & tested by the community » Needs work
Issue tags: +Needs issue summary update

Can we trace down when the URL param was removed? The original issue summary says there was originally a link but it wasn't in the string.

i.e. I think the original issue has been resolved and I'm not sure we're gaining much with the current patch.

It looks to me like the original issue was fixed in #2062103: Skipped translation import shows dblog link message that is not yet available in installer - so either we need an issue summary update with the new intent or we can close this as duplicate.

Please advise.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.