Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
5.1
-
None
Description
The reason for adding and using internal parameter $updatePathIdentificationString was support for (in PAPI deprecated) ezcontentobject_tree.path_identification_string, which is specific for Legacy Storage engine.
Alternatives would have involved adding too much complexity to the Legacy Storage engine.
Some references:
https://github.com/ezsystems/ezpublish-kernel/pull/207
https://github.com/ezsystems/ezpublish-kernel/pull/334
Attachments
Issue Links
- relates to
-
EZP-20106 Repository is aware of legacy storage specific ezcontentobject_tree.path_identification_string
- Closed