May 31, 2018 at 4:37 pm #6951
I translated the plugin in the desired language but still, there are many strings that I couldn’t find.
How can I translate everything in the WP Travel Checkout page? (Billing info, Booking options, Payment Mode etc)
Thank you.June 1, 2018 at 4:41 am #6953
All the static strings in WP Travel plugin are translation ready and can be translated to your desired language using translation plugins.
Regarding the strings on the checkout page also, the “Billing Info” text and other texts are translation ready while we have tested the translation.
If you are having trouble with the translation, please provide us details on the translation plugin you are using, explaining the issue further, so that we can look into it further and provide you with some precise fix.
Best Regards !!June 1, 2018 at 2:21 pm #6978
Unfortunately I couldn’t find the strings I mentioned in the wp-travel.pot file, as them didn’t exist.June 2, 2018 at 4:58 pm #6981
WP Travel AdminKeymaster
The string you tried to translate is already made translation in the theme as you can see in below given screenshot:
As the strings are already translation ready, you can translate it using the plugin like loco translate.
If you find any confusion while translating the string using the plugin then please write back to us.
Regards!!November 19, 2019 at 1:08 pm #21405
Hello WP Travel Team,
the fuktionality of your plugin in total is thoughtful tuned.
It works very good in English, but it’s quite complicated to translate the travel card, travel checkout page and all following customer interaction in other languages.
Could you help to find a solution?
At the moment I’m using Loco Translate, Polylang and Elementor. Tried a few other plugins.
Also on your recomended “Tourable” theme with a clean index data the travel card is shown in English even if you choose an other site at the settings.
Thank you in advance!November 20, 2019 at 4:34 am #21418
Thank you very much for your appreciation.
Regarding your query, can you please mention the string that you are having trouble in translating in the cart page and checkout page so that we can help you further. As for the string translation, you can use Loco Translate plugin.
As for making the multilingual site, our plugin recommends using WPML plugin.
Hope this clears the confusion.
If you have any issues further then kindly let us know.
Thank youNovember 20, 2019 at 1:36 pm #21440
Thank you a lot for the reply.
its not a specific string. You can switch the language with polylang and all the sites after WP Travel Card are displayed in the right language what seems to be the right step but if you try to book the trip out of an other language it switches to the last chosen language for WP Travel Card.
Also creating a new translation of WP Travel Card for example with pasting the short code does not work.
The side cant be found or the english version gets loaded.
So I understand there is no option to go with a free plug in like polylang and loco for translation?
An other question:
Do you have any seat counter after booking option so dates dont get over booked or is it only possible to change the reservation volume manually? Also: Do you leave the price per year for your plug in or does it cost 250.99$ next year?
NikitaNovember 21, 2019 at 5:54 am #21455
As for the cart page issue, the issue is noted as the known issue and we are working on it.
We will let you know as soon the issue is fixed and the update is released.
As for the counting feature, yes we do have the inventory option which counts the no of available seats and will deduct the seat once the seat is booked.
for this you need to either use WP Travel Utilities plugin or WP Travel Pro plugin. As for the price, we have not yet decided about the price increase for till then the price will be same for the plugin.
Hope this clears the confusion.
Thank you.November 28, 2019 at 9:12 pm #21647
Hi there Im trying to translate the “view Group discount” text, but i could find it.Im using the Loco translate pluginNovember 29, 2019 at 5:48 am #21653
You must be logged in to reply to this topic.