Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for issue dev/#5037: Standalone install in another language #29522

Conversation

jaapjansma
Copy link
Contributor

Overview

Fixes an issue in the installer user interface (for standalone) after selecting a different language.

Before

When installing CiviCRM Standalone through the user interface and one selects a different language an fatal error did appear.

After

When installing CiviCRM Standalone through the user interface and one selects a different language the setup continues and CiviCRM is installed in the selected language.

Technical Details

The issue was caused by not propagating the correct cms.root path.

Comments

Good to know is that the installer downloads the translation files after selected the right language. So no need to download those before installing.
After this PR is merged the installation documentation for standalone in a different language needs an update.

See https://lab.civicrm.org/dev/core/-/issues/5037

Copy link

civibot bot commented Feb 27, 2024

🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷

Introduction for new contributors...
  • If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
  • A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
  • A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
  • If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
  • Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
  • A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
  • To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
  • For more information about contributing, see CONTRIBUTING.md.
Quick links for reviewers...

➡️ Online demo of this PR 🔗

@civibot civibot bot added the master label Feb 27, 2024
@seamuslee001
Copy link
Contributor

@artfulrobot @ufundo does this work for you folks

@artfulrobot
Copy link
Contributor

I found it hard to test this because standalone won't install through the browser until #29352 is merged. But applying this patch together with that patch, I was able to see it working!

One note that I found a bit confusing: here's the process:

  1. visit installer page, it's in English
  2. select a different language from the drop down. The page immediately reloads. If the language files are installed, the page will be in the selected language, but otherwise it's still in English.
  3. Complete install form.
  4. Success message is in selected language.
  5. If you delete the db and settings file and access the installer again, then at step (2) you'll see the language because it was downloaded in step 3.

@artfulrobot artfulrobot merged commit c5ae181 into civicrm:master Mar 6, 2024
3 checks passed
@artfulrobot
Copy link
Contributor

Thanks @jaapjansma

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants