Rooster One

Changelog

Earlier releases are listed in full in changelog.txt, which ships with the
plugin. Only the most recent are repeated here, to stay inside the length
WordPress.org allows for this section.

11.1.5 – 2026-08-29

• Search, consent and tracking scripts work again on cached pages. One entry in the list Rooster One hands WP Rocket contained a slash, and WP Rocket’s own pattern builder cannot escape one. The pattern failed to compile, and because a failed pattern is not told apart from «no match», every inline exclusion on the site stopped working: Rooster One’s, and every other plugin’s. Consent banner, Consent Mode, attribution, session tracking and the captcha token minter were all being delayed to page load despite being explicitly excluded, and on one shop it stopped the search autocomplete from starting at all for logged-out visitors. Only visitors saw it, never anyone signed in, because caching plugins leave signed-in pages alone.
• Thumbnails under a product image now work on a phone. Tapping a thumbnail moves the main image, and swiping the main image scrolls the strip to keep the current thumbnail in view. Neither did before on a narrow screen, where the strip scrolls sideways and the arrows are hidden, so the active thumbnail was usually off screen. The vertical strip on desktop follows the main image now too.
• The lightbox filmstrip is centred. When the thumbnails fit across the viewer they sit in the middle rather than pinned to the left edge, and when there are too many to fit the strip still scrolls from its true start.
• Variation images no longer depend on which script loaded first. Rooster One and WooCommerce both have a way to change product images when a variation is chosen, and which one won was decided by script load order, which differs between a cached page and a signed-in one. Ownership is now stated outright: with WooCommerce’s variation gallery switched on it swaps the whole gallery, thumbnails included, and Rooster One stands aside; with it off Rooster One swaps the image in place. Rooster One also stops filling in a variation gallery for shops that have the feature switched off, which was quietly turning it on for them.
• Private sign-in address and sign-up fixes. The custom sign-in address no longer leaks through a second path, the «not found» page no longer names WordPress, sign-ups get their own answer instead of being closed by accident, and two-factor enrolment works again.
• SEO redirects: fewer loops and a cleaner table. Loops that travel through WordPress’s own canonical hop are now caught, and the redirect table reconciles itself when the pinned category changes.

11.1.4 – 2026-08-27

• Branch restock worksheets with a real approval flow (Pro). Each branch gets a worksheet over the whole preorder-eligible catalogue with its own 30/60-day sales. Staff type shelf counts and requested quantities, press Submit requests, and the lines file under Supplier Orders as requests: approval, per-supplier order batches with XLSX and one-click email, receiving, and a read-only reconcile against the ERP’s deliveries. Every step is written to an audit trail with the real user behind it. The old board’s export quietly rewrote the sheet as a side effect; submitting is now an explicit, confirmed step that tells you how many lines it filed.
• Branch staff see only their own branch. Four assignable «Branch staff» roles, one per branch: each opens its own worksheet and nobody else’s, including staff at the head branch. The approval queue across all branches stays with the administrator, so the business owner decides who manages requests.
• A fullscreen product lightbox of Rooster One’s own. Built on the image viewer WooCommerce already ships, so nothing new loads and swipe, pinch zoom and the keyboard come free. Rooster One adds a scrollable thumbnail filmstrip along the bottom, pager dots, an image counter, autoplay with loop, a choice of arrow styles, and a backdrop that can be dark, light or frosted glass. One click or tap anywhere on the main product image opens it. Every setting lives on a new «Gallery thumbnails and lightbox» page in Storefront Display, together with the gallery thumbnail strip’s own height and count.
• The lightbox can open by itself when a visitor arrives. Always, only when they come from a product listing, or from any internal page but never from a search engine or a typed address. The decision is made in the visitor’s own browser, so it stays correct behind full-page caching, and it opens whichever viewer the shop uses, Rooster One’s or the theme’s.
• Choose whose look the gallery, the lightbox and the recommendation rails wear. The Theme compatibility screen now decides the product image gallery and the fullscreen lightbox as well, beside the variation swatches and the recommendation carousels it already covered: for each surface separately, keep the theme’s rendering or hand it to Rooster One. Gallery and lightbox are independent choices, so the theme can lay out the product page while Rooster One owns the fullscreen view. Nothing changes until you choose, and a shop that never opens the screen behaves exactly as it does today.
• Four ERP purchasing reports (Pro). Purchases by supplier, VAT reconciliation, landed cost and margin, and supplier price drift, built from the invoice scanner’s own data.
• The first charts on reports. A report can now carry a chart above its table, drawn from the current view and refreshed by the same filters and search as the rows.
• Every admin data table now behaves the same way. The long conversion completed: some 250 data tables across the whole admin share one component, with server-side sorting, filters, search, exports, bulk actions and honest empty states, and several reports that read retired third-party tables were rebuilt on the plugin’s own data.
• Who may see, edit, run and export reports is now yours to decide. Four new capabilities and two assignable roles (Rooster Data Exporter, Rooster Data Editor), seeded so nothing changes on upgrade day, and revocable from day two, which the old gates could never be.
• The event guest-list export now requires the export permission. Names, emails and phones leave the site only with the same permission every report export carries, no longer with any account that can edit posts.
• Stock Recovery honours the quantity you type. The Qty box was posted and ignored; the number you type is now the restock quantity, and an empty box still uses the engine’s suggestion.
• Both recoverable-value readings, side by side. The recovery queue shows the in-store-anchored recoverable figure and the sales predictor’s modelled estimate as two labelled columns. They measure different things; now they can be compared instead of confused.
• Customer records finally carry the shop’s own latest-order date. The eshop latest-transaction field had been empty since the day it was created. It now fills for every customer with an order and stays current as orders arrive.
• A product mapped onto one of your subcategories now lands in the whole tree (Pro). Matching a feed category to, say, «Portable fridges Igloo» filed the product under that leaf alone, so it appeared in neither «Portable fridges» nor «Camping». Every category attach in the import pipeline now carries the ancestors too, and «Refresh all details» repairs the products already imported without their tree.
• The variable parent gets the SKU rule too (Pro). A feed rule that prefixes SKUs reached every variation but left the parent with the bare vendor code. Parent and variations now go through the same rule by construction, and parents imported earlier with the bare code are found and re-keyed automatically on the next run instead of turning into duplicates.
• Rule the category mapping in bulk (Pro). The «Match the feed categories to yours» screen gains row selection with select and deselect all, Confirm selected, Reject selected, and «Set category on selected»: pick five feed categories and file them under one of your categories in a single click. Every mass ruling still teaches the matcher the way a one-by-one ruling does, and the Suggest and Accept-at-threshold buttons are untouched.
• A real import log (Pro). Every finished feed run now lands in an Import run history kept for 30 days: which products were created and updated, by name, which rows errored and why, and the feed-quality notes. «27 errors» stops being the whole story.
• The feed source tables join the house tables. «Your feed sources» and the scheduler’s «Feed imports on a clock» were still hand-rolled, with no sorting; both now render through the same component as every other table, sortable, with their row actions intact.

11.1.3 – 2026-08-23

• Product pages with many variations open in a fraction of the time. On a shop whose theme draws its own colour and image pickers, a product with dozens of variations could take fifteen seconds to appear whenever the page was not already cached. The list of variations was being rebuilt once for every swatch on the page, so a product with sixty shades built that list sixty times over instead of once. It is now built once and reused for the rest of the page. Nothing about the page changes, it is the same shop with the same pickers. Measured on a live shop: 15.5 seconds down to 1.2.
• A new screen decides what Rooster One takes over from your theme. Many themes draw their own variation swatches and product carousels, and where they do, both they and Rooster One were reaching for the same place on the page. Storefront Display now has a Theme compatibility screen that names the theme it found and lets you choose, for each part of the shop separately, whether the theme keeps it or Rooster One takes it over. Nothing changes until you choose, so a shop that never opens the screen behaves exactly as it does today.
• Our variation pickers can wear your theme’s design. If you hand the pickers to Rooster One, you can still keep the appearance your theme gives them. The page gets the speed without being redesigned.
• Rooster One now works out what your attributes are. Every swatch plugin has its own name for what a colour or an image attribute is, so a picker built by your theme could be one we did not recognise. A one-off detection reads your own products and works it out, and it is not repeated when a page loads.
• Variation swatches can be placed anywhere. A new [aieo_product_swatches] shortcode, and a block that no longer has to sit inside a product loop, so the picker can be dropped into an Elementor or Bricks layout.
• A Greek label read as a hardware term. The wording for the recommendations surface was translated as a name for mounting rails rather than a part of a shop page. Corrected.

11.1.2 – 2026-08-22

• Feeds can bring weight and box dimensions with them (Pro). The catalogue importer could read a code, a name, a price, stock, pictures and categories, and nothing about the physical thing — so every imported product arrived with no weight and no box, and somebody typed them in a second time. Weight, Length, Width and Height can now be mapped, from three separate fields or from one field written as «10x20x30». Both simple products and each variation of a variable one get their own figures, which is what shipping actually reads.
• When the feed’s units are not your shop’s (Pro). A supplier publishing kilograms into a shop that works in grams is out by a factor of a thousand, and nothing would have told you. Make a field that multiplies the supplier’s, and map that: the importer already had the arithmetic, and the four new fields explain it where you need it.
• «Refresh all details» (Pro). A repeating feed is deliberately allowed to change only price and stock, so a supplier cannot overwrite a name you rewrote. That also means products imported before today will never gain a weight. The new button beside a feed’s «Run now» re-reads it once and rewrites everything onto the products that already exist, filling in what they were imported without. It does not change what that feed does on its schedule, and anything you pinned is still left alone.
• Signing in by email works again. Asking for a sign-in link answered with a bare «not found» error, on every site, for as long as the feature has existed. The address the form posts to was only ever created on ordinary page views, and never on the request that actually uses it. The message read like a permissions problem and was not one.
• The sign-in form no longer stops accepting you. After about ninety seconds on a page, the security check behind the login and registration forms quietly stopped renewing itself, and a submission was then rejected with nothing on screen to explain why. It now waits for that check to be ready, renews when you start typing, and paces itself so renewing cannot trip your host’s rate limit.
• The «connect by email» button and its window survive any theme. In themes that rebuild the page as it is drawn, the button’s icon appeared at full picture size and the window opened at the very bottom of the page instead of over it. Both now carry their own appearance, so a theme that discards the stylesheet can no longer break them.
• Greek wording that said the wrong thing is corrected, across the whole admin. Sixty-two labels were translated into a real Greek word with the wrong meaning, which is why nothing looked broken. A tracking event was called a social function, so «Raw events», «Total events» and the Meta and TikTok «Events API» fields all read as though they were about running an event. Reconciliation was called making peace, on the courier invoice screen, the promotions report and the marketplace importer alike. A rejection said a date where it meant a marketplace name. Every one was checked against the screen it appears on before it was changed.
• «Event» now reads correctly in both of its meanings. The word was one entry serving two unrelated things: the column heading over a log of tracking events, and the name of the Events feature itself. Greek has a separate word for each, so the two are now separate entries. Your Events section keeps its name and the log columns say what they are.

11.1.1 – 2026-08-22

• Text that should have been in your language, and was not. Wording you can override in the settings, such as the wishlist tooltips, the free-shipping progress messages, the SALE and NEW badges, the SKU and barcode labels, the add-to-cart button and the checkout invoicing fields, could get stuck in English. It happened whenever the built-in wording was saved into the database instead of being looked up when the page is drawn, and once it was saved it stayed, whatever language your shop was set to. All of it now resolves as the page is built, and an update repairs the values already stored. Anything you typed yourself is left exactly as you typed it, in any language.
• Wording set by one language of admin no longer reaches everyone else. If a shop has staff working in different languages, the person who pressed Save decided what every visitor saw. That is no longer possible for settings, and search engine descriptions are now built in the shop’s language rather than in the language of whoever last edited the product.
• Two hundred pieces of text can be translated for the first time. The marketplace importer’s messages were written against a translation file that was never loaded, so they were English everywhere no matter what you did. They are now part of the normal translation set.
• Some text could not be translated at all. The badge labels, the add-to-cart button text, the product code labels and the trust badges were fixed English wherever you were. They are translatable now, and Greek is included.
• Your shop’s own loyalty points are recorded again. Rooster One awards points on an order, but the figure never reached the customer’s record, so the «Eshop Loyalty Points» field on a customer sat empty next to the points your accounting system had sent. It is now filled from the points ledger and stays correct, including for shops that were already awarding points before this update. Points that are not whole numbers are kept as they are rather than rounded down.
• A faster storefront on every page a visitor loads uncached. Rooster One was asking your database the same questions on every single page view: whether its tables existed, and what character set they use. Neither answer changes between page views. They are now looked up once and remembered, which removes about 22 milliseconds of database work per page, and every table check and table creation from the storefront entirely. Cart, checkout and account pages, which are never served from cache, benefit most.
• Table creation no longer runs on shopper page views. Setting up the database is now done where it belongs, in the admin, on the command line, and on scheduled tasks. Nothing about your data changes; it simply stops happening on a page a customer is waiting for.

11.1.0 – 2026-08-20

This release also carries everything listed under 11.0.13 below, which was never published separately.

• Pro features now carry their code in the Pro plugin. The catalogue importer, product feeds between sites, duplicate products, and the Greek text matching all three rely on, have moved into Rooster One Pro. The free plugin keeps every screen, every description and the upgrade path, so you can still find these features, read what they do and see what they would give you — and a screen whose engine is not installed says exactly that instead of failing. If you use any of them, update Rooster One Pro to 11.1.0 at the same time.
• Screens that were always Pro now say so. «Import products from a marketplace» and «Product feeds between sites» have been Pro in the capability list since it was written, but neither screen showed it and the feeds screen never checked. Both now show what Pro gives you, and the Connections page marks every Pro service in its directory instead of listing them as though they were included.
• The one-click marketplace import (eFood, Wolt, Etsy, Amazon) requires Pro. It always counted as a Pro feature; it simply never enforced it.
• Nothing changes on your storefront. Recommendation rails, related content and audience filtering keep reading what was already computed for them, exactly as before, and keep working if the Pro plugin is ever deactivated. Behavioural data collection stays in the free plugin so a shop that upgrades later still has its history.

11.0.13 – 2026-08-20

• Prefix or suffix the SKU a feed creates. A supplier’s code 101.55.3 can be stored as ELDIC0-101.55.3, so you can see at a glance which supplier a product came from. The rule is applied as each row is read, so the SKU the catalogue is searched on and the SKU a new product is created with are always the same value: a match updates, a miss creates, and the two can never disagree.
• Filter an import by SKU or barcode. Include or exclude by shape rather than by list: 101.55.3* takes only codes starting with it, *-EL only those ending with it, and a plain EL- any code containing it. A dot stays a dot, so real codes behave the way you type them.
• The same code patterns target offers. Brand discounts, brand gifts and free shipping accept the same include and exclude patterns, matched against a product’s SKU and barcode, so one supplier’s whole range can be covered without listing it.
• Products are identified by SKU only. A barcode can no longer establish identity, because the same article carries different barcodes per country and per revision, which meant an import could update the wrong product or duplicate one. Barcodes remain imported, stored and filterable.
• Give suppliers to products you already had. A feed records the supplier on everything it imports, but products that were in the shop first had none, and showed as unresolved on the re-order boards. A feed source can now link the brands it carries to its supplier, which repairs those older products without touching them: a product finds its supplier through its brand when it has none of its own. It previews what it would change first, never overwrites a brand that already names a supplier, and modifies no products.
• Supplier Orders: pick the orders first, then the supplier. The supplier list is built from what those orders actually contain, several suppliers can be chosen at once through the usual product-picker modal, and the item list no longer stops at the first 500 orders.
• Fixes a multi-select on the feed filter screen that lost its styling once you picked something, and a colour-swatch help text that could never be translated.

11.0.12 – 2026-08-20

• Feed rules: reshape a feed before it becomes products (Pro). Five ways to make a field out of what a feed really sends: cut at a delimiter or by pattern (the parent code hiding inside a SKU, an attribute inside a specifications blob), multiply (a feed that carries only the wholesale price maps it to Cost price, and a made field «retail» — the same price times 1.5 — becomes the Price), sum per-warehouse quantities into one stock figure, or pick one named warehouse’s value. «Set a value» rules watch feed fields and write stock, prices or a discontinued flag; conditions on repeating groups are paired within one entry, so «address is X AND it says available» is true only when that one warehouse says both.
• Filter what a feed imports (Pro). Per-feed include and exclude lists over the feed’s own categories, brands and tags, combined with AND or OR; an exclusion always wins. The pickers read the whole feed even when a test cap is set.
• Import at most N products (Pro). Set it to 1 and watch how a single product of a new feed actually lands before letting the whole catalogue through.
• The feed’s categories are matched to yours, and your rulings teach it (Pro). Vendor category paths are scored against your category tree, Greek-aware; a review panel shows every suggestion with its score, and you confirm, correct or reject each one. Rulings persist in a register that survives deleting the feed and transfers to other suppliers’ feeds: an exact path applies at full confidence, and a near match raises a lexical half-match to a strong one. A category with no match can be created locally, skipped, or keep the product out entirely — your choice per feed.
• Availability words teach a register too (Pro). A rule that says what a feed’s availability word means is remembered, and feeds that use the same word get the same reading without a rule.
• New: a discontinued state. A rule or availability word can mark a product discontinued: out of stock and hidden from the catalogue while its page stays live, and the state is sticky — a feed that simply stops mentioning the product never quietly revives it.
• Wholesale prices land in WooCommerce Cost of Goods. A new «Cost price (wholesale)» mapping target writes straight into Cost of Goods (WooCommerce 9.5+): set on create, moved on change, filled where empty on enrich — and never cleared by a feed that omits it.
• Feed schedules got a real calendar. Hourly, daily, weekly or monthly, with the hour, the weekday or the day of the month, all in the site’s own timezone and self-correcting across daylight-saving changes. The Data preparation page gained an audit card showing every source’s cadence and next run, and the Connections page now counts your own feed sources instead of reporting the importer «not set up».
• New: Supplier Orders. One page that answers «what should I order from each supplier»: items from open orders or any period, aggregated per product, exportable to XLSX, and emailable to the supplier’s order-taking address in one click. The staff pre-order boards moved here from the Branch Scanner, so purchasing lives in one place.
• The supplier is part of product vitals. Each product’s supplier is resolved nightly into the vitals table (direct assignment first, then the ERP catalogue, then the brand’s supplier), so order screens answer instantly instead of walking the chain per product.
• Duplicate products reads more Greek (Pro). Two colours in one variant («Τιρκουάζ/Πράσινο») stay one colour value; litres keep their unit; dimensions such as «40 X 127 Cm» bind the unit to the numbers so a trailing code stays a code; and colourway groups — the same sizes repeated across colours — coalesce into one product with both size and colour axes.
• Fix: a PHP 8 fatal on malformed text from imported catalogues. Invalid UTF-8 bytes in a title could take down the Duplicate products screen and the content indexer’s word count. Both now degrade instead of fataling, which is the resolver’s contract with catalogue data.
• Fix: editing a saved feed source no longer loses its address. The file picker stopped clearing the URL, an empty address on save keeps the stored one (a single – removes it), and re-picking «One product is» during an edit works from the stored sample. The default for «one product» now prefers the row that carries SKU and price signals over an equally-nested warehouse row.
• The whole new surface speaks Greek. 149 new strings translated, and the match-score column header corrected — it read «Αγώνας», a sports match.
• The update screen reads like an update screen again. The upgrade notice is one short paragraph; the story stays here in the changelog.