{"id":14939,"date":"2015-04-03T17:39:26","date_gmt":"2015-04-03T17:39:26","guid":{"rendered":"https:\/\/docs.wpgeodirectory.com\/?p=14939"},"modified":"2019-01-02T09:06:34","modified_gmt":"2019-01-02T09:06:34","slug":"translating-custom-fields","status":"publish","type":"post","link":"https:\/\/wpgeodirectory.com\/docs\/translating-custom-fields\/","title":{"rendered":"Translating Custom Fields"},"content":{"rendered":"

Introduction<\/h3>\n

If your site is only in one language, you create your custom fields in the language used on your site.<\/p>\n

But if your site is in more than one language, you will need to use WPML<\/a>. The instructions below are different depending on the version of WPML you use. The String Translation<\/strong><\/em> module is only available in the\u00a0Multilingual CMS<\/strong><\/em> version of the plugin.<\/p>\n

Translating Custom Fields using WPML’s String Translation module<\/h3>\n
    \n
  1. Make sure you have selected to use String Translation, use one of the two options:
    \n\"\"<\/li>\n
  2. Create your custom field, and enter description, front end title etc. For this example we are creating a text field:
    \n\"\"<\/li>\n
  3. Then go to GD > Tools >\u00a0Load custom fields translation<\/strong><\/em>:
    \n\"\"<\/li>\n
  4. This will scan your DB for custom fields and copy them to a file in your geodirectory plugin folder called\u00a0db-language.php<\/strong><\/em><\/li>\n
  5. WPML will then be able to scan this file and allow you to translate them.<\/li>\n
  6. To translate them go to WPML > String Translatio<\/strong><\/em>n, where you will see the new fields added:
    \n\"\"<\/li>\n
  7. Now you can translate them and save:
    \n\"\"<\/li>\n
  8. This would be the result on the Add Listing page:
    \nFrench<\/strong><\/em>
    \n\"\"
    \nEnglish<\/strong><\/em>
    \n\"\"
    \nDutch<\/strong><\/em>
    \n\"\"<\/li>\n<\/ol>\n

    <\/a>Translating Custom Fields without WPML’s\u00a0String Translation module<\/h3>\n
      \n
    1. If you are only using the\u00a0WPML blog version<\/a>, then first follow steps 2\u00a0and 3\u00a0as explained above.<\/li>\n
    2. That will create a file called\u00a0db-language.php<\/strong><\/em>\u00a0that you will find in your geodirectory<\/strong><\/em> folder on the server.<\/li>\n
    3. Copy that file and your GD core language file<\/a> to\u00a0your computer and then open the .po file and rescan<\/strong><\/em> the project.<\/li>\n
    4. This will add the translations to the .po file and you can then follow the normal translation process as explained here<\/a>.<\/li>\n
    5. Below you can learn more about the process for merging the custom field data with the normal language files.<\/li>\n<\/ol>\n

      Instructions<\/h4>\n
        \n
      1. After you scanned the database for custom fields, download a copy of the GD core plugin from your server to your local computer using FTP:
        \n\"\"<\/li>\n
      2. Then open \/wp-content\/plugins\/geodirectory\/geodirectory-languages\/geodirectory-en_US.po<\/strong><\/em> using PoEdit:
        \n\"\"<\/li>\n
      3. From the catalogue<\/strong><\/em> menu, choose Update from sources ..<\/strong>.<\/strong><\/em>:
        \n\"\"<\/li>\n
      4. That will merge db-language.php:
        \n\"\"<\/li>\n
      5. Save the file and then follow the instructions for translating your core language file [first time translation]<\/a> or updating your language file [if already translated earlier]<\/a>.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

        Introduction If your site is only in one language, you create your custom fields in the language used on your site. But if your site is in more than one language, you will need to use WPML. The instructions below are different depending on the version of WPML you use. The String Translation module is … <\/p>\n

        Continue reading “Translating Custom Fields”<\/span><\/a><\/p>\n","protected":false},"author":1670,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[13],"tags":[],"amp_validity":null,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/posts\/14939"}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/users\/1670"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/comments?post=14939"}],"version-history":[{"count":0,"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/posts\/14939\/revisions"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/media?parent=14939"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/categories?post=14939"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/tags?post=14939"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}