WPML Translation – Complete Settings Tuto

Homepage Forums WP Travel WPML Translation – Complete Settings Tuto

This topic contains 18 replies, has 4 voices, and was last updated by  Support Team 2 weeks, 6 days ago.

Viewing 15 posts - 1 through 15 (of 19 total)
  • Author
    Posts
  • #7593

    alex
    Participant

    Config : WordPress 4.9.7 / WP Travel 1.4.9 / WPML 4.0.5 / WPML Media 2.3.5

    I will update this post according to dev answers

    What are the parameters (don’t translate – copy – copy once – translate) you recommend ?

    For Custom fields translation :
    wp_travel_address
    wp_travel_arrival_date
    wp_travel_booking_count
    wp_travel_booking_status
    wp_travel_country
    wp_travel_departure_date
    wp_travel_email
    wp_travel_enable_multiple_fixed_departue
    wp_travel_enable_pricing_options
    wp_travel_enable_sale
    wp_travel_enable_trip_enquiry_option
    wp_travel_end_date
    wp_travel_enquiry_email
    wp_travel_enquiry_name
    wp_travel_enquiry_query
    wp_travel_faq_question
    wp_travel_featured
    wp_travel_fixed_departure
    wp_travel_fname
    wp_travel_group_size
    wp_travel_itinerary_gallery_ids
    wp_travel_label_processing
    wp_travel_label_submit_enquiry
    wp_travel_lname
    wp_travel_minimum_partial_payout
    wp_travel_minimum_partial_payout_percent
    wp_travel_minimum_partial_payout_use_global
    wp_travel_multiple_trip_dates
    wp_travel_note
    wp_travel_outline
    wp_travel_pax
    wp_travel_payment_id
    wp_travel_payment_mode
    wp_travel_payment_status
    wp_travel_phone
    wp_travel_post_id
    wp_travel_price
    wp_travel_price_per
    wp_travel_pricing_options
    wp_travel_start_date
    wp_travel_tabs
    wp_travel_trip_duration
    wp_travel_trip_duration_night
    wp_travel_trip_enquiry_data
    wp_travel_trip_exclude
    wp_travel_trip_facts
    wp_travel_trip_include
    wp_travel_trip_itinerary_data
    wp_travel_trip_price
    wp_travel_use_global_tabs
    wp_travel_use_global_trip_enquiry_option

    For custom Post Types
    Trips (itineraries) <== Already managed by xml config provided
    Bookings (itinerary-booking) <== I use ‘Not Translatable’
    Enquiries (itinerary-enquiries) <== I use ‘Not Translatable’
    Payments (wp-travel-payment) <== I use ‘Not Translatable’
    Coupons (wp-travel-coupons) <== I use ‘Not Translatable’

    For Taxonomy translation
    Trip Types (itinerary_types) <== I use ‘Translatable’
    Destinations (travel_locations) <== I use ‘Translatable’ (for listings to be in correct language)
    Keywords (travel_keywords) <== Already managed by xml config provided
    Activities (activity) <== I use ‘Translatable’
    I recommend here to use “Set different slugs in different languages” for each taxonomy

    For Tabs Translation
    1. Go in WPML > String Translations > Translate texts in admin screens » (in small at the end and left of the page)
    2. Then Search and expand : wp_travel_settings > global_tab_settings > Each of the tabs you want to translate and select their labels.
    3. Go at the end of the page and clic Apply
    4. Continue to String Translations and Select Domain “admin_texts_wp_travel_settings”
    5. Translate each one

    I hope this could clarify WPML Translation for some users 🙂

    Thank you WEN for your awesome plugin and support !!

    #7594

    alex
    Participant

    About it I have an issue with gallery images / WPML Media translation

    Expected behaviour :
    – Put images in gallery in original language single itinerary
    – Update Translation : Translate Image Name – Save & Close
    – Image used by translated single itinerary will be translated image

    Behaviour I encounter :
    – Put images in gallery in original language single itinerary
    – Update Translation : Translate Image Name – Save & Close <== Only Featured image is present here
    – Image used by translated single itinerary is original image and not translated one both in gallery and cover

    #7605

    Support Team
    Keymaster

    Hello @alex,

    Thank you very much for the tutorial.

    As for the other issues, we will check the plugin with the WPML plugin and come up with the possible fixes.

    Thank you.

    Have a good day 🙂 .

    #7619

    seal
    Participant

    Hello,

    Is WPML now the best solution to translate ?

    Thanks

    #7620

    Support Team
    Keymaster

    Hello @leisureandadventure,

    If you want to make your site Multilingual then WPML is definitely the best choice. Furthermore, the compatibility of WP Travel plugin is also tested with the plugin.

    Additionally, if you just want to translate the available strings in the plugin then you can use Loco translate plugin.

    Link:

    https://wordpress.org/plugins/loco-translate/

    Thank you.

    #7627

    alex
    Participant

    @support

    It’s my pleasure !

    Do you have recommendations for custom fields translation ?
    I think first that fields concerning bookings & enquiries should not be translated, right ?

    And this one a little bit confusing : wp_travel_itinerary_gallery_ids
    If it is storing gallery image ids, then images should be translatable with WPML media translation but not to translate the raw ids, how to do ?

    @leisureandadventure

    WPML is a well known plug-in for managing content on multi-lingual websites, it looks a bit expensive at the beginning but finally much better and/or cheaper than competition.
    Use cases are almost unlimited, documentation is rich, compatibility is wide and support reactive !

    • This reply was modified 1 year, 1 month ago by  alex.
    #7631

    Support Team
    Keymaster

    Hello @alex,

    The custom fields translations for the trips can be done with WPML for all required strings. However, ids/dates and other fields are not be translated in languages.

    Regarding the translation of wp_travel_itinerary_gallery_ids meta option, the meta actually stores the ids of the images in the gallery for the trip and thus does not need to be translated.

    To translate the media files, WPML’s media translation addon can be used, which when translation is complete, loads the correct translation for the currently active language from the same id saved in the gallery ids option.

    If you are still having trouble with the media translations, please let us know the details on the issue and we will check the issues again though, providing you with a fix.

    Best Regards !!

    #16813

    seal
    Participant

    Hello,

    We have used Loco translate to translate the TABS.
    But now only the translated version (french) appear and not the original language (english).
    What do you think ?

    Regards

    #16819

    seal
    Participant

    Hello,

    We have a problem with the Trip type taxonomy translation with WPML.

    All the other taxonomy are perfectly working with translation.

    For the Trip type taxonomy, the synchronisation does not work between the original and the translated version.

    Thanks for your help

    #16845

    Support Team
    Keymaster

    Hello @seal,

    When we tested the issue by translating the taxonomy using the WPML plugin, it was working fine.

    Only those trips(Trips created with the same language as the trip type) that are assigned to the translated trip type is displayed at the archive page.

    https://prnt.sc/o1orbd
    https://prnt.sc/o
    https://prnt.sc/o1oset

    Also as for the tab, since you need to create a separate trip for each different language, you can enter the tab label in as per the language you have created that trip.

    As for the global tab setting, the labels are translation ready so you can translate it in any language you want using the WPML plugin.

    Hope this helps.

    Thank you.

    #16875

    seal
    Participant

    Dear support,

    Thanks a lot for your quick answer and for your great job. We love what you do with WP Travel.

    About the Tip type translation with WPML :

    This screenshot does not work :
    https://prnt.sc/o

    Do you mean that activities and destinations are translatable with synchronisation ?
    But Trip types are not ?

    About the tabs translation :

    For the global tab setting, we have translated the label using the WPML plugin.
    But when we use the website in english we only see the french version.
    And when we use the website in french we see the french version.

    Thanks for your help

    #16913

    Support Team
    Keymaster

    Hello,

    The trip type is also translation ready and can be translated into any language. To be more clear on this, please refer to below-given screen record:

    https://www.loom.com/share/8f6b6a809cd445d48c9be4cf3bc7085f

    As for the tab translation, the translated string will not be displayed in the backend setting but it will be displayed on the frontend. It will reflect the translated string at frontend. So once verify by checking the string in front as well.

    Hope this helps.

    If you have any issues further then kindly let us know.

    Thank you.

    #16914

    seal
    Participant

    Dear Support,

    Thanks for your quick answer.

    Actually we have followed the same operation and after some minutes, WPML lose the synchronisation between the Trip types translations.
    But for all the other taxonomy, it works perfectly.
    What do you think ?

    About tabs, unfortunately, front end, back end and published website show the same language on tabs.

    Have a nice day

    #16942

    Support Team
    Keymaster

    Hello @seal,

    Since we could not figure out what is causing the issue, we need to inspect your specific setting.

    For this, we need your admin login so please send in your credential in the email below:

    wptravel.io[at]gmail.com

    Hoping to hear from you soon.

    Thank you.

    #16987

    wensolutions
    Keymaster

    Hello @seal,

    Thank you for the detail.

    When we inspected your site, we found that you do not have the plugin “WPML String translation” which is must for the translation of the string in the global tab setting.

    Screenshot:

    https://prnt.sc/o3qbwg

    Also, you do not have the latest version of the plugin due to which there is no issue in taxonomy translation like trip type.

    So please make sure the plugins are up to date and have all the necessary plugin.

    Hope this clears the confusion.

    Let us know if you have any confusion further.

    Thank you.

Viewing 15 posts - 1 through 15 (of 19 total)

You must be logged in to reply to this topic.