Changelog

  1. 1.8.0

    Stable

    The release about how your store looks and what it reports. A Look screen under Configuration changes a Foundra store's design (preset, colours, fonts, header, footer) beside a preview of the home page, without a trip to Template Styles. Solidshop gets a cookie consent banner of its own, with Google Consent Mode v2, and the order confirmation page can report each order once to Google Tag Manager, GA4 and any tag on the page, which the new Conversion Tracking add-on builds on. Products can be listed in more than one category, and a tag can have a shop page of its own. A WooCommerce product export now imports as it is: categories, sale prices, stock, attributes, variations, weight units, virtual and downloadable products, from a shop in any of 36 languages. And a payment that fails or is cancelled at the provider no longer ends on the order confirmation.

    Security fixes: storefront listings, their counts and search suggestions no longer show visitors products they cannot open, and a store's tax settings can no longer be changed from another store's Tax tab.

    Schema: one new table, #__sshop_product_categories (a product's additional categories). One update file corrects the product content type Joomla's tag pages read, and the tag-page copies of tagged products.

    Added

    • A Look screen. Solidshop → Configuration → Look changes the design of a store that wears the Foundra template — preset, colours, fonts, logo, header, footer, page background, corners, custom CSS — in Solidshop's own back office, beside a preview of the home page drawn with the changes before they are saved, at desktop and phone width. It renders the template's own options form, so a setting Foundra adds reaches the screen with no Solidshop change; the preset is shown as a picture of a store wearing each. It needs the right to change Solidshop's options, never access to Template Styles, so a merchant's staff Administrator can use it. The preview is a token the back office signs with the site's secret, posted to the home page; the page drawn with it is never cached or indexed, and a token that is altered, expired or made for another style draws the store as saved (Solidshop\Lib\Template\Preview). On a site whose default template is not Foundra the screen says so and links Template Styles for a user who may open it. Foundra 1.2.0 draws the preview; an older Foundra shows the store as saved
    • Orders reported to your analytics, once. The confirmation page a shopper sees after paying now reports the order the way Google Tag Manager, Google Analytics 4 and every tracking script expect: a GA4 ecommerce purchase pushed to window.dataLayer and a solidshop:purchase event in the browser, with the order's amounts, currency, coupon, products and payment state and no personal data. It fires once per order, never on a refresh, and never for an order that was voided, cancelled or refunded. Two switches on the store's new Tracking tab: Publish orders to the data layer (off by default; nothing is sent anywhere until a tag on the page reads it) and Count orders not yet paid (on by default, so a store that sells on bank transfer or cash on delivery still counts its sales, flagged as not paid). Plugins get the same order from a new onSolidshopOrderConfirmation event instead of reading the page; the Conversion Tracking add-on builds on it
    • A cookie consent banner. Options → Cookie consent turns on a banner of Solidshop's own on every page of the site: a box, bar or centred dialog in the site's language, with Necessary cookies always on and Analytics, Marketing and Preferences offered as you choose. It asks only when the page has something to ask about — a script marked to wait for consent, or a tracker a plugin adds — so a store with no tags shows no banner. Scripts marked type="text/plain" data-category="…" run only after the shopper accepts their category, Google tags get Consent Mode v2 signals (everything denied until a choice, updated on each one), the choice is kept for the months you set and asked again when you raise the revision number, and a #cookie-settings link reopens the dialog. The banner links the master store's privacy policy, takes your own wording, and follows the template's light and dark colours and direction. On the vendored CookieConsent 3.2.1; quickstart sites have it on
    • Additional categories: one product on more than one shelf. A product keeps one Main category and can now be listed in any number of Additional categories, chosen under it in the product form. It shows on each of those category pages, in the Filters module's category filter and its counts, in the Categories module's tiles (a category holding only additional listings borrows its picture from one of them), in the Products and Reviews modules set to a category, in Smart Search's Category filter, and in the category lists of the XML sitemap and /llms.txt. The main category still decides the product's breadcrumb, who may see it, its custom fields, its admin permissions and its place in the admin ordering; an unpublished or restricted additional category hides only its own listing. Opened from a menu item for one of its additional categories, a product's breadcrumb follows that menu item, without the main category added on top. Product URLs and canonicals carry no category and do not change
    • Batch: Add to category, Remove from category. Tick products in the Products list to list them in a category besides their main one, or to take them out again, without opening each form. The list shows a product's main category followed by "+N" when it has additional ones, with their names on hover and focus, and its Category filter finds products listed in the category either way
    • CSV: Additional Categories column. Category paths separated by |, matched and created like Category. A filled cell replaces the product's additional categories; a blank cell leaves them alone. Export writes them sorted
    • CSV: WooCommerce's Categories column. A WooCommerce product export lists every category a product is in, in one cell (Clothing, Clothing > Hoodies, Music). It used to become one category named after the whole cell. Now the deepest category becomes the product's main category and the others its additional categories; a / stays part of a name and \, is a comma inside one, as WooCommerce writes them. A row that also fills Category uses Category. Import only: Solidshop's own export keeps Category and Additional Categories
    • CSV: WooCommerce's virtual and downloadable products. A new product WooCommerce marks virtual imports as a virtual product, and one marked downloadable as a downloadable product with its download limit and expiry, or as a virtual product when the Downloadable add-on is not installed. Files are not downloaded; the import lists the products that need them. A product already in the shop keeps its type
    • CSV: WooCommerce's variations become variants. A variable product's variations, wherever they are in the file, become its variants, each with its own price, sale price, stock, weight and SKU; the attributes they choose by become the product's options, and the product is priced from its lowest variation. Combinations WooCommerce does not sell, and disabled variations, come in sold out. A variation left at "any" value becomes a variant for each value, its counted stock split between them. Past three options or 150 combinations a product comes in without its variations, unpublished. WooCommerce's GTIN, UPC, EAN, or ISBN column fills the barcode
    • CSV: WooCommerce exports from a shop in another language. WooCommerce writes its column headings in the shop's language (Catégories, Poids (livres)), and only English headings mapped on their own. The import now recognises them in 36 languages, regional variants included, from WooCommerce's own translations
    • Catalogue API and MCP: additional categories. A product's detail carries additional_categories (id, title, listing URL), the list additional_category_ids, both limited to categories a guest may open; filter[category] and the MCP category_id list through either route. category stays the main category. The MCP product text adds an "Also listed in" line
    • Tag listings: a shop page for a tag. The Products menu item has a new Tags option: pick one or more tags and the page lists every product that carries any of them, with product cards, prices, sorting and the Filters module, under the menu item's own title and address. A "Black Friday", "Gifts" or "New arrivals" collection is a tag on the products and one menu item, with no change to the category tree. Categories and Products on Sale Only narrow it further. Search engines index it like any menu page, and on it the Filters module's Tags section leaves out the listing's own tags
    • Products module: Tags option. The products module can show only products with any of the chosen tags, for a "Black Friday" strip on the home page
    • Add-ons can add settings to the store's Tracking tab, as cards of their own beside the core's two switches. The Conversion Tracking add-on puts its destinations there

    Changed

    • The product form's Category is now Main category. Its meaning is unchanged
    • Discounts for a category reach products listed in it as an additional category. A percentage, fixed or tiered discount scoped to the items of a category discounts a product whose main category it is and a product also listed in it alike. The Discount & Coupons plugin's Product Category rule and Fixed price action follow from its 1.1.0
    • The Filters module's category filter offers only categories the visitor may open. A category with a Registered or Special access level was listed to guests, with nothing to show under it
    • Unpublished and restricted tags list nothing. The Filters module's tag filter matched a tag after it was unpublished, and offered tags whose access level the visitor did not hold. A tag now has to be published and in the visitor's view levels to list products, in the filter as on a tag listing, as on Joomla's own tag pages

    Fixed

    • A tax zone can no longer be saved without a territory. A zone applies only to the countries and states listed as its territories, but it saved with none, and a territory row left on Select a country was quietly dropped, so a zone named after a country could charge no tax anywhere with nothing to show for it. Saving now asks for at least one territory and a country on every row; a new zone opens with its first row ready. A zone saved empty before is marked No territories on the Tax tab instead of "—"
    • A WooCommerce product export imports its prices, stock and attributes. Its Sale price column took the Price column, so a product not on sale came in without a price; In stock?, a yes/no flag, took Quantity, so a product in stock came in with one unit; and an attribute stopped its row with "no value given for option". Now a product on sale gets its sale price, with the regular price as its compare-at price, and any other product its regular price; a sale outside its dates imports the regular price. Stock WooCommerce counted is tracked, stock it did not count is not, so the product stays orderable. An attribute fills the product custom field of the same name, so a Color field can still be filtered on, and otherwise becomes a specification row. The mapping screen proposes matching by SKU, as the file has no alias, and a product without a SKU is reported instead of merging into the product above it. A grouped product is saved unpublished, without a price, as Solidshop has no grouped products
    • A WooCommerce product export imports its weight in the store's unit. WooCommerce names its unit in the heading, Weight (lbs), so the column did not map, and mapped by hand it stored pounds as kilograms. Kilograms, grams, pounds and ounces are now converted to the unit the store keeps
    • A product CSV that lists only some of a product's variants no longer puts the others on sale for nothing. A product has a variant for every combination of its option values, and the ones a file left out were created at price 0 with stock not tracked, so they could be bought free. A new combination the file leaves out is now created out of stock at the product's lowest variant price, and the import lists the products that have one. Adding an option value used to reset every variant the file did not list as well: those now keep their prices, stock and SKUs. The VirtueMart migrator writes through the same path, so its partial variant sets are fixed too
    • A variant row with a blank Variant Price takes the product's price. A variant the import created from a row without a Variant Price was on sale at 0. It now takes the product's Price. A variant that already had a price keeps it, and one with no price on either side is named in the import's report
    • Import messages showed " instead of quotation marks, as in ""cotton-tee" already exists and this run only creates new products"
    • The import's column mapping showed raw language keys for the colour and image swatch columns (Option1 Display, Option1 Swatch and the rest). A column without a translated name now shows the file's English heading
    • Security: listings show only products the visitor may open. A product with an access level such as Registered or Special, or a product in a category with one, was listed to every visitor: on the storefront listing and in its filter counts, in the Products module, in the Categories and Brands modules' counts and in the picture a category tile borrows from its products, and in search suggestions. Its own page then answered "403 Forbidden". Every one of them now checks the product's access level and its category's, as the product page does. Search suggestions also leave out products that are scheduled, expired or in an unpublished category
    • Security: the XML sitemap and /llms.txt leave out products in restricted categories. They checked the product's access level but not its category's, so a product in a Registered or Special category was listed for search engines and AI agents, which then got "403 Forbidden"
    • Security: a store's tax settings stay its own. Saving a tax zone, class or rate from a store's Tax tab checked the admin's right to edit that store, but not that the zone, class or rate named in the request belonged to it: an admin of one store could rename another store's tax rows and move them into their own, and a rate could be linked to another store's zone or class. A save now refuses a row, zone or class of another store with "Tax record not found.", and removing a zone leaves other stores' territories alone. A product saved through the API or an import could likewise take another store's tax class, which has no rates in its own store, and sell without tax; the save is now refused. Only a site with more than one store, and an admin allowed to edit some of them but not all, was exposed
    • A category that products still belong to can no longer be deleted. Joomla guards the categories of its own articles and contacts, but let a Solidshop category go: its products then pointed at a category that no longer existed, and the storefront stopped showing them without a word. Deleting a category that is still a product's category, or whose subcategories are, is now refused with the number of products to move first, counting products in the trash
    • Every product has a URL of its own. A product URL carries its alias and no category, but an alias was only checked against products in the same category. Two products with one name in different categories, a Classic Tee under Men and under Women, both became classic-tee, and both links opened the older one. An alias is now unique within its store (and, with multilingual content on, within a language; a product in All languages counts in every one): a taken alias gets the next free number, and the product form says so on save. A blank alias made from the name, a typed alias with spaces or capitals, CSV import, the migrator and batch copy all follow the rule. The update gives every product that had no working URL an alias of its own and lists them; no URL that worked changes
    • Tagged products on Joomla's tag pages link to their product page, and stay listed under a language filter. A Tagged Items menu item and the Similar Tags module linked a product through a generic URL carrying its category, and with the menu item's language set to anything but All they left Solidshop products out. Products now link to the URL their own page names as canonical and count as written for every language. Products tagged before the update are corrected by it
    • A payment that fails or is cancelled off the page no longer ends on the order confirmation. A shopper who left to pay at the provider (Klarna, Affirm, iDEAL, Amazon Pay through Stripe, or another gateway's hosted page) came back to the confirmation page whatever had happened there, and the order confirmation e-mail went out with it. The shop now asks the gateway first: a payment that failed or was cancelled voids the order and brings the shopper back to the checkout with their cart and a message to pay again or another way. Stripe 1.0.1 answers, and records a payment that went through at once instead of waiting for its webhook; a gateway that does not answer keeps the old behaviour
    • Orders on a store never saved through its form start Pending. Checkout gives a new order the store's Default payment status; a store that had never been saved has none, and the order then started Authorized instead of Pending, the form's own default. Cash on delivery and bank transfer orders on a new or quickstart store read as authorised payments in reports and integrations. They now start Pending, as they would after a first save
    • Search Customer on the Create Order screen finds customers again. In 1.7.0 typing a name or e-mail address there sent no search and showed nothing
    • The sample products can be saved on a new install. Editing one of the three products a fresh install comes with failed with "Invalid field: Created By", because they named an owner the site did not have. A new install now gives them to the user who installed Solidshop, and the update repairs them on a site that still has them
    • Every listing opens on its first page. The page number was kept per visitor for all listings at once: after page 3 of the shop, a category, the Deals page or the shop's own menu link opened on page 3 too, often showing a single product. A listing's page now comes from its address
    • Uninstalling Solidshop removes only the menu items it made. It removed the first site menu item with a matching link, wherever it was, so it could take a shop page of your own from your main menu and leave its own items and its hidden Solidshop menu behind. It now removes its pages from the menu it created, and that menu once it is empty
    • The Products list shows "Category: None" for a product without a category, such as the three a new install comes with, instead of "» » (Trashed)". The link to a product's parent category no longer ends in a stray character
    • Screen readers read the right name for the Countries, Currencies, States and Stores tables. Their hidden captions read a language key, or another list's name
    • The add-on screen describes Square as it works: shoppers pay on Square's hosted checkout page
    • The import screen's Import as lists stay readable. Long sample values with no spaces, such as the image addresses in a WooCommerce export, pushed the lists down to two letters on a laptop screen with the admin menu open

    Upgrade notes

    • Update Solidshop first, then the add-ons. Discount & Coupons 1.1.0, VirtueMart Migrator 1.1.1, Conversion Tracking 1.0.0 and Square 1.0.0 need 1.8.0 and refuse to install on 1.7.0. Foundra 1.2.0 and Stripe 1.0.1 still install on 1.7.0, but the Look screen's preview needs Foundra 1.2.0, and Stripe checks a redirect payment on the shopper's return only on 1.8.0
    • Some product aliases may change. Products that shared an alias with an older product of their store had no working URL. The update gives each of them an alias of its own and lists them in its message; no URL that worked changes. Check the list for links you shared to those products
    • A category that still has products can't be deleted. Move its products first, including those in the trash, which count too
    • Tax zones saved with no territory show No territories on the Tax tab. They never charged tax; add a territory, or remove the zone
    • Category is now Main category in the product form. Nothing about it changes
    • The Filters module hides more. Categories the visitor may not open, and tags that are unpublished or restricted, are no longer offered
    • The cookie banner is off until you turn it on (Options → Cookie consent), and the order data layer is off until you switch on Publish orders to the data layer on the store's Tracking tab. Nothing changes on the storefront after the update until you do
    • System → Database may report "One Problem" for Solidshop, on #__sshop_products_translations and the file 1.7.0.sql. The column is right: Joomla's checker misreads one statement in that file, and has reported it on every site since 1.7.0. Fix is harmless, and so is leaving it
  2. 1.7.0

    Stable

    The release about finding the right product. Shoppers can filter listings by Colour, Size, Material and any other product option or list custom field, matched on one variant they can actually buy, and option values can show as colour or image swatches. Products take specification rows of their own, and a product with variants describes each variant to search engines, with its own price, stock and barcode. A product can be limited to one per order. Phone numbers get a country code and show on the order page, and formatted addresses print the customer's first name again. Solidshop gets its own entry in Joomla's administrator menu, with a dashboard behind it, and the System page tells you which template overrides are older than the file they replace.

    Tax: rates marked On Shipping now tax the shipping, an order entered or changed on the order screen is taxed the way checkout taxes it, and changing Price input type no longer moves the totals of past orders. Invoices on payment and restocking on refund now follow every payment and refund a gateway records, not only the ones marked on the order screen.

    Security fixes: with Joomla's cache switched on, a guest could be shown another guest's cart and order; a crafted URL could make the storefront listing show unpublished and trashed products; e-mail templates could reach the site's configuration and the store's payment keys, and were open to any user of the Solidshop administrator; and the bundled PDF, template and HTTP libraries move past their published advisories. A fresh install files its storefront pages in a menu of its own instead of the site's main menu.

    Schema: #__sshop_options.display (text / color / image, default text) and #__sshop_option_values.swatch (a hex colour or a media path), both added by 1.7.0.sql. Existing options read as text, so nothing renders differently until a merchant switches an option. #__sshop_products_translations.name and .alias become nullable, and blanks already stored in them are set to NULL, which is what makes a translation fall back to the product's own name and alias. #__sshop_products.specs and #__sshop_products_translations.specs (JSON, the specification rows; NULL means none, and on a translation "use the default language's rows"). #__sshop_facets (the filters declared under Catalog → Filters) and #__sshop_filter_index (the values each product carries, per variant; derived, rebuilt by Solidshop, no foreign keys), both created by 1.7.0.sql; the installer builds the index. #__sshop_products.sold_individually (1 = one per order, default 0), added by 1.7.0.sql; every existing product stays 0, so nothing a store sells today changes on update. #__sshop_orders.prices_include_tax (1 = the order's prices included tax), which the update sets on existing orders from the current Price input type; #__sshop_tax_rates.is_inclusive, never read, is dropped.

    Added

    • Filters on product options and custom fields. A new Catalog → Filters screen declares the filters the storefront's Filters module offers on top of category, price, rating, brand and tags: a Colour filter that reads the options named Colour and Color, a Size filter, a Material filter that reads a list custom field. Option names are matched ignoring case, spaces and punctuation, and the form suggests the names your products use with every spelling and how many products carry each, so "Colour", "colour" and "Color" end up in one filter. Filters appear after Category in the panel, in the order of the list (drag to reorder); a filter with no value on the current listing stays out of it
    • Option filters match one variant a shopper can buy. Navy and M together list a product only when one variant is both Navy and M and is in stock (or untracked); a sold-out Navy M leaves the product out of Navy + M while Navy alone and M alone still list it. Custom-field filters describe the whole product and never look at stock. Every count in the panel follows the same rules: the number next to a value is what ticking it lists
    • An In stock toggle in the Filters module keeps only products a shopper can buy now. It shows only when it would leave something out
    • The Values tab of a filter lists every value it gathers today, the other spellings merged under each, where each comes from (option or field) and on how many products. Values are ordered naturally — letter sizes in garment order (XS, S, M, L, XL), then numbers, then A–Z — or by Most products first
    • Custom fields as filters. A list, radio or checkboxes field of products with Public access can feed a filter; the panel shows the field's own option texts, translated when they are language keys. The filter form refuses a field that is unpublished or not Public, and the Filters list names a filter whose field has since become unusable
    • Filter URLs: ?filter_colour=black,navy&filter_size=m, the values the same in every language. A value that no longer exists is ignored rather than emptying the listing. Filtered listings carry noindex, follow
    • Rebuild index on the Filters toolbar, and php cli/joomla.php solidshop:filters:rebuild [--product=ID] for a catalogue of any size. The index follows product saves, variant and product deletes, batch moves and custom-field changes by itself; stock is read live and never needs a rebuild. A product that cannot be indexed is saved all the same, and the reason goes to com_solidshop.filters.php in the site's log folder
    • The panel stays quick on a large catalogue. The values each filter offers on a listing are cached, because working them out costs more than the rest of the page; the counts beside them never are. Every change that updates the index clears the cache, and so do publishing, unpublishing or trashing a product and changing a product category. A product whose publish date arrives brings its values to the filters within 15 minutes
    • New Filters module options: Show Option and Field Filters and Show In-Stock Filter (both on)
    • A fresh install seeds a Size and a Colour filter for the sample T-shirt
    • For developers: Solidshop\Lib\Facet — FacetKey (the key a name or value is matched by), FacetSelection (a request's filter_{alias} parameters), FacetMatch (the listing predicate and every count), IndexRowBuilder, FacetValueOrder, FacetRepository::forListing() — all but the repository pure and unit-tested. ProductListingQuery::applyFilters() reads stock and every filter_{alias}. The listing JSON's facets gains attributes (filter_{alias} → value key → count), stock and stock_total
    • Colour and image swatches for product options. Each option in the product form gets a Show values as setting: Text buttons (the default and what every existing option is), Colour swatches or Image swatches. Under colour, a colour picker sits in front of each value and the product page shows a round chip per value; under image, the picker uploads a swatch image or picks one from the store's swatch library and the page shows a thumbnail per value. Swatch images are the store's, not the product's: they live under files/shop/{store}/swatches apart from product photos, are cut to a 120px square, and the same "Navy" swatch serves every product that comes in navy. A value with no swatch stays a text button, and an image-mode value with no image of its own borrows the image of a variant that has one, so a merchant who already gave each colour variant a photo gets image swatches by flipping the setting. The picked value's name follows the option name ("Colour: Navy"), shows on hover and is read to screen readers; the selected chip carries a ring parted from the chip by the page background, so it reads on a chip of any colour. Switching modes keeps the stored colours and images. Works in dark mode, right to left, and in Foundra. The sample store's T-shirt seeds its Color option as swatches
    • Swatches in CSV export and import. Option1 Display and Option1 Swatch (through Option3) join the variant columns: the display repeats on every row like the option name, the swatch belongs to the row's value. A file without the columns keeps a product's stored swatches; a swatch change updates in place and never rebuilds variants
    • Swatches in the catalogue API and the MCP product tool. Each option carries display, each value a swatch: a hex colour under colour, an absolute swatch-library image URL under image, null for a text button
    • For developers: Solidshop\Lib\Product\OptionDisplay (the enum, read leniently from storage), OptionSwatch (normalises a colour or file name for storage; resolves the ResolvedSwatch a value shows under a mode) and Solidshop\Lib\Media\SwatchLibrary (the per-store folder, names, URLs and the upload behind task=swatch.upload / swatch.browse). The field/options.php layout now renders each option as a fieldset with a legend, and the selected value's name lands in a data-option-selected span the product page script fills
    • Phone numbers with a country code. The address form's Mobile and Phone — at checkout, in the account address book and on the admin customer and order screens — and the store's Phone get a country code dropdown in front of the number. It starts on the address's country (the store's country for the store phone) and lists the countries published under Solidshop → Countries, the same list as the Country field. Shoppers type their number the way they know it: 0912 345 678 on a Vietnamese address is saved as +84 912 345 678. A number from a country the store does not list is still accepted when typed with its own + code. Mobile devices bring up the dial pad, browsers can fill in the shopper's saved number, and each number is checked for the right length for its country when the shopper leaves the field. Works right to left and in dark mode
    • The customer's phone on the order page. The mobile and phone numbers show under the shipping and billing addresses as tap-to-call links. The phone was collected at checkout but shown nowhere
    • For developers: the SolidshopPhone form field (countryfield, defaultcountry; validates with Joomla's tel rule on the international plan unless the form says otherwise), Solidshop\Lib\Phone (PhoneNumber::toE164() and telHref() for anything that dials or sends a number) and the com_solidshop.fields-phone asset preset
    • Specifications on a product. A new Specifications tab on the product form takes rows of a label and a value — Wattage: 60 W — that belong to that product alone, with no custom field to define first. The product page lists them in its Specifications tab after the custom fields shown there, and the tab appears for a product that has rows and no fields. Rows are plain text, shown exactly as typed (<5 mm reads as written; HTML is not interpreted), up to 50 per product, with labels up to 100 characters and values up to 500; a row missing its label or value is not saved, and a message after saving names it. They are never used as filters — the tab points to custom fields for an attribute many products share. The sample products seed a few rows each
    • Specifications in every language. The Translations drawer has a Specifications box: one Label: Value per line, or two columns pasted from a spreadsheet. A translation replaces the whole list, the box shows how many rows the default language has, and an empty box shows the default language's rows. A line that cannot be read is reported with its language and line number
    • Specifications travel with the product: in its structured data (each row an additionalProperty, always — every row is on the page), in Smart Search, in the catalogue API and the MCP product tool (after the custom fields, with source: "product" and no name; fields now say source: "field"), and in CSV export and import as a Specifications column, one row per line, with Specifications [vi-VN] for translations. A blank cell leaves the list alone, so a file never clears it
    • For developers: Solidshop\Lib\Product\ProductSpecs (the one set of rules every writer uses: normalise() with its warnings, the line format, JSON). The site product item carries the rows decoded on $item->specs, and the product/fields.php layout renders them after the fields
    • The System page checks your template overrides. The Template overrides tab used to list the override files it found and leave the judgement to you. It now compares each override with the Solidshop file it replaces through the @version both carry, and shows a status per file: Outdated (copied from an older version of the file, or Joomla recorded that the file changed in an update since), Unknown age (no @version Solidshop can compare), Up to date, Not checked (the file it replaces has no @version) and No Solidshop file (an alternative layout of your own). Overrides of plugin pages, of modules and in an administrator template are checked the same way, an override that Joomla's Updated Files list knows about links there so you can mark it checked, and only an outdated override turns the summary red. Paths are shown relative to the site root
    • For developers: every file a template can override — the component's tmpl/ and layouts/ (site and administrator), each mod_sshop_* module's tmpl/, and the views and layouts the Solidshop plugins ship — now carries a real @version in its header: the version of the extension that ships it, raised whenever the file changes. Copy the header along with the file and the check dates your override; raise the @version once you have brought it up to date. The check is Solidshop\Lib\TemplateOverride (pure, unit-tested) behind TemplateOverrideHelper in the administrator component
    • Solidshop in Joomla's administrator menu. Solidshop has a top-level entry right below Home Dashboard, grouped Catalog / Sales / Customers / Marketing / Configuration / Localization / System, on every site. Until now that grouping was an opt-in menu preset that replaced the whole administrator menu; everyone else had a flat list of 26 links under Components. On a phone the entry is behind Joomla's menu button. Each user sees only the links they may open: a screen that needs Manage order, Manage product, Manage customer or admin rights on Solidshop drops out of the menu for a user without that permission, where it used to answer the click with an error
    • A Solidshop dashboard. The grid icon next to the entry opens a Joomla dashboard for Solidshop: a card for each menu group and one for the Dashboard, and the pending, unpaid and unfulfilled order tiles across the top. They are the tiles the Quick Icon - Solidshop plugin puts on the Home Dashboard, which keeps them. Like any Joomla dashboard it takes modules of your own
    • For developers: plg_system_solidshop builds the entry from the component's presets/solidshop.xml (Joomla\Plugin\System\Solidshop\Menu\AdminMenu), which is also the dashboard's card layout, so a new administrator view needs its link there as well as in the manifest's <submenu>. A preset item's permission attribute now hides it from the menu entry as well as from the cards. plg_quickicon_solidshop also answers the solidshop_quickicon quick icons group
    • Variants in structured data. A product with variants is described to search engines as a ProductGroup, each variant a product of its own: its SKU, its barcode, its image, its price and stock, and a link that opens the page with that variant picked. The group is identified by the product's id (productGroupID). Options named Color or Colour, Size, Material or Pattern, and any option shown as colour swatches, become the variant's color, size, material or pattern and are listed in variesBy; other options stay in the variant's name ("Tee - S / Red"). Until now a product with variants was one Product with a list of offers, prices and stock with nothing to say which variant each belonged to. A product without variants stays a Product with one offer
    • Barcodes as GTINs. A barcode that is a valid GTIN (UPC, EAN, ISBN-13, GTIN-14: the right length and a check digit that adds up) is published as gtin8, gtin12, gtin13 or gtin14, on the product or on each variant. Any other barcode, such as a warehouse code, is left out
    • Sales in structured data. An original price above the price becomes the offer's struck-through price (priceSpecification with StrikethroughPrice)
    • Limit a product to one per order. A new Limit to one per order switch on the product's Inventory tab lets a shopper buy one of the product in an order, whichever variant they pick, the way WooCommerce's Sold individually does. The product page shows no quantity box for it, the cart and the mini-cart state its quantity as text, and adding it again, adding a second variant of it or asking for two is refused with a message that says why. Buy now on a product already in the cart goes on to checkout. A cart filled before the switch was turned on is brought back to one when the cart or checkout page shows it, with a message, and an order is never placed with more. New subscription products start with the switch on, because a paid subscription line starts one subscription for its quantity: two in the cart is one subscription for two, not two subscriptions. Existing products keep selling as they do until you change them
    • The Batch button on the Products list works. It opened nothing; it now opens a dialog that sets Limit to one per order on every selected product at once — filter the list by product type, tick them all, choose Yes. CSV export and import carry the setting as a One Per Order column, which also reads WooCommerce's Sold individually? header
    • For developers: Solidshop\Lib\Seo\ProductSchema builds the node from resolved values and Solidshop\Lib\Product\Gtin reads a GTIN out of a barcode, both pure and unit-tested. onSolidshopProductJsonLd listeners now receive a ProductGroup for a product with variants — see Upgrade notes
    • For developers: OrderPaymentStatusChangedEvent (onSolidshopOrderPaymentStatusChanged) fires whenever an existing order's payment status is stored with a new value, whoever stores it: a gateway's return or webhook, a refund, checkout voiding a failed payment, the order screen. OrderTable::store() dispatches it after the row is written, so a gateway added later is covered without doing anything; the order screen's model defers it (OrderTable::deferPaymentStatusEvent()) and dispatches it itself once the lines are written and its transaction committed, next to OrderStatusChangedEvent. Both import the solidshop plugin group just before they dispatch, so its plugins hear a payment a gateway records from its own com_ajax endpoint (PayPal's capture, Stripe's confirm step), a request that loads only the solidshoppayment group. A listener that throws is logged and does not fail the write. It is not fired for a new order. OrderStatusChangedEvent is unchanged and still comes only from the order screen and OrderHelper::saveOrder(). Core's on-payment invoices and refund restock now listen to the new event. The Subscription plugin (1.0.3) starts, extends and ends subscriptions from it, through the new Solidshop\Lib\Subscription\SubscriptionOrderSync; the rules it applies are the pure, unit-tested SubscriptionPurchase, and SubscriptionPeriods records which order paid for which stretch of a subscription
    • For developers: AfterOrderCreatedEvent also fires for an order created on the order screen, after its lines are written and before its status events, so listeners see a manually entered order the way they see a checkout one
    • For developers: RenewalPricingResolver::resolve() takes the subscription, the plan product and the source order — no longer the source order's lines — and always returns a RenewalPricing: a renewal bills the subscription line alone
    • For developers: Solidshop\Lib\Cart\SoldIndividually is the one-per-order rule (pure and unit-tested), asked by every path that sets or grows a cart line. The field/quantity.php layout takes a fixed key that states the quantity over a hidden input
    • For developers: ProductPageTabsEvent::getTabs() leaves out a tab whose html is blank, so a listener whose layout renders nothing leaves no empty tab on the page
    • For developers: #__sshop_orders.prices_include_tax records whether an order's prices included tax; Solidshop\Lib\Order\OrderTotal::grandTotal() and ReportQueryHelper::grandTotalSql() read it instead of the current setting. #__sshop_tax_rates.is_inclusive is dropped and TaxChoice::ratePayload() loses its fourth parameter
    • For developers: TaxHelper::computeOrderTaxBreakdown() taxes an order's lines and its shipping in one call and returns a Solidshop\Lib\Tax\TaxBreakdown: rows() for what an order records (shipping tax in rows of its own, is_shipping_tax), byRate() for a summary. Checkout's tax comes from CheckoutHelper::taxBreakdown(), which the checkout page and the order share. computeItemTaxBreakdown() takes an optional price mode, so an existing order is taxed the way it was placed. Solidshop\Lib\Order\OrderTaxRows writes an order's tax rows

    Fixed

    • Security: the storefront listing no longer takes its scope from the URL. A crafted listing URL could make the product listing show unpublished and trashed products, by name and price, to any visitor. The listing now ignores every request parameter that sets what it may list; the filters a shopper ticks, the search term and the sort are unaffected
    • Security: the bundled libraries move past their published advisories. Dompdf 2.0.8 becomes 3.1.6 (local files read or probed through SVG images and @font-face, a chroot bypass, memory exhausted by declared image sizes). Twig 3.24 becomes 3.30 (PHP code injected through a crafted {% use %} template name or a _self macro reference, and a series of sandbox bypasses). Guzzle 7.10 becomes 7.15.5 and psr7 2.9 becomes 2.13.1 (host confusion, CRLF injection, cookie scope, proxy credentials sent to the origin). Dompdf draws invoice PDFs, Twig renders every e-mail including the templates edited under Stores → Email Templates, and Guzzle carries the address lookup
    • Security: only store managers can read and change e-mail templates. The Email Templates tab sits on the store screen, which needs Solidshop administrator rights or the right to manage shipping or payments, but the requests behind it — open, save, preview, restore previous — accepted any user allowed into the Solidshop administrator. They now ask for the same rights as the screen
    • Security: e-mail templates render in a sandbox. A template edited in the administrator could call PHP functions by name (map('…')) and reach the application, the request and the signed-in user, and through them the site's configuration, database password included. Templates now render with an allow-list of tags, filters and functions — everything the shipped templates use plus common formatting filters — can read the values they are sent with but call no method on them, and no longer see the app, input, lang, user and uri variables or the JPATH_* paths. A saved template that steps outside the list no longer stops the e-mail: it goes out with the shipped default for that e-mail, the reason is logged (category com_solidshop), and Preview shows it so the template can be fixed. Saving a template now refuses one that steps outside the list, does not parse or includes a file that does not exist, instead of storing it. Templates also no longer receive the store's payment and shipping-carrier settings, which hold the Stripe, PayPal and Square keys and the Shippo API key: anyone allowed to edit templates could print them into an e-mail sent to themselves. The same settings are no longer copied into each queued e-mail either
    • Security: with Joomla's cache on, guests are no longer shown each other's pages. With Global Configuration → Cache switched on, the first guest to open the cart, the checkout, its order confirmation or the order tracking page had that page stored, and every later guest was shown it: another guest's cart, name, address and order. Catalogue pages were stored in the currency the first guest had picked, with promotions worked out from that guest's cart. Those pages are now never cached, and catalogue pages are cached only for guests who have not picked a currency, filled a cart or entered a coupon; any other guest gets a page of their own. Joomla's System - Page Cache plugin, which stores whole pages, now skips every Solidshop page, and other pages for a guest with a cart, a chosen currency or a recently viewed product. Signed-in customers were never affected
    • E-mails built by a task that cron runs link to your site. A cron line with no --live-site gave a subscription reminder's Renew button and the store logo the address https://joomla.invalid/…, and one whose address had no trailing slash a path under cli/joomla.php. The missing slash is now corrected, and with no address at all the links are left out rather than broken. The System page's Scheduled tasks list says, for the subscription task, how to give cron the address when Live Site is not set
    • The currency switcher's links work on a cached page. Shown as links, the switcher put the visitor's form token in each link, and a page stored by the System - Page Cache plugin kept the first visitor's token, so switching failed for everyone else. The links are now buttons in a small form, which the cache gives each visitor's own token; they look the same. A template override of the switcher's links layout (mod_sshop_currency default.php) keeps the old links: the System page lists it as older than the file it replaces
    • The storefront pages the installer creates always show under Menus. Installing filed Products, Cart, Checkout, Wishlist and Account under the menu mainmenu, whatever the site's menus were called. Where that menu had been renamed or deleted the pages worked, but no screen listed them, so they could be neither edited nor removed; where it existed, five links appeared in the site's navigation unasked. A fresh install now files them in a menu of its own, Solidshop, which no module shows. Updating gives pages stranded that way a menu, Solidshop pages (mainmenu): nothing moves, and pages in a menu the site has stay where they are. Uninstalling removes the menu Solidshop created once nothing else is in it
    • The System page's file check no longer flags the shipped library. Every install reported about 650 of the library's third-party files as modified, and PayPal and Square each reported two files missing, because the checksums were taken before the package was assembled. They are now taken from the files that ship, so a clean install reports nothing
    • Solidshop installs on a site upgraded from Joomla 3. On such a site one column of Joomla's content types table still requires a value, and the row a fresh install adds there for Solidshop products gave it none (NULL), so the install stopped with a database error
    • Orders for products with no sales statistics row count as sold again. Products the sample data adds, among others, have no statistics row, and when an order holding one reached a status that counts as sold — at checkout or on the order screen — creating that row failed with an error after the order was saved, so the product's sold count never moved. The row is now created
    • Filter counts match the products a filter lists. The Filters module counted every published product, so a count could promise products the page it led to did not show: ones in an unpublished category or outside their publish dates, outside the menu item's categories, not on sale on a Deals listing, or not matching the search term. Every count now comes from the same query as the listing, and the price slider spans the products the listing can show rather than the whole catalogue
    • Filtered pages are never served from the page cache. With Joomla's cache switched on, a visitor who filtered, sorted or searched a listing could be shown the page cached for the unfiltered listing. A listing carrying a filter, a sort or a search term now skips the cache; the plain listing and its later pages are cached as before
    • Filter values come back when they have products again. With Hide empty filters on, a category, brand or tag hidden because the current filters left it empty stayed hidden until the page was reloaded, and so did the rating and on-sale sections. They now reappear as soon as another change gives them products. A ticked value that a later filter leaves empty can always be unticked: after a page reload it came back greyed out
    • Hide empty filters works with Show counts off. After the first filter change it stopped hiding anything
    • Filter counts sit after their value on right-to-left sites. With a Latin value such as a brand name or a size (S, XL) on a Persian or Arabic page, the count landed between the checkbox and the value
    • Template overrides of the recurring invoice screens load again. The Invoice plugin's Recurring list and edit views pushed their own template path in front of the administrator template's override folder, so an override of either screen was silently ignored
    • Administrator template overrides of three layouts apply. The customer screen's address list (address/customer_list.php), the product form's search-engine preview (field/search_snippet.php) and its option editor (field/variant_option.php) were rendered with a fixed base path that Joomla searches before the template. An override of any of them in the administrator template was silently ignored. The storefront's account address book was not affected: it already rendered through Solidshop's layout helper, so a site template's override (Foundra's included) applied there
    • The variant image picker lists images only. It offered every product media item, so a video's poster and a 3D model's viewer were listed as if they were pictures, and a video poster stretched the modal
    • Formatted addresses print the customer's first name. The last name overwrote the first, so every formatted address showed the last name only: order emails, invoices (on screen and PDF), the checkout address lists and confirmation page, order tracking, the account order page and address book, and the admin order page. The two names now follow each country's order — given name first in the United States, family name first in Vietnam
    • Product structured data states the price the page shows. It published the price as stored, so a store that enters prices without tax and shows them with tax (the default) told search engines a lower price than shoppers read. Prices also went out as text with six decimals ("20.000000"); they are numbers in the currency's precision now
    • A variant's stock in structured data follows the variant. Availability read the product's Track quantity switch instead of the variant's own, the one checkout uses, so a variant could be marked out of stock that checkout sells, or in stock that checkout refuses
    • The product description in structured data is plain text. The summary's HTML went out as written, tags included
    • Add to cart works on a link to a deleted variant. The product page script stopped on a ?variant= id that no longer exists before it wired up Add to cart and Buy now, so both buttons did nothing on that page. Search engines now follow these links, so an old one can bring shoppers in
    • Custom field labels written as language keys are translated. The product page's Specifications tab, the product's structured data, the catalogue API and the fields captured on an order printed a label exactly as typed, so a label set to a language key — one definition that reads in every language — showed the key itself. Labels and field group titles now go through the site's language files, as Joomla's own field display does
    • A product translation without a name keeps the product's name. A translation that left the name blank showed the product with no name at all in that language, and saving a second such product in the same language failed. Three ways led there: a CSV import with only some translation columns filled (Description [it-IT], say) overwrote the translated name and URL alias already stored for that language with blanks; the same file for a product with no translation yet created one with neither; and the Translations drawer accepted a translation with only a description. Now a translation without a name or URL alias of its own uses the product's own, an import only changes the translation columns its file fills, and the language switcher links such a product to its working address. The update repairs translations already saved with a blank name or alias
    • An order entered on the order screen is treated like one placed at checkout. A line added in the administrator was stored without its product's type, details and capabilities, and the order never announced itself as new, so an order created there got no download links, no booking, no invoice when the store invoices on order, and no subscription. Lines added there now record what their product is the way checkout does, and a new order gets the same follow-up as a checkout order
    • Invoices set to be created on payment are created for every payment. With Generate invoices set to on payment, only an order marked paid on the order screen was invoiced: a payment recorded by PayPal, Stripe or Square — at checkout or later by webhook — created none, and neither did a free order or an order entered as already paid. All of them are invoiced now
    • A refund your payment provider reports gives the stock back. A full refund restored stock only when it was issued from the order screen; one issued in PayPal's or Stripe's dashboard, which reaches the store by webhook, left the stock taken
    • Ending a subscription keeps the user groups another one still grants. When the Subscription plugin ended a subscription — at expiry, on a plan change, or from its administrator screen — it kept a group only while another active subscription of the same customer granted it. A paused, past-due, or cancelled but still paid-through subscription granting the same group lost it too, and nothing gave it back. Every subscription that still grants access now counts
    • Order statuses on the storefront are readable in any colour. The account pages, order tracking and the order confirmation printed a status in its own colour as text, and the default colours are badge colours: Archived, where every completed order ends up, was 1.2:1 against a white page, Draft and On hold 1.3:1, Canceled and Unfulfilled 2.5:1, where text needs 4.5:1. The label now prints in the text colour with the status colour as a dot beside it, in both colour schemes. Foundra 1.1.0 shows the same as a neutral chip
    • Every account page, the cart, the checkout and order tracking have one main heading. The account pages' titles ("My Orders", "Invoices", "Order Detail") and the tracking page's were second-level headings with nothing above them, the checkout and the empty-cart checkout had no title at all, and the cart's title vanished with the cart when it was empty, so screen-reader users had no main heading to jump to. Each page now titles itself with its main heading ("Checkout" on the checkout) and the headings under it follow without skipping a level. With Show Page Heading on in the page's menu item, which these pages ignored before, the item's page heading becomes the main heading and the page's title sits under it, as on Joomla's article pages; it is off unless you switch it on
    • The order tables name their last column. The column of View buttons in My Orders, the account overview's recent orders and Invoices had an empty header, so screen readers read its buttons without a column name; it is now headed "Actions" for screen readers. The Downloads pages printed the untranslated key JACTIONS in the same place
    • The checkout's order summary reads as a summary. The edit button beside "Order summary" had no name, so a screen reader announced only "link"; it is now "Edit cart". Subtotal, shipping, payment fee, discount and the estimated total were headings and filled the page's outline; they are plain rows now and look the same. The "Shipping address" label above a saved address was faded below readable contrast (3.1:1), and the "Home" or "Office" line under it is no longer a heading either
    • Order and invoice references read in any template. They print in the template's monospace face but the text colour: Cassiopeia's code pink is 3.8:1 on white. The struck-through original price on a product card was 3.6:1 in Cassiopeia and is now 5.8:1
    • The Downloads page says why a file cannot be downloaded in readable text, where a faded, button-shaped label was 2.5:1
    • The product gallery's pictures stay links to screen readers. The slider marked each one as a group and renamed it "1 / 3"; each keeps its link role and is named by its picture's alt text
    • Non-combinable discounts on different products both apply. A cart kept one non-combinable discount in all, so "35% off Product A" and "30% off Product B", each set to Product level scope, gave a cart holding both products only the first: B paid full price, and the customer paid more than by buying the two in separate orders. A renewal added to a cart that already held another product lost its discount the same way. Non-combinable discounts now never stack on the same product instead: they are taken in priority order, and one that reaches a product an earlier one already discounts is skipped. Two rules on the same product still do not add up, and a Cart total discount, which reaches every product, competes with all of them by priority as before. The order lists and counts the use of each discount that applied
    • Shipping is taxed by the rates marked On Shipping. The box was saved but never read, so no order paid tax on its shipping. A rate with it ticked now taxes the shipping, after any shipping discount, the way the rate taxes the goods: added on top with tax-exclusive prices, taken out of the shipping price with tax-inclusive ones. An order with products of several tax classes splits its shipping between them by what the products in each class cost. The checkout summary, the order screens, the order e-mail and the invoice show it in the rate's one line, and the Tax collected report lists it as shipping tax
    • Orders created or changed on the order screen get their tax worked out. An order created there recorded no tax, and changing an order's products kept the tax it had before. Saving the products now taxes the order the way checkout does, at its shipping address and with the current rates, and the order summary shows the tax while the products are being edited
    • Changing Price input type no longer changes the totals of past orders. Every order's grand total — on the order screens, in the lists, the dashboard, the reports, invoices and the amount sent to Square — was read with the setting as it is now, so switching it moved the totals of every order placed before. Each order now records whether its prices included tax when it was placed; the update records the current setting on the orders already there
    • For developers: StoreTable, OptionTable, OptionValueTable and LocationTable delete the row they have loaded when delete() is called with no key, as Joomla's Table::delete() does, and accept a key array by column name. With no key, the store table raised a warning and deleted nothing, and the other three skipped the cleanup of their child rows, so an option value's delete then failed on its variant combinations' foreign key. Solidshop's own screens always pass an id and were not affected

    Changed

    • A fresh install turns the e-mail queue's task plugin on. Task - Solidshop Email Queue was installed disabled, so a new store offered no task type to send its order e-mails with until someone found the plugin. A fresh install now enables it, as it does the core payment methods; creating the scheduled task (System → Manage → Scheduled Tasks) is still the merchant's step, and an update leaves the plugin as it is
    • Invoice PDFs are drawn by Dompdf 3. The Detailed layout now prints on A4 landscape, as its name and the documentation say; Dompdf 2 ignored the page size the layout asks for. Foundra's invoice gets its accent colour, borders and grey labels in the PDF, which Dompdf 2 dropped because they are CSS variables. The Default, Compact and Modern layouts print as before. In an SVG logo, text set in a named font with a space in it (font-family="DejaVu Sans") now prints in Times: use a generic family such as sans-serif, or convert the text to outlines. PHP 8.4 no longer logs deprecation notices for every PDF
    • For developers: Dompdf's font and SVG libraries are now dompdf/php-font-lib and dompdf/php-svg-lib (they were phenx/*); the FontLib\ and Svg\ namespaces are unchanged. Twig's compiled-template cache is keyed on its version, so templates compile afresh after the update
    • For developers: e-mails render through Twig\Sandbox\Sandbox with Solidshop\Lib\TemplateEngine\EmailSecurityPolicy. Email::compileTemplate() returns a sandboxed template unless its new $trusted argument is set (for shipped files only), and Solidshop\Lib\TemplateEngine\Twig::getSandboxed() sits beside getInstance(). Neither environment registers globals any more. A partial a plugin contributes through TwigPathsRegisterEvent renders inside the sandbox when an e-mail includes it, so it must keep to the same list. Who may edit templates is Solidshop\Lib\Email\EmailTemplateAccess::canEdit(). store.params reaches a template, and the e-mail queue's payload_json, without its payments and shipping_carriers groups (Solidshop\Lib\Email\TemplateData); a plugin that needs one of its settings in an e-mail passes it through BeforeEmailRenderEvent, as bank transfer now passes its details as bank_transfer. Email::renderPreview() renders a body with the preview's sample data
    • Filtered listings are kept out of search results. A listing narrowed to one category or one brand is still indexed, under its own heading. Any other filter state — two categories, a price band, a rating, the on-sale toggle, a tag, or several filters together — now asks search engines not to index it (noindex, follow), so its links to products are still followed. Before, only a listing with two or more different filters was kept out, which left every single-filter combination in the index
    • For developers: the listing's scope — published state, publish window, view levels, menu-item categories, search term, featured and on-sale modes — is Solidshop\Lib\Product\ListingScope, applied by ProductListingQuery::applyScope(); the site ProductsModel exposes it as getListingScope(). FiltersHelper::computeFacetsForResponse() takes the scope as its second argument. In the Filters module's markup a checkbox facet is a section with data-solidshop-facet-param (its URL parameter), each value row carries data-solidshop-facet-item, and counts are keyed data-facet-count="{param}:{id}". Every facet row is rendered, empty ones hidden
    • Components no longer lists Solidshop. Its links are in the Solidshop entry. A custom administrator menu, and a site with the System - Solidshop plugin switched off, keep the list under Components
    • Phone numbers are tidied when saved: spaces, dashes, dots, slashes and brackets become single spaces, and the (0) some countries write after the code is dropped, so +44 (0)20 7946-0958 saves as +44 20 7946 0958
    • In the administrator, phone fields no longer offer to fill in the admin's own number: the number typed there is a customer's
    • Once saved in the new form, the store phone is published with its country code in structured data, /llms.txt, the catalogue API and the email footer
    • The product gallery's slider loads from your own site. Swiper, which drives the product page's image gallery, was fetched from a CDN on every product page, at whichever 11.x release was newest that day. Solidshop now ships Swiper 11.2.10 in media/com_solidshop, with its MIT licence, so a product page makes no third-party request for it and the version changes only with a Solidshop update
    • All 22 translated locales carry this release's strings — the Filters screen and module, swatches, specifications, phone numbers, the override check and the administrator menu groups
    • A tax rate no longer has an Inclusive box. It was saved but never read: whether prices include tax is the site's Price input type, for every rate. The rate form now says which way the site's prices are entered and where to change that. The update removes the stored flag

    Upgrade notes

    • Check your edited e-mail templates. Open each template you have changed under Stores → Email Templates and preview it. If Preview reports something templates cannot use, that e-mail is being sent with the default template until you change it; templates you never edited are unaffected. A template that prints the bank details itself, instead of including the shipped bank-transfer block, now reads them from bank_transfer (for example bank_transfer.iban) rather than store.params.payments.banktransfer
    • A new install no longer puts shop links in your navigation. Products, Cart, Checkout, Wishlist and Account go in the hidden Solidshop menu; add a Menu Item Alias to your own menu for each page you want visitors to find. Existing sites keep their menus as they are
    • If you use Foundra, update it to 1.1.0 straight after this update. Foundra 1.0.1 keeps working on 1.7.0, but it shows every option as text buttons, no specification rows, and every one of its overrides as Unknown age on the System page. Foundra 1.1.0 requires 1.7.0, so update the core first
    • The filter index is built during the update. On a large catalogue the installer stops after about 20 seconds and Catalog → Filters shows how many products are left, with a Finish building button; the storefront works meanwhile, and filters simply cannot find the products not indexed yet. No filter exists until you declare one, so nothing changes on the storefront until you do
    • Template overrides of the Filters module (mod_sshop_filters default.php) need updating from the shipped layout: the category, brand and tag checkboxes are now found through data-solidshop-facet-param, so an older override's checkboxes no longer filter the listing, and only the shipped layout renders the new option, custom-field and in-stock sections. The System page lists such an override as older than the file it replaces. Foundra ships no override of this module
    • Template overrides of product/fields.php show no specification rows until they are updated from the shipped layout. The custom fields keep rendering as before. Foundra 1.1.0 carries the updated override; an override that reads $item->specs should escape both parts, since rows are plain text, not HTML
    • The JSON-LD on product pages escapes < and > (as \u003C / \u003E). The data is unchanged for anything that parses the JSON; a test that matched the raw page source for a value containing those characters needs updating
    • A plugin that edits product structured data (onSolidshopProductJsonLd) gets a ProductGroup for a product with variants. Facts about the whole product (ratings, reviews, extra properties) go at the top level as before, and the Reviews plugin needs no update. Offers moved: a ProductGroup has none of its own, each entry of hasVariant carries its own offers, and a Product's offers is now a single Offer rather than a list of one
    • The Solidshop dashboard is set up once. The update to 1.7.0 adds its menu cards and order tiles where nothing sits in their positions yet (cpanel-solidshop, icon-solidshop); no later update adds them back, so a module you remove stays removed. If you switched Quick Icon - Solidshop off, the dashboard's Orders module stays empty until you switch it on
    • If the Solidshop menu preset is your whole administrator menu, nothing changes: the menu shows the preset as before, without the new entry on top
    • Your existing overrides show as Unknown age until you stamp them. An override copied before this release carries no @version (Solidshop's own files carried a placeholder until now, or nothing), so the new check cannot date it. Compare it with the file it replaces, then copy that file's @version line into the override's header. This applies to Foundra 1.0.1 too: its overrides gained their stamps after 1.0.1 shipped, so a site on Foundra 1.0.1 sees them as Unknown age (or Outdated, where Joomla recorded a changed original) until it updates to Foundra 1.1.0
    • The override notice in every administrator file used to name the site template folder; it now names /administrator/templates/TEMPLATENAME/…, where those overrides actually live
    • Template overrides of the quantity box (field/quantity.php) and of the pages that render it (product/default.php, cart/default.php, minicart/items.php) show a quantity box for a product limited to one per order until they are updated from the shipped files. The limit holds either way: the cart refuses a second unit. Foundra 1.1.0 carries the updated overrides
    • Template overrides of field/options.php keep working: the radio inputs, their names and ids and the variant-check class are unchanged. An override written before this release shows every option as text buttons until it is updated from the shipped layout (or Foundra's), which is where the swatch markup lives. The option name moved from a <label> pointing at nothing to a <legend>, so the values form a proper radio group
    • Template overrides of the account pages, the cart, the checkout and order tracking keep working, with the old headings and status colours, until they are updated from the shipped files; the System page lists them as older than the files they replace. Two new layouts carry the shared parts: order/status.php (a status with its colour dot) and page/heading.php (the menu item's page heading). Each page's view has $this->pageHeading, whose tag() is the element for the page's own title and tag(1) the one for the headings under it. Foundra 1.1.0 carries the updated overrides
    • Saved numbers are not rewritten. A number without a + code stays as it is until the form it is on is next saved. Opening that form reads the number in the address's country and shows it in international form, so saving stores that. A number that cannot be read has to be corrected before the form saves — including in the order screen's address modal, which used to save any text
    • Orders placed from an address saved before this release keep that address's old number: an order is a copy of the address at the time of sale
    • To limit the country codes offered, unpublish countries under Solidshop → Countries. That removes them from the Country field too
    • Template overrides: the field renders through a new layout, form/phone.php, which a template can override at html/layouts/com_solidshop/form/phone.php. The address layouts are unchanged, so existing overrides of them — Foundra's included — show the new field without an update
    • Check the On Shipping box on your tax rates. It did nothing before this release; from now on a rate with it ticked taxes the shipping of every new order. Tick it where your country taxes delivery and clear it where it does not. Orders already placed keep the tax they recorded
    • Template overrides of checkout/default.php keep showing the goods' tax but not the tax on shipping, which the order still records, until they are updated from the shipped file: the summary now takes its tax from CheckoutHelper::taxBreakdown(). Foundra 1.1.0 carries the updated override
  3. 1.6.0

    Stable

    The release about a store's first hour. A fresh install opens on a setup wizard for the sample store, then a Store setup checklist tracks what is left. The sitemap covers the whole site rather than only the catalogue, and a merchant can choose what the product page shows. Tax is now charged by zone, as the Tax tab always implied, and order lines record their cost at the time of sale.

    Schema: one nullable column on order lines.

    Added

    • Setup wizard for a fresh store. While the store email is still the sample store@example.com, the dashboard offers Set up your store: the store's details, how it charges tax (not at all, one rate for the country, or later) and one payment method with its own settings, saved together on Finish setup. It keeps no state of its own, and replaces the sample tax only while it is still untouched. Works without JavaScript, in dark mode and right to left
    • Store setup checklist on the dashboard — ten steps, from store details and a first product to live payments, worked out from the store's own data on every visit and each linked to the screen that completes it. Nothing is stored as done, so a step that is undone reopens. Tax and shipping can be marked not needed; the panel can be hidden per user and collapses to one line when complete
    • Move the sample products to the trash from a notice on the Products list. Only the three seeded products are touched, never one that has been ordered
    • A sample tax setup on fresh installs — a Standard class, an Illinois zone and a 6.25% rate matching the sample store's address, so a first test order shows a tax line
    • The sitemap covers the whole site. The new core plugin Solidshop - Site Content Sitemap adds menu items, articles and article categories to the sitemap a store has already submitted, so no second sitemap extension is needed. Noindex pages, sign-in, search, cart, checkout and account pages, and articles no menu item leads to, are left out. Enabled on install and once on this update
    • /sitemap.xml — Options → Sitemap → Serve at /sitemap.xml, off by default because another extension may already serve that path. System → Overview warns when a sitemap.xml file shadows it or the site is set to noindex
    • Choose what the product page shows — a new store Storefront tab with switches for the sold count, the share button and the wishlist button, all on by default, in Cassiopeia, Foundra and the booking and download product pages. The sold count is now a translated, plural-aware string
    • For developers: SetupStepsRegisterEvent (add a checklist step), SitemapSourcesRegisterEvent (add a paged sitemap source; SitemapUrlsEvent stays for small sets), PaymentPluginAbstract::isConfigured() / isTestMode() (PayPal, Stripe and Square override them in their next releases and work without them meanwhile), and Solidshop\Lib\Store\StoreParams / ProductPageSettings for typed store settings

    Fixed

    • Tax rates apply where their zone says. A rate's zone was never consulted, so every rate was charged on every order wherever the shopper was. Checkout now charges the rates whose zone covers the shipping address — a state territory covers that state, a country territory the whole country, and overlapping zones stack — and updates as the address changes. Prices shown before checkout use the store's own address. Order tax lines now record the rate they were charged under (tax_rate_id)
    • "Store default" taxes the product. A product left on - Store default - paid no tax at all; it now follows the store's default tax class
    • Still open in tax: ZIP-range territories, tax on shipping, the per-rate inclusive flag, and tax in the order editor's recalculation
    • Editing an order no longer rebuilds its lines. Saving the order editor deleted and re-inserted every line, losing download links, line types, the product name at the time of sale and the line ids that reviews and subscriptions point at. Lines are now updated in place in one transaction, and a line on a shipment cannot be removed. A row added after removing one from the middle is no longer lost
    • One Product per product page. Product modules below a product page declared every card as a Product of its own, which cost the page its rich result in Google. Cards on listing pages now carry image, description and sku
    • Sitemap URLs follow the SEF plugin's Site Domain, so they match the pages' canonicals. A shard that fails answers 503 with Retry-After, and only a guest's rendering is cached
    • Admin screens that showed a blank or a raw language key: 23 strings, including an unnamed entry in a menu item's Layout dropdown and unlabelled search boxes. Brands and Stores show their empty-state page
    • The loading indicator is announced to screen readers and follows the template's colour scheme (--solidshop-loader-* variables)
    • Outline buttons on admin screens were unreadable in Atum's dark mode — navy, green, red and blue text on a near-black page. They now use the dark theme's own colours on every Solidshop admin screen, plugin screens included
    • The Cost per item help text described the compare-at price
    • The store's Time zone field offers UTC. Without it, a store set to UTC (as the sample store is) was saved as Africa/Abidjan
    • The sample T-shirt was seeded checked out by a user that does not exist (existing installs: System → Global Check-in)

    Changed

    • Order lines record their cost at the time of sale — the variant's Cost per item, else the product's, else unknown, and never recomputed. Nothing displays it yet: a profit report can only cover orders placed after recording began. Generate variants leaves the cost empty rather than 0
    • The store phone number is optional; a blank one is left out of structured data, /llms.txt, the catalogue API and the email footer

    Upgrade notes

    • Check each store's Tax tab. Tax now depends on the shipping address: a rate on a zone with no territories or on an unpublished zone stops being charged, a shopper outside every zone pays no tax, and products on Store default start paying the default class's rates. With tax-inclusive prices, a shopper outside every zone pays the same price with no tax taken out of it
    • Foundra users: update to Foundra 1.0.1 at the same time. Foundra 1.0.0's checkout page shows tax at the store's address rather than the shipping address
    • 1.6.0.sql adds cost_per_item to order lines. Existing lines stay unknown: they are never backfilled from today's cost
    • Download links lost by editing an order on an earlier release are not recovered; re-issue them by hand
    • Product pages look the same after updating (every switch reads Show). A template override of product/stats.php or product/share_wishlist.php ignores the switches until it is updated from the new layout
    • The setup checklist appears on the first dashboard visit for admins with core.manage and collapses to one line on an established store. A store still on store@example.com is offered the wizard instead
    • The sample tax setup and sample product fixes apply to fresh installs only; an updated store keeps its own data
  4. 1.5.0

    Stable

    The release that gives a store a front page. Five new storefront surfaces — a slideshow hero, category tiles, a brand band, a recently-viewed strip and a Storefront home menu item — plus a Deals page built from the product's own compare-at price, so a landing page is modules rather than an empty article holding hand-written HTML.

    Alongside them: every store becomes discoverable to AI agents from its domain alone through /llms.txt, the admin gains an Extensions tab over everything Solidshop has installed, and prices get their decimal places back — a $104.32 product had been rendering as USD104, and being handed to payment gateways as 104 minor units.

    Schema: two nullable columns on brands, plus one guarded data migration.

    Added

    • Storefront home menu item (view=home) — a landing page is modules, and until now they needed an empty article to sit on. It prints at most a page heading (off when a hero carries the H1) and the store tagline, and does the head's work: title and meta description from the store, canonical on the site root, and one JSON-LD block with an Organization node and a WebSite node whose SearchAction points at the Products menu item. Nodes built by Solidshop\Lib\Seo\StorefrontSchema (pure, unit-tested); a new Tagline field on Store → SEO is printed on the page and published as the slogan.
    • Slideshow module (mod_sshop_slideshow, core bundle) — a slides subform of picture, eyebrow, heading, text and a button linking to a product, a category (RouteHelper::getCategoryRoute(), the URL that listing publishes as canonical), a menu item or a URL. CSS scroll-snap track, so swiping and keyboard scrolling work before any script runs and the first picture is fetchpriority=high; the script adds Previous / Next, dots, an optional 3–60 s timer with Pause and WAI-ARIA carousel semantics (paused on hover, on focus, off-screen and for reduced motion). One slide is a static hero. No slider library in front of the page's largest element.
    • Category showcase module (mod_sshop_categories, core bundle) — a 2–6 column grid or a scroll-snap strip of category tiles: everything below a parent to a chosen depth, or categories picked by hand. A tile borrows the first product's picture when the category has none, the optional count uses the listing's own predicates, empty categories are left out, and no tile links to a category the visitor may not view. The query count does not move with the tile count.
    • Brands module and brand logos (mod_sshop_brands, core bundle) — brands gain a logo (media field, resolved under the store's media folder), and the module prints a "Shop by brand" band, grid or strip, each logo linking to the listing filtered by that brand. Two queries whatever the band holds; brands with nothing published are left out. The logo plate stays light in both colour schemes, since brand artwork is nearly always dark ink on transparency.
    • Brands carry a store scope — a nullable store_id on #__sshop_brands, NULL on every existing row, meaning the brand belongs to the site and every store may use it. Solidshop\Lib\Product\BrandQuery is the single place that says which brands a store may use and resolves a name to an id; the CSV importer and the VirtueMart migrator go through it instead of assuming a brand name is unique across the table.
    • Recently viewed module (mod_sshop_recent, core bundle) — the shopper's own trail, written into the session by the site display controller (a guest's product page is served from Joomla's view cache, where the view never runs) and nowhere else: no table, no profile. Solidshop\Lib\Product\RecentlyViewed (pure, unit-tested) holds the rules — a repeat view moves rather than repeats, session junk is dropped, twenty ids are kept so a product that has gone gives up its place instead of shortening the strip. Cards carry the shopper's view levels.
    • Deals — sale surfaces on the product's own price pair. price_origin > price is now one predicate in ProductListingQuery, with four surfaces on it: a Products on Sale Only menu item (a Deals page), Show / Hide / Only plus a Discount ordering on the products module, an On sale filter toggle counted like every facet, and a Biggest discount sort key (discount_desc), also on the REST API and the MCP solidshop_search_products tool. The product row and nothing else: a discount granted at cart time is not a listing predicate.
    • The filters module folds into a drawer on narrow screens. Below Drawer Below Width (default 992 px) the panel moves into an off-canvas drawer and a Filters button appears on the listing toolbar beside the sort control. Filters still apply live; the primary button reads Show N results, a Clear all sits beside it, and the toolbar button counts the active values. Dialog semantics as the mini-cart drawer — focus trap, Escape, scroll lock, reduced motion, RTL. 0 keeps the panel inline.
    • /llms.txt agent-discovery file. Served at the domain root through a parse rule in the core system plugin, and at the raw URL index.php?option=com_solidshop&view=llms&format=raw (&store_id={id} for one store). Rendered on request from the store: name and summary, country, currencies and languages, the MCP endpoint and its tool names, the REST routes, the sitemap, up to 50 top-level categories with a visible product, policy pages, contact details, merchant notes, plugin sections and a platform credit. Declarative throughout — it states what exists and where, never instructs the agent; merchant text is escaped and headings in it flattened. text/plain, one-hour cache, X-Robots-Tag: noindex, and a physical llms.txt in the web root always wins.
    • AI-discovery settings — Options → AI discovery (llms.txt) (serve the file, per-store documents, list categories, platform credit; all on by default), two Store → SEO fields (Store summary for AI agents, also the store description in the MCP solidshop_get_store_info, and Notes for AI agents), and a System → Dashboard card with the URLs and two group-aware robots.txt checks (RFC 9309): which of GPTBot, OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot are shut out of the site, and which are shut out of the catalogue API — Joomla's stock robots.txt ships Disallow: /api/, so that row is red on every unmodified install and shows the Allow: line that reopens the Solidshop routes.
    • LlmsSectionsEvent (onSolidshopLlmsSections) so a plugin can append a store-aware section, and ToolRegistry::CORE_TOOLS, the pinned MCP tool names the file prints, asserted against the tools/list snapshot so the two cannot drift.
    • System → Extensions tab — every Solidshop extension on the site with its version, enabled state, pending update and anything wrong with it, then the add-ons published but not installed here. Rows are discovered from #__extensions by naming convention plus the three plugin groups we own, so a third-party plugin in them is reported too and the tab cannot go stale against later releases. Updates come from #__updates including the unmapped rows com_installer hides, and an extension shipping an update server with no update site row is flagged — Joomla would never offer it an update. What discovery cannot know is declared in Solidshop\Lib\Extension\ExtensionCatalog, guarded by two drift tests.
    • Regenerate images after a media-settings change. Derivatives are named after their size, so changing a size or the aspect ratio left the storefront asking for files that were never written. The media manager now counts the mismatched images and offers Regenerate images: a batched, resumable AJAX run with a written / up-to-date / failed summary, an optional force rewrite and an optional prune of sizes no longer configured. Same run on the command line — php cli/joomla.php solidshop:media:regenerate with --store=, --force, --prune, --dry-run. ThumbnailSizes and ThumbnailPlanner hold the decisions, pure and unit-tested; uploads now cut all four sizes from one decode.
    • sku on the product page's JSON-LD, on the Product node and every Offer; and Media::storeImageUrl(), one resolver for a store's logo URL.

    Fixed

    • Prices rendered without decimal places. Currency::parse() fell back to number_decimal_points = 0 while the same field's form default is 2, and no currency has ever shipped with params — so the fallback was what every store used, and a $104.32 product read USD104 everywhere. Precision is not cosmetic: toFlatAmount() multiplies by 10^precision for the minor-unit amount a gateway is charged, so the same order was worth 104 minor units — a hundredth of the real total.
    • Currencies whose ISO 4217 minor unit is not 2 are corrected with it — 0 for BIF, CLP, DJF, GNF, ISK, JPY, KMF, KRW, PYG, RWF, UGX, UYI, VND, VUV, XAF, XOF, XPF, ZWD; 3 for BHD, IQD, JOD, KWD, LYD, OMR, TND. Rows that already carry params are left alone — saving a Locale tab is an opinion an update must not overwrite.
    • Choosing a variant answered "Variant does not exist" for most combinations. The lookup joins the combinations table once per chosen value and bound each join's placeholder to the loop variable; Joomla's bind() holds a reference and reads it when the query runs, so every join carried the last value. Only a combination sorting first among those sharing that value ever resolved — shipped since 1.1.0. Each placeholder now binds to its own array slot.
    • A blank box in the variants grid discarded every variant edit. The grid posts '' for a blank box, and '' in a DECIMAL column is rejected under STRICT_TRANS_TABLES, so a variant with no compare-at price failed its UPDATE and took the new price with it — for every variant of that product. Blank price, compare-at, cost and weight now bind as NULL, blank quantity as 0. The failure was silent because the product model ignored the variant model's return; both loops now propagate it.
    • Product and category pages contributed no breadcrumbs. No storefront view had touched Joomla's pathway, so a product read Home › Shop — and the breadcrumbs module builds its BreadcrumbList structured data from that same pathway, so search engines saw the same gap. A product now appends its category (linked through the route its canonical uses) and its own name, unlinked; a listing narrowed to one category or brand names itself the same way; nothing is added when the menu item already is that page.
    • The mini-cart drawer's remove button and quantity stepper did nothing on every page but the product and cart views. Both primitives lived in order.js, which only those views load, while mod_sshop_cart correctly depends on com_solidshop.core alone; the stepper threw into a silent fetch handler before the badge could sync. Both are generic cart-line behaviour and moved to core.js.
    • Option buttons wrapped onto rows with no space between them — the values were inline-block labels in a container with no layout, so their only spacing was markup whitespace, which spaces nothing vertically. Now a wrapping flex row with an 8 px gap.
    • The products module ignored its own ordering and Featured settings — the model read only the shopper-facing sort key and defaulted it to popular, so a "Featured products" strip listed the same products as "Best sellers". ProductListingQuery gained applyOrdering() (an unknown key degrades to the default sort rather than failing the page) and applyFeatured() on show / only / hide; the module's ordering list gained Price and Units Sold.
    • A facet section with nothing in it printed a header over an empty box — with hide empty filters on, rows were skipped but nothing checked whether all of them had been, and since core ships no review plugin the Rating facet hit this on every storefront. Sections now gate on the rows that will render, in the template and after an AJAX refresh. Also: Clear All Filters left the boxes ticked over an unfiltered grid.
    • The four media size settings were never filtered — the attribute was misspelled (fitler="uint"), so 800px raised a warning on every image and an emptied field took the page down with a TypeError. They are now required, integer-filtered and bounded, and srcset candidates carry the width each file was actually cut at instead of four hard-coded defaults.
    • Capability badges on the order page were unreadable — bg-info text-dark was written against stock Bootstrap's light cyan, but Atum redefines --info to a dark blue, giving roughly 2.8:1, below WCAG AA. Dropping text-dark restores Atum's white at about 5.4:1 in both schemes; four badges were affected, and the order products table gained the edge gutter its neighbouring cards have.
    • The Stores list reported the country as the store's state — the state join selected the country table's columns.
    • The XML sitemap was served as text/html with no X-Robots-Tag — the view queued both headers and then closed the application before Joomla's response stage flushes them. Found while building /llms.txt on the same pattern.

    Changed

    • The default store a fresh install starts from. sql/sample.sql runs unconditionally, so its row is every merchant's first screen — and it shipped as Lotus S.p.A with an Italian address, contact@solidshop.app as the store email and Joomla's powered_by.png as the logo, in EUR against the US dollar rate table seeded beside it. Now My Store, US/USD matching the seeded Springfield IL location, store@example.com (RFC 2606; the field is the merchant's own notification recipient, so it cannot be blank), and empty legal_business_name and phone, both of which print as-is on documents carrying legal weight. Existing installs are untouched.
    • Fresh installs show a currency's sign rather than its code — $104.32, not USD104.32. Seeded onto the currencies that ship published rather than made a global default: how an existing store renders a price is not an update's decision. Switchable per currency under Currencies → Locale.
    • The sample catalogue has brands, so a plain install has a working Brand facet instead of a filter panel that silently drops the section.
    • The filters module renders only on view=products — a product page that inherits a listing's menu item inherited its module assignment too, and the panel there was a set of links to another page.
    • All 22 translated locales re-synced against en-GB — 161 keys each (AI discovery, media regeneration, the home menu item, the Extensions tab, the on-sale surfaces, the filters drawer, the products module's new options), rebuilt from the en-GB skeleton so key order matches line for line; existing translations pass through untouched.

    Upgrade notes

    • Schema. 1.5.0.sql adds image and a nullable store_id to #__sshop_brands (existing rows stay NULL — shared by every store), and sets number_decimal_points on the currencies whose ISO 4217 minor unit is not 2, only where params is unset, so a Locale tab you have saved survives.
    • Prices change on screen, and in what gateways are charged. A store that never opened Currencies → Locale has been formatting without decimals; the same catalogue now reads $104.32 where it read USD104. Nothing stored changes — but the flat amount handed to a gateway was a hundredth of the real total for a two-decimal currency and is now correct. Check any price set to compensate, and reconcile gateway records across the update.
    • The core package gains four site modules — mod_sshop_slideshow, mod_sshop_categories, mod_sshop_brands, mod_sshop_recent. Joomla installs modules unpublished and position-less; publish and place the ones you want. An update never touches an existing module layout.
    • Check System → Dashboard → AI discovery. Joomla's stock robots.txt ships Disallow: /api/, which shuts AI crawlers out of the catalogue API /llms.txt points them at; the card shows the single Allow: line that reopens the Solidshop routes. The file is on by default and can be switched off under Options → AI discovery.
    • A storefront with a customised products toolbar keeps the filters button in the module's own position rather than on the toolbar — the drawer needs the slot the shipped toolbar template renders.
  5. 1.4.0

    Stable

    A release about the hours spent inside the admin. The two Core 1.4 roadmap items land — an Email Queue screen so a failed send is no longer invisible, and a quick search box in the administrator header — and the product edit form is rebuilt around product types, so a product only ever shows the tabs and defaults that apply to what it is.

    It is also the core Downloadable Products 1.0.0 (free) pins as its minimum. The invoicing that ships in core gained an approval workflow that actually gates PDF generation, the customer email and customer visibility, plus a privacy fix — cached invoice PDFs are no longer reachable by guessing an integer.

    No schema changes.

    Added

    • Email queue admin UI + resend order email — failed sends are no longer invisible. A new Email Queue screen (Components → Solidshop → Email Queue, also in the Solidshop admin-menu preset under System) lists every queued email with recipient, subject, context, the related order (linked), delivery status badge, attempt count and the last error; filter by status/context, search by recipient/subject (id: and order: prefixes supported), and click a subject to preview the exact stored email body in a new tab. Failed rows can be selected and retried from the toolbar — they return to pending with a fresh attempt budget and go out on the next plg_task_solidshopemailqueue run — and rows can be deleted (core.delete). The screen is gated through EmailqueueModel::authorise() (core.admin / core.manage.order — the per-store seam). The order detail toolbar gains Resend Confirmation: re-renders the confirmation from the order's current state (so address fixes, order edits and template fixes are picked up) and queues the customer copy only, guarded by the queue's per-recipient idempotency check; the action is logged to the order timeline as a new email_requeued entry. Library additions: Solidshop\Lib\Email\QueueStatus enum (unit-tested) and EmailQueueService::find()/retry()/deleteRows().
    • Admin quick search (mod_sshop_quicksearch) — a universal search box in the administrator header: type an order id/reference, customer name or email, product name, SKU or barcode (variant SKUs/barcodes included), or a discount name/coupon code and jump straight to the matching record, grouped by entity with status badges and per-group "View all" deep links into the pre-filtered list views. Ctrl+K / ⌘K focuses it from anywhere in the admin, / too when not already typing; full ARIA combobox pattern (activedescendant navigation, live result announcements). Query-shape detection with staged fallback (numeric → id/reference first, email → email columns, else broad LIKE) lives in the new Solidshop\Lib\Search domain (QueryClassifier, SearchQuery, SearchResultItem, SearchProviderRegistry — unit-tested), providers are thin query adapters in the component, and QuicksearchRegisterEvent (onSolidshopQuicksearchRegister) lets feature plugins register more result groups (invoices, subscriptions, reviews — follow-up work in their own plugins). Endpoint is task=quicksearch.search (CSRF + core.manage gated; each provider additionally checks its own core.manage.* action, so a user with partial rights just gets fewer groups; every result carries store identity per the multi-store rule). First administrator module in the bundle: build/build.php gained an admin-module packaging pass, and the package script auto-publishes the module to Atum's status position on fresh installs only — updaters get a pointer to the module manager instead. Customers group is deliberately restricted to users with commerce activity (an order or a saved address).
    • The product edit form follows the product type. Creating a product now starts with a set of icon cards — Physical plus whatever types the installed plugins register (Downloadable, Service, Subscription); on a saved product the control is the familiar dropdown. Changing the type reloads the form and preserves unsaved edits, so the tabs on screen always match the type, and the Shipping tab is gated on the type's Shippable capability instead of always being present. Track quantity now defaults from the type's Stockable capability (on for Physical, off for Downloadable/Service/Subscription/Virtual) and stays switchable everywhere — a service with limited seats can still track stock. The media field accepts drag-and-drop uploads straight onto the media area rather than requiring a trip through the media manager. Tabs and sidebar are reordered: SEO is its own tab (meta description, page title and the search-snippet preview) instead of sharing one with publishing data, and the sidebar groups status, product type, category, brand, tags, access and language in a single fieldset. The summary editor is height-capped so a long description no longer pushes the rest of the form off screen.

    Fixed

    • Cached invoice PDFs were reachable by guessing an integer. Generated PDFs sat at files/shop/{store}/invoice/{id}.pdf inside the web root with no deny rules — walking the ids exposed other customers' invoices (name, address, order contents). InvoicePdf::cachedPath() now appends a 64-bit HMAC token keyed with the site secret, and secureDir() drops .htaccess (Apache 2.2/2.4/LiteSpeed), web.config (IIS) and a blank index.html into the cache directory — called from saveToFile() and, self-healing for existing installs, from cachedPath(). The first securing of a directory sweeps legacy token-less {id}.pdf files; they regenerate on demand at the tokened name, and pdf_path stays write-only so stale DB values are inert. On nginx, which honours neither guard file, the unguessable filename is the protection.
    • The invoice approval workflow did not gate what it claimed to. The PDF/email task now only processes ISSUED invoices; approve() re-queues the PDF so it carries the approval-stamped invoice date, and the customer email goes out strictly post-approval. The admin PDF download preserves a queued row instead of swallowing the pending email. Customers no longer see or download draft/pending invoices anywhere (account list, print, PDF, order-detail button). Approve is also offered on drafts so a rejected invoice is not a dead end, the approval message/toolbar language keys are fixed, and the admin list gained the missing Pending Approval filter option.
    • Invoice items now carry the per-line tax aggregated from the order's tax rows, so the Detailed layout's tax column shows real values instead of zeros. Credit notes store all money columns negated, matching the documented behaviour and what an accounting import expects. Layout resolution is unified in InvoiceLayoutResolver with an on-disk existence check, so the PDF task can no longer email a blank PDF for a stale layout key.
    • Emails rendered from a payment callback were incomplete. Email::dispatchBeforeRender() now imports the solidshop / solidshoppayment plugin groups itself: renders triggered from com_ajax payment flows (the PayPal capture, for one) never pass through the component dispatcher, so plugin listeners were silently absent and plugin-contributed blocks and the bank-transfer instructions never rendered.
    • Public order-tracking URLs are SEF-routed. The tracking view was never registered with the component router, so its links stayed in raw index.php?option=… form on sites with SEF URLs enabled.
    • A phantom empty media entry produced an empty storefront slideshow. MediaManagerField seeded its hidden input with [""] for a new product, so saving without ever opening the picker stored a blank entry in the media column; the site model hydrated it into a bogus slide and the downloadable/service templates gated their gallery on the raw entry count. The field no longer seeds blank entries, the admin model strips blank rows on save (healing existing records), the site model filters them when decoding, and both templates (component + Foundra) gate on the typed media counts like product/default.php does.
    • Cart page: the Estimated total row is laid out like the Subtotal row above it (space-between instead of a right-aligned pair with a margin), so label and amount line up down the summary column.
    • Product form: the brand field's placeholder typo is fixed, and the variants checkbox label is properly associated with its input.

    Changed

    • Plugin-owned account pages moved their queries out of the templates. The subscriptions, downloads and bookings account templates each carried their own SQL, copy-pasted verbatim into the Foundra override (and, for downloads, into the component stub as well). Each plugin now ships a site model (DownloadModel, SubscriptionModel, BookingModel) under site/com_solidshop/src/Model/, shadowed into the component namespace by the plugin autoloader and reached through the component's MVCFactory — the pattern the review plugin already used. All seven templates now ask a model and hold no query. The download paid/expired/limit predicate is extracted into the library as DownloadAvailability + DownloadState, replacing four independent copies (three templates and Download.file), so the account page and the controller agree on both verdict and reason; unit-tested. SubscriptionController::processPlanChange() and the plan picker now share one definition of a switchable plan, the picker is scoped to the subscription's own store, and the Foundra subscriptions/bookings overrides render the Plugin Required notice instead of querying tables that do not exist when the plugin is absent.
    • The Payment received email no longer promises a shipment on an order with nothing to ship: the intro and next-step notice gained NO_SHIPPING variants (23 locales), used when the order carries no shipping rate — the shape of a digital-only order.
    • Email seed versions bumped: order.order_completed → 1.0.12, order.payment_received → 1.0.2. Both defaults gained a {% include 'downloadable/downloads.twig' ignore missing %} line, so a store running the Downloadable plugin gets a "Your downloads" block and a store without it renders exactly as before.

    Upgrade notes

    • No schema changes — 1.4.0.sql is empty. Nothing to migrate, nothing to back out.
    • Publish the quick-search module. Joomla installs administrator modules unpublished and position-less. Fresh installs get it placed automatically; on update the package script enqueues a notice instead, because an existing module layout is the merchant's. Publish mod_sshop_quicksearch to the Atum status position under System → Administrator Modules.
    • Stores that customised the Order confirmation (seed 1.0.11 → 1.0.12) or Payment received (1.0.1 → 1.0.2) bodies will see a drift banner. Reset to the default, or add the {% include 'downloadable/downloads.twig' ignore missing %} line by hand where the download block should appear; the payment-received default also picked up the no-shipping wording.
    • Existing invoice PDF caches are secured lazily: the guard files are dropped and legacy token-less files swept the first time the directory is touched after the update. On nginx, add a deny rule for files/shop/*/invoice/ (or move the directory outside the web root) — nginx honours neither .htaccess nor web.config, so there the tokened filename is the only protection.
    • Downloadable Products 1.0.0 pins 1.4.0 as its minimum core and refuses to install against anything older; update core first.

2026

  1. 1.3.2

    Stable
    Release notes for version 1.3.2

    The core the first commercial Solidshop extension needs. Discount & Coupons 1.0.1 pins 1.3.2 as its minimum: somewhere to store per-action settings, a discount that can reduce shipping and have that survive into the order and the invoice, a shopper-facing seam for offers that have not paid out yet, and per-line discount allocation so a free item carries no tax.

    That work exposed three tax and totals bugs that were never plugin-specific — tax charged on the pre-discount subtotal, tax-inclusive stores double-counting tax in every derived grand total, and a discount engine that treated an unknown condition as no condition. Those are fixed for every store, discounts installed or not.

    Added

    • Promotion notices — a seam for telling the shopper about an offer that has not paid out yet. PromotionNoticesEvent (onSolidshopPromotionNotices) fires when the promotion.notices layout renders on the cart or a product page; listeners contribute plain-text PromotionNotice objects and the layout owns the markup. The cart re-renders the fragment on every cart.update, so an offer can appear or lapse on a quantity change without a reload. DiscountEngine::resolveApplicable() is split out of evaluate() so listeners share checkout's exact definition of "qualifies". First consumer: the Discount plugin's free-item notice.
    • Shipping discounts. New total_shipping_discount column on #__sshop_orders and #__sshop_invoices; checkout writes what the discount engine resolved and every grand total subtracts it (order screens, orders list, customer spend, account order list, reports, invoices, subscription renewals, the Square plugin's order total). A "Shipping discount" line (COM_SOLIDSHOP_ORDER_SHIPPING_DISCOUNT, 23 locales) shows wherever totals are printed — admin, account, checkout finish, every invoice layout, and the order_completed / invoice_issued emails — only when greater than zero. The Sales-by-period report's Shipping column is net of it so the row still sums to its total.
    • Discount engine: a discount whose action only reduces shipping is now recorded in DiscountResult::$appliedDiscounts (new shipping_amount key), so it gets a usage row, a coupon badge and a name on the order instead of reading "invalid". On the cart page such a code is accepted and marked "Confirmed at checkout", like a location-restricted code — the shipping cost is unknown until a rate is chosen. Both clamps are unchanged.
    • Orders: new discount_total column on #__sshop_order_products — the promotion amount allocated to that line at checkout, kept separate from the manual admin line-discount rule. SUM(discount_total) equals orders.total_discount for checkout-created orders. Admin edits round-trip it (so editing a coupon order no longer erases the promotion from the totals), InvoiceGenerator folds it into invoice_items.discount_amount, and the Sales-by-product report attributes coupon discounts to the right products. Renewal pricing ignores it — a one-time coupon must not reprice every renewal.
    • Discounts list: a Published status filter. The model already honoured it; the field was missing from the filter form, so drafts and finished campaigns could only be found by scanning.

    Fixed

    • Tax is now calculated on the discounted amount. The engine allocates every cart discount to the lines it belongs to (DiscountResult::$lineDiscounts, opt-in LineAllocatingActionInterface, proportional proration for scalar actions). Checkout, the checkout summary, the cart and the mini-cart feed each line's discounted subtotal to the tax computation, so a free item carries $0 tax and a 10 % discount reduces each affected rate by exactly 10 %, in both tax modes. Previously tax was computed pre-discount and subtracted after — the shopper paid tax on money they never spent, and #__sshop_order_taxes overstated collected tax.
    • Tax-inclusive stores no longer double-count tax in derived grand totals. With tax_price_input_type = inclusive the subtotal is gross and already contains total_tax, but every grand-total formula added it again — inflating the admin order screen, orders list, dashboard KPIs, customer spend, the account order list, stored invoice totals and (worst) the amount handed to payment gateways. All formulas now branch on the new TaxHelper::pricesIncludeTax(). Exclusive-mode stores are byte-identical to before; checkout summaries were already correct.
    • Per-line clamping also corrects over-stacking: two 100 % product-scoped discounts on one line no longer both pay out against unrelated lines' money — each sees only the headroom earlier discounts left. appliedDiscounts[n]['amount'] is now the post-clamp figure.
    • Discount engine: a condition whose handler is not registered now fails closed. Previously disabling the Discount & Coupons plugin turned every discount gated only by a rule-builder condition into an unconditional one.
    • Cart page and mini-cart: the discount row shows the display-basis (tax-adjusted) amount, so subtotal − discount = estimated total holds on screen when prices include tax. The cart.update JSON keeps its discount_total key; only the basis changed.
    • Payment method names read as labels, not slugs. payment_method_id stores a machine id (cod, banktransfer, free) and several surfaces printed it raw — confirmation, payment-received and order-cancelled emails said "Payment method: Cod", and the report and admin order screen showed cash / free / (none). New PaymentMethodHelper::label() resolves both key namespaces and de-slugs when the string is missing, so an uninstalled plugin can no longer leak a raw language key to a shopper. Every display surface funnels through it (emails via a new payment_method_label variable); the stored id is unchanged and stays what reports group on and CSV exports carry.
    • The orders-list payment filter now offers every method the orders actually used. Its options came from enabled payment plugins only, so admin-created orders (cash, bank_transfer, other), free orders and orders with no method were never offered — and disabling a plugin made every order paid through it unreachable. Options are now read from the orders themselves (PaymentMethodUsage, store-scoped); orders with no method are offered as Not specified. New composite index idx_#__orders_store_payment_method keeps that query index-only.
    • The cart's "Discount" row no longer renders when nothing was discounted. The row carries hidden, but that attribute's display: none comes from the UA stylesheet and lost to Bootstrap's .d-flex and Foundra's summary-row rule — so every cart with no qualifying discount showed a green "Discount −$0.00". Both stylesheets now carry a [hidden][hidden] { display: none !important } guard, which fixes every hidden toggle at once: under Foundra that also covers the collapsed coupon form, the billing address block, and the mini-cart badge's "0" bubble on an empty cart.
    • Checkout no longer fatals on a free product. A product saved with no price stores NULL, and the cart line carried it into DisplayCurrency::format() — a type error whenever a free item was in the cart, exactly what the Discount plugin's Free item action produces. CartController casts on add and quantity change, and both checkout summaries coerce on render, so existing sessions are safe too.
    • Filters module: the section headers were dead on a clean install — they are Bootstrap collapse toggles and nothing loaded bootstrap.collapse, so with Collapsed by default on, every filter stayed hidden. The module now declares the dependency itself.
    • The applied-coupon chip showed a wide gap before its remove control (.btn-close padding plus ms-1 plus a collapsed source newline). The chip is now flex, btn-sm ms-1 is gone from both coupon layouts, and under Foundra the cross is masked from currentColor so it works in both themes.
    • The component stylesheet now has an owner on every view that needs it. com_solidshop.core was reaching checkout second-hand from the mini-cart module, which is not rendered under tmpl=component. Checkout, Account and Tracking load it themselves, covering the Foundra override and the plugin-owned account templates too; the redundant layout-level call is removed.

    Changed

    • Discount edit form: the action row's config JSON now carries handler-specific settings submitted through an action_config group, and loadItem() exposes the decoded JSON so fields bind back on edit. Only keys whose showon matches the chosen action type are stored, so hidden fields' defaults don't leak between types. This is the seam plugin action types (BOGO, Fixed price, Tiered, Free item) save through — no plugin-side save hook needed. Released 1.3.1 accepted these fields and dropped them on save.
    • Discount edit form: saving a discount whose stored action type the form cannot offer (a plugin-registered type while that plugin is disabled) leaves the action row untouched instead of rewriting it as a plain percentage discount.
    • Filters module: colours resolve through the active template's tokens — --solidshop-filters-* falling back Foundra → Bootstrap → literals — so the module follows the active Foundra preset and its dark values and still looks right under Cassiopeia.
    • Admin list filters: the empty option on the discount and invoice status filters reads - All - (JALL), matching the other Solidshop lists and Joomla's own.

    Upgrade notes

    • Schema update 1.3.2.sql adds total_shipping_discount to #__sshop_orders and #__sshop_invoices, discount_total to #__sshop_order_products, and the composite index on #__sshop_orders. Existing rows keep NULL / 0 and their totals are unchanged — historical orders are never restated; new orders on discounted carts simply collect less tax (the fix).
    • Third-party discount actions registered via DiscountRegisterEvent keep working unchanged: calculate() is untouched and scalar amounts get prorated allocation automatically; LineAllocatingActionInterface is opt-in. Callers evaluating the engine without cart_items keep the previous cart-level behaviour.
    • Discount & Coupons 1.0.1 pins 1.3.2 as its minimum core and refuses to install against anything older; update core first.
    • Stores that customised the order_completed (seed 1.0.11), invoice_issued (1.0.1), order_cancelled (1.0.1) or payment_received (1.0.1) bodies will see a drift banner: those defaults gained the shipping-discount row and now print payment_method_label instead of payment_method_id. A customised body keeps the old lines until it is reset to the default; the raw payment_method_id stays available to templates that branch on it, such as the bank-transfer instructions partial.
  2. 1.3.1

    Stable
    Release notes for version 1.3.1

    A maintenance release: no schema changes and no storefront changes. It adds the order backlog to the Joomla administrator dashboard, teaches the order screen to render the payment entries the gateway plugins record, and moves the shared payment-callback form field into the component so two payment plugins can ship the same field without colliding.

    Added

    • Order backlog quick icons: new bundled plugin plg_quickicon_solidshop puts the shop's backlog on the Joomla administrator home page — three tiles counting Pending, Unpaid and Unfulfilled orders, each linking to exactly the rows it counted. Pending is on by default and reads the same Options → Pending order status the dashboard alert uses, so the two can never disagree; the other two tiles are opt-in. The panel it appears in (Third party / Site / System / Notifications) is a plugin option, and a tile is never shown to a user the orders list would 403.
    • Payment entries on the admin Activity Timeline: captures recorded by the payment plugins now render as readable lines instead of blank generic rows — a partial payment says so, a webhook-reconciled capture names the webhook, an inline confirm at checkout stays unqualified, and the gateway transaction id prints underneath in muted type for copying into the gateway dashboard.

    Changed

    • Library: OrderDescriptor builds the description a gateway shows in its own dashboard from the store name and the order reference, trimming the store name (never the reference) to fit each gateway's field limit; OrderTimelineHelper::log() gained a dedupeOn parameter so a capture reconciled twice logs one entry; FulfillmentStatus joins PaymentStatus in Solidshop\Lib\Status instead of the seeded code being hardcoded at call sites.
    • Orders ACL funnels through OrdersModel::authorise(), the same shape as ReportsModel::authorise() — one seam per feature where a per-store restriction attaches when multi-vendor lands.
    • The callbackurl form field type moved out of the PayPal plugin into the component (Joomla\Component\Solidshop\Administrator\Field\CallbackurlField) and gained a payment XML attribute; its language keys moved to com_solidshop.ini across all 23 locales. Joomla resolves field types from one global prefix stack, so two payment plugins shipping the same type name collided.

    Upgrade notes

    • The core package gains plg_quickicon_solidshop. It publishes itself from its own scriptfile on first install, so sites updating from 1.3.0 get the tiles too; every later update arrives as an update, so tiles you switch off stay off.
    • Payment plugins must be current for the timeline entries to appear: Stripe 1.0.0 and PayPal 1.0.2 are the versions that record them, and both pin 1.3.1 as their minimum core.
    • Update PayPal to 1.0.2 alongside this release. PayPal 1.0.1 and earlier still ship their own callbackurl field class, which now collides with the component's — the symptom is a Webhook URL field on another payment plugin's tab rendering PayPal's URL.
  3. 1.3.0

    Stable
    Release notes for version 1.3.0

    Added

    • Custom fields on products: define product attributes in Joomla's own Custom Fields screens (all 19 field types, validation, view levels, groups, ordering, language assignment). Values save and roll back with the product, render in a storefront Specifications tab, emit Schema.org additionalProperty on the product's JSON-LD node, index into Smart Search (value and/or facet per field), round-trip through CSV as Field: {name} columns, and read/write through the REST products API. {field N} / {fieldgroup N} placeholders work in descriptions
    • Custom fields at checkout: an Additional information panel collects order-level input (gift message, delivery slot, PO number) — required/pattern rules enforced server-side before the order is created
    • Custom fields on addresses: address book, admin customer screen and both checkout addresses; each field can be restricted to shipping, billing, or asked on both
    • Custom fields on order lines: per-item input on the product page (engraving, recipient, date), assigned to products via the field's Category assignment. Lines with different answers stay separate cart lines and draw on shared stock; identical answers merge. Editable from the cart; shown in cart, mini-cart and checkout summary
    • Captured values are frozen onto the order with their labels — renaming, retyping or deleting a definition never rewrites a placed order. They appear on the order screen (editable with the same validation, timeline-logged), the customer's order detail, the confirmation and shipment emails; per-field switches gate each surface
    • Related products: pick and drag-order suggestions on a product's Related tab; shown as ordinary product cards under the description. One-directional by default with an opt-in "both ways" display option resolved at read time — nothing is written to the other product, unlike HikaShop's mirror rows. Storefront visibility rules apply (unpublished / windowed / access-restricted products drop out); enabled and sized via Options → Products
    • Currency switcher: new module mod_sshop_currency (dropdown or links; labelled by code, sign, name) lets shoppers read catalogue, cart and checkout in any published currency that has an exchange rate; the sidebar price filter follows. Display-only: the order, invoice, emails, reports and the gateway amount stay in the store currency — stated with the exact amount at checkout. Hides itself when only one currency qualifies
    • Catalog REST API: read-only GET v1/solidshop/products|categories|brands (+ :id, products/:id/variants) with search / category / brand / price / stock filters, lang and currency args, served by the rebuilt plg_webservices_solidshop. Guest-visible data only — no cost prices, no stock quantities (boolean in_stock), no customer or order data. Public by default; a Public catalog access plugin switch gates everything behind Joomla API tokens instead
    • MCP server: POST v1/solidshop/mcp exposes the catalog to AI agents as five read-only tools (solidshop_search_products, solidshop_get_product, solidshop_list_categories, solidshop_list_brands, solidshop_get_store_info) over stateless Streamable HTTP. Same shapers and visibility rules as the REST layer; every response carries the canonical storefront URL, so agent referrals land on the merchant's own pages

    Changed

    • Product descriptions now run through Joomla's content plugins (this is what renders {field N}); Options → Run content plugins on product descriptions turns it off if literal {…} braces matter
    • The order confirmation email gained an Additional information block and per-line custom fields under each item; the shipment email lists them per shipped item. Customised bodies are offered the change via the editor's drift banner
    • Stock checks now sum every cart line of the same product instead of checking each line alone — with per-line fields one product can sit on several lines. Same correction for admin order-product edits

    Fixed

    • Address forms posted radio groups, checkboxes and multi-selects incorrectly — every radio in a group and every checkbox, ticked or not
    • Product cards in listings emitted an empty priceCurrency in their microdata; they now carry the store's currency code

    Upgrade notes

    • Schema: nullable JSON custom_fields columns on #__sshop_orders / #__sshop_order_products, and the new #__sshop_product_related table (both sides cascade on delete)
    • The core package gains mod_sshop_currency (installs unpublished, like every module) and plg_webservices_solidshop (enabled on install; disabling it removes all API routes)
    • Currency switching is display-only by design; Joomla's System - Page Cache plugin serves one cached copy per URL to all guests, so leave it off on priced pages if you publish the switcher
    • Related products are not yet in the CSV columns or the REST products API; listing pages cannot yet filter or sort by a custom field value (Smart Search facets cover narrowing inside search results)
  4. 1.2.0

    Stable
    Release notes for version 1.2.0

    Added

    • Reports: new admin screen with four reports over a date range — sales by period (day / week / month), sales by product, tax collected, sales by payment method — each downloadable as a self-describing CSV. Payment-status scoped, store-scoped, one section per currency (never summed across); plugins can register more via onSolidshopReportRegister
    • Smart Search: new bundled plugin plg_finder_solidshop indexes products into Joomla's site-wide search (com_finder) — live sync on save/delete/publish, storefront-visibility parity, per-language entries, and Type / Category / Brand / Language filters
    • SEO: native XML sitemap of product and category URLs at view=sitemap&format=xml — sharded index, honest per-product lastmod, guest-visibility parity, per-language alternates, plus a per-store SEO tab and an Options → Sitemap fieldset
    • Mini-cart: mod_sshop_cart gains an off-canvas drawer — line items, quantity stepper, tax-adjusted estimated total including discounts, View cart / Checkout — updating live via the new onSolidshopCartChanged document event. Legacy badge-only behaviour stays available via the Display mode option
    • Cart: coupon field plus subtotal / discount / estimated-total rows on the cart page, so automatic discounts are visible before checkout; a code applied in the cart carries into checkout. Location-restricted codes are accepted with a "Confirmed at checkout" hint
    • System: cache-directory health check with one-click repair — reports the Twig and email cache areas with owner and mode, and the chown command for what PHP cannot fix itself

    Changed

    • Currency is now a store property, set on the Store edit screen; the global "Default currency" option is removed and migrated automatically on update (if the two disagreed, the option's value wins — that is what orders were placed in). Storefront behaviour is unchanged
    • Dashboard KPIs, sales chart, top products and customer insights now use the Reports engine and its payment scope. Revenue reads lower than in 1.1.x — pending, unpaid and abandoned-at-payment orders no longer count as revenue. Revenue and AOV cover the store currency only; in-scope orders in other currencies are flagged with a link to Reports
    • Cart badge counts units (sum of quantities), not lines; cart.add / cart.update expose the same value in a new count field
    • Shipping: a profile with no assigned products covers the whole catalogue, so the store page shows it as a plain badge instead of an alert — the warning invited a "fix" that broke shipping
    • Account: removed the "Payment Methods" page, which only ever showed "Coming Soon"; the sidebar highlight now follows the layout that actually rendered
    • System: every filesystem path renders through one layout — LTR-locked, escaped, JPATH_ROOT stripped

    Fixed

    • Checkout: an unwritable cache/com_solidshop directory aborted checkout and payment callbacks; templates now recompile per render and log instead of throwing
    • System: the "Menu items" panel matched the wrong view for Customer Profile, omitted Products, and hid unpublished or trashed items — all states are reported now, badged, and scoped to site menus
    • Shipping: the seeded sample rates capped order value in every non-domestic zone, so carts above it matched no rate and checkout offered no shipping. Rebuilt as five gapless zones covering 77 countries
    • Coupons: an invalid code no longer reports "Coupon applied!" when an unrelated automatic discount happens to be active
    • Cart / checkout: load the SweetAlert preset so Solidshop.alert dialogs render as dialogs, not unstyled text at the page bottom
    • Translations: 110 new keys synced to all 22 locales; el-GR double-escaped ampersands at checkout, de-DE carried a raw & in markup, hi-IN mistranslated Subtotal. build/validate.php now checks placeholder parity and ampersand encoding
  5. 1.1.0

    Stable
    Release notes for version 1.1.0

    Added

    • Products: CSV import and export — one file, one row per variant, with auto-mapping of Shopify/WooCommerce headings, per-language Name [xx-XX] columns, and chunked processing so large catalogues import without timeouts. Empty mapped cells leave stored values alone, so a two-column alias+price file is a safe bulk update.
    • Installer: uninstalling the Solidshop package is now blocked while Solidshop add-on plugins are still installed — the error message lists them, so add-ons are removed first and never left stranded without the core tables and library their own uninstall depends on.

    Changed

    • Product listing: build cards from the listing row instead of a per-card detail-model round trip (82 fewer queries on a 20-card page); mod_sshop_products gets the same win.
    • Product listing: share one visibility predicate between the list and detail queries so a draft, scheduled, or category-unpublished product no longer 404s the whole page.
    • Product List menu item: honour the menu item's category selection (was ignored — every menu item listed all products).
    • Wishlist: join what the cards read and batch variant options instead of per-row detail-model lookups; one unpublished wishlisted product no longer 500s the page — it is left out like the listing already does.
  6. 1.0.6

    Stable
    Release notes for version 1.0.6
    • Security: fix SQL injection via cart option values (reported by Krzysztof Zając, CERT PL)
    • Shipping: product-level profile assignment covers all variants, tri-state variant picker
    • Shipping: match rates against total shipment weight (variant weight x quantity, summed per profile)
    • Shipping: match every state of a multi-state zone region, not just the last
    • Shipping: rate-less zones return empty instead of TypeError, drop unpriced carrier rates
    • Checkout: mirror the shipping address when no separate billing address was supplied
    • Checkout: URL-encode the guest email so plus-addressed buyers can check out
    • Address: require address_1 and city, filter both as string
    • Product listing: show star ratings on product cards
    • Orders: drop the foreign keys from status columns to #__sshop_statuses
    • System: link multi-routine task plugins in the Task Scheduler health check
  7. 1.0.5

    Stable
    Release notes for version 1.0.5
    • Install: load language in postflight, require Joomla 6.0.0 stable
    • SEO: merge review rating into the single Product JSON-LD node
    • PayPal: capture reconciliation via webhooks, min core version on install
    • Checkout: close the inventory oversell race
    • Install: scope postflight menu lookup to site items (client_id=0) so admin submenu links don't falsely skip site menu creation
    • Install: remove site menu items on uninstall + auto-publish core payment plugins (COD/Bank Transfer) on fresh install
    • Orders: admin list filters for order/payment/fulfillment status, store and created date range
    • Orders: translate invoice_email_sent timeline entry in admin order view
    • Orders: store activity-timeline timestamps in UTC to fix +7h timezone offset in admin display
    • Admin menu: reorder submenu into logical groups and sync with preset
    • Checkout: store-scoped policy consents
    • Responsive admin lists: admin list views now reflow into mobile cards below the md breakpoint via a shared %solidshop-list-cards SCSS placeholder
  8. 1.0.4

    Stable
    Release notes for version 1.0.4
    • Payment: add per-plugin logging facility, instrument COD + bank transfer
    • Core JS: dark-mode aware SweetAlert dialogs + prettier pass
    • Search module: match input height to submit button
    • Admin menu - Menu preset
  9. 1.0.3

    Stable
    Release notes for version 1.0.3
    • Add Bank Transfer to the Core installation package
    • Discount: move action_scope field to plg_solidshop_discount
    • Discounts: alias 'published' to 'state' on DiscountTable so toolbar publish/unpublish works
    • Products: expose variant SKU input in product edit variant table
    • Products: hide media section and silence thumbnail warning when product has no renderable media
    • Products: replace base64+atob share button pattern with TEMPLATE tag clone
    • Customer: declare core.edit.value ACL and remove com_fields force-enable workaround. Customer edit form no longer force-enables every custom field on the site client. The core.edit.value ACL on the com_users asset is now respected — admins must grant core.edit.value to the customer user group (Users → Options → Permissions) so logged-in customers can fill or update Joomla custom fields on their profile.
  10. 1.0.2

    Stable
    Release notes for version 1.0.2

    First public release of Solidshop. This entry establishes the baseline that all future changelog entries are deltas against.

    • Single-store catalog with products, options, variants, brands, categories, and per-SKU product stats.
    • Multi-step cart and checkout with guest support, address book, shipping rate selection, and order-time tax calculation.
    • Customer accounts linked to Joomla users — order history, address book, and wishlists.
    • Order lifecycle with order, payment, fulfillment, and return statuses, plus per-order timeline.
    • Tax engine with classes, zones, and zone × class rate resolution (inclusive/exclusive pricing).
    • Shipping engine with profiles, zones, regions, and rate tiers.
    • Stackable discount engine with pluggable conditions and actions.
    • Auto-generated invoices with credit-note support.
    • Wishlists for logged-in customers.
    • Customisable email notification templates editable from the admin — order confirmations, shipping updates, and status change emails.
    • Store dashboard with KPI cards, sales analytics, recent orders, product insights, and a plugin-extensible widget system.
    • Granular Joomla ACL integration across every admin view (view, create, edit, delete, publish, manage).
    • Product Filters module for category-page filtering by category, brand, price, rating, and tags.
    • Built-in payment plugins: Bank Transfer, Cash on Delivery.
    • Storefront translations for 23 languages including full RTL support (Arabic, Hebrew, Persian).
    • Multilingual content — translate product, category, option, status, and email-template text with per-language slugs, hreflang tags, and recipient-language emails.
    • SEO-optimised storefront — clean URLs, semantic H1 hierarchy, canonical tags, Open Graph and Twitter cards, dynamic stock availability, and Product/Offer JSON-LD structured data.
    • WCAG 2.1 AA accessibility — semantic landmarks, ARIA attributes, full keyboard navigation, visible focus states, and a contrast-preserving dark-mode palette.
    • Joomla 6.x native; requires PHP 8.4 and MySQL 8.4 / MariaDB 11.4+.