Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The confirmation message and the submit button of the subscribe block is not translateable.
Comment | File | Size | Author |
---|
Issue fork mailchimp-2932189
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:
Comments
Comment #2
ytsurkComment #3
AnybodyWell I think it would be cleaner to solve this via configuration translation, but the patch can be seen as hotfix....
Comment #4
samuel.mortenson@Anybody I agree - some values that come directly from Mailchimp may need wrapped in
t()
, but values from config entities should be translatable. What do we need to do to enable that in the module?Comment #5
ytsurkIt needs a correct configuration schema, according to https://www.drupal.org/docs/8/multilingual/translating-configuration, i have not reviewed the one in this module so far.
This then probably will need an update hook for existing installations ... so good testing is needed
Comment #6
mvonfrie CreditAttribution: mvonfrie commentedThere are some other UI texts which need to be translated, e. g. the #2968016: Add GDPR checkbox for opt-in consent consent message. Please make all texts translatable!
We are using this module in a site which currently is translated to English, German and Czech will follow within the next months. As many of the users of that site don't speak English we need to translate everything. Thanks.
Comment #7
joco_sp CreditAttribution: joco_sp commentedI changed the category to Bug report, becasue if you have a multilingual site you can't translate those strings.
I updated the patch, so it should work with the latest dev version of the module. I also found two descriptions on the form without the translation possibilities.
Comment #8
joco_sp CreditAttribution: joco_sp commentedThe patch for the 8.1.11 version is here - https://www.drupal.org/project/mailchimp/issues/3145660#comment-13663886
Comment #9
drupal.ninja03 CreditAttribution: drupal.ninja03 at TA Digital commentedI have added more changes for the deprecated t() calls.
Comment #10
gcbComment #11
gcbComment #12
Shashwat Purav CreditAttribution: Shashwat Purav at Portage CyberTech for Drupal Association commentedThe patch in #9 failed to apply to 8.x-1.x branch.
Comment #13
anoopsingh92Hi
Anyone is working on this issue? Because I am not seeing any activity from the last 3 months on that issue. If someone is not working then I request you to please realize it and change it to unassigned.
Thank You
Comment #14
anoopsingh92Hello @spncr,
I want to review the provided patches. If I will get any issues with the patches or other things then I will try to provide a clean patch for this.
Thanks
Comment #15
gcbHey @anoopsingh92. @spncr isn't working on this project anymore. I've unassigned this ticket. Any feedback or testing results you have would be welcome.
Comment #16
anoopsingh92Hi @gcb,
Thank you so much for thae change assign value as unassigned. Now i will check this ticket if i will get any issue on this then i will try to fix and give my feedback on this.
I am working on it.
Thanks
Comment #17
anoopsingh92Hello,
Please review this patch. I didn't change related to the Coding standards in this patch.
Thanks
Comment #18
xenophyle CreditAttribution: xenophyle commentedIt looks like the changes from the latest patch exist in the current 2.x dev branch. Does anything else need to be done to close this issue?
Comment #19
MegaChriz CreditAttribution: MegaChriz at WebCoo commentedI see that indeed everything in #17 is addressed.
I do however see in the code base that there is more usage of literal strings where I think that translated strings should be used. You could search in the code base for:
'#title' => '
'#title' => "
Note: on '#description' I did not find anything that should be changed.
Would it be good to address '#title' strings translations here, or is that out of scope?
Comment #20
xenophyle CreditAttribution: xenophyle commented@MegaChriz Might as well make translatable strings a new issue.