Email Field Prioritiezed option does not render correctly on checkout page

This topic has 6 replies, 3 voices, and was last updated 7 months ago ago by Rose Tyler

  • Avatar: ecommercedev
    ecommercedev
    Participant
    September 25, 2023 at 02:29

    Hi,
    I want to use the ‘Email Field Prioritiezed’ option for my checkout process. However it seems there is some clash between the email and first name fields. How can I make it work?

    https://ibb.co/n1sfpnj

    Please, contact administrator
    for this information.
    5 Answers
    Avatar: Tony Rodriguez
    Tony Rodriguez
    Support staff
    September 25, 2023 at 05:38

    Hello, @ecommercedev,

    Thank you for contacting us and for using XStore.

    We apologize for any inconvenience you may have experienced. We would like to clarify that if you are utilizing the Advanced Cart Layout and have enabled the ‘Email Field Prioritized’ option, the email field will be moved to the first position in the billing details form. This will make it the highest priority field to be filled in, compared to the other fields.

    The functionality to display the email field following the First Name field in the billing details form is a default feature of the options provided.

    If you wish to disable the prioritization of the Email Field, you can easily do so by navigating to XStore > Theme Options > Woocommerce > Cart/Checkout Layout > Advanced Layout in your settings. Once there, simply switch it to ‘OFF’ and ensure you publish the changes.

    Best Regards,
    Team 8Theme.

    Avatar: ecommercedev
    ecommercedev
    Participant
    September 25, 2023 at 23:54

    OK, this does not solve my problem. If this option is available for use with your default checkout layout, it would be at least good to have it look .. not like in the screenshot above. Otherwise I don’t think anyone will use it?

    Either way. It would be nice to get ability to order the email field before all other form fields as I understand its a matter of setting priority on the email field.

    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    September 26, 2023 at 06:38

    Hello, @ecommercedev,

    We appreciate your prompt response.

    Please add the next custom CSS code:
    .form-row-first, .form-row-last {width: 100%;padding: 0px;}

    Kind Regards,
    8theme team

    Avatar: ecommercedev
    ecommercedev
    Participant
    September 26, 2023 at 13:29

    This does not prioritize email field as I would see it. I mean for me ‘prioritize email field’ option means it is brought all the way to the top.

    However, at least now it renders OK with your custom css.

    EDIT:
    And this is exactly how you describe it in your documentation https://xstore.helpscoutdocs.com/article/175-customizing-cart-checkout-page-layouts

    Email Field Prioritized: To streamline the checkout process, you can prioritize the email field by moving it to the first position in the billing details form. This ensures that customers fill in their email address promptly.

    So either changing name of that option or fixing the priority value for email field would be a solution. Since I can see it has the exact same priority attribute as first name field in HTML.

    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    September 26, 2023 at 16:17

    Hello, @ecommercedev,

    Please provide temporary wp-admin and FTP access, it looks like a plugin is causing the problem.
    Or try this custom code first:

    add_action('init', function() {
     if ( get_theme_mod('cart_checkout_advanced_email_first', false) ) {
         add_filter('woocommerce_billing_fields', function($fields) {
             if ( isset($fields['billing_email'])) {
                 $fields['billing_email']['priority'] = 2;
             }
         });
     }
    }

    add it via FTP into the functions.php file of the child theme.

    Kind Regards,
    8theme team

  • Viewing 6 results - 1 through 6 (of 6 total)

The issue related to '‘Email Field Prioritiezed option does not render correctly on checkout page’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.