Error Mesage when clicking on the three dots to access create menu for content item which doesn't allow child types and editor has access to the settings section and the site is running in Production Mode

[marcemarc]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

12.3.7

Bug summary

This is super-obscure and only really raising it as it might be a good first-time issue for someone...

Here goes....

We are talking about what happens when you click the three dots, on a node to try to create something underneath:

In this example 'Guides' doesn't allow any document types to be created under it.

So Editors get a slidey out panel that says, you can't create anything here...

... but ...

if you are a super editor who has access to the 'Settings' section, then you'll get an option to 'Edit permissions for this Document Type'

That's handy!

But not if your environment's runtime is set to be production Umbraco:CMS:Runtime:Mode (https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/runtime-modes)

In this mode, backoffice editing things are disabled and instead of seeing this button to click to edit permissions (which you can't do in production runtime mode) - you get the following error

So I think in runtime production mode we just need to update this panel, so it doesn't try to request the API, and just says the same message as the editors you can't create things here...

It's not a show stopper! - but might be interesting for someone to dig into etc

Specifics

No response

Steps to reproduce

See steps above

Expected result / actual result

Just a message to say you can't create things here

[github-actions]

Hi there @marcemarc!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[Migaroez]

@marcemarc Nice find, I will mark it as up for grabs.

[github-actions]

Hi @marcemarc,

We're writing to let you know that we would love some help with this issue. We feel that this issue is ideal to flag for a community member to work on it. Once flagged here, folk looking for issues to work on will know to look at yours. Of course, please feel free work on this yourself ;-). If there are any changes to this status, we'll be sure to let you know.

For more information about issues and states, have a look at this blog post.

Thanks muchly, from your friendly Umbraco GitHub bot :-)

[prjseal]

Thanks for raising this @marcemarc, I'm gonna try and work on it at the hackathon today

[marcemarc]

yey good luck @prjseal gutted I can't be there this time to hack away too.

[prjseal]

@marcemarc PR raised, above. Fingers crossed.