Support » Plugin: Newsletter » No Translations in Subscription page

  • Resolved henkmat


    I have add and translated all 5 languages of my site for the Subscription pages.
    Each language gets his own form X.
    Example French:
    [newsletter_form form=”4″]
    But on screen I only see the English text in the newsletter_form, rest of the page is correct translated via the page itself.

    Question: How do I get the correct translations workable.
    If possible please give me an example.

Viewing 15 replies - 1 through 15 (of 16 total)
  • I have change the shortcode on Newsletter page into:
    [newsletter form=”4″]
    Now the submit button and email input field are correct.
    But the rest of the translation is still in English.

    I do not get it anymore!

    In Subscription Configuration – Subscription page I declared this:

    <p class="textwhite fontbigger"><b> Inscrivez-vous aujourd'hui.</b></p>
    <p class="textwhite">S'il vous plaît remplir votre adresse e-mail.</p>
    <p class="textwhite">Je peux me désinscrire à tout moment.</p>
    <p class="textwhite">{subscription_form}</p>

    English text and French button. What is the solution. Already the second day finding my way through the plugin. Should be easier.

    Screenshot of Subscribe

    • This reply was modified 3 months, 1 week ago by  henkmat.

    Is there a possibility that you give me a solution.

    Plugin Author Stefano Lissa


    Hi, but are you sing a translation plugin like WPML?
    you are nesting shortcodes [newsletter] and [newsletter_form]. You should use only [newsletter_form] the other one is a general shortcode for messages.


    I use Polylang with the mentioned 5 languages.
    I also use [newsletter form=”1″] and each lang does get the right form number.
    Maybe you can take a look if so then please send me an email then I can send you the credentials for admin.

    Plugin Author Stefano Lissa


    If you use polylang in the admin are you can select a language and change the labels directly in the form fields panel (for each language).


    Yes I know. I did all that. But it does not work. See screenshots I give you before.
    Every form has his own language.

    • This reply was modified 3 months ago by  henkmat.

    Here example what I did.
    4 = french
    [newsletter form=”4″]
    <p class=”textwhite fontbigger”><b>Register today.</b></p>
    <p class=”textwhite”>Please fill-in your emailadress.</p>
    <p class=”textwhite”>I can unsubscribe at any time.</p>
    <p class=”textwhite”>{subscription_form_4}</p>
    custom form:
    <div class=”tnp tnp-subscription”>
    <form method=”post” action=”” onsubmit=”return newsletter_check(this)”>
    <input type=”hidden” name=”nlang” value=”fr”>
    <div class=”tnp-field tnp-field-email”><input class=”tnp-input-field” type=”email” placeholder=”Email” name=”ne” required></div>
    <br />
    <div class=”tnp-field tnp-field-button”><input class=”fusion-button button-flat button-round button-large button-green” id=”button-full-width” type=”submit” value=”Inscription gratuite”>

    • This reply was modified 3 months ago by  henkmat.
    Plugin Author Stefano Lissa


    Hi, it works only if you use the [newsletter_form] tag without the form number. If you set a form number of course the plugin uses your specific code.

    Or there is a bug somewhere with our polylang integration.


    Stefano, you describe literally that I must use [newsletter form=”4″] in the documentation when working with multilanguage. Every lang gets there own form while the form depends of the translated text. It is very confusion now.
    Can you please take a look into my site. I will send you the credentials via your privat mail. Please confirm if this is okay.

    • This reply was modified 3 months ago by  henkmat.
    Plugin Author Stefano Lissa


    Hi, could you lead me to that documentation page? That page is wrong or better, if one have WPML or Plylang we integrated them into the core to translate directly the form labels.

    This is the multilanguage documentation page:


    Doing this way does not give me a solution. The only way that you as dev can interpret my code is by edit it. But if you do not want it to see what I did with the multilanguage then I stay stuck in this issue.
    Hope my customers will understand the dual languages in the forms.

    Plugin Author Stefano Lissa


    Sorry but I’m still not understanding what you did in your blog.

    If you created distinct CUSTOM forms which you recall with [newsletter_form form=”X”] you should see in that page just the code you saved in the forms panel at the text area number X.

    Of course, as said, do not use [newsletter][newsletter_form form=”X”][/newsletter], that is an incorrect syntax.

    When you use custom forms (a custom form MUST contain all the form HTML code with every fields), only that code should be shown. Newsletter does not add other parts. And you should not use on custom form the {subscription_form} tag since it is just a placeholder for the custom form.

    Finally, if you use only the [newsletter_form] shortcode without ANY form number, the standard form is generated. That form is translated using the current frontend language using the translations you provided, for each language, in the form fields configuration panel.

    If that is not happening, or the translations has not been added or the language detection is not working. If you provide a page (address) with a form and where there is the polylang language switcher, we can check it.

    ps: as said there could be bugs with the use of custom forms and a multilanguage site, since the multilanguage support is rather invasive on a plugin code, but checking online could be of help.

    I send you the invitation with creds for the site via satollo mail.

    Plugin Author Stefano Lissa


    Hi, now it’s clear the setup in your blog, and there is a bug. Try to update to version 5.8.8.

    Anyway I wouldn’t use that setup, but in your case it’s better to create a landing page for subscriptions, translatred via polylang and containing where needed only the [newsletter_form] shortcode (not [newsletter form=”x”] as it is now). Then you can create a dedicated page for newsletter where messages are shown (like the welcome message and so on). That last page must contain only the [newsletter] tag and do not need to be translated.

    Let me know if the update solves your problem.

    Thank you, Stefano.

Viewing 15 replies - 1 through 15 (of 16 total)
  • You must be logged in to reply to this topic.