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.

Translation issues 1.7.2

  1. It would be nice if you guys make sure to put all strings arround the translation functions. The following strings can't be translated in version 1.7.2:

    • Form Basics
    • Form Layout
    • Form Button
    • Restrictions
    • Form Options
    • Update Form Settings
    • Form Title (form_list.php#189)
    • Form Description (form_list.php#194)
    • Create Form (form_list.php#199)
    • Select A Field Type (form_detail.php#287, text domain 'gravityforms' missing)
    • This form doesn't have any fields yet. Follow the steps below to get started. (form_detail.php#283, text domain 'gravityforms' missing)
    • Select A Field Type (text domain 'gravityforms' missing)
    • Start Over There (text domain 'gravityforms' missing)
    • etc.

    There are probably a lot more text that are not wrapped in the __() and _e() functions. Also the 'gravityforms' text domain is missing sometimes. You guys should really add this to an checklist before deploying an new version :-).

    Maybe it's also nice to mention the "Gravity Forms (nl)" translation plugin on the "Translations" page:
    http://www.gravityhelp.com/downloads/translations/
    http://wordpress.org/extend/plugins/gravityforms-nl/

    We also have all the Dutch Gravity Forms translations for in an GlotPress installation:
    http://glotpress.pronamic.nl/projects/gravityforms

    Posted 11 years ago on Friday April 26, 2013 | Permalink
  2. Thanks for the heads up! And yeah, we really should add this to a pre-release checklist. Do you know of a tool that will allow us to more easily spot untranslated strings?

    I'll talk to Carl about getting the Gravity Forms (nl) translation plugin added to the Translations page. :)

    Posted 11 years ago on Friday April 26, 2013 | Permalink
  3. Do you know of a tool that will allow us to more easily spot untranslated strings?

    Unfortunately I don't know any tools for this.

    Posted 11 years ago on Monday April 29, 2013 | Permalink
  4. We've added the Gravity Forms (nl) plugin to the Translations page:

    http://www.gravityhelp.com/downloads/translations/

    I've sent you an email with the latest hotfix version of Gravity Forms which fixes the reported unlocalized strings. :)

    Posted 11 years ago on Wednesday May 1, 2013 | Permalink
  5. Thanks for the fix, this version however isn't working correct for me.

    /wp-admin/admin.php?page=gf_edit_forms = main panel is empty
    /wp-admin/admin.php?page=gf_new_form = main panel is empty

    Is it also possible to replace the following images with an HTML/CSS solution so the texts are easily translatable:

    /wp-content/plugins/gravityforms/images/gf-pagebreak-first.png
    /wp-content/plugins/gravityforms/images/gf-pagebreak-inline.png
    /wp-content/plugins/gravityforms/images/gf-pagebreak-end.png

    Thanks.

    Posted 11 years ago on Saturday May 11, 2013 | Permalink
  6. The issue is solved, we have updated the "Gravity Forms (nl)" translation plugin:
    https://github.com/pronamic/wp-gravityforms-nl/commit/3493fb152a1e9993c716712d9dd6c8a1588cae50

    Posted 11 years ago on Friday May 17, 2013 | Permalink
  7. David Peralty

    Glad to hear it got sorted out.

    Posted 11 years ago on Friday May 17, 2013 | Permalink