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
Feature request: support for multilingual sites #179
Comments
I've tried setting up multilingual site with drupal & wordpress (latest) with Civi 5.8.2 and gdpr 2.7 - and it seems to work fine w.r.t functionality (not breaking anything). When you say 'does not support' - do you mean mainly translations or see problems with functionality? |
Unless I am missing something, the extension assumes the contacts will only
visit the site in a single language - the text boxes are not translatable,
and there's untranslated hard-coded text so everyone sees the same text and
pdf files regardless of the language they're using the site in. We are
using JS to translate our fields and other text and have created a single
PDF with both the English and French policy info in it as a workaround, but
that means our client can't change/update any of the translations
themselves, they have to rely on a developer.
…On Dec 24, 2018 12:14 PM, "Deepak Srivastava" ***@***.***> wrote:
I've tried setting up multilingual site with drupal & wordpress (latest)
with Civi 5.8.2 and gdpr 2.7 - and it seems to work fine w.r.t
functionality (not breaking anything).
When you say 'does not support' - do you mean mainly translations or see
problems with functionality?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#179 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB923qBi-SlkRxCS_HX5FOxD9795bYQBks5u8QuOgaJpZM4Y0JGw>
.
|
Assuming fixed in recent release. Please re-open if still is an issue (PR welcome). Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The extension current only supports a single language. We are currently checking to see if it would be within out client's budget to contribute to the addition of this feature, which we may be able to help with the development of.
Can you highlight any caveats in the current logic that may make this difficult to implement?
Thanks!
The text was updated successfully, but these errors were encountered: