Feature #30051
Short, unique identifiers for elements
| Status: | Accepted | Start date: | 2011-09-19 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | Andreas Wolf | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Complexity: | ||||
| Votes: | 0 |
Description
The current way of generating identifiers creates some problems with deeply nested structures, e.g. in IRRE. Therefore, we should try to avoid these long identifiers in the future.
One possible approach would be to generate an identifier per record, that is used as part of a prefix for all elements, and then do the identifiers for all fields as is currently done for the topmost TCEforms level, like this:
normal fields: data[tt_content][1][somefield] -> data[32493ca2][somefield] FlexForm fields: data[tt_content][1][pi_flexform][sDEF][lDEF][somefield][vDEF] -> data[21879ac3][sDEF][lDEF][somefield][vDEF]
with 32493ca2 being the identifier for tt_content:1 and 21879ac3 the identifier for the contents of the FlexForm field pi_flexform in tt_content:1. This would also apply to all other identifiers, e.g. ids.
We then also need a mapping table from the identifiers to the old structures, e.g. for re-mapping on the server side before passing the data to TCEmain.
Maybe we could also get rid of the overly complex structures for FlexForms, at least in TCEforms.