Lock footer - by shivas-irons - on WordPress WooCommerce support

This topic has 5 replies, 2 voices, and was last updated 4 years, 12 months ago ago by Olga Barlow

  • Avatar: shivas-irons
    shivas-irons
    Participant
    December 22, 2020 at 01:09

    Theme is xStore

    I’ have a screenshot of what’s happening.

    https://www.dropbox.com/s/85843piuw4jitnj/footerspace.jpg?dl=0

    How do I control the footer placement so it does not rise upwards when there is limited content on any given page.

    Please, contact administrator
    for this information.
    4 Answers
    Avatar: Olga Barlow
    Olga Barlow
    Participant
    December 22, 2020 at 16:50

    Hello,

    Unfortunately, there is no option to control this. You can add the below code to set the min-height of the page content to Theme Options > Custom CSS

    .page-wrapper .content-page {
        min-height: 75vh;
    }

    Regards

    Avatar: shivas-irons
    shivas-irons
    Participant
    December 22, 2020 at 20:22

    Ok, yeah that’s too bad yet thx for the code. I do have something else here I made a screenshot of. Not certain how to alter the form fields in the shopping cart. At the point where someone is about to order. They all appear tiny.

    https://www.dropbox.com/s/1e93yu2uttkmjfr/screen%20shot%202020-12-21%20at%203.49.06%20pm.png?dl=0

    Avatar: shivas-irons
    shivas-irons
    Participant
    December 22, 2020 at 20:44

    The code for the CSS footer issue worked great!

    You may have advice on this as well so I’ll go ahead and leave this question instead of opening a new ticket:

    https://www.dropbox.com/s/ie1x8gtcbhx16f6/product.mp4?dl=0

    Avatar: Olga Barlow
    Olga Barlow
    Participant
    December 23, 2020 at 15:57

    Hello,

    Checkout issue, product page issue caused by styles of the blog-designer-for-elementor plugin http://prntscr.com/w8j1fa
    So, disable that plugin.

    Regards

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

The issue related to '‘Lock footer’' 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.