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.
Spent 40 minutes on reading discussions about difficulties with translating Mailchimp fields, but yet it doesn't work on Drupal 8.
Well, I also checked out all README files in the module(s) distribution and found absolutely no information about translating, localization or something.
We have a bilingual website: English and Italian. We don't use some i18n module - just core things. And I don't see any possibilities to translate those fields - neither on Form translation nor in User interface translation.
Using 1.3.0 version
Drupal 8.3.7
Comment | File | Size | Author |
---|---|---|---|
#4 | 2903123-4_signupblock-formlabel-translation.patch | 534 bytes | ytsurk |
#3 | 2903123-3_signupblock-formlabel-translation.patch | 531 bytes | ytsurk |
Comments
Comment #2
OnkelTem CreditAttribution: OnkelTem commentedComment #3
ytsurkThe issue #2667782: How do I translate the subscription block? popped up again.
I don't know what's the purpose of the
is_string
check, but it makes no sense to translate an @-var ...Comment #4
ytsurkSorry .. the patch was wrong ..
Comment #6
ruscoe CreditAttribution: ruscoe at ThinkShout for Mailchimp commentedInteresting.
t('@mergevar', array('@mergevar' => $mergevar->name))
has been in the code for years and I suspect it was intended to force$mergevar->name
to always be a string.However, I can't think of a situation where
$mergevar->name
would be anything other than a string or an empty value (unlikely) and your patch will handle both those situations perfectly well.Committed. Thanks!