On a current project we have a few properties which exist on some content types which should be visible to all but editable only by members of certain user roles. We could implement something to handle and cancel the save event but that's a bit late in the game and frustrating for the user. Ideally we would just want to render the property as read only in the UI for users without the required roles. Has anyone implemented anything like this?

We are migrating a site to azure and would like to use deployment slots. Currently we deploy updates to a staging slot and then swap them. When we swap the slots, the umbraco folder is also swapped, including the caches and log files. This coould lead to corrupted indexes. Is it possible to use an external storage for the umbraco log and cache files?

Hi all 👋 , I'm building an NextJS website with the Content delivery API. 1) What are the best practise to create a multi level navigation, are you using a custom made API or is it possible to get it from the delivery API ? 2) Is it fine to do different API calls for one page if you want to load sub-content or other content? As it doesn't seems to be possible to fetch different pages in one call. Thanks for your inputs

I want to make use of the block settings to enable some basic styling for all blocks like: background color, spacing top & bottom, padding. Is there a way to make it available for all blocks and a simple way to update the code which makes it work for all blocks.cshtml?

We're using the content api in Umbraco 13 (Cloud) and render it in a completely standalone SvelteKit-frontend. Now I want to utilize the members and the content api to create a login, is this possible and how would one go about doing so?

What would be the steps to go from NuPickers in Umbraco 7 to Contentment in Umbraco 8? We see a lot of upgrade guides that will do this for 9+ sites. But we need to get it working in v8. Any suggestiongs? Blogs? Etc?

I have a project with the following settings:

"ModelsBuilder": {
        "ModelsMode": "SourceCodeManual",
        "ModelsDirectory": "~/../MyProject.Models",
        "ModelsNamespace": "MyProject.Models",
        "AcceptUnsafeModelsDirectory": true,
        "FlagOutOfDateModels": true
    }

This works locally: I generate the models, see them added to my class library, build successfully, and the application runs without issues. However, when deploying to staging, I encounter an ambiguous reference error. It seems to reference Umbraco.Cms.Web.Common.PublishedModels instead of MyProject.Models. It’s almost as if the appSettings.Staging configuration is being ignored. I’ve added the same settings to the base appSettings. I suspect the the staging configuration is ignored; as the back office prompts for connection details during the first boot and then adds the connection string to the default appSettings file. Comparing with another site that has the same settings/setup and generates .cs files in the MyProject.Models folder, my newly deployed site only generates a .dll. I can’t find any differences in the build/publish profiles, Program.cs, appSettings, etc. Is there something obvious I’m missing? Why would it work locally but fail on the server?

Hi there - we're seeing some crazy usage numbers on some sites in Umbraco Cloud and I can't really figure out if the CDN Cache settings are doing anything... I'm assuming that if I set a TTL of 6 hours, any request for a static asset in this timeframe would not be count in the usage section? Or do I just not get how this should work?

I'm struggling with the issue that is also described here: https://github.com/umbraco/Umbraco-CMS/issues/11771. When trying to apply Vary by Culture to an existing property on a document type with Vary by Culture enabled, I get an error that says "The existing DocumentCultureVariationDto was not found for node x and language y". This blocks us from using the property in different locales. Does anyone know a solution or work around? We could create a new property with vary by culture on as a replacement, copy the content over for all the sites and remove the old non-very by culture property, but this is a very cumbersome and undesirable approach. The project is using Umbraco 13.1.0. To reproduce: 1. Create a document type with Vary by culture enabled 2. Add a property that does not have Vary by culture enabled 3. Add a second language to the project 4. Create a node of the document type in the other, new language 5. Try to enable Vary by culture for the property 6. See the exception pop up when trying to save the document type https://cdn.discordapp.com/attachments/1256162148267069462/1256162148846141440/image.png?ex=667fc3aa&is=667e722a&hm=3597c16bd3e3fd3b2014135e0cd86eb8d67cb76e3614e274d6267f4f793c3f25&

Hey, I have a folder of svg icons. I want the CMS user to be able to select one from a list or dropdown. Ideally I want the svgs to render so the user can choose visually. To be clear, I don’t want to use the Umbraco icon picker, this is a svg that’s on the file system. Any packages I can use for this? Thanks