11 versions
WOOBE - WooCommerce Bulk Editor Professional history.
Every release of WOOBE - WooCommerce Bulk Editor Professional is archived here with its changelog, file size, and security scan result. Use the archive to roll back to a stable release or audit what changed between updates.
9 of 11 releases scanned clean
v2.2.6Latest
October 27, 20264.4 MBScanned
Added
- a variation's own image in the Thumbnail column shows a × on hover that removes the image (History keeps it for rollback); with a variation gallery the cell shows its first image faded again.
- with WooCommerce 11.1 or newer, variation galleries can be edited in BEAR: the Gallery column and bulk edit work for variations, and the MCP image tools (woobe_product_images, woobe_set_images, woobe_upload_link and the other image tools) accept a variation id; on older WooCommerce variations keep the lock as before.
Other
- MCP server fix: woobe_create_product dropped the attributes of simple, external and grouped products without a word; they are saved now, as woobe_update_product saves them.
- MCP server fix: term names came back HTML-escaped (Clothing & Shoes) from woobe_list_terms and the other tools; they are plain text now (Clothing & Shoes).
- MCP server fix: woobe_update_product of an attribute, a category, a tag or another taxonomy answered an empty "returned"; it shows the value stored after the write.
- MCP server fix: on a new install, edits made through the MCP server before the BEAR page was first opened were not recorded in History and could not be rolled back; the History tables are now created by the first write.
- MCP server fix: categories, tags and other taxonomies given as a comma list ("16,17") kept only the first term, and a name or an id of another taxonomy quietly emptied the product's terms; comma lists are read in full now, and a value that is not a term id of the field is refused with nothing written (woobe_update_product and bulk edits).
- MCP server fix: an attribute value that matched no term (a name instead of an id, or a comma list) cleared the attribute without a word; ids (also comma separated) and names given as {"name": "..."} are accepted now, an unknown value is refused with the list of allowed ones, and the answer shows the stored values with their names.
- MCP server fix: images set through the MCP image tools were not recorded in History, so they could not be rolled back; they are now, for products and variations.
- MCP server fix: the answer of woobe_set_images after a replace showed the tail of the old gallery; it shows what is stored.
- MCP server fix: images written to one product at the same time (files sent at once to an upload link, parallel woobe_set_images calls) overwrote each other, and the upload link lost track of what arrived; they are written one after another now.
- MCP server fix: woobe_top_customers stopped with a critical error on dates it could not read; it answers like the other reports.
- MCP server fix: woobe_export_csv stopped with a critical error when an id was not a product of the shop; such ids are left out and named in the answer.
- MCP server fix: any text was accepted as a product status, and the product vanished from the shop, the admin lists and the filters; only the shop's statuses are accepted now.
- MCP server fix: numbers were cast without a word - "12,50" became 12, a price could be negative, "2.5" pieces of stock became 2; such values are refused with the reason, in woobe_update_product and in bulk edits.
- MCP server fix: woobe_create_order turned a quantity of 0, -2 or 2.5 into 1; it is refused now.
Fixed
- a SKU already used by another product was saved anyway and the table showed no error; it is refused now with a message and the old SKU stays, in the table, in bulk edit and through the MCP server.
- a SKU changed in the table, in bulk edit or through the MCP server did not reach WooCommerce's product lookup table, so the old SKU stayed reserved and other plugins reported "Invalid or duplicated SKU".
- CSV exports (the Export tab and the MCP server) wrote values starting with = + - @ as they are, so a spreadsheet ran them as formulas; such values get a leading apostrophe now, as in WooCommerce's own export.
- with TranslatePress active, variation titles in the table, in the line above it, in the Thumbnail tooltip and in the popup editor titles showed markup as text (Shoe - Red).
- a variation without its own image showed the placeholder in the Thumbnail column although its WooCommerce variation gallery has images; the first gallery image is shown faded, with a note that it is not set as the variation image yet (display only, nothing is saved).
- images uploaded in the "Add Image" window of the Gallery popup did not show up in that window's media library and could not be selected; they show up selected now, ready to add.
- opening the Gallery popup from a cell that already has images scrolled the page to the top, so after Apply or Cancel the table was no longer where it was; the page stays in place now.
- the line above the table showed "&" in titles with an ampersand (Black & White); it shows "&".
October 13, 20264.5 MBScanned
* MCP server fix: a change written to particular variations (include_variations matching) with variations_only reached every variation of the product, not only the chosen ones.
* MCP server fix: include_variations matching with two attributes took the variations matching either of them; it now takes only those matching all of them.
* MCP server fix: include_variations matching did not narrow anything on attributes with non-Latin names and took every variation of the product.
* MCP server: a selection taken with include_variations matching holds only the chosen variations, without their parent products - reports, export and deletion now work on exactly those variations; deleting such a selection no longer moves the whole product to the trash.
September 28, 20264.5 MBScanned
Other
- MCP server: MCP access for selected users - the administrator grants MCP to named users, each gets a personal key and works under his own WordPress account and rights; two-factor connection is always on for them.
- MCP server: permission map for MCP (hook woobe_mcp_permissions) - full / read / none per area of the shop, per user.
- MCP server: every report answer says in one line that its figures come from WooCommerce Analytics and, while Analytics imports orders on a schedule, how many newer orders are not in them yet.
- MCP server fix: GET request to the MCP endpoint caused a PHP fatal error.
- MCP server fix: MCP rollback left an empty bulk entry in History.
- MCP server fix: woobe_find_products refuses a filter key it cannot use, or a value in another shape, and says why; before, such a condition was ignored and the whole catalogue was selected.
- MCP server fix: number ranges of the product filter work as the tool description says - from included, to excluded, a missing end open, from equal to to exactly that value; a stock range 0 to 0, a stock "from" alone or a weight of 0 selected the whole catalogue.
- MCP server fix: whole_catalogue in the answer of woobe_find_products is true whenever the selection holds every product.
- MCP server fix: arguments of the wrong type are refused with a readable error instead of PHP warnings or an HTTP 500; a text such as "maybe" no longer counts as a confirmation.
- MCP server fix: several product finds in one request carried each other's conditions.
- MCP server fix: a product read of an id that is no product caused a PHP fatal error.
- MCP server fix: gallery, upsells, cross-sells and grouped products given as a list of ids were emptied.
- MCP server fix: creating a product with a SKU already in use now says the SKU was left empty.
- MCP server fix: creating a product with a category name or a missing category id now warns instead of saying nothing.
- MCP server fix: an order for a customer that does not exist is refused.
- MCP server fix: the margin report logged a WooCommerce notice per product when Cost of Goods Sold was off.
- MCP server fix: a unix timestamp given for a date field (the sale dates) was stored as 1970 - it is read as the day it falls on in the shop's time zone, and woobe_list_fields names the formats a date field takes.
- MCP server fix: the bulk preview checked each operation of a run against the stored values, so a sale price set together with a new regular price showed as refused; it follows the run's operations in order now, as the apply does.
- MCP server fix: creating a variable product refused a list with the same variation twice; both were created and checkout sold only one.
- MCP server fix: adding variations with the same combination listed twice dropped the second one without a word; it is now refused.
- MCP server: the product creation preview now warns about a SKU already in use and about attribute values that look like existing ones (S next to Small), before anything is written.
- MCP server fix: the "product with this name already exists" warning no longer counts products in the trash.
- MCP server fix: the bulk preview showed a new stock for variations that sell from their parent's shared stock and for variable products without stock management, although nothing is written on them; they are now shown unchanged and named in the stock_not_tracked warning.
Added
- History shows who made each change and whether it was done by hand or through the AI assistant; administrators see and can roll back everyone's history, other users see only their own.
Improved
- History filter "by Author" replaced by "Who made the change" with an extra "by hand / through AI agent" filter (administrators only).
- stock quantity, weight and dimension filters - an empty "from" now means no lower limit, so "to" alone also finds negative stock (it started at 0), as through the MCP server.
Fixed
- History rows written in the same second could disappear from the list.
- PHP warnings for shop managers when the field visibility settings had never been saved.
- History pagination jumped several pages after the list was reloaded.
- the rollback of a bulk stock edit put a product that does not track its stock - a variable product whose variations hold the stock - under stock management, at 0 and out of stock.
- History revert of a gallery, upsells, cross-sells or grouped products change emptied the field.
- History revert of a sale date deleted the sale schedule.
- History list pages after the second could not be reached after the page size was changed.
- sale price filter with only "from" found nothing; PHP warnings for a price or stock range with one end.
- a stock quantity range or a product URL filter that matched no product selected every product.
- stock quantity filter with only "from" filled in selected every product (with "from" 0, only a stock of 0); an empty "to" now means no upper limit, as for the regular price.
- weight, length, width and height filters with only "from" filled in found nothing; an empty "to" now m
v2.1.9Unavailable
May 21, 20263.3 MBScanned
Improved
- Codebase aligned with WordPress Coding Standards (WPCS) and PluginCheck recommendations.
Other
- security fix, thanks to Bonds and patchstack.com
Fixed
- Sale price range filter could return incorrect results in certain edge cases. Type handling improved for reliable numeric comparison.
- Regular price range filter had the same issue and has been corrected.
- Improved handling of empty values in price filters.
v2.1.7.1Unavailable
April 2, 20262.3 MBScanned
v2.1.7Unavailable
March 28, 20262.2 MBScanned
* set of small fixes
* security fix, thanks to daroo and patchstack.com
v2.1.6Unavailable
February 23, 20262.0 MBScanned
* 2 security fixes, thanks to Dmitrii Ignatyev and wordfence.com
Why archive
Sometimes the latest release isn't the one you need. The archive lets you pin WOOBE - WooCommerce Bulk Editor Professional to a known-good version, or roll back while a bug is investigated. Every release stays scanned and reachable.