Core 1.8.0 Stable Security: Low

Released on: Wednesday, 11 November 2026 06:15

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

Solidshop Core v1.8.0

Joomla! 6.0 Joomla! 6.1 Joomla! 6.2

File size 10.72 Mb
SHA-256 Signature 6f63c3d4f0dc5984a8035fdb025d407e133ecabc5e39006878a93815105e1e76
Compatibility Joomla! 6.0 Joomla! 6.1 Joomla! 6.2