-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v8: Allow creation of all types of content in root if unset #4414
Comments
I've got this. I'm assuming this should also be extended to moving/copying/restoring content. Fun fact: This is already the case for media (although it doesn't work for move/copy). |
PR in #4418 |
@kjac Thanks for the PR!! 😄 haha I somehow just knew you would pick this up .. actually thought about pinging you, but figured you would snatch it up anyways 😃 |
Hahaha! I'm all in it for the editor experience 😆 |
All tested & fixed. Thanks @kjac |
If no content types have been defined with the 'Allow in root' setting - all content types should be allowed when creating root content.
It makes very little sense for new developers that they cannot create content of the content type they just created if they did not see and set the 'Allow in root' setting while creating it.
As soon as this setting has been used on at least one document type, it should however be enforced to only allow selected types as root content.
The text was updated successfully, but these errors were encountered: