Is there a build-in way to load a stylesheet in the Umbraco 14 backoffice? In most cases you would declare the CSS as part of the HTML element, but in some cases loading a stylesheet globally might be needed.

I've seen several live V13 sites today telling me to either buy or configure a license. They were all working a few days ago.

I have a form which is rendered from a View Component and posts to a Surface Controller. When it's done what it needs to, the Surface Controller tries to do a

return CurrentUmbracoPage();

But fails with the above error. Is there something about it being instigated from a View Component rather than a Razor page directly?

I am using Umbraco 13.0.3:

<PackageReference Include="Umbraco.Cms" Version="13.0.3" />

Trying to run

dotnet clean

I get this error:

(ResolvePackageAssets target) -> 
         /usr/share/dotnet/sdk/8.0.100/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1064: Package Lucene.Net, version 4.8.0-beta00016 was not found. It might have been deleted since NuGet restore. Otherwise, NuGet restore might have only partially completed, which might have been due to maximum path length restrictions.

Does this mean there is a dependency on a non-existant package? I can run

dotnet restore

without problem. Is this expected behavior?

Failing to generate TypeScript from Swagger using @hey-api/openapi-ts 0.47.0

Trying to get my head around this. We are running headless, so no templates at all. The site has over 100 DocTypes. That said we do add a .Net GraphQL layer on top of an API. All the v8 content is in Nested Content which we hope to use uSync migrations to get to Block Grid / Block List, and then use the Content Delivery API as a base for the GraphQL layer. Does it make any sense for us to even consider going straight to v14? There is no rush as long as we meet the v8 EOL deadline next year. If we decide to go to v13, what will the upgrade path look like to v14?

When i publish my Umbraco website and put it on the server. it generates and error and the log shows Unhandled exception. System.IO.DirectoryNotFoundException: d:\web\localuser\site.dk\public_html\wwwroot\media\ at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root, ExclusionFilters filters) at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root) at Umbraco.Cms.Core.IO.PhysicalFileSystem.Create() But the media folder is not created in the published content. I use the 14.3.1 version Do anyone knows why or what it could be?

Does anybody know why Umbraco (Cloud) sometimes thinks the URL is on one of the azurewebsites domains? The only "fix" we've been able to find is to restart the site, which is not great but also really not that bad. But the major issue is that when it happens — because the site is built with uSkinned SiteBuilder — the whole site screams "NO VALID LICENSE" everywhere - which is very unfortunate when the client has in fact paid a good chunk of money for a valid license. Is there a way to make sure this doesn't happen?

Hi everyone, We need to use UI Builder to manage some data held in a separate database and, because of the slightly complex nature of the data we need to save/load, we're using a repository as described here: https://docs.umbraco.com/umbraco-ui-builder/v/13.ui-builder.latest-lts/advanced/repositories From there, we stubbed out our tree with some noddy data just to get it visible and we get an error that the table name doesn't exist (

Invalid object name 'Company'.

is the precise error message). After digging around, I can see that the scope provider that gets injected into our repository is pointing to the default Umbraco connection string even though we set the correct connection string in the application startup:

services.AddUmbracoDbContext<CustomDBContext>(options =>
            {
                options.UseSqlServer("name=ConnectionStrings:CustomDB");
            });

I'm at a bit of a loss as to why this would be the case. Does anyone have any ideas? Thanks

Hi all, Using uSync Migrations to migrate a site from v8 to v13. The site is undergoing quite a transformation with content being reorganized into a more logic tree structure. During the uSync migration is there a way to move a content node? Below is an example: From

Home -> Products -> [Node Currently Resides]

To

Home -> Products -> Product Category -> [Node should reside]

Thanks!