Make it easier to allow varying properties, or set as mandatory

[skttl]

When you are converting a regular site to be multilingual, you have to click through every property setting dialog and mark as "allow varying". I would like to be able to do this a bit easier.

Without taking the option away from the dialog, I propose to add a simple button (could be visible only on hover/focus) for doing this right from the overview, see gif:

You could also make the * Mandatory on the left clickable, to remove the mandatory setting from the property.

The options in the hover-part should be in context to the doctype, so if the doctype does not allow varying, the button for allow varying on the property should not be shown.

[nul800sebastiaan]

Sure, it definitely could be easier. But I can pretty much predict the answer to be: not in this way. 😉

I'll get back to you after we have a chat at HQ.

[skttl]

Cool :) There is a similar discussion going in #5438

[umbrabot]

Hiya @skttl,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant
This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[skttl]

@umbrabot still relevant

[umbrabot]

Hiya @skttl,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant
This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[skttl]

@umbrabot still relevant

[Zeegaan]

As this is a feature request, I am moving it to the discussions board 👍