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
Assign a superordinate category to a news article ('vegetable')
Editing the the news archive, restrict available categories (that's ctrl_limitCategories in the backend html) to only subordinate categories ('melons' and 'pumpkins')
After that, individual news articles of this archive can not be saved anymore, producing the error
"Categories: Your selection contains invalid page IDs!" (didn't look up the english message, I am reading here "Ihre Auswahl enthält ungültige Seiten-IDs!")
I would like to suggest a more telling error message, for example, "One or more of the selected categories are not available for this news archive"
Would anybody like to support a feature request? Wouldn't it be cool to be able to assign some categories -- not necessarily superordinates -- to a news archive as a whole, while not allowing editors to unset these categories for individual news articles?
Versions used in testing: Contao 4.13.16, contao-news_categories 3.4.23
The text was updated successfully, but these errors were encountered:
On a previously working installation, but after upgrading to Contao 4.13.x, I noticed the following situation (steps to reproduce):
"Categories: Your selection contains invalid page IDs!" (didn't look up the english message, I am reading here "Ihre Auswahl enthält ungültige Seiten-IDs!")
I would like to suggest a more telling error message, for example, "One or more of the selected categories are not available for this news archive"
Would anybody like to support a feature request? Wouldn't it be cool to be able to assign some categories -- not necessarily superordinates -- to a news archive as a whole, while not allowing editors to unset these categories for individual news articles?
Versions used in testing: Contao 4.13.16, contao-news_categories 3.4.23
The text was updated successfully, but these errors were encountered: