Core 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 carrynoindex, 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 tocom_solidshop.filters.phpin 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'sfilter_{alias}parameters),FacetMatch(the listing predicate and every count),IndexRowBuilder,FacetValueOrder,FacetRepository::forListing()— all but the repository pure and unit-tested.ProductListingQuery::applyFilters()readsstockand everyfilter_{alias}. The listing JSON'sfacetsgainsattributes(filter_{alias}→ value key → count),stockandstock_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}/swatchesapart 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 aswatch: 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 theResolvedSwatcha value shows under a mode) andSolidshop\Lib\Media\SwatchLibrary(the per-store folder, names, URLs and the upload behindtask=swatch.upload/swatch.browse). Thefield/options.phplayout now renders each option as a fieldset with a legend, and the selected value's name lands in adata-option-selectedspan 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 678on 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
SolidshopPhoneform field (countryfield,defaultcountry; validates with Joomla'stelrule on the international plan unless the form says otherwise),Solidshop\Lib\Phone(PhoneNumber::toE164()andtelHref()for anything that dials or sends a number) and thecom_solidshop.fields-phoneasset 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 mmreads 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: Valueper 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, withsource: "product"and noname; fields now saysource: "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 theproduct/fields.phplayout 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
@versionboth 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@versionSolidshop 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/andlayouts/(site and administrator), eachmod_sshop_*module'stmpl/, and the views and layouts the Solidshop plugins ship — now carries a real@versionin 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@versiononce you have brought it up to date. The check isSolidshop\Lib\TemplateOverride(pure, unit-tested) behindTemplateOverrideHelperin 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_solidshopbuilds the entry from the component'spresets/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'spermissionattribute now hides it from the menu entry as well as from the cards.plg_quickicon_solidshopalso answers thesolidshop_quickiconquick 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'scolor,size,materialorpatternand are listed invariesBy; other options stay in the variant's name ("Tee - S / Red"). Until now a product with variants was oneProductwith a list of offers, prices and stock with nothing to say which variant each belonged to. A product without variants stays aProductwith 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,gtin13orgtin14, 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 (
priceSpecificationwithStrikethroughPrice) - 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\ProductSchemabuilds the node from resolved values andSolidshop\Lib\Product\Gtinreads a GTIN out of a barcode, both pure and unit-tested.onSolidshopProductJsonLdlisteners now receive aProductGroupfor 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 toOrderStatusChangedEvent. Both import thesolidshopplugin group just before they dispatch, so its plugins hear a payment a gateway records from its owncom_ajaxendpoint (PayPal's capture, Stripe's confirm step), a request that loads only thesolidshoppaymentgroup. A listener that throws is logged and does not fail the write. It is not fired for a new order.OrderStatusChangedEventis unchanged and still comes only from the order screen andOrderHelper::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 newSolidshop\Lib\Subscription\SubscriptionOrderSync; the rules it applies are the pure, unit-testedSubscriptionPurchase, andSubscriptionPeriodsrecords which order paid for which stretch of a subscription - For developers:
AfterOrderCreatedEventalso 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 aRenewalPricing: a renewal bills the subscription line alone - For developers:
Solidshop\Lib\Cart\SoldIndividuallyis the one-per-order rule (pure and unit-tested), asked by every path that sets or grows a cart line. Thefield/quantity.phplayout takes afixedkey 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_taxrecords whether an order's prices included tax;Solidshop\Lib\Order\OrderTotal::grandTotal()andReportQueryHelper::grandTotalSql()read it instead of the current setting.#__sshop_tax_rates.is_inclusiveis dropped andTaxChoice::ratePayload()loses its fourth parameter - For developers:
TaxHelper::computeOrderTaxBreakdown()taxes an order's lines and its shipping in one call and returns aSolidshop\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 fromCheckoutHelper::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\OrderTaxRowswrites 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_selfmacro 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 theapp,input,lang,userandurivariables or theJPATH_*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 (categorycom_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-sitegave a subscription reminder's Renew button and the store logo the addresshttps://joomla.invalid/…, and one whose address had no trailing slash a path undercli/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_currencydefault.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
JACTIONSin 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,OptionValueTableandLocationTabledelete the row they have loaded whendelete()is called with no key, as Joomla'sTable::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 assans-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-libanddompdf/php-svg-lib(they werephenx/*); theFontLib\andSvg\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\SandboxwithSolidshop\Lib\TemplateEngine\EmailSecurityPolicy.Email::compileTemplate()returns a sandboxed template unless its new$trustedargument is set (for shipped files only), andSolidshop\Lib\TemplateEngine\Twig::getSandboxed()sits besidegetInstance(). Neither environment registers globals any more. A partial a plugin contributes throughTwigPathsRegisterEventrenders inside the sandbox when an e-mail includes it, so it must keep to the same list. Who may edit templates isSolidshop\Lib\Email\EmailTemplateAccess::canEdit().store.paramsreaches a template, and the e-mail queue'spayload_json, without itspaymentsandshipping_carriersgroups (Solidshop\Lib\Email\TemplateData); a plugin that needs one of its settings in an e-mail passes it throughBeforeEmailRenderEvent, as bank transfer now passes its details asbank_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 byProductListingQuery::applyScope(); the siteProductsModelexposes it asgetListingScope().FiltersHelper::computeFacetsForResponse()takes the scope as its second argument. In the Filters module's markup a checkbox facet is a section withdata-solidshop-facet-param(its URL parameter), each value row carriesdata-solidshop-facet-item, and counts are keyeddata-facet-count="{param}:{id}". Every facet row is rendered, empty oneshidden - 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-0958saves 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 examplebank_transfer.iban) rather thanstore.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_filtersdefault.php) need updating from the shipped layout: the category, brand and tag checkboxes are now found throughdata-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.phpshow 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->specsshould 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 aProductGroupfor 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: aProductGrouphas none of its own, each entry ofhasVariantcarries its ownoffers, and aProduct'soffersis 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@versionline 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.phpkeep working: the radio inputs, their names and ids and thevariant-checkclass 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) andpage/heading.php(the menu item's page heading). Each page's view has$this->pageHeading, whosetag()is the element for the page's own title andtag(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 athtml/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.phpkeep 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 fromCheckoutHelper::taxBreakdown(). Foundra 1.1.0 carries the updated override
Solidshop Core v1.7.0
| File size | 10.48 Mb |
| SHA-256 Signature | 38f1d6193ccc8eab3955ccb0fd69302cf8019b82f1b3731467e2d20af4b80223 |
| Compatibility |