Details
-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
None
Description
The last refactoring for version/content has left an issue:
The SPI content contains an array of locations. This is not synced with public API yet with "ugly" consequences: If PAPI impl wants to fetch locations for a content info it has to load the whole content.
(e.g. content is then loaded unnecessarily on loading trash items)
In PAPI we have an extra method loadLocationsForContent.
Refactoring Steps:
- Remove locations from SPI Content
- Add a similar method to location handler:
getLocationsForContent($contentId, $rootLocationId) - reimplement loadLocationsForContent in PAPI
- fix all other Implementations using the loadContent method for fetching locations
Attachments
1.
|
Design new SPI methods needed for LocationHandler |
|
Closed | Unassigned | ||||||||
2.
|
Add childCount to SPI Location object |
|
Closed | Unassigned | ||||||||
3.
|
Add mainLocationId on SPI ContentInfo |
|
Closed | Unassigned |
|
|||||||
4.
|
Move SPI ContentInfo from Content to VersionInfo |
|
Closed | Unassigned |
|
|||||||
5.
|
Review new SPI methods for LocationHandler |
|
Closed | Petar Spanja (Inactive) |
|
