Sticky BUY NOW button area at the bottom shows overlapped text

This topic has 5 replies, 2 voices, and was last updated 1 years, 3 months ago ago by aniwalunj

  • Avatar: aniwalunj
    aniwalunj
    Participant
    September 12, 2023 at 20:14

    Sticky BUY NOW button area at the bottom shows overlapped text on single product pages. Kindly guide me for the resolution.

    Thank you for your understanding.

    4 Answers
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    September 13, 2023 at 05:30

    Hello, Aniwalunj,

    Thank you for contacting us and for using XStore.

    Please add the next code in Theme Options > Theme custom CSS:

    .etheme-sticky-cart .stock {
        display: none;
    }

    Kind Regards,
    8theme team

    Avatar: aniwalunj
    aniwalunj
    Participant
    September 13, 2023 at 05:34

    I have added this code to global CSS. Is that OK?

    May I know what is the result expected out of this?

    Avatar: aniwalunj
    aniwalunj
    Participant
    September 13, 2023 at 05:40

    I am not seeing any visible difference to the site speed after adding the code. One of the things that I had noticed between staging site and live site was that, when I clicked the back button on staging site the previous page didn’t load again. The previous page just snappily appeared on the screen. Whereas, for the live site each time I go to the previous page it loads every single time. You can test this behavior on your end too.

    Note: I am seeing these results in incognito mode.

    Avatar: aniwalunj
    aniwalunj
    Participant
    September 13, 2023 at 05:44

    Oops! I mistakenly sent the messages related to the other topic in this thread. Please ignore these two messages. It was a mistake on my part. The intended resolution to the problem has been achieved!

    You can consider this topic closed.

    Thank you.

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

The issue related to '‘Sticky BUY NOW button area at the bottom shows overlapped text’' 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.