Hi @antibiz,
I think something like the following can help make that logo smaller.
.woocommerce-active .site-branding {
width: 50%;
}
Hi @antibiz,
Could you help me with a few screenshots of where you are referencing for the specific the text and image widget? I looked at the site and might be missing it right in front of me. Is it in the sidebar, footer, etc…
Thanks!
Hi @lucida,
This is happening as each H1 also has a different class and slightly different mark up with different CSS styling applied to each.
For example on your shop page, it has an additional 40px on the top of the H1. The below CSS would remove that.
.woocommerce-products-header {
margin-top: unset;
}
It should then match the normal page template used on the About or Contact page. Now regarding the homepage there is a breadcrumb div that’s missing when it is on other pages.
Link to image: https://cld.wthms.co/bbj9kC
I didn’t see other pages or parts of your site using breadcrumbs, so it could be something you consider removing with a little code snippet as outlined here. If removed the other page spacing should then match your homepage. Alternatively you can also add that padding to the homepage, like the following CSS.
.home .entry-content {
padding-top: 1.2em;
}
Hopefully that is helpful. 🙂
-
This reply was modified 7 years ago by Ryan Ray.
-
This reply was modified 7 years ago by Ryan Ray.
-
This reply was modified 7 years ago by Ryan Ray.
Hi @vd11,
I think I figured out what was going on here. 🙂
The action didn’t have a priority. I added one at 100 which should make it fire later than anything else enqueuing the font, and it seems to have worked. My snippet looks like the one below.
function storefront_remove_google_fonts() {
wp_dequeue_style( 'storefront-fonts' );
}
add_action( 'wp_enqueue_scripts', 'storefront_remove_google_fonts', 100);
BEFORE:
Link to image: https://cld.wthms.co/FMpsmL
AFTER:
Link to image: https://cld.wthms.co/MjtLtz
I hope that helps!
Hi there @hofewo,
I would recommend playing with the position property to start. This can help you add the correct positions selectors to the container div, then the two divs that have the product list and sidebar.
https://css-tricks.com/almanac/properties/p/position/
Something like this seemed to work out ok for me, but I would of course test this out on a staging site and tweak to your needs.
.col-full {
position: relative;
}
div#primary {
float: left;
width: 100%;
margin-top: 100%;
}
div#secondary {
float: left;
width: 100%;
position: absolute;
left: 0;
right: 0;
}
-
This reply was modified 7 years ago by Ryan Ray.
Hi @lucacdq,
I think there could possibly be a couple of easier options for you to accomplish having a logo, a site title, and tagline.
We’re (WooCommerce support) not able to help write the CSS for you, but I would use a ::before selector to add your logo to the existing site title/tagline. Then further CSS can help style and position it.
You can read more about the ::before selector here.
We highly recommend contacting one of the services on our Customizations page if you were interested in hiring someone to write this code for you (https://woocommerce.com/customizations/)
I hope that helps.
Hi @hrishikeshbharaligmailcom,
It seems like you’d found some solution at this point, I see the appropriate menu based on my browser width.
https://cld.wthms.co/wLHxy7
Am I missing anything? 😛
Hi @infotrailexplorerscouk,
I can see just a smidge of the tested site at the time in the image below, it obviously doesn’t quite look right which is why then (I think) you are getting the results you are.
Link to image: https://cld.wthms.co/YGOGAO
I’m not sure why Google rendered it that way, and while I’m not 100% familiar with Google Search Console, that’s definitely not how your site looks on a real device.
Link to image: https://cld.wthms.co/HarKiD
Maybe there was something wrong with the test at the moment, or a setting to change with Search Console?
Hi @taisho,
Thanks for bringing this issue up. I agree that in this instance it would be nice to have more control over this font file compared to others. Luckily someone already added this request via GitHub. 🙂
https://github.com/woocommerce/storefront/issues/1089
If it helps for now, you could use a CDN for your site itself which would upload all your specified files and not just this one font file. Something like Stack Path could be great. –> https://www.stackpath.com
Either way, I hope that issue on GitHub becomes a part of the theme soon.
Hi @kristinubute,
Thanks for the couple of messages here. I’ll try to separate what you’ve asked us about and explain our rationale for the way Storefront works.
To begin, Storefront was built with its mobile layout first. It then adapts to larger screens. From what I can see we’ve implemented our own parts of a framework called Susy. –> https://susy.readthedocs.io
Link to image: https://cld.wthms.co/KoX4db
^ That above is the pixel breakpoints to go from handheld, to a tablet in-between, then to the desktop size. 568px is the max width for handheld, then 569-767px would be tablet, finally 768px and beyond is desktop.
I would continue using those breakpoints in your media queries to target certain layouts/devices to customize to your liking. So to answer the part about Galaxy S3s, that depends on their screen size which I’m sure you can find out somewhere.
Regarding Mega Menus, if you are using our extension for that it doesn’t currently work on mobile devices. It falls back to the normal menu in that case. What do you mean when you see 2 items? Also, can you help us understand what your MOBILE MENU is and what NO formatting means? 🙂
Hi @hencca,
It looks like if you update to 2.4.6 or later that should fix the Subscriptions troubles. See here.
Link to image: http://cld.wthms.co/XYSAl0
Also, feel free to reach out to our support team for any purchased extensions. 🙂
Hi @busfan210,
I think I could help explain some of the initial confusion with Square and WordPress.com accounts.
When you’d gone through the WooCommerce on boarding wizard there are some services that require a connection to WordPress.com so it asks you to create and/or login to WordPress.com. Things like automated tax rates or printing USPS labels require this, but Square doesn’t.
The on boarding wizard will install the Square extension, which can be removed and not used. Hopefully that helps explain things there. 🙂
The order numbers not being sequential is a downside of the way WordPress works with post types, which orders are a post type in WordPress. Every time a post is created, no matter the post type, it gives it an ID number. So you could have an order placed and it gets an order number (post ID) of #1, then if you publish a post on your blog that would get Post ID #2, and finally if another order is placed that second order would get order #3 (Post ID 3). Does that also make sense?
Hi @carlwan,
This did become an issue with the release of WordPress 5.0.2, but if you can update to WooCommerce 3.5.3 it should fix that for you.
Nonetheless, glad you did find a solution as well!
Hi @stwow,
That almost seems like when switching over to HTTPS something isn’t 100% right and isn’t allowing the AJAX file to load/be accessed. It may be trying to load over HTTP instead of HTTPS and then the site/browser doesn’t allow that unsecured connection.
Do you see any errors in your browsers console when using HTTPS?
Hi @besmannmachine & @liselefebvre,
As @josk79 said, it could be helpful to see the system status reports from both of your sites. 🙂
You can find it via WooCommerce > Status.
Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.
I’d also suggest reaching out to your hosts as my first assumption is that something is going on with your .htaccess file the host likely uses to help permalinks function as they should. Depending on your hosts system they may use other tech to do that, but .htaccess is a good starting point. You should need to be re-saving permalinks to have pages work as they should.
