• Resolved chaneswin

    (@chaneswin)


    “Booking form label” and “Time slots not found message” in Translation Tab become unreadable code after save settings if using Traditional Chinese.
    Id in appointment cannot order correctly since it‘s string.

    By the way, is it possible to add checking existence while entering phone in a form?

    • This topic was modified 7 years, 7 months ago by chaneswin.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Webba Appointment Booking

    (@webba-agency)

    Hi,

    Can you post here what you are trying to set in “Booking form label” and “Time slots not found message”.

    >> Id in appointment cannot order correctly since it‘s string.
    Thank you for reporting about this bug, we added it in our fix list.

    >> By the way, is it possible to add checking existence while entering phone in a form?
    Please, clarify what do you mean under checking existence?

    Thread Starter chaneswin

    (@chaneswin)

    “Booking form label” in Traditional Chinese:
    “您已選擇 #service : 時間是 #date   #time”.

    “Time slots not found message” in Traditional Chinese:
    “預約已額滿,沒有剩餘可預約時段”.

    My test server can display correctly however in main server they become unreadable code. (Both lite and premium versions have this problem.)

    Checking existence means for example customer type phone number 0911222333 and I don’t want the same person booking again so next time if someone type 0911222333 in phone input then this form cannot be submitted.

    • This reply was modified 7 years, 7 months ago by chaneswin.
    Plugin Author Webba Appointment Booking

    (@webba-agency)

    >> however in main server they become unreadable code
    We tried this on our server and it works.
    Could you please send us a screenshot of this to [email protected] or link to the page with booking form ?

    >> Checking existence
    We don’t have such option. If you provide us more information about what fields you need to use for block and for a what time to block, we will include it in some of the new release.

    Thread Starter chaneswin

    (@chaneswin)

    Problem Solved!
    Thank you so much!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘unreadable code and incorrect order’ is closed to new replies.