Create action not always default

[bjarnef]

Which Umbraco version are you using?

16.2.0

Bug summary

I have noticed while working recently with v16, that create action is not always registered as default action.

Sometimes I have even got the Deploy actions here initially instead of the normal + create action.

Often not an issue when just refreshing the page.

But I wonder why it sometimes happens?

Specifics

No response

Steps to reproduce

Expected result / actual result

No response

[github-actions]

Hi there @bjarnef!

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 🤖 🙂

[nielslyngsoe]

Hi @bjarnef, since this is not happening for any of the Core Actions, it might reveal that it is a race condition. Cause by the deploy action uses the exact same weight as the Core item. And then the order comes down to who registers first.
I will transfer this to a Deploy Issue.

[ronaldbarendse]

Hi @bjarnef! I've not seen this before and can't seem to reproduce it, although we did fix a tree related issue in Deploy 16.0.1 (so make sure to update to the latest version).

@nielslyngsoe Regarding the weight, I see the CMS uses weight: 1200 for the create document action and all Deploy actions have a weight below 100:

Alias	Weight
Deploy.EntityAction.Queue	95
Deploy.EntityAction.EnvironmentRestore	90
Deploy.EntityAction.TreeRestore	80
Deploy.EntityAction.PartialRestore	70
Deploy.EntityAction.Compare	60
Deploy.EntityAction.Import	60
Deploy.EntityAction.EnvironmentExport	50
Deploy.EntityAction.Export	40

This should exclude the race condition/registration order issue, right?

[bjarnef]

@nielslyngsoe @ronaldbarendse it doesn't happen all the, but mainly after being logged out and logging back in. I also noticed once the "reload/refresh" was default action, but refreshing page in that scenario solves the issue.

The project is using CMS 16.2.0 and Deploy v16.0.2

[ronaldbarendse]

Hmm, interesting! This doesn't sound like a Deploy specific problem then. Are the entity actions not correctly ordered or are some completely missing?

@nielslyngsoe I'll leave it up to you to re-open this issue and move it back to the CMS tracker, if you think it requires further investigation/fixing in the CMS.

[bjarnef]

Just saw this after logged in on live environment for the first time:

It trigger in this case "Create" modal:

Weird thing is it use icon from "Import" action:

but import trigger this modal:

It seems mainly to be related to after being logged in (and when signed out and logging back in).
Perhaps something regarding registration at this state.

[nielslyngsoe]

Hi @bjarnef your latest finding here should be fixed in next version of Umbraco Backoffice. :-)

[bjarnef]

@nielslyngsoe not sure if it is same issue, but I also noticed different ordering in tree nodes:

After refresh:

[github-actions]

Hi there @bjarnef!

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 🤖 🙂

[ronaldbarendse]

I've transferred this back to the CMS issue tracker and reopened it, since it does look like the weight of multiple things (at least the default entity action and tree nodes) isn't always rendered correctly...