Multilingual and Hotel Booking

Viewing 14 posts - 31 through 44 (of 44 total)
  • Author
    Posts
  • #1507579

    Ciao! Ho seguito il tuo consiglio e torna tutto. Grandissimo!!! L’unica cosa che non va è il calendario nella seconda lingua che non fa selezionare i giorni per le prenotazioni. Come hai risolto?

    #1507601

    Risolto

    #1510072

    Thanks for sorting this out.

    #1519067

    I made the mistake of buying the plugin without checking if it worked with polylang. I’m not willing to pay 100 USD extra every year for WPML to make it work.

    Please add polylang support ASAP, it can’t be that hard.

    #1520037

    Hi Kathrine, thanks for your feedback. You may also check this plugin, however, we have not tested it yet.

    #1556337

    Hi,

    I’m having the same issue like the OP while using three languages, WPML is expensive, and Polylang doesn’t offer the options to translate the [mphb_checkout] page, the [mphb_search_results] page and the header with call to action buttons. Any other way to manually translate it?

    #1559712

    Hi Josip,
    Unfortunately, WPML is the only multilingual plugin that has been tested so far. You can check the plugin from the previous comment but we did not test it either.

    #1628460
    This reply has been marked as private.
    #1628891

    Hi Patrick, The Polylang is not compatible with the Hotel Booking plugin yet.

    #1655463

    Ciao, ho lo stesso problema. Come lo hai risolto?

    #1655600

    Ho seguito le istruzioni di FABRIZIO BARTOLINI

    #1676629

    Hi,

    I would also be glad to use Polylang with your plugins.

    Regards,
    Luca

    #1676728

    Thank you for your feedback.

    #1763483

    Still no roadmap — five years later.

    Honestly, it’s getting hard to understand why something so basic and widely requested — Polylang support for Hotel Booking — still hasn’t made it onto the roadmap.

    • Feb 2020 – First request.
    • 2020–2024 – A dozen+ users echo the need. All we get is “thanks for the upvote.”
    • June 2023 – A workaround appears (getPageId + pll_get_post), but it breaks constantly.
    • Oct 2024 – Still “we’re collecting feedback.”
    • May 2025 – No beta, no ETA, no public issue. Just silence.

    Why it matters:<BR>
    This isn’t just about UX polish — it affects trust, conversion, and retention. And right now, silence speaks louder than any missing feature.

    • Churn risk: Lack of a translation support that does not require a *yearly* payment of XX$ for less than 10pages to be translated is now the main reason of this thread. A one-time translation payment is needed. Or caps for eg: 10000 words pay as you go
    • Market mismatch: WPML is great, but too pricey (and yearly) for small B&Bs. Supporting Polylang means wider reach.
    • Hidden costs: Every workaround (that then crash) support ticket costs time that could go into building this right.

    Bottom line: Until we see a dated roadmap, the message is “multilingual isn’t a priority.” That erodes trust — fast.<BR><BR>

    Suggestion: Publish a short <LINK>video tutorial</LINK> and blog post like “Localise Hotel Booking with free tools in 2025”. It’s an effort with importants return.

Viewing 14 posts - 31 through 44 (of 44 total)
  • You must be logged in to reply to this topic.