Hi @ssk2019,
Thanks for reaching out to us!
I am not seeing any products on desktop or mobile under your https://shyamalascuisine.com/shop/ page or any of the sub-pages I see in the “Shop” dropdown menu. Here’s a screenshot of what I see:
Link to image: https://d.pr/i/pNLQi6
I see that your shyamalascuisine.com domain is hosted on our WordPress.com platform, which makes you eligible for our premium support.
Please contact us at WooCommerce.com > My Account > Support for further help, as we will be able to take a closer look at your site and help you set up Storefront and WooCommerce there.
Please include a link to this forum thread, so that we can keep track of what’s already been done.
We will be able to help you further there. I will also mark this post as resolved.
Thank you!
Hi @jamierood,
Thanks for reaching out to us!
Vertical images are much larger than horizontal – guess Woo Commerce Storefront theme just goes by the Horizontal width setting
In general, we recommend uploading images that are the same width and height (e.g., 800 × 800 pixels). The images on https://jamierood.com/shop-ls/category/fine-art-prints/ appear to be either landscape or portrait images, so they have different widths and heights.
I am not quite sure what you mean by:
For instance a 300×200 pixel image should display the same as a 200×300 pixel image
These images sizes are different and cannot be displayed the same way. One is 300 pixels in height and the other is 200 pixels in height, for example. Are you asking if it possible for both to appear as 300 × 200 pixels, or say 300 × 300 pixels?
Glad to hear that and thanks for the update!
I’ll go ahead and mark this post as resolved. If you have any further questions or need additional help with the Storefront theme, please start a new thread and we’ll be able to help you out there.
Thank you!
Hi @freelylw,
Thanks for clarifying. I added a Secondary Menu to my test site like the one you share in the screenshot.
I think the reason the Secondary Menu does not move over to the right to replace the search bar is because of its width set in the CSS stylesheet. The menu’s width accounts for the width of the search bar. After removing the search bar, the width of the menu will not increase to take its place.
To fix that, please add the code snippet I shared above using something like the Code Snippets plugin if you have not already done that:
/**
* Disable the Search Box in the Storefront Theme
*/
add_action( 'init', 'remove_sf_actions' );
function remove_sf_actions() {
remove_action( 'storefront_header', 'storefront_product_search', 40 );
}
Next, please add the following CSS code to your site’s Customizer at Appearance > Customize > Additional CSS:
/* Increase width of Secondary Menu and align it to right of page when search bar remove | https://wordpress.org/support/topic/hide-the-search-widget-on-the-top-of-every-page/ wpniall */
@media (min-width: 768px) {
.storefront-secondary-navigation.woocommerce-active .site-header .secondary-navigation {
width: 69.5652173913%;
float: right;
margin-right: 0;
}
}
Here’s what that looks like on my test site:
Link to image: https://d.pr/i/TD7C79
Please let us know if that works for you!
Hi @boppar,
Thanks for reaching out to us.
It should be possible to set uncropped images for all categories except for one category using a PHP code snippet. I understand you’d like that one category to be 1:1, right? I am not aware of a setting or a plugin that can add this functionality.
Would you mind letting us know the category ID for the category you would like to make 1:1?
Thank you!
Hi @freelylw,
Hmm, it looks like your site’s navigation menu is slightly different than the default Storefront navigation menu.
Here’s what I see on my test site:
Link to image: https://d.pr/i/g4B9Ae
I think you could remove the search bar using CSS, as explained in this blog post. However, I think your site would still appear the same way as in your screenshot using this method.
Another method is to use the premium Storefront Powerpack plugin to remove the search bar, as explained in the plugin’s documentation.
Would you mind sharing your site’s URL, so we can take a closer look and provide further help?
Hi @freelylw,
It looks like the problem is that the two ` tags need to be removed from the beginning and end of the code. Can you please try this code on your site?
/**
* Disable the Search Box in the Storefront Theme
*/
add_action( 'init', 'remove_sf_actions' );
function remove_sf_actions() {
remove_action( 'storefront_header', 'storefront_product_search', 40 );
}
It should remove the search bar from the Storefront header.
Please let us know how that goes or if you need further help!
Hi @waveshops,
Hope you managed to change your homepage. We haven’t heard back from you for a while, so I’m going to mark this post as resolved. If you have any further questions or need additional help with the Storefront theme, please start a new thread and we’ll be able to help you out there.
Thanks!
Hi @timt007,
I replied to you on https://wordpress.org/support/topic/not-great-24/ and https://wordpress.org/support/topic/hidden-fields-are-not-picking-up-the-credit-card-expiry-date/ to let you know that the issue has been fixed and released in WooCommerce 5.4.1.
If you had not checked those threads yet, I can confirm that payments made using the eWay extension are working correctly with WooCommerce 5.4.1 (I tested that myself with the latest eWay 3.2.2 version).
We recommend testing the WooCommerce 5.4.1 update on a staging site provided by your host or using a plugin like WP Staging by following this guide before updating WooCommerce on your live site.
Please let us know how that goes or if you need further assistance!
Hi @timt007,
Sorry to hear you had this problem. I just replied to you on this thread to let you know the problem has been fixed and released in WooCommerce 5.4.1.
I can confirm that payments made using the eWay plugin are working correctly with WooCommerce 5.4.1 (I tested that myself with the latest eWay 3.2.2 version).
Please test the WooCommerce 5.4.1 update on a staging site provided by your host or using a plugin like WP Staging by following this guide before updating WooCommerce on your live site.
If you have any further issues, please let us know!
Hi @jmkingfernandez @scottink @tenpastten @acon @reneegoodog,
I would just like to let you know that the issue has been fixed and released in WooCommerce 5.4.1. I can confirm that payments made using the eWay plugin are working correctly with WooCommerce 5.4.1 (I tested that myself with the latest eWay 3.2.2 version).
We recommend testing the WooCommerce 5.4.1 update on a staging site provided by your host or using a plugin like WP Staging by following this guide before updating WooCommerce on your live site.
Please let us know how that goes or if you need any further help!
Hi @webkix @devalexdev @reneegoodog @timt007,
I would just like to let you know that the issue has been fixed and released in WooCommerce 5.4.1. I can confirm that payments made using the eWay extension are working correctly with WooCommerce 5.4.1.
We recommend testing the 5.4.1 update on a staging site provided by your host or using a plugin like WP Staging by following this guide before updating WooCommerce on your live site.
Please let us know how that goes or if you need any further help!
Hi @a1varock,
Thanks for reaching out to us! Sorry to hear you are having this problem.
These errors appear to be about a known bug that has been reported to the Facebook for WooCommerce developers. You can learn more about this bug here: https://github.com/facebookincubator/facebook-for-woocommerce/issues/1777
The recommended steps for getting around this issue are the following:
- Check that your pixel is connected. This Chrome extension created by Facebook will verify that your Facebook pixel is working properly.
- Make sure there aren’t any browser extensions blocking Facebook user agent and IP addresses
- Enable debug logging and see if you are getting any obviously errors
Could you please enable logging, repeat the steps to replicate the issue, and then share the log for us to review? To do so, please follow the below steps:
- Head to Marketing > Facebook.
- Enable debug mode at the bottom of the screen and save the settings.
- Repeat the steps to replicate the error.
- Head to WooCommerce > Status > Logs.
- Choose the Facebook log from the dropdown and click the “View” button to display the log. Please note that the log may be in UTC/GMT time, so it may be offset by a few hours.
- Copy and paste the log into https://snipboard.io and share the resulting link. You can also paste the logs directly in your reply.
Thank you!
Hi @scottink @jmkingfernandez,
I set up a new test site using the latest WordPress 5.7.2, WooCommerce 5.4.0, and eWay 3.2.2 versions with the Storefront Theme (latest 3.7.0 version).
In eWay sandbox mode, I tested payments using Visa, Mastercard, Amex, and Diners test credit card numbers, which are all the card types supported by eWay.
I see what you mean, as the expiration field shows an error and prevents a payment from being made despite the expiration date being valid:
Link to image: https://d.pr/i/fCWRe3
I have reported this bug to our developers for further investigation.Once again, thank you so much for reporting this problem to us!
Please do let us know if you have any questions.
Best,
Niall
WooCommerce Support
Hi @scottink @jmkingfernandez,
Thank you for reporting this problem to us.
I am going to test this problem out on my local testing site, as I do not see any bugs or issues reported on our side. I will get back to you once I have further information.
Best,
Niall
WooCommerce Support
