ezsystems/ezpublish-kernel
eZ Publish Kernel is the core of the eZ Publish/eZ Platform CMS, providing the content repository, field types, search integration, and services for building and extending PHP-based content applications with a modular, API-driven architecture.
Changes affecting version compatibility with former or future versions.
Requirements for PHP has been increased to PHP 7.1 as it is by now supported by all platforms, and provide substantial improved experience developing and working with PHP compared to PHP 5.
Requirement for Symfony has been lifted to 3.4 (LTS).
SPI: eZ\Publish\SPI\Persistence\User::deletePolicy adds role id argument Id of Role is added on deletePolicy() to be able to properly clear cache for the affected role.
"cache_pool" service is now a Symfony 3 Cache Pool instead of Stash. if you type hinted against PSR-6 you should be somewhat safe, but be on the lookout for nuances in behaviour. If you used Stash features like cache hierarchy, you'll need to adapt. Recommendation is to adapt to use Symfony Cache, but you can also setup and use Stash yourself.
Identifiers and remoteIds can no longer contain {}()/\@ characters as they are not supported in cache keys with
Symfony cache.
"cache_pool_name" siteaccess setting has been removed & replaced by "cache_service_name" as the semantic is different. The new setting should contain the full service name of a symfony cache service, by default app_cache.app is used.
The method eZ\Publish\Core\FieldType\Time\Value::fromTimestamp returns Time\Value without
taking into account the timezone. The reason for this change is consistency with the behavior of
eZ\Publish\Core\FieldType\DateAndTime\Value::fromTimestamp.
The Twig block eztime_field of eZ/Bundle/EzPublishCoreBundle/Resources/views/content_fields.html.twig is rendered using UTC timezone to avoid server timezone-related issues.
REST API no longer supports editing User Content (Content containing ezuser Field)
using Content Service. Use UserService REST API endpoints instead.
7.0 is a major version, hence does not introduce deprecations but rather removes some previously deprecated features, and in some cases changes features.
How can I help you explore Laravel packages today?