Andy

[Andy]

I can see that you have a caching plugin, so you may need to refresh the cache files after making changes to the header image.

[Andy]

This should center the footer content and widget titles

@media screen and (max-width: 768px){
    #colophon{
        text-align: center;
    }
    #colophon h5.widget-title:after{
        left: 50%;
        margin-left: -40px;
    }
}

but note that content generated by third-party plugins may have it’s own CSS rules which could need overriding.

[Andy]

If I am understanding correctly what you want to achieve, please try this:

@media screen and (min-width: 769px){
    #site-branding {
        width: 40%;
    }
    #site-description.eighty {
        width: 60%;
    }
    .site-navigation {
        width: 60%;
    }
}

@media screen and (max-width: 768px){
    #site-branding {
        padding-top: 20px;
    }
}

.toggle-nav {
    top: 18px;
}

[Andy]

To make the top bar fixed so that it does not hide when scrolling down the page, add this in Additional CSS:

#masthead.scrolled #top-bar {
    padding: 10px 0 10px 0;
    opacity: 1;
    max-height: unset;
    transform: translateY(0px);
}

[Andy]

Go into Customize > Theme Options and there is now the new Masthead Navigation Responsive Break-Point setting where you can select the screen width for the point at which the desktop menu becomes the mobile menu.

[Andy]

Oh yeah that’ll work. Just be aware giving it a fixed height if you add content to the top bar for example, you may need to account for the extra height.

Glad you’ve found a solution that works 🙂

[Andy]

It makes use of javascript to dynamically change the height to take account of the featured service boxes and also on all pages to take into account that the menu or top bar height could be different on different sites depending on setup.

The javascript which controls this is in the ‘trusted-custom.js’ file. You could copy this file to a child theme and amend it accordingly to suit your own needs.

[Andy]

Hi

If you want to display a different image on mobile/tablet screens, use this CSS (replace path-to-image-url with your actual image path/url

for tablet and mobile:

@media screen and (max-width: 1024px){
    .main-header{
        background-image:url('path-to-image-url') !important;
    }
}

for mobile only:

@media screen and (max-width: 768px){
    .main-header{
        background-image:url('path-to-image-url') !important;
    }
}

[Andy]

Hi, that looks like it could be caused by a plugin.

I would recommend that you temporarily deactivate all currently active plugins, check to see if the problem has gone, then reactivate your plugins one-by-one to see which plugin is causing the error.

[Andy]

Try this CSS first

.woocommerce div.product:after{
    clear: both;
}
.woocommerce div.product:before,
.woocommerce div.product:after{
    content: "";
    display: table;
}

If this doesn’t fix it, yes please email the child theme to me at the email on the docs page.

[Andy]

I don’t think it is related to removing woocommerce_output_related_products. Are you removing or altering any other WC functions?

[Andy]

In that case it would be need quite a lot of custom work and testing.

If you simply wanted to load the font in a custom stylesheet and apply the font to a specific element of your content, that would be quite simple to achieve.

[Andy]

Thanks for letting me know and glad it’s fixed now 🙂

[Andy]

Thanks, I can see that you are running PHP version 5.2.17

That part of the theme requires at least version 5.6 of PHP.

I would very much recommend that you update (or ask your web host to update) your PHP version to 5.6 or later (preferably version 7) as you will most likely encounter more problems with other themes/plugins and possibly even the core WordPress installation.

See the WordPress requirements which states that the absolute minimum required is 5.2.4 and that even this version has reached end of life and may expose your site to security vulnerabilities. Link here: https://wordpress.org/about/requirements/

[Andy]

Sorry to see you are experiencing a problem with the theme.

We are not getting this error on any of our test sites or our demo.

So that I can investigate this further, could you let me know the version of PHP that your server is running?

If you have WooCommerce installed, go to ‘WooCommerce’ > ‘Status’ and under the ‘Server environment’ heading it will say PHP version:

If you are not using WooCommerce, could you install the Debug Info plugin, then look in ‘Dashboard’ > ‘Debug Info’ where it will show which version of PHP you have.

[Author]

Posts