Details
-
Story
-
Resolution: Fixed
-
High
-
5.3, 2014.07, 5.4-dev
-
None
-
Castor Core S7
Description
For 5.4, 2014.09 and 5.3.3:
As 5.3 is a stable version, only the bc changes are introduced in 5.3, see below for further changes introduced in 5.4.
- Introduce new $useAlwaysAvailable argument for ContentService methods allowing language filtering, false by default
- Update Search service to pass $fieldFilters 'languages' and 'useAlwaysAvailable' to ContentService->load(), set it to true if not set.
For 5.4 and 2014.09
- Change default $matchAlwaysAvailable value of LanguageCode Criterion to true
- Change default value of $useAlwaysAvailable to true
Important reminder for 5.3 and 5.4: LanguageCode criterion still must be specified in the search query if one wants to filter by language. $fieldFilters is only present to filter translations on each and every returned Content objects.
Attachments
Issue Links
- relates to
-
EZP-21747 Translated name should be accessible from ContentInfo
- Closed
-
EZP-21171 No REST API to manage languages
- Closed
-
EZP-23116 Change SPI Content Search Handler to return ContentInfo
- Closed
-
EZP-23450 As a User I expect API's with language filters not cause exceptions when used without languageCode criterions
- Confirmed
- links to