I am trying to build a multilingual site which also has simplenews. I have the newsletter block on to make end users sign up for the newsletter. I cannot find a way to translate that block.

I can neither

  • turn the block language to "all languages (translatable)", nor
  • can I find the strings through the search interface function nor
  • can I duplicate that block for every language.

I would be grateful for any ideas.

Thanks
Maurice

Related issues, but different since different versions of Drupal and simplenews

Comments

vthirteen’s picture

vthirteen commented

subscribe

gbuyers’s picture

gbuyers commented

Same issue here

vthirteen’s picture

vthirteen commented

solved inserting a simplenews block inside a new translatable or per language block. not the most elegant choice maybe, but it works.

mokko’s picture

mokko commented

Thanks for the workaround, vthirteen! I do not quite understand what you mean,i.e. I don't know how I can create block inside a block. What I am about to do is to create a new block (from scratch) with all languages translatable and simply link from there to the subscription page. This should work.

Eland’s picture

Eland commented

I used the following code snippet to insert default simplenews subscription form into my custom (translatable) block:

$block = module_invoke('simplenews', 'block', 'view', 2);
print $block['content'];

And, of course, we need 'php code' input format to be set for the block.

mokko’s picture

mokko commented

cool! Thanks. I never did this. Now we have two workarounds, but no real solution.

Farreres’s picture

Farreres commented

The way to translate the block title is to go to the newsletter taxonomy and make it localizable. Then refresh taxonomy strings in translation interface for taxonomy. And there you have it.

pauln600’s picture

pauln600 commented
Version: 6.x-1.0-rc6 » 6.x-1.0

I also have this problem, but in a strange way. In the french version (language set by domain switching), the subscribe block only shows up on admin pages - any idea why? The block is configured to appear on every page. I've tried putting the subscribe block inside of a translatable block via module_invoke.... in this case the container block appears, but not the subscribe form.

Paul N.

pauln600’s picture

pauln600 commented

Well, I just fixed this by deleting the newsletter term and re-adding it. Odd...?

Christian Hudon’s picture

Christian Hudon commented

Used block translation

Created 2 newsletters, in my case one in French, the other one in English

It gives me 2 different blocks

In block configuration, I select the correct language in "Multilingual settings"

French pages will then show my subscribe block for the French newsletter and my English pages will show the subscribe block to my English newsletter.

Seems to work fine...

Christian Hudon’s picture

Christian Hudon commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

mikpouet’s picture

mikpouet commented

It wasn't clear for me neither, and I think people missed something explained in the README.txt
I will add, for my experience tweaking around that if you just want the title of your block to be translatable,
you can use 'Localized terms' for the Newsletter Vocabulary.
But if, like me, you want a full block translation, it's just working with the title...
So choose 'Per language terms' for the Newsletter Vocabulary and make your terms by pair (or more if you have more languages) using the Translate tab in your terms list to match them.
By doing this you will have language separated mailing-lists AND BLOCKS, which is not the case with a 'Localize terms' Vocabulary.

Here is the README part about it:

Multilingual taxonomy of 'Localized terms' and 'per language terms' is
supported. 'per language vocabulary' is not supported.
I18n-taxonomy module is required.

Use 'Localized terms' for a multilingual newsletter. Taxonomy terms are
translated and translated newsletters are each taged with the same
(translated) term. Subscribers receive the newsletter in the preferred
language set in their account settings or in the site default language.

Use 'per language terms' for mailing lists each with a different language.
Newsletters of different language each have their own tag and own list of
subscribers.

Path prefixes are added to footer message according to the subscribers
preferred language.

The preferred language of anonymous users is set based on the interface
language of the page they visit for subscription. Anonymous users can NOT
change their preferred language. Users with an account on the site will be
subscribed with the preferred language as set in their account settings.

Thanks for your help.
Mik