{"id":949,"date":"2025-03-24T14:28:06","date_gmt":"2025-03-24T14:28:06","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/how-to-translate-custom-fields-with-wpml\/"},"modified":"2025-04-03T15:24:27","modified_gmt":"2025-04-03T14:24:27","slug":"how-to-translate-custom-fields-with-wpml","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/translations\/how-to-translate-custom-fields-with-wpml\/","title":{"rendered":"How to Translate Custom Fields with WPML"},"content":{"rendered":"\n

If your site is in more than one language, you can use the WPML<\/a> plugin to manage translations and translated content. The instructions below may vary slightly with different versions of WPML. The String Translation<\/em> module is only available in the Multilingual CMS<\/em> version of the plugin.<\/p>\n\n\n\n

Translating Custom Fields using WPML’s String Translation module<\/h2>\n\n\n\n
\n

The String Translation module is only available in the WPML Multilingual CMS version<\/a><\/p>\n<\/section>\n\n\n\n

    \n
  1. Make sure you have selected to use\u00a0String Translation, use one of the two options:
    \"\"<\/figure><\/li>\n\n\n\n
  2. Create your custom field, and enter description, front end title etc. For this example we are creating a text field:
    \"\"<\/figure><\/li>\n\n\n\n
  3. Then go to\u00a0GeoDirectory > Status > Tools > DB text translation:
    \"\"<\/figure>
    <\/li>\n\n\n\n
  4. This will scan the database for custom fields and copy them to a file in your\u00a0geodirectory\u00a0plugin folder called\u00a0db-language.php<\/em><\/li>\n\n\n\n
  5. WPML\u00a0will now be able to scan this file and allow you to translate the custom fields. Go to\u00a0WPML > Theme and plugins localization > Strings in the plugins > GeoDirectory > Scan selected plugins for strings
    \"\"<\/figure>
    <\/li>\n\n\n\n
  6. To translate them go to\u00a0WPML > String Translation, where you will see the new fields added:
    \"\"<\/figure>
    <\/li>\n\n\n\n
  7. Now you can translate them and save:
    \"\"<\/figure>
    <\/li>\n\n\n\n
  8. This would be the result on the Add Listing page:\u00a0French
    \"\"<\/figure><\/em>English
    \"\"<\/figure><\/em>Dutch
    \"\"<\/figure><\/em><\/li>\n<\/ol>\n\n\n\n

    Translating Custom Fields without WPML’s String Translation module<\/em><\/h2>\n\n\n\n
      \n
    1. If you are only using the WPML Multilingual blog<\/a> plugin, then first follow steps 2\u00a0and 3\u00a0as explained above.<\/li>\n\n\n\n
    2. That will create a file called\u00a0db-language.php<\/em>\u00a0that you will find in your\u00a0geodirectory<\/em>\u00a0folder on the server.<\/li>\n\n\n\n
    3. Copy all files in the\u00a0geodirectory<\/em>\u00a0folder to\u00a0your computer:
      \"\"<\/figure>
      <\/li>\n\n\n\n
    4. Open the\u00a0\/wp-content\/plugins\/geodirectory\/geodirectory-languages\/geodirectory-en_US.po\u00a0file with poEdit<\/a>:\u00a0
      \"\"<\/figure>
      <\/li>\n\n\n\n
    5. From the\u00a0catalogue\u00a0menu, choose\u00a0Update from sources …:\u00a0
      \"\"<\/figure><\/li>\n\n\n\n
    6. That will re-build the\u00a0geodirectory-en_US.po\u00a0file:
      \"\"<\/figure><\/li>\n\n\n\n
    7. Save the file.<\/li>\n\n\n\n
    8. You now have a new base language file including the new custom fields. You can now use that file to create your other language files, read more at How To Translate Or Localize GeoDirectory<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

      If your site is in more than one language, you can use the WPML plugin to manage translations and translated content. The instructions below may vary slightly with different versions of WPML. The String Translation module is only available in the Multilingual CMS version of the plugin. Translating Custom Fields using WPML’s String Translation module The String Translation module is only […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[627,811,812],"article\/categories":[211,432,434],"class_list":["post-949","gd_place","type-gd_place","status-publish","hentry","gd_place_tags-wpml","gd_place_tags-wpml-fields","gd_place_tags-wpml-custom-fields","gd_placecategory-tips-tricks-more","gd_placecategory-how-tos","gd_placecategory-translations"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/949","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/types\/gd_place"}],"author":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/comments?post=949"}],"version-history":[{"count":0,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/949\/revisions"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=949"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=949"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=949"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}