FS_LIST, PAGE type → CMS_INPUT_SECTIONLIST

Please observe the following when converting FS_LIST to CMS_INPUT_SECTIONLIST.

Data that has been saved using an FS_LIST, PAGE type can be read, processed, and saved by a CMS_INPUT_SECTIONLIST component following a conversion to CMS_INPUT_SECTIONLIST (so long as the identifier is kept – the name attribute).

Sample form

Form definition for the FS_LIST input component:

<FS_LIST name="IDENTIFIER">
    <DATASOURCE type="page"/>
      <LANGINFOS>
        <LANGINFO lang="*" label="Sections of this page"/>
      </LANGINFOS>
</FS_LIST>

Form definition for the CMS_INPUT_SECTIONLIST input component:

<CMS_INPUT_SECTIONLIST name="IDENTIFIER">
  <LANGINFOS>
    <LANGINFO lang="*" label="Sections of this page"/>
  </LANGINFOS>
</CMS_INPUT_SECTIONLIST>

Output

The output must be adjusted accordingly during the template migration. The data format is compatible in both directions, so CMS_INPUT_SECTIONLIST can read the data from FS_LIST and vice versa.

FS_LIST

$CMS_FOR(section, fs_list_page)$
    <li>
        <a href="#$CMS_VALUE(section.uid)$">
            $CMS_VALUE(section.label)$ -> Sectionname: $CMS_VALUE(_section.uid)$
        </a>
    </li>
$CMS_END_FOR$

CMS_INPUT_SECTIONLIST

$CMS_FOR(section, st_sectionlist)$
    <li>
        <a href="#$CMS_VALUE(section.anchorName)$">
            $CMS_VALUE(section.text)$ -> Sectionname: $CMS_VALUE(section.sectionName)$
        </a>
    </li>
$CMS_END_FOR$