You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In backend.js an identifier is required even if {{slug}} is not used in the config.yml::collections:slug
IDENTIFIER_FIELDS includes title and path but searches for title first. So if you specify both title and path as fields, title is always preferred.
For a microblog, the title needs to be an empty string in the rss.
In my configuration, I set title to an empty string, and path to an identifier, but I always get Collection must have a field name that is a valid entry identifier error because title is empty.
I'm not sure what the right solution is given how the logic is distributed, but ideally it would support title as an empty string with path specified as the identifier. Or more basically, only require the identifier field if {{slug}} is in the slug template string
The text was updated successfully, but these errors were encountered:
Describe the bug
Confluence of assumptions:
In
backend.js
an identifier is required even if{{slug}}
is not used in theconfig.yml::collections:slug
IDENTIFIER_FIELDS
includestitle
andpath
but searches fortitle
first. So if you specify bothtitle
andpath
as fields,title
is always preferred.For a microblog, the
title
needs to be an empty string in the rss.In my configuration, I set
title
to an empty string, andpath
to an identifier, but I always getCollection must have a field name that is a valid entry identifier
error becausetitle
is empty.I'm not sure what the right solution is given how the logic is distributed, but ideally it would support
title
as an empty string withpath
specified as the identifier. Or more basically, only require the identifier field if{{slug}}
is in theslug
template stringThe text was updated successfully, but these errors were encountered: