- This topic has 3 replies, 2 voices, and was last updated 7 years, 7 months ago by
.
You can add all of this code I added in my custom CSS in the history of support
in the next update?
.sh-woo-layout-left.col-md-6,
.sh-woo-layout-right.col-md-6 {
width: 100%;
}
.product .sku_wrapper {
display: none !important;
}
.sh-header:not(.sh-header-4):not(.sh-header-5):not(.sh-header-6) .sh-nav > li.menu-item > a {
padding-top: 10px;
padding-bottom: 10px;
}
#page-container .sh-header-mobile-navigation .sh-nav-container {
padding: 10px 0;
}
#page-container .header-standard-position li a {
font-weight: 500;
}
.sh-testimonials-quote-icon {
display: none!important;
}
#page-container .sh-pricing-enlarge {
overflow: visible;
}
.woocommerce div.product form.cart .variations select {
width: auto;
}- If you add some of this code in the update what can i do with the code i have, erase?
2. How can I know the code you add in the next updates for erase?
Thanks a lot.
Hi @Antalvespo,
I hope you are well today and thank you for your question.
I am not sure why you want the shared CSS code in the theme update as other theme users are comfortable using the theme without this CSS code so it will mess with their sites.
You can just use it adding in your theme settings custom CSS option.
Best regards,
Shufflehound teamBecause more of them are errors in the theme, i imagine you add in the next updates, like the popover or woocommers options, etc. If you add in the future updates enter in some conflict with my codes or what?
Thanks a lot.
We couldn’t reproduce the issues on our test site or any other users site but if we do then we’ll resolve it in the future version of theme.
No future update won’t conflict with your existing CSS code.
