• Resolved demonshi

    (@demonshi)


    Hello. There are two questions:

    1. You added the features “WPML and Polylang now translate the booking panel’s own interface text” and “Emails are sent in the client’s or agent’s language.”

      But how do I translate my own text within the emails into multiple languages? And what if it’s custom text?
    2. Is there a way to create a blacklist? Some clients don’t show up, so I need to block them or require prepayment. The block should then only be removable manually.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Reedwanul Haque

    (@reedwanul)

    Dear @demonshi ,

    Hi, thanks for both questions — let me take them one at a time.

    • Translating your own email text

    This already works, and it covers custom text too. The whole subject and the whole body of each email template are registered as translatable strings, so whatever you type in there — your own wording, extra paragraphs, custom HTML — becomes translatable automatically.

    With WPML: go to WPML → String Translation and filter by the domain admin_texts_rox_appointment_booking_email_templates. You’ll find every template’s subject and body there, one row per language.
    With Polylang: go to Languages → Strings translations and look for the plugin’s group.
    When the email is actually sent, the plugin switches to the recipient’s own language before rendering it, so each customer or agent gets the version in their language. The same applies to your sender name, company name and company address.

    Two things worth knowing:

    If you later edit the English (default-language) body, the existing translations are flagged as “needs update” — just re-check them in String Translation.
    Placeholders like {service_name} pull their value from your services, which are translated separately (also in String Translation, under the plugin’s own groups).

    • Blacklisting customers

    There’s no blacklist in the plugin today — you’re right that it’s missing, and it’s a fair request. It’s now on our roadmap, and we’re planning it in the shape you described:

    Block a customer from the Customers list, with an optional reason
    A blocked customer can’t complete a booking from the front end
    The block never expires on its own — it stays until you remove it manually
    A follow-up step: instead of a full block, flag a customer as “prepayment required” so they can still book but only after paying upfront
    In the meantime, if you’re comfortable with a small code snippet we can send you one that rejects bookings from specific email addresses right away — just let us know.

    If there’s anything about the no-show customers you’d like the blocking to handle differently, tell us now while the feature is still being designed — it helps us build the right thing.

    Best Regards,
    Reju

    Thread Starter demonshi

    (@demonshi)

    Thank you for detailed answer.

    Unfortunately, entering email addresses manually is inconvenient; it would be better to wait for the development of full client-blocking functionality.

    You described exactly the functionality we need, so we will wait for the plugin update. Could you just let us know roughly when to expect it?

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.