Navigation
This is archived content. Visit our new forum.

Tagged: 

  • Author
    Posts
  • #1273372
    xthemer
    Participant

    Hey there,

    Two questions:

    1) I have a problem with my footer/.x-colophon.top. Specifically, the border of the #text-6 widget area appears in the wrong place on screen sizes between 767px and 979px. How can I resolve that?

    2) More generally, I did not see any option within x theme to add hook boxes/multiple rows to the footer. Other themes I have used in the past make that easy. So I just turned widget area columns to 100% width to get them to stack like rows. However, that does not feel like the right approach. Is there a different approach I should be taking here?

    Site is not yet online. URL and credentials follow.

    Thanks.

    #1273380
    xthemer
    Participant
    This reply has been marked as private.
    #1273385
    Joao
    Moderator

    Hi There,

    I guess you forgot to post your website and credentials.

    Thanks

    Joao

    #1273394
    xthemer
    Participant
    This reply has been marked as private.
    #1273442
    Nabeel A
    Moderator

    Hi again,

    Thank you for providing the URL.

    1. Please add the following code in your Customizer via Appearance > Customize > Custom > Edit Global CSS:

    .x-colophon.top #text-6 {
        clear: both !important;
    }

    2. You can achieve this by adding sections at the bottom and use widget area inside. You can save the template with the bottom sections and use it on every page.

    Hope this helps!

    #1273474
    xthemer
    Participant

    Thanks Nabeel,

    Concerning point 1: The code worked in as much as the line is now displayed correctly. But now the top-margin for .x-colophon.top #text-6 is gone. How do I fix that?

    Concerning point 2: If I use an individual footer section on every single page and, say, need to change the footer content (which is highly probable), then I will have to change each page manually, right? With currently 20 pages and around 30 planned, that does not seem reasonable and kind of beats the purpose of having a theme framework to manage core areas globally.

    Best

    #1273492
    Joao
    Moderator

    Hi There

    1- Your footer looks good on top I don´t see the need of adding margin to the top, but if you would like to do that you can add to Appereance > customizer > Custom > CSS

    
    .x-colophon.top {
    margin-top: 3%; 
    }

    2- I don´t understand your question, if you go to Appereance > Widgets and change your footer widgets it will reflect on all pages, would you mind to clarify?

    Thanks

    Joao

    #1273584
    xthemer
    Participant

    Joao,

    Clarification concerning 1: The margin affected spaces .x-colophon.top #text-5 and .x-colophon.top #text-6 (not the top footer margin). The spacing should be 40px, but on screens between 767px and 979ps, the margin collapses as a result of the code suggested above. The fix?

    Concerning 2: I think I understand now what you meant (bottom sections for pages with widgets areas implemented via cornerstone’s template function and styled through global CSS). Thanks.

    #1274065
    Friech
    Moderator

    Hi There,

    Sorry, but the way you setup it makes it complicated. You could place the #text-6 (widget) content on the Footer Content. You can enable that on Customizer under the Footer panel. That also means you need to set your Footer Widget Areas to one column now.

    If the Footer Content does work with this, please let us know why.

    Actually you can address the current border issue with this custom CSS:

    @media (min-width:  768px) and (max-width: 979px) {
    	.footer-first-row .x-column {
    		margin-bottom: 40px;
    	}
    }

    Thanks.

    #1280521
    xthemer
    Participant

    Friech,

    The css you provided worked fine. I also moved part of my widget content to x theme footer content as you suggested. That worked, too. Thanks for the help!

    #1280528
    Christian
    Moderator

    You’re welcome.

  • <script> jQuery(function($){ $("#no-reply-1273372 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>