Not translating dynamically generated content

  • Resolved mattcass

    (@mattcass)


    2 years, 6 months ago

    Hi, great plugin! It’s working perfectly except I’m noticing that a few pieces of text aren’t translating:

    1. content set via CSS using :before – like this:

    .slick-dots-container .slick-dots:before { content: “No matter your preference, Upper E Apartments has a floor plan designed for you, offering studio, 1- and 2-bedroom layouts. You are destined to find your perfect space here at Upper E Apartments in Dallas, TX.”; }

    We use this method to overwrite the default slick slider text. This is visible at https://wordpress-693319-3949868.cloudwaysapps.com/ – first translate to Spanish (top right of page) then scroll down 25% to see the text that doesn’t translate.

    2. Gravity Form field value text set via $field_values – like this:

    $prefill = “Please send me more information about ” . get_the_title() . ” Apartments at Upper E.\n”;
    echo gravity_form(‘Contact Us’, 0, 0, 0, array(‘comments’ => $prefill), 1);

    We use the gravity_form function to output our form, and prefill the textarea field using a custom text string. This is visible at https://wordpress-693319-3949868.cloudwaysapps.com/our-communities/athenian/ – first translate to Spanish (top right of page) then scroll down to the form to see the field text that doesn’t translate.

    (More info on gravity_form function at https://docs.gravityforms.com/adding-a-form-to-the-theme-file/#function-call)

    Thanks for your help in trying to solve these!

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author edo888

    (@edo888)

    2 years, 6 months ago

    Hi,

    1. That is correct, we do not translate CSS content, however you can add more CSS code to specify translations for different languages use something like this instead:

    
.slick-dots-container .slick-dots:before {content:"English goes here";}
html[lang="es"] .slick-dots-container .slick-dots:before {content:"Spanish goes here"!important;}
html[lang="it"] .slick-dots-container .slick-dots:before {content:"Italian goes here"!important;}
...

    2. Correct, we skip the translations of textarea input content. For your specific case you can possibly add a hidden field with some unique information to identify which property is the contact about and remove the textarea field completely or rename it to Additional comments (optional).

    Thanks! 🙂

    • This reply was modified 2 years, 6 months ago by edo888.
Viewing 1 replies (of 1 total)

The topic ‘Not translating dynamically generated content’ is closed to new replies.

Tags