As previously announced via banners and our newsletters, support is no longer available through this platform.

For easier navigation, you can still click on "Submit a Ticket" here, choose the appropriate category, and you'll be redirected to the correct support channel for your plugin.

You can still access your previous tickets and browse public tickets, but please note that responding to tickets is no longer possible.

Paid customers: Please log in to your store account for support.

Pre-purchase questions: Use the support widget in the bottom-right corner of our websites:
https://wpamelia.com
https://wpdatatables.com
https://wpreportbuilder.com

Okay
  Public Ticket #3452797
booking form doesn't fully support RtL language
Closed

Comments

  •  3
    Barad Dediashwili started the conversation

    as you see in the screenshot, a few things don't work well with a website that works on RtL language like Hebrew.

    maybe there are some CSS solutions that could work if you can help me with this, but I would love it if you could fix it in the plugin itself.

    Attached files:  Screenshot 2023-09-06 171838.png
      Screenshot 2023-09-06 171857.png
      Screenshot 2023-09-06 171903.png
      Screenshot 2023-09-06 171914.png

  •  3
    Barad Dediashwili replied

    For now, i made some adjustments using CSS to make it look a bit better, so please take notice of the Screenshots and not the website

  •  1,896
    Miloš replied

    Hi Barad,

    Yes, at the moment, our Forms are not 100% fully RTL compatible 'out of the box' ,

    but our developers are working to improve them as soon as possible.


    We had another user who found some issues with RTL for our Step 2.0 Forms,

    and with help of our developers, here is some CSS you can add in order to fix, we hope all of the issues,

    this is what this user used, and he reported it was fixed :

    [dir=rtl] .amelia-v2-booking #amelia-container .am-fs-sb {
        border-radius: 0 0.5rem 0.5rem 0 !important;
    }
    [dir=rtl] .amelia-v2-booking #amelia-container .am-fs-sb__step-checker {
        margin-right: auto !important;
        margin-left: 0 !important;
    }
    [dir=rtl] .amelia-v2-booking #amelia-container .am-fs__main-heading-inner .am-heading-prev {
        margin: 0 0 0 12px;
    }
    [dir=rtl] .am-icon-arrow-left:before {
        content: '\e907';
    }
    [dir=rtl] .am-icon-arrow-right:before {
        content: "\e906";
    }
    [dir=rtl] .amelia-v2-booking #amelia-container .am-button-group>.am-button:first-child {
        border-radius: 0 6px 6px 0;
    }
    [dir=rtl] .amelia-v2-booking #amelia-container .am-button-group>.am-button:last-child {
        border-radius: 6px 0 0 6px;
    }
    [dir=rtl] .amelia-v2-booking #amelia-container .am-advsc__header>div {
        margin-left: 24px;
        margin-right: 0;
    }
    [dir=rtl] .amelia-v2-booking #amelia-container .m-phone-number-input__country-flag {
        left: auto !important;
        right: 16px !important;
    }
    [dir=rtl] .amelia-v2-booking #amelia-container .el-input__suffix {
        left: 12px;
        right: auto;
    }
    [dir=rtl] .amelia-v2-booking #amelia-container.am-fs__wrapper .el-form-item__label {
        text-align: right;
    }
    [dir=rtl] .amelia-v2-booking #amelia-container.am-fs__wrapper .el-form-item__label {
        text-align: right;
        padding-right: 10px;
        padding-left: 0;
    }
    [dir=rtl] .amelia-v2-booking #amelia-container .el-form-item.is-required .el-form-item__label:before {
        left: auto;
        right: 0;
        margin: 0 0 0 4px;
    }

    Custom code needs to be applied to the page where the booking form is. Depending on what you're using (Gutenberg blocks, or some page builder), adding the CSS or JS can be done in a few different ways. 

    If you need help with adding custom CSS to the page, please take a look at this article.

    Let us know how it goes, and if this solves all the details you found?


    We'll definitely be applying these fixes in the future, but I can't promise that it will be in our upcoming update.

    Once the plugin updates, remove the CSS temporarily to see if the fixes have been applied.


    You can also certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

    and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

    Thank you.

    Kind Regards, 

    Miloš Jovanović
    [email protected]

    Rate my support

    Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/

    wpDataTables: FAQ | Facebook | Twitter | InstagramFront-end and back-end demo | Docs

    Amelia: FAQ | Facebook | Twitter | InstagramAmelia demo sites | Docs | Discord Community

    You can try wpDataTables add-ons before purchasing on these sandbox sites:

    Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables