Hello,
we're just finishing the migration of the FS_LIST components in our templates (we're late, I know). Most things worked as expected, but now I have run into problem.
In a DB-Schema template, we had one FS_LIST component (type inline, for section templates) which was replaced with a FS_CATALOG component as per the migration guide. The replacement has worked as far as I can tell: When viewing an entry in the corresponding datasource, the catalog component is shown and its entries are there.
I changed the HTML output of the template as follows (gallery is the mapped column for the FS_CATALOG field in the form):
...
$CMS_FOR(picture, #row.gallery)$
$CMS_VALUE(picture.item)$
$CMS_END_FOR$
...
When using "Display preview errors" for an entry in the datasource now, I see errors like:
09.06.2020 13:10:20.968 WARN ($CMS_VALUE(picture.item)$ at 207, 7): Replacing null value with empty default! Undefined field 'item'!
My assumption was that this happens because the values in the database are still stored in the old FS_LIST format? So I manually re-saved an entry to update it. After doing so, the preview errors disappeared.
But now the list entries do not appear anymore on the page. In fact, the list is shown as empty when I add some debugging information in the HTML:
$CMS_VALUE(#row.gallery.size())$ $-- shows 0 ??? and #row.gallery.isEmpty would evaluate to true --$
But the FS_CATALOG entries are clearly there in the datasource entry...
What has happened here? Do I need to access the FS_CATALOG differently here? Any info would be appreciated.