Details
-
Bug
-
Resolution: Fixed
-
High
-
2.2.3, 2.3.2, 2.4.2, 2.5.0-rc2
-
None
Description
The in-memory changing changes introduced in 2.5-rc2 breaks bc for handlers and for documented way to clear cache in cases like:
- $pool->clear()
- $pool->deleteItems(['ez-language-2'])
- $pool->invalidateTags(['language-2'])
These currently don't clear in-memory cache.
The two last are not common, however the first one is, and once we try to add caching for content info or locations meta info there will be common use cases for clearing content cache that will break.
Attachments
Issue Links
- clones
-
EZP-30335 As a Developer I want in-memory cache to clear cache using LFU approach
- Documentation Done
- relates to
-
EZP-29470 As a developer I want trace for uncached Persistence calls
- QA
-
EZP-29659 As a v2 Developer I want support for InMemory SPI cache
- QA
-
EZP-30006 As a Developer I possibility to load several languages at once
- QA
-
EZP-29821 As a Developer I want less SPI calls to be done by Admin UI
- Closed