Can't use "Author" as Content Type

[hishamco]

Nowadays, we can't use Author as a content type, which is unusual. I remember @MikeAlhayek created a list of reserved names - if I'm not wrong -

IMHO, such names are reserved in the ContentItem, but we can use them as fields, for instance. I don't think that any of us was using Author in any app, but this seems not applicable in the latest bits

/cc @Skrypt @Piedone @sebastienros

[Piedone]

Are you saying that "Author" can't be used as a content type name, and this restriction should be removed? How does OC prevent you from using it?

[hishamco]

Try to create a content Type Named Author, a message will appear "The Technical Name is reserved for internal use."

https://github.com/OrchardCMS/OrchardCore/blob/9420ab72d986a42a6a98b75d64eb54ba6bd5f7ef/src/OrchardCore.Modules/OrchardCore.ContentTypes/Controllers/AdminController.cs#L126-L129

[MikeAlhayek]

I did not add this restriction. I am not sure what is the reason for this restriction, but we can't lift it without first looking into the reasoning it was added to begin with.

[hishamco]

Sorry @MikeAlhayek, I thought you did it; I will check the history

[hishamco]

FYI the @deanmarcussen who added this restriction in #9353

[Piedone]

Seems justified, then. Nothing to do here, I think.

[sebastienros]

We have a lot of names that can't be used as content types due to our design decisions. Maybe we could have a service that allows module to provide such names. But that might leak some content management notions everywhere.

[github-actions[bot]]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.