Translating booking widget text with WPML or GTranslate

What you are seeing. On a HomeRunner-powered WordPress site that uses WPML or GTranslate, standard string translation does not cover most of the booking widget text.

Why this happens. HomeRunner’s booking widget, availability calendar, checkout flow, and price-breakdown modal render their text through JavaScript, not through standard WordPress PHP templates. Because of this, WPML’s string scanner and GTranslate’s page-level translation do not reach most of the booking interface text automatically.

What you can do. To fully translate a HomeRunner site, you need a small set of PHP code snippets that:

1. Force WordPress to load the correct locale based on the active language.
2. Pass the locale into the booking widget so it formats dates and labels correctly.
3. Translate calendar day and month labels.
4. Swap the booking widget’s built-in JavaScript string table for your translated strings.
5. Fix asset URLs so translated pages do not break the widget by rewriting the path.

HomeRunner provides a starter snippet package for HomeRunner translation. Adapting these snippets to your specific language combinations or site structure may require additional scoped work.

Still stuck? Contact the HomeRunner team with your site address and what you tried, and we take it from there.