6.11.0-beta1

List of changes since v6.10.1.

Have a look at the BC Notes.

Bugfixes

• Large container class file when there are many siteaccesses (#2009, EZP-27497)
• Multiple StateGroup limitations in one policy combine with the "or" relationship instead of the "and" one (#2035, EZP-27528)
• Wrong language_id value in ezcontentobject_name table after updating a always available content (#2053, EZP-21753)
• Router have wrong context after language switcher link (#2051)
• Fixing deprecation notices (#2061, EZP-27652)
• Minor User & UserGroup properties fixes (#2021)
• [YML] Remove duplicated defintions of legacy search services (#2023)

Improvements

• EZP-27097: Can't copy objects to an authorized location limited by policies (#2057)
• EZP-24800 Support allowed classes limitation for object relation fields (#2022)
• EZP-27666: Services should depend upon UrlRedecoratorInterface instead of UrlRedecorator (#2056)
• EZP-27509: Improve UserService to load new translated API properties via prioritized languages list (#2043)
• EZP-27417: As a Developer I want API to allow removal of the translation from all content object versions (#2031)
• EZP-27295: Add support for Search facets in REST API (#2024)
• EZP-26885: As a Developer I want to future proof my Field Types by using Doctrine [in external storage] (#1993)
• Added community badges (#2034)
• EZP-26885: Refactor Field Types external storages to inject gateways and connection handler via DI (#1985)
• [Spec] EZP-27417: Proposed spec on content object translations removal (#2001)
• EZP-27344: Make declaration of twig "settings" block optional for custom Field Types
• EZP-27344: Move the decision about throwing MissingFieldBlockException to the rendering functions
• EZP-27473: Add methods to allow checking of version statuses (#2017)
• [APIDoc] Add missing deprecated on un-implemented loadTranslationInfos()
• [APIDoc] Add missing deprecated on un-implemented loadTranslationInfos()
• EZP-27399: Tag failing Scenario as broken because of security issue fix (#2015)