For a complete list of breaking changes please refer to the bc changelog changelog file.
The minimum required PHP version for Shopware 6.4.0.0 is now PHP 7.4. Please make sure, that your system has at least this PHP version activated.
We've also added support for PHP 8.0. While Shopware is de-facto ready for PHP 8.0,
some dependencies do not support PHP 8.0 in their composer.json in theory.
Until these dependencies add official PHP 8.0 support in their composer.json,
we decided to set the config.platform.php of the development root composer.json to 7.4.0.
This is to prevent composer failing to update dependencies, because of PHP version constraints.
The PHP extension sodium is now a requirement for Shopware 6.4.0.0.
With Shopware 6.4 we are now requiring the composer-runtime-api with version 2.0.
These means that Shopware is now only installable with Composer 2.
Installation with Composer 1 is no longer possible and supported.
Symfony was upgraded to 5.2.x. It is now locked to the minor 5.2 version.
Corresponding to the semantic versioning strategy of Shopware, we changed the API versioning to match the major versions of Shopware. As the API stays backward compatible for the life cycle of the whole major version, there is no need for a separate versioning. Therefore we also removed the unnecessary version from the URL pattern.
- /[store-]api/v{version}/...
+ /[store-]api/...With Shopware 6.3.5.0 we already made the new URL pattern available as an additional alias. This enables you to test your application with the new URL pattern within the 6.3 major cycle, before updating to the 6.4 version.
Of course, it is still important for an external service to know, which version of Shopware is used. Therefore we added a new information endpoint, which provides this information. The new endpoint is also available with Shopware 6.3.5.0, so you can switch to this pattern in the 6.3 major cycle.
GET /api/_info/versionTo have the version within the URL pattern offered the advantage of telling Shopware which version requirement you expect with the request. To still fulfill this need, we extended the possibilities even further. You can send additional expectations via headers within your request, which is not only limited to the version.
GET /api/test
sw-expect-packages: shopware/core:~6.4,swag/paypal:*This example expects that the Shopware version is at least 6.4, and the PayPal extension is installed in any version. If the conditions are not met, the backend will respond with a 417 HTTP error.
During the life cycle of a major version, there still might be non-breaking changes to the API.
To make this information available, every new field will have a since flag, which indicates, when the new field was added to the API.
All new fields will be included in the response.
You can still remove unwanted fields from the response by using the includes property to reduce the output.
The information is shown in the Swagger documentation, in the description of the route in the schema if the request / response.
/api/_info/swagger.htmlAlso deprecated fields, which will be removed with the next major version, are marked in the schema with a deprecated flag.
This enables you to react to upcoming changes as early as possible.
The default of the currency filter in the administration changed. It will now display by default 2 fraction digits and up to 20, if available.
- value is 15.123456 -> output is 15.12
- value is 15.12345678913245 -> output is 15.12
- value is 15.123456 -> output is 15.123456
- value is 15.12345678913245 -> output is 15.12345678913245
In case you've been creating empty feature sets using the current faulty behaviour, please make sure to at least include
a name for any new feature set from now on.
System and plugin configurations made with
config.xmlcan now have less than 4 characters as configuration key but are not allowed anymore to start with a number.
We've deprecated $asset-path because it was generated at compilation time and contained the APP_URL by default,
which should only be relevant to administration. Instead, $app-css-relative-asset-path is to be used, which is an
url that is relative to the app.css that points to the asset folder.
As a side effect, the fonts are now loaded from the theme folder instead of the bundle asset folder. This should work out of the box, because all assets of the theme are also copied into the theme folder.
The plugin manager in the administration is removed with all of its components and replaced by the sw-extension module.
The controller for the plugin manager with all of its routes is removed and replaced by the ExtensionStoreActionsController.
The new ApiAware flag replaces the current ReadProtected flag for entity definitions.
See NEXT-13371 - Added api aware flag
The league/oauth2-server and lcobucci/jwt dependencies were upgraded to their next respective major versions.
This comes with a break in our current oauth2 core implementation.
See the commit on GitHub for details.
Previously all Storefront relevant SCSS files (*.scss) of an extension have automatically been loaded and compiled by shopware when placed inside the directory src/Resources/app/storefront/src/scss.
Because all SCSS files have been loaded automatically it could have let to inconsistent results when dealing with custom SCSS variables in separate files for example.
This behaviour has been changed and now only a single entry file will be used by extensions which is the YourPlugin/src/Resources/app/storefront/src/scss/base.scss or YourApp/Resources/app/storefront/src/scss/base.scss.
All the SCSS files in this example directory have been loaded automatically:
└── scss
├── custom-component.scss
├── footer.scss
├── header.scss
├── product-detail.scss
└── variables.scssNow you need a base.scss and need to load all other files from there using the @import rule:
└── scss
├── base.scss <-- This is now mandatory and loads all other files
├── custom-component.scss
├── footer.scss
├── header.scss
├── product-detail.scss
└── variables.scssThe base.scss for the previous example directory would look like this in order to load all SCSS properly:
// Content of the base.scss
@import 'variables';
@import 'header';
@import 'product-detail';
@import 'custom-component';The current default mailer Swift_Mailer was exchanged with Symfony\Mailer.
If you have configured the Mailer using the environment variable MAILER_URL, you have to change this to the new syntax.
Refer to the Symfony Documentation for the updated syntax.
Previously, the sales channel object in the context contained all countries assigned to the sales channel. This data has now been removed.
The access via $context->getSalesChannel()->getCountries() therefore no longer returns the previous result.
To load the countries of a sales channel, the class \Shopware\Core\System\Country\SalesChannel\CountryRoute should be used.
If you're using the api.custom.store.download route, be aware that its behaviour was changed.
The route will no longer trigger a plugin update.
In case you'd like to trigger a plugin update, you'll need to dispatch another request to the
api.action.plugin.update route.
- Removed the column
currency.decimal_precision. The rounding is now controlled by theCashRoundingConfigin theSalesChannelContext - Removed the column
product.purchase_price. Replaced byproduct.purchase_prices - Removed the column
customer_wishlist_product. This column was never used, and the feature still requires a feature flag.
We've grouped the migrations into major versions. By default, all non-destructive migrations are executed up to the current major. In contrast, all destructive migrations are executed up to a "safe" point. This can be configured with the mode.
There are three possible values for the mode:
--version-selection-mode=safe: Execute only "safe" destructive changes. This means only migrations from the penultimate major are executed. So with the update to 6.5.0.0 all destructive changes in 6.3 or lower are executed.--version-selection-mode=blue-green: Execute as early as possible, but still blue-green compatible. This means with the update to 6.4.1.0 from 6.4.0.0 all destructive changes in 6.3 or lower are executed.--version-selection-mode=all: Execute all destructive changes up to the current major.
To allow this selection, we've moved all migrations from \Shopware\Core\Framework\Migration\MigrationSource.core
into \Shopware\Core\Framework\Migration\MigrationSource.core.V6_3. core is now empty by default. You can still extend it.
The execution order is now like this:
core.V6_3core.V6_4- newer majors...
core
This means all new migrations need to be created in the matching major folder. Currently, this is src/Core/Migration/V6_3,
it will be src/Core/Migration/V6_4 soon. To keep the backwards compatibility, Migrations still need to be defined in src/Core/Migration.
To accomplish that, just create it in the versioned folder and create a class in the old folder that simply extends the other class without changing anything.
The method \Shopware\Core\Framework\Migration\MigrationCollectionLoader::collectAllForVersion will return a collection with all "safe" MigrationSources including core.
bin/console database:migrate --all core
Should do the sames as before. Alternatively, you can run it for each major:
bin/console database:migrate --all V6_3bin/console database:migrate --all V6_4- etc
bin/console database:migrate-destructive --all core
This behavior changed! By default, this will only executes "safe" destructive changes. It used to execute all destructive migrations.
To get the old behavior, run:
bin/console database:migrate-destructive --all --version-selection-mode=all core
To run the destructive migrations as early as possible but still blue-green, run:
bin/console database:migrate-destructive --all --version-selection-mode=blue-green core
Changes to auto updater
We've changed the updater to only execute safe destructive migrations. It used to execute ALL destructive changes.
To allow implementing this feature with a feature flag, we've to create a legacy migration in src/Core/Migraiton,
which simply extends from the real migration in src/Core/Migration/$MAJOR. All migrations have been changed in that way.
The bin/console database:create-migration command automatically creates a legacy migration.
Due to the way that img's object-fit works, it is not possible to mimic the 'Auto' setting of the block background. This means that elements that currently have 'Auto' set as their background mode will look different.
This change update the primary key of cms_page, cms_slot, cms_block and cms_section and the corresponding translation tables. If your plugin incorporates foreign keys to these tables you will need to update your migrations and dal entity definitions.
Please use bin/console dal:validate to see if you have to adjust your plugins anywhere.
If your plugin is already installed the shopware core migration will take care of adjusting the foreign key.
A new column {TABLE_NAME}_version_id is created, and the constraint widened.
You will just have to add a version reference field in your definitions.
For a cms_page relation this would make these lines mandatory in your field definition like this:
use Shopware\Core\Content\Cms\CmsPageDefinition;
use Shopware\Core\Framework\DataAbstractionLayer\Field\ReferenceVersionField;
new ReferenceVersionField(CmsPageDefinition::class);If your plugin is newly installed you should add a combined foreign key to your CREATE TABLE statement.
CREATE TABLE _TABLE_ IF NOT EXISTS
`cms_page_id` binary(16) DEFAULT NULL, # the existing column
`cms_page_version_id` binary(16) NOT NULL, # from now on mandatory
# [...]
KEY `_NAME_` (`cms_page_id`,`cms_page_version_id`),
CONSTRAINT `_NAME_` FOREIGN KEY (`cms_page_id`, `cms_page_version_id`) REFERENCES `cms_page` (`id`, `version_id`) ON DELETE CASCADE ON UPDATE CASCADE # notice the two column on two column key
);Due to the migration changing the product table as well, the update process might be slower than usual.
Removed default for detail.showReviews, use core.listing.showReview instead.
We upgraded the guzzle dependency to a new major version v7. Please refer to the guzzle upgrade guide to make sure your plugins are compatible.
To improve the performance and reliability of Elasticsearch, we have decided to refactor Elasticsearch in the first iteration in the Storefront only for Product listing and Product searches. This allows us to create a optimized Elasticsearch index with only required fields selected by an single sql to make the indexing fast as possible. This also means for extensions, they need to extend the indexing to make their fields searchable.
Here is an simple decoration to add a new random field named myNewField to the index.
For adding more information from the Database you should execute a single query with all document ids (array_column($documents, 'id'')) and map the values
<service id="MyDecorator" decorates="Shopware\Elasticsearch\Product\ElasticsearchProductDefinition">
<argument type="service" id="MyDecorator.inner"/>
<argument type="service" id="\Doctrine\DBAL\Connection"/>
</service><?php
use Shopware\Core\Defaults;
use Shopware\Core\Framework\Context;
use Shopware\Core\Framework\DataAbstractionLayer\EntityDefinition;
use Shopware\Core\Framework\Uuid\Uuid;
use Shopware\Elasticsearch\Framework\AbstractElasticsearchDefinition;
use Shopware\Elasticsearch\Framework\Indexing\EntityMapper;
use Doctrine\DBAL\Connection;
class MyDecorator extends AbstractElasticsearchDefinition
{
private AbstractElasticsearchDefinition $productDefinition;
private Connection $connection;
public function __construct(AbstractElasticsearchDefinition $productDefinition, Connection $connection)
{
$this->productDefinition = $productDefinition;
$this->connection = $connection;
}
public function getEntityDefinition(): EntityDefinition
{
return $this->productDefinition->getEntityDefinition();
}
public function getMapping(Context $context): array
{
$mapping = $this->productDefinition->getMapping($context);
$mapping['properties']['myNewField'] = EntityMapper::INT_FIELD;
// Adding nested field with id
$mapping['properties']['myManyToManyAssociation'] = [
'type' => 'nested',
'properties' => [
'id' => EntityMapper::KEYWORD_FIELD,
],
];
return $mapping;
}
public function extendDocuments(array $documents, Context $context): array
{
$documents = $this->productDefinition->extendDocuments($documents, $context);
$productIds = array_column($documents, 'id');
$query = <<<SQL
SELECT LOWER(HEX(mytable.product_id)) as id, GROUP_CONCAT(LOWER(HEX(mytable.myFkField)) SEPARATOR "|") as relationIds
FROM mytable
WHERE
mytable.product_id IN(:ids) AND
mytable.product_version_id = :liveVersion
SQL;
$associationData = $this->connection->fetchAllKeyValue(
$query,
[
'ids' => Uuid::fromHexToBytesList($productIds),
'liveVersion' => Defaults::LIVE_VERSION
],
[
'ids' => Connection::PARAM_STR_ARRAY
]
);
foreach ($documents as &$document) {
// Normal field directly on the product
$document['myNewField'] = random_int(PHP_INT_MIN, PHP_INT_MAX);
// Nested object with an id field
$document['myManyToManyAssociation'] = array_map(function (string $id) {
return ['id' => $id];
}, array_filter(explode('|', $associationData[$document['id']] ?? '')));
}
return $documents;
}
}When searching products make sure you add elasticsearch aware to your criteria to use Elasticsearch in background.
$criteria = new \Shopware\Core\Framework\DataAbstractionLayer\Search\Criteria();
$context = \Shopware\Core\Framework\Context::createDefaultContext();
// Enables elasticsearch for this search
$context->addState(\Shopware\Core\Framework\Context::STATE_ELASTICSEARCH_AWARE);
$repository->search($criteria, $context);The rules for line items are now considering also nested line items. Before the change, only the first level of line items was taken into account. Check your rules, if they still take effect as intended.
We've replaced \Shopware\Core\Framework\DataAbstractionLayer\Indexing\TreeUpdater::update with \Shopware\Core\Framework\DataAbstractionLayer\Indexing\TreeUpdater::batchUpdate,
because update scaled badly with the tree depth. The new method takes an array instead of a single id.
We've added the new method prefetchExistences to the interface \Shopware\Core\Framework\DataAbstractionLayer\Write\EntityWriteGatewayInterface.
The method is optional, and a valid implementation is to not prefetch anything. The method was added to allow fetching the existence of more than one primary key at once.
We've added the new method normalize to the interface \Shopware\Core\Framework\DataAbstractionLayer\FieldSerializer\FieldSerializerInterface.
A valid implementation is to just return $data. The AbstractFieldSerializer does that already.
The method should normalize the $data if it makes sense. For example, the core serializers do the following in the normalize step:
- generate missing ids (
IdField) - resolve foreign keys (
FkFieldandAssociation) - normalize structure for example for translations (there are multiple ways to define them)
- collect primary keys in
PrimaryKeyBag
All events that are dispatched in a sales channel context now implement ShopwareSalesChannelEvent. The return type getContext may have changed from SalesChannelContext
to Context. To get the sales channel context, use getSalesChannelContext.
We've added a new implementation to calculate product prices. product.cheapestPrice replaces product.listingPrices.
Update your queries accordingly.
The BlacklistRuleField and WhitelistRuleField implementations were dropped.
Create an own many-to-many association to achieve this functionality
The DAL cache was removed.
Therefore, calling Shopware\Core\Framework\Context::disableCache has no more effect.
The following SQL operations will throw an exception, if called with Doctrine\DBAL\Connection\::executeQuery:
UPDATE, ALTER, BACKUP, CREATE, DELETE, DROP, EXEC, INSERT, TRUNCATE
We've enhanced the DAL to automatically detect a pattern following the AntiJoinFilter.
Therefore, it was removed.
We've replaced the ProductPriceDefinitionBuilder by the ProductPriceCalculator
Removed the parameter swagShopId from StorefrontRenderEvent, Use appShopId instead.
The modal to select payment or shipping methods was removed entirely.
Instead, the payment and shipping methods will be shown instantly up to a default maximum of 5 methods.
All other methods will be hidden inside a JavaScript controlled collapse.
The changes especially apply to the confirm checkout and edit order pages.
We refactored most of the payment and shipping method storefront templates and split the content up into multiple templates to raise the usability.
According to document of flatpickr (https://flatpickr.js.org/formatting/), ISO Date format is now supported for the datepicker component.
With datetime-local dateType, the datepicker will display the user's browser time.
The value will be converted to UTC value.
- Both dateType
datetimeanddatetime-localuse UTC timezone(GMT+00:00). - If user selects date
2021-03-22and time12:30, the output is2021-03-22T12:30:000+00:00.
- With dateType
datetime, user selects date2021-03-22and time12:30, the output is2021-03-22T12:30:000+00:00. - With dateType
datetime-local, user selects date2021-03-22and time12:30and timezone of user isGMT+07:00, the output is2021-03-22T05:30.00.000Z.
We removed the following deprecated color / gradient variables:
$color-biscay
$color-cadet-blue
$color-crimson
$color-contrast
$color-deep-cove
$color-emerald
$color-gray
$color-gutenberg
$color-kashmir
$color-iron
$color-light-gray
$color-link-water
$color-pumpkin-spice
$color-purple
$color-shopware-blue
$color-steam-cloud
$color-gradient-dark-gray-start
$color-gradient-dark-gray-end
$gradient-dark-grayThis package has now version 6.4.1, take a look at the github changelog for breaking changes.
Removed node-sass package because it is deprecated. Added the sass package as replacement. For more information take a look deprecation page.
The shopware.config variable was removed. To access a system config value inside twig, use config('my_config_key').
The shopware.theme variable was removed. To access the theme config value inside twig, use theme_config('my_config_key').
The properties in the product stream are now defined with a allowed list. This can cause some missing fields which were available in earlier releases. If you need them also in feature releases then you can add them to the allowed list with an plugin.
Just use the method addToEntityAllowList or addToGeneralAllowList from the productStreamConditionService.
Example:
Shopware.Service('productStreamConditionService').addToEntityAllowList('product', 'yourProperty');