Problem/Motivation

When the try to access the homepage a page not found error is returned if Portuguese is chosen on Drupal CMS 2.2.3 installation. When installing in english it shows the expected home page.

Steps to reproduce

Install Drupal CMS 2.2.3 with Horizon Aid and Portuguese as default language. Probably the same issue also exists in any other language except english.

Proposed resolution

Remaining tasks

  • ✅ File an issue
  • ➖ Addition/Change/Update/Fix
  • ➖ Testing to ensure no regression
  • ➖ Automated unit testing coverage
  • ➖ Automated functional testing coverage
  • ➖ UX/UI designer responsibilities
  • ➖ Readability
  • ➖ Accessibility
  • ➖ Performance
  • ➖ Security
  • ➖ Developer Documentation
  • ➖ User Guide Documentation
  • ➖ Reviewed by human
  • ➖ Code review by maintainers
  • ➖ Full testing and approval
  • ➖ Credit contributors
  • ➖ Review with the product owner
  • ✅ Release notes snippet
  • ✅ Release

User interface changes

  • N/A

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

  • N/A

Issue fork horizonaid-3629922

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

xpete created an issue. See original summary.

rajab natshah’s picture

rajab natshah
he/him
commented

I see, thanks for reporting.
Adding multilingual support for sure

Only 25 September the Drupal CMS allowed for that in Drupal CMS 2.2.0
Drupal CMS 2.2: Multilingual, out of the box

xpete’s picture

xpete commented

It's the version I'am trying to use since 25 September.

xpete’s picture

xpete commented
Issue summary: View changes
rajab natshah’s picture

rajab natshah
he/him
commented
Title: Home page not found when when language is portuguese » Home page not found when language is portuguese
Assigned: Unassigned » rajab natshah
rajab natshah’s picture

rajab natshah
he/him
commented
Status: Active » Needs work
rajab natshah’s picture

rajab natshah
he/him
commented
Status: Needs work » Active

rajab natshah opened merge request !119

rajab natshah’s picture

rajab natshah
he/him
commented
Status: Active » Needs review

Thanks xpete for the clear report.

Cause: recipe.yml sets page.front: /home, which is an alias, and every default content file pins its path alias to langcode: en. On a non-English install the content importer moves each entity to the site language, but the alias keeps its explicit en, so /home is not found in Portuguese and the front page 404s. Other aliases, and menu links that point at them, are hit the same way.

Fix in MR !119: drop the pinned langcode from the path item in all 177 content files, so each alias follows its entity's language. English installs are unchanged.

Tested locally: YAML lint, an English install and functional bucket 01 pass. On the MR pipeline, YAML lint and the Drupal CMS install job pass, and the functional jobs are still running. Not tested yet: a real Portuguese install from the MR, plus one more language. If you can try the MR on a Portuguese install, that would help.

AI-Generated: Yes

  • rajab natshah committed 8baf9a84 on 1.0.x 
    fix: #3629922 Home page not found when the default language is not...
xpete’s picture

xpete commented

Tested with the dev brunch and it worked. Thanks for the great work!

rajab natshah’s picture

rajab natshah
he/him
commented

Thanks, xpet for reporting
Follow up with this in
#3636515: Home page not found when the default language is not English
#3636516: Home page not found when the default language is not English
#3636517: Home page not found when the default language is not English

rajab natshah’s picture

rajab natshah
he/him
commented
Issue summary: View changes
Status: Needs review » Fixed
Issue tags: +horizonaid-1.0.10

✅ Released in horizonaid 1.0.10

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.