PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

WPML & GravityForms Paging Steps & button images?

  1. I'm working on a site which is using WPML to localize things into 10 languages.

    GravityForms seems to work very well with WPML in this regard.

    The two areas i'm having issues with are form paging step titles and the pervious, next & submit buttons when images are used instead of text.

    The page fields don't seem to accept the php escape code. is there another way to ensure these are added to a po file?

    Also is there a way to dynamically swap the button images based on the current language?


    Posted 11 years ago on Monday October 15, 2012 | Permalink
  2. The paging step titles as well as the previous & next button are configured on a form by form basis, so this is something that would have to be handled by the WPML plugin (similar with how it changes the other form specific settings). I would suggest you get in touch with them as see if this is something they can help you with. We would be glad to help them if needed.

    Posted 11 years ago on Tuesday October 16, 2012 | Permalink
  3. Hi Alex,

    Thanks for the reply. I understand what you're saying. It almost seems like the paging fields don't have the proper php escape codes around them or something. The actual titles are definitely in the po & mo files.

    Posted 11 years ago on Wednesday October 17, 2012 | Permalink
  4. Sorry for my ignorance, but I am not sure what you mean by "proper php escape codes"

    Posted 11 years ago on Thursday October 18, 2012 | Permalink
  5. sorry for the tardy reply.

    What I mean by "php escape codes" are the gettext string escape tags (e.g. <?php _e('Text to be replaced', 'textdomain');?>).

    Posted 11 years ago on Monday January 21, 2013 | Permalink
  6. I'll forward this on to Alex to make sure we make those strings translatable.

    Posted 11 years ago on Monday January 28, 2013 | Permalink
  7. @donaker, we took a look at the plugin files. All the strings are localized with either the _e() or __() function. The issue is that the strings you want to translate are configurable in the form builder, so they do not appear in the translation file. You manually translate them in the form builder.

    Alex said:

    I think I know what going on. I know that WPML supports the field labels and submit buttons, so they have a way of translating those via their UI, but I suspect they do not support the page names, which is why you can't translate those into multiple languages like you need.

    Posted 11 years ago on Wednesday January 30, 2013 | Permalink