Tagged: , ,

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • October 11, 2014 at 9:05 am #334212
    Yory

    Hi
    I’ve got about 12 forms created with Avia Layout Builder, one in each portfolio item on English pages.
    When creating these portfolio items in a secondary language they retain their English in Form Title and all field labels.
    Translated .po files are in place for both Enfold and WP and they work properly for all strings, except the ALB forms.
    I also have WPML String Translation but it does not bring up the ALB form strings.
    Is there a way to have the ALB form strings translatable in String translation or in .po?

    Thank you

    October 11, 2014 at 9:42 am #334227
    Yory
    This reply has been marked as private.
    October 11, 2014 at 10:44 am #334257
    Dude

    Hey!

    No, you need to translate the form field captions manually. Click the “Translate independently” button on the editor page, then click on the “Contact Form” element and edit the contact form fields to translate the field captions.

    Regards,
    Peter

    October 11, 2014 at 10:50 am #334264
    Yory

    I see
    why are these stings not translatable via WPML as all other strings are?

    October 12, 2014 at 10:13 am #334468
    Dude

    Hi!

    Because the captions are not hardcoded text strings but shortcode values. The contact form is generated with a shortcode and if the shortcode contains the English captions (because you just duplicated the content from the English page) the po/mo translation will not be used.

    Regards,
    Peter

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.