The behaviour of how content elements are retrieved can be controlled by one mechanism at the moment. The “collect” flag. But just see description for the possible properties of
10.source.postUserFunc.XXXXX
in the table below:
Property: | Data type: | Description: | Default: |
|---|---|---|---|
field | string | The name of the fields from which the content elements shall get retrieved. This is required. | |
collect | boolean (0/1) | If set to 1 not just the contents of the first page which contains content elements will get shown but rather all content elements of all pages below the actual one get collected and displayed. | |
reverse | boolean (0/1) | If set the elements from collected pages will be concatenated in reverse order. Just important if collect = 1 | |
innerReverse | boolean (0/1) | If this flag gets set the content elements from each column will get displayed in reverse order. This is true wheter or not collect = 1. | |
uid | stdWrap | Use this option to define the UID from where the content should be inserted | |
max | integer | This option defines the amount of content parts to be displayed | |
slice | string | Same function as the php function: http://php.benscom.com/manual/de/function.array-slice.php Examples:(including Parts 1,2,3,4,5)slice = 2 -> Parts: 3,4,5slice = -2,1 -> Parts: 4slice = 0,3 -> Parts: 1,2,3 | |
langChild | integer | set to 1 if translation is by translation field or by language children (l18n_parent) | 0 |
