Today we released the Shopware 6 Release Candidate (RC) - one of the last steps before the final release in January. You can download the RC here. As always you will find all the details about the changes in the changelog. In this blog post, we present to you the highlights of the release candidate.
What does Release Candidate mean?
This version serves to collect last feedback before the release. Breaking changes can still happen up to the release if they are carried out as part of bug fixes. After the release of the RC up to the final version no new features will be added, only bugs will be fixed. With the RC you already have an overview of the almost final version of Shopware 6.
These are the highlights of the Release Candidate
The Production Template facilitates the setup and deployment of changes via GitHub. Shopware 6 can now be set up via a simple composer workflow.
The sections of the adventure worlds now have a sidebar with actions. By clicking on the section icon, the section "active" will appear and the menu for editing will open. The section settings now share the menu with the block settings.
The CMS form view, which is also located in the category tab "Contents", has been adjusted. So it harmonizes better with the sections.
The Admin API and the Sales Channel API are versioned. This means that whenever a breaking change affects the API, we will release a new API version. We only release a new API version with each major release, the old API version will remain supported until the next major release, e. g. 6.2.0 or 6.3.0.
The API version you want is determined by the API route you call, e. g. /api/v1/.... for version 1 of the Admin API or /sales-channel-api/v2 for version 2 of the “SalesChannelApi”.
The currently available API versions are available as container parameters at kernel.supported_api_versions.
Google Pagespeed is an important tool to measure the speed of a page, here important suggestions for improvement have been implemented by Google. Among other things, we have optimized the following points:
Missing alt-, title- and aria-attributes added
async attribute for central <script> tag added to storefront
Removed unused fonts and optimized font loading with "font-display", see https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/font-display
Contrasts and colors improved for better legibility
Several display errors fixed
Each Storefront POST request is checked for a valid CSRF token to prevent Cross-Site Request Forgery. Shopware offers two different token generation mechanisms:
By default, the recommended method is to generate CSRF tokens server-side via Twig and include them in forms.
Ajax can also be used to generate tokens and attach them to POST requests. The CSRF mode must be set to work with ajax. This mode is required if a third-party cache provider such as Varnish is to be used. Read more here.
Of course, Shopware 6 also comes with a cookie consent tool, which allows you to leave the configuration of the cookies to the shop user. Plugin manufacturers must design all cookies and local storage entries in such a way that they are only set when the cookies of the plugin are accepted. You can read more about this here.
With the sales channel type "product comparison", file exports can be generated from dynamic product groups and imported into comparison portals such as billiger.de, idealo.de or Google Shopping.
404/Maintenance layouts from the CMS
In the master data, CMS layouts can be selected as a 404 error page and content for displaying the maintenance mode.
The maintenance mode can be activated in the settings of each sales channel.
Reaching your goals together
We are incredibly grateful to all users and contributors who have tried Shopware 6 since its inception and given us feedback every step of the way. Shopware 6 Final will be released in January. So install the Release Candidate now and make sure that your feedback, thoughts, and expertise are incorporated into the final version.