WooCommerce Lightspeed POS Version 3.4.0 Changelog

* Feature – Mark Lightspeed POS X-Series sales as paid and closed by recording a payment of a chosen Lightspeed payment type when the WooCommerce order is paid
* Feature – Add an exclusion tags setting for Lightspeed POS X-Series so staff can control from Lightspeed which products appear in WooCommerce
* Tweak – Skip the Lightspeed inventory check when a crawler or bot adds a product to the cart, preserving API rate limit for real shoppers (R-Series and X-Series)
* Tweak – Download Lightspeed POS X-Series product images in batches with immediate follow-up runs, so large catalogs import images much faster
* Tweak – Update WooCommerce product images when they are replaced in Lightspeed POS X-Series, and show pending image downloads on the Sync screen
* Fix – Retry Lightspeed POS X-Series product image downloads after a temporary failure instead of dropping the image
* Fix – Apply Lightspeed POS X-Series background polling frequency changes as soon as the settings are saved
* Fix – Reuse existing media library images when reconnecting Lightspeed POS X-Series, instead of downloading the whole catalog's images again as duplicates
* Fix – Allow X-Series product image sync to initialize on sites with a long database table prefix
* Fix – Show the Lightspeed POS R-Series sales sync settings fields and stop failing order syncs when the enable option was stored in a legacy format
* Dev – Update the bundled Fenix framework to v1.13
* Misc – Require WordPress 6.3+ and WooCommerce 9.9+

WooCommerce Wishlists Version 2.3.22 Changelog

* Fix: Empty wishlists were being created for requests that could not add anything. On a variable product, following the add-to-wishlist link without choosing options created the list first and only then discovered there was nothing to put in it, leaving it behind – so search engine crawlers, which follow that link, produced one empty temporary list per visit. One store accumulated 11,000 of them. The product is now resolved and checked before any list is created, so a request that cannot add anything leaves nothing behind. Existing empty lists are not removed by this update; they can be deleted safely.
* Fix: Choosing a variation through the add-to-wishlist link failed with "Please choose product options" even when the options were named in the URL. The variation lookup read only posted data, while the link is a normal link and carries its attributes in the query string. It now reads both, matching the validation immediately after it, which always did.

WooCommerce Product Feeds Version 12.1.0 Changelog

* New: Add support for document_link
* New: Add support for questions & answers. Fix encoding & defined prop errors for item_group_title
* New: Add support for item_group_title
* New: Add support for popularity_rank
* New: Add support for variant_option
* Fix: Issue where variation description wasn't always added to the description in the feed
* Fix: Bing feed could be corrupted if invalid availability values were supplied via filters
* Fix: Avoid crashes when reviews are returned with no matching product

WooCommerce GravityForms Product Add Ons Version 3.8.2 Changelog

* Fix: On themes that add products to the cart via AJAX, a single click of Add to Cart could add a quantity of 2. Affected products used any attached form, including forms with no pricing fields. These themes (BeTheme is one, when WooCommerce's "Enable AJAX add to cart buttons on archives" setting is on) take over the Add to Cart button, serialise the whole form with FormData and post it to admin-ajax.php as a woocommerce_add_to_cart request. FormData omits submit buttons but includes hidden inputs, so the hidden "add-to-cart" field we add to the form travelled with that request – and WooCommerce then added the product twice from the one request, once through its form handler (which runs on any request carrying an add-to-cart value) and once through its AJAX handler. WooCommerce's own templates already carry that value on every purchasable product type – on the submit button for simple products, and on WooCommerce's own hidden input for variable and grouped ones – so our copy was redundant on a normal product page. It is only needed on the pages of a multi-page form, where we remove the submit button and move between pages by submitting the form in the background. It is now emitted only in that case, so the AJAX request no longer triggers the second add.

@WPspringcom Facebook
Item added to cart.
0 items - $0