Change Log

All the HikaShop team puts a lot of energy in this project and works every day to improve the component and your user experience, by adding new features and fixing bugs.

We advise you to update HikaShop each month to enjoy the latest version.
(You can download the package in your member area or click on the automatic update button directly on your back-end.)

Here is the list of each release since we started the HikaShop adventure...

HikaShop 6.7.1

Release date : October, 20 2026

Improvements (4)

• The web cron of hikashop.com is set up from the Cron tab of the HikaShop configuration itself: "Show the web cron" displays whether it runs, its frequency, its next and last run and its last report, and you can switch it on or off and change its frequency there. A website not yet attached to your subscription gets a link to attach it on hikashop.com. Before, the "Create/Edit your Cron task" button opened a page of hikashop.com in a popup, which browsers refused to display or which asked you to log in on hikashop.com without keeping the login.
• The Bambora (Beanstream) payment plugin now sends the customer to the Shift4 payment page (checkout.bam.shift4api.net), the new address of the Bambora hosted checkout. The former address stops working on December 31, 2026, so update before that date. Your Bambora account, merchant id and hash key stay the same.
• On Joomla, when HikaShop was updated without its install script running to its end, as an update made by a remote site manager or files uploaded by FTP can leave it, the first page loading HikaShop now finishes the update of the database. Before, the tables stayed as they were and the frontend pages failed with an "Unknown column" error, such as "Unknown column b.product_hidden_languages" on the product listings after an update to 6.7.0, until the "Check database" button of the configuration was used.
• The shipping methods of the checkout now refresh when a guest, or a customer registering during the checkout, changes the country, state, city or postal code of the address in the registration form, as they already did for the address of a logged in customer, and they follow the "Same address for shipping" checkbox. Before, they only refreshed once the registration was submitted. It needs the "Dynamic address refresh" setting of the shipping block of the checkout, which is on by default.

Bug fixes (25)

• The "None" choice of the lists in the settings of the Google Products plugin now reads "None". Before, it showed HIKASHOP_NONE.
• Security hardening in several areas, updating is recommended.
• The payment plugins which check each notification of their payment service with a secret key, a password or a hash (Alipay, AtosSIPS, Beanstream, BluePaid, Borgun, CardSave, ePay, Monetico, Moneybookers, Ogone, PayGate, PayPal Advanced, PayU India, PostFinance, Servired and others) now refuse every notification while that setting is empty on the payment method, so no order can be confirmed by a message that cannot be verified. Before, the empty setting was used as the secret.
• The Authorize.Net payment plugin now refuses every notification while neither a signature key nor an MD5 hash is set on the payment method, and tells you by email. Before, the notification was checked against a value anyone could compute from the login id of the account, so it could confirm an unpaid order.
• With the Bambora (Beanstream) payment plugin, a notification announcing an amount different from the order total is now refused and written to the log, and the order keeps its status. Before, it moved the order to your invalid status, which could cancel an order which was already paid.
• The CardSave and PostFinance payment plugins now leave the order as it is and email the merchant when a notification carries an amount or a currency that differs from the order. Before, they cancelled the order. The PostFinance, Monetico and AtosSIPS plugins also now check the amount and the currency of the notification against the order, which some of them did not do.
• A PostFinance notification which is not signed, or whose signature is wrong, now only warns the merchant by email. Before, it cancelled the pending order it named.
• In a report with the Table display, a "Taxes" row now gives all the taxes of the orders: those of the products, the shipping and the payment fee, minus the tax taken off by the coupon, so that it matches the order totals and the sales with and without taxes. A "Sales" row without taxes nor shipping but with the coupon now deducts the coupon once per order and without its tax. Before, the "Taxes" row only added the taxes of the products before the coupon, and that "Sales" row deducted the coupon with its tax once per product of the order.
• A row of a report with the Table display now counts the orders of every status when "All" is selected in its order statuses. Before, such a row always gave 0.
• A HikaShop content module showing categories, with the brands category (or one brand) as its main category, now lists the brands. Before, since the main category setting accepts several categories (6.6.0), such a module listed the categories of the root of the shop instead (product category, taxation category, order status...).
• The suggestions of a text filter shown on a product page (a filter module in the header, for example) now list the products of the whole shop, as on the other pages, and so do those of a filter module sending its search to another menu item when it is shown on a category listing. Before, on a product page they only listed the products of the category whose id happened to be the id of the product shown, so most products could no longer be suggested there, and on a category listing they only listed the products of that category while the search itself looked in the whole menu item.
• A product suggestion of a text filter (the "cards" style) now opens the product at the first click, however long the mouse button is held, and pressing Enter in a text filter set to "Submit on click" now applies the typed text at the first press, also on the product listing itself and when the suggestions had not appeared yet. Before, holding the button a little sent the search instead of opening the product, or closed the suggestions without opening it, and Enter could do nothing visible or open the suggestions, so a second click or a second Enter was needed.
• On Joomla 6.2 and newer, the checkout opened without a menu item in its address, such as /component/hikashop/checkout reached from an old add to cart link, now redirects to the menu item set in "Force a menu on the checkout". Before, it ended on a 500 error "A key is required" as soon as the cart had a product. The same check now protects the language associations of HikaShop's pages.
• A text filter set to "Submit on click" in the filters shown above a product listing now keeps what the customer types, the cursor and the suggestions while the listing refreshes as they type, and a text filter of a filter module now refreshes the listing even when the listing shows the same filter above its products. Before, the field of the listing was rebuilt after the first letter, the following letters and the suggestions were lost, and the module did not refresh the listing in that case.
• In a filter module whose Filter button is hidden, pressing Enter in a text filter while its suggestions are open now applies the typed text and opens the results, like the button would. Before, Enter only closed the suggestions and nothing was searched.
• The name of an Australia Post v2 service in the order emails, the order pages and the backend now follows the language override of its key followed by _NAME (for example AUS_PARCEL_REGULAR_NAME), the same key as on the checkout. Before, those pages always showed the plugin's English name, such as "Parcel Post (your own packaging)", whatever the overrides.
• A listing with a price filter and a filter whose conditions contain a sub-query, such as a dates filter, now shows the products. Before, the price filter's query changed every WHERE of the filter's SQL, including the ones of the sub-query, and the page ended on a "Subquery returns more than 1 row" error.
• The "Back" and "Check database" buttons of the page showing the result of the database check now work. Before, clicking them did nothing.
• After an update of HikaShop, the translations of the shop are downloaded for the new version as soon as a HikaShop page of the backend is opened. Before, they were only downloaded at the next login, so emails and settings kept showing the new texts in English until then.
• With the "Generate WebP images" (or AVIF) setting on, two images with the same name and different extensions, such as c1.jpg on one product and c1.png on another, now each get their own WebP and AVIF copy, named after the whole name of the image (c1.jpg.webp, c1.png.webp). Before, both used the same c1.webp copy, so the two products showed the same picture, the one of the image whose thumbnails were made last.
• Saving a variant, or the product while a variant is open, at the moment its description editor (JCE, for example) is still loading now keeps the description of the variant. Before, the description could be replaced by the word "undefined", which then showed on the product page instead of the description.
• An account created at the checkout, from the registration form or from the page offered after a guest checkout now gets a customer of its own in HikaShop. Before, it took over the guest orders placed with the same email address, and the orders of a deleted account which had that address, so whoever registered with someone else's email address saw those orders and their addresses.
• The account created from the page offered after a guest checkout now gets the order of that page, and it waits for the confirmation of its email address when the Joomla user activation asks for one. Before, it was active at once and the order stayed on the guest customer.
• A guest order opened, paid or cancelled without the link of its email now goes to the login page. Before, the page showed an error.
• With WebMCP turned on in the UCP plugin, the commerce endpoints now only accept the browser requests made from a page of the shop by the visitor themselves, and still ask the API key from everything else. Before, turning WebMCP on also let other clients use them without the API key. Updating is recommended if you use WebMCP.

All versions

Older releases (HikaShop 4.7.5 and earlier) are listed in the HikaShop Change Log Archive.