If you are having trouble losing the string translation made using the Loco Translate upon update to the latest WP Travel plugin then this is the post for you.
Actually, what happens is, upon translating the string using the Loco Translate plugin, you will get an option to store the string in the custom location or directly in the wp-content/wp-travel/i18n/languages folder.
If you choose the option to save the .po and .mo file in the location (wp-content/wp-travel/i18n/languages) then upon update to the latest WP Travel version all of the changes that you have made will be lost.
So we suggest you choose the custom location to save the .po and .mo files.
For clear information regarding the query, please have a look at the video we made for you.
https://www.loom.com/share/7e18cf603b3c458085110acf9b7a9338
Conclusion
Check WP Travel documentation to learn more about configurations, modules, payments, and shortcodes.
Your feedback helps us improve. Feel free to share your thoughts!
Need assistance? Contact our support team, join our Facebook community, and subscribe to our YouTube Channel for video tutorials.
You can also find us on Facebook, Instagram, LinkedIn, TikTok, and X. Thank you for choosing WP Travel.
If you are a WP Travel Free user thinking about upgrading to Pro, simply click on the banner below.
WP Travel Editorial is a team of WordPress and travel industry experts dedicated to delivering technical resources, travel business guides, and general travel insights. With over 10 years of experience, the team provides in-depth release notes, feature updates, and informative articles to help tour operators and travel enthusiasts succeed in the evolving travel landscape.
From plugin updates and industry trends to practical travel resources, WP Travel Editorial shares valuable content that supports both the travel industry and avid travelers.
