We use subtypes in Composer to match a type of article with a specific layout. All our articles are migrated with the original subtype from our old publishing platform.
Now in ARC, we are not going to use anymore the subtype=3 to create new articles because in the new design we merge the layouts 3 and 1. The subtype 3 is deactivated in Composer Settings and everything is working well with the resolver and the article in production looks good but if we use Composer UI to edit a subtype=3 article, the field subtype is blank.
In the future it will be normal for us to add new subtypes or deactivate others and we expect that if we deactived a subtype, the field in the meta article (Composer UI) should be displayed regardless of whether it is active or not. Maybe what Composer should not let me do is save the article without selecting an activated subtype.
It also seems unnecessary to us that if we deactivate a subtype we have to massively modify all the historical articles that have that parameter and for that maybe the solution should be in Composer UI.
Mauro Terrizzi
| Categories | Other |
Hi Lawrence! Exactly. If you edit a story with subtype=x (deactivated) in the field subtype you will see an empty/null value. It´s not clear if the article use a deleted or deactivated subtype or if something is broken. Maybe could be a good idea to show a value similar to subtype="X (Deleted/Deactivated)" or subtype="Not available" instead of null.
Hello! Thank you for your idea. Just to clarify, the problem you are facing is that:
If I delete or deactivate a subtype 'x', that subtype 'x' will no longer show in the field of a story that I know historically used subtype 'x'.