Version 6.0.x
Release Notes 6.0
Recent changes (not versioned yet)
New features / improvements
16/01/2025 | Update containerfile to use NodeJS 22 (from 18)
Fixes
15/01/2025 | Moved return of 404 page when order does not exist to CheckoutController as ViewComponent's does not allow this.
20/01/2025 | Handle edge case where the webshop would repeatedly fetch all deletes when no products were published.
21/01/2025 | Remove unnecessary delivery date update as it may result in api failure during page loads.
22/01/2025 | Fix brand list images. ImageSharp should use rendermode BoxPad as it defaults to cropping when both width and height is in use.
6.0.1
14/01/2025
New features / improvements
03/01/2025 | Added Trustpilot review collector widget.
07/01/2025 | Make sure index is ready before starting to serve content
08/01/2025 | Changed Umbraco backoffice idle timeout to 1 hour.
09/01/2025 | Change sitemap limit to 50.000.
10/01/2025 | All types of IO-resources now be served via website/domain instead of CDN
14/01/2025 | Updated UiKit framework to version 3.21.16
14/01/2025 | Move index fieldtype config to global settings.
Fixes
09/01/2025 | Fixed sitemap.xml redirect.
14/01/2025 | Fixed main navigation subcategories stacking bug.
6.0.0
01/12/2024
This release introduces significant technological upgrades to enhance performance, functionality, and future-proofing of the system:
Upgrade to .NET 8: The codebase has been migrated from .NET Framework 4.7.2 to .NET 8, delivering improved speed, stability, and security.
Umbraco 13: The platform has been upgraded from Umbraco 8 to Umbraco 13, providing a modern CMS experience and better support for future developments.
Lucene 4: The search and indexing engine has been updated from Lucene 3 to Lucene 4 via Lucene.NET, eliminating the need for third-party libraries for filtering.
Process for Updating Customized Solutions
Preparation and merge:
Ensure the solution is updated to the latest Chainbox webshop Version 5. Updates introduced in v5 were designed to minimize disruptions during the migration.
Manual review:
Customizations with fundamental impacts on the application must be manually reviewed and adapted for compatibility with the new platform.
Search/Index customizations:
Any modifications related to Lucene 3 need to be reimplemented for compatibility with Lucene 4, ensuring consistent search and filtering behavior.
Testing and validation:
The migrated solution must undergo thorough testing in staging and production environments to ensure stability and functionality.
This version lays a modern, robust foundation for future enhancements and ensures compliance with the latest technology standards.
Last updated