Skip to content
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

Describe why there is no create options at the content root #7571

Closed
nielslyngsoe opened this issue Feb 4, 2020 · 4 comments · Fixed by #7635
Closed

Describe why there is no create options at the content root #7571

nielslyngsoe opened this issue Feb 4, 2020 · 4 comments · Fixed by #7635

Comments

@nielslyngsoe
Copy link
Member

nielslyngsoe commented Feb 4, 2020

When a user opens the create dialog on the root of the tree, but doesn't have any DocumentTypes allowed for creation in the root, the user sees the following screen:

image

Instead, we should allow all Document Types to be created at root, and thereby list them in the dialog. Or mention that a Document Type should be allowed.

And if there are no Document Types in the solution, we should show a screen describing that and link to the Settings Section, potential a direct link to create a new Document Type.

Something similar to this dialog, this example is taken from the create dialog on a content-node:
image

@kjac
Copy link
Contributor

kjac commented Feb 7, 2020

@nielslyngsoe this used to be the case. But if you have a look at #6580 you'll see why it isn't any longer 😀

Instead of listing all content types at root when none are configured, #6573 was introduced to aid newcomers in setting things up correctly.

@nielslyngsoe
Copy link
Member Author

@kjac thanks for highlighting that. Well good perspectives, we just need to ensure that newcomers don't reach a dead-end.
I will be back with an updated issue! :-)

@kjac
Copy link
Contributor

kjac commented Feb 11, 2020

@nielslyngsoe turns out the changes added in #6573 to help newcomers didn't work at all 🙈

#7635 fixes it 👍

@nul800sebastiaan
Copy link
Member

Fixed in #7635

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants