Handbag results show “Showing 10–12 of 12 results” but as of today there should only be 7 handbags. Also, the Shop By Color -> Red category has a similar problem. All other categories display the results and pagination correctly.
Handbag results show “Showing 10–12 of 12 results” but as of today there should only be 7 handbags. Also, the Shop By Color -> Red category has a similar problem. All other categories display the results and pagination correctly.
Provided
in Settings -> Reading -> “Blog pages show at most” is set to 9 and has not been changed since I installed Blanco theme. Pagination has not been an issue with all of the other product categories (such as https://contessaboutique.com/product-category/bracelets/). Only handbags does not page correctly.
I changed the “Blog pages show at most” to 6, and still saw pagination issue. Only 5 products on page 1, page 2 showed 3 products, page 3 no products.
Thank you Eva for your help. Looks like I’ll have to use a WooCommerce widget or write custom code.
Please see private content for site access comments
Please see private content
Question about site access limited in private content
Thank you Eva. There should not be any limitations on site access. You can see the area where I’d like to display linked products by going to https://contessaboutique.com/product-category/handbags/, click any handbag. I’d like to display linked products below the Secured by GeoTrust graphic which is in a sidebar. I don’t want to show upsell products in the Product Description tab.
I tried to use shortcode [etheme_related_products per_page=”4″] in the sidebar, but I saw literally “[etheme_related_products per_page=”4″]” appear.
Provided. Thank you!
Hi Eva, are you asking for login and FTP for @Johnboy_65 or @roxiebaby007?
Hi Eva, thank you for the help. At this point you may not need to FTP and log into the site with WooCommerce issues because I have been able to upgrade to Blanco 3.0 and run WC 2.3.3. Instead, would you be able to send a link to the changes in Blanco 3.0?
@ztrain727:
I discovered that WordPress is doing the WooCommerce auto update. The plugin Simple History showed me. Here’s a snippet of the details:
pluginupdateinfoplugin woocommerce/woocommerce.php
pluginupdateinfopackage https://downloads.wordpress.org/plugin/woocommerce.2.3.3.zip
pluginprevversion 2.2.11
messagekey pluginupdated
_wpcron_running 1
I never set it up to auto update WC. Quite odd…
Had to come up with quick fix, so I went with a plugin (rather than figuring out how to block WC update in wp-config). Installed “Disable Updates Manager” to block any updates to WooCommerce. It worked well and blocked the mysterious auto update to WC 2.3.x until I explicitly unblocked it and upgraded. I am able to run Blanco 3.0 with WC 2.3.3.
Regarding the heavily modified Blanco, I also have custom code and have noted which source files have modified PHP. When there’s a Blanco update, I use BeyondCompare to diff my customized PHP files against the PHP files in the new Blanco version. After I merge code where necessary, I overwrite files via FTP. Hope this tip will help you!
Same issue here when Cloud Zoom is disabled. If click on additional product image, then the direct path to the JPG (in the wp-content/uploads folder) opens in the browser tab.
When I enable Cloud Zoom, then the additional product images in the slider below the featured image appear in the main-image div (as expected).
I installed Blanco 3.0 with WooCommerce 2.3.3 today.
I just installed Blanco 3.0. Does this release address the incompatibility with WooCommerce 2.3.x? I tried to view the details of this update, but the info would not load.
here it is
provided
At this point I suspect the Envato Toolkit. I’m trying to remember if I visited that page in my WP admin before each time I discovered that WC was updated. The Envato Toolkit mentions something about auto updating my theme and will make auto backup before performing upgrade. It didn’t mention anything about WC or other plugins, but perhaps it does try to be overly efficient (my theme is made for WC). I’m hesitant to browse to it now to verify specific verbiage because I don’t want to trigger an update.
When do you expect to release a theme update to address the incompatibility with WooCommerce 2.3.x?
Same problem here. I manually reverted to WooCommerce 2.2.11, and my products reappeared. However, I just noticed that WooCommerce updated itself to 2.3.1. I verified that 2.2.11 was installed and active earlier today, and I purposely did not choose to update WooCommerce. Now, WooCommerce has mysteriously upgraded itself to 2.3.1, and I’m in the middle of manual revert again.
Blanco 2.9.4 seems to be incompatible with WooCommerce 2.3 on WordPress 4.1. All of my products disappeared. I had to revert to WooCommerce 2.2.11.
I downloaded the most current WooCommerce plugin zip file, extracted the package to my hard drive, located the WooCommerce files that were reported as outdated, and manually updated them via FTP. Please let me know if you need more details instructions.