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

Question: Proper support of multiple languages #75

Open
DanielSiepmann opened this issue Mar 3, 2021 · 1 comment
Open

Question: Proper support of multiple languages #75

DanielSiepmann opened this issue Mar 3, 2021 · 1 comment
Labels
bug Something isn't working enhancement New feature or request
Milestone

Comments

@DanielSiepmann
Copy link
Contributor

DanielSiepmann commented Mar 3, 2021

We have the following setup:

A default language (German).
A foreign language (English).
We created periods in default language (0).
And we created facilities in both languages (0, 1).

The extension always creates orders in default language (0).

This leads to issues if users create reservations in foreign language (1).
The confirmation and cancel link won't work, as the order can't be found. The Link uses foreign language, but records only exist in default language.

This also leads to always partly default language content in emails. As content partly comes from facility, which also is fetched from default language during argument mapping, as the order is created with default language.

The question:
What's the proper setup to solve the issues? Can this be added to the documentation?

@pascal20997 pascal20997 added the bug Something isn't working label Oct 22, 2021
@pascal20997
Copy link
Contributor

Hey Daniel, currently we haven't tested multilanguage for reserve. This is an issue we need to address and fix but it may take some time.

@pascal20997 pascal20997 added this to the v2.0 milestone Oct 22, 2021
@pascal20997 pascal20997 removed this from the v2.0 milestone Mar 10, 2022
@pascal20997 pascal20997 added the enhancement New feature or request label Jun 9, 2022
@pascal20997 pascal20997 added this to the v3.0 milestone Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants