hey out there, we've been experimenting with the idea of removing the

GeneratedCodeAttribute

from the models builder and we're trying to work out what kind of impact this would have? it came up after reviewing pull requests of umbraco upgrades. as every single generated model is regenerated, not only are our pull requests more bloated than they need to be but it also makes it very hard to spot if the upgrade has changed a property type when it was generated... when we found the

IModelsGenerator

interface in the core https://docs.umbraco.com/umbraco-cms/reference/templating/modelsbuilder/understand-and-extend#imodelsgenerator we threw some code together that strips the attribute out which results in much cleaner models. based on our experiments, this doesn't impact the running of umbraco but we're wondering if this is a safe thing to do?! according to msdn:

The GeneratedCodeAttribute class can be used by code analysis tools to identify computer-generated code, and to provide an analysis based on the tool and the version of the tool that generated the code.

we're not running the code through an analysis tool and we know that the umbraco core has generated the code.... so we're happy to live without it if its not strictly needed? any feedback would be great!

Having set the solution and project to dotnet SDK8 and C#12, I'm getting the following error when upgrading in nuget:-

Package restore failed. Rolling back package changes for 'Web'.
Version conflict detected for Umbraco.Cms.Examine.Lucene. Install/reference Umbraco.Cms.Examine.Lucene 13.1.1 directly to project Web to resolve this issue. 
 Web -> Umbraco.Cms 13.1.1 -> Umbraco.Cms.Targets 13.1.1 -> Umbraco.Cms.StaticAssets 13.1.1 -> Umbraco.Cms.Web.Website 13.1.1 -> Umbraco.Cms.Web.Common 13.1.1 -> Umbraco.Cms.Examine.Lucene (>= 13.1.1 && < 14.0.0) 
 Web -> Our.Umbraco.Extensions.Search 3.1.0 -> Umbraco.Cms.Examine.Lucene (>= 11.0.0 && < 13.0.0).

Similar if I just try to upgrade to V13.1.0 too. Any ideas or tricks? Thanks.

Hello. I've been working with Umbraco for a few months and have been tasked with upgrading a legacy (v8.x) Umbraco site to v13.6. This has gone fairly smoothly and the site is (mostly) up and working. However, the original site uses several Contact Us type forms implemented using Umbraco Forms. So I installed Umbraco.Forms.Core (v13.4.0) via NuGet and rebuilt the app. Immediately upon running the site in my dev environment I get the error "System.AggregateException: 'Some services are not able to be constructed (Error while validating the service descriptor 'ServiceType: Umbraco.Forms.Core.PropertyEditors.ValueConverters.FormPickerValueConverter Lifetime: Singleton ImplementationType: Umbraco.Forms.Core.PropertyEditors.ValueConverters.FormPickerValueConverter': Unable to resolve service for type 'Umbraco.Forms.Core.Services.IFormService' while attempting to activate 'Umbraco.Forms.Core.PropertyEditors.ValueConverters.FormPickerValueConverter'.)'" I've spent some time Googling this problem and my reading suggests that its some form of dependency injection problem (some object cannot be constructed), however I could find nothing specific to Umbraco Forms. I'm reaching out to the community in the hope that someone can point me in the right direction. I have access to the original v8 app and it has an UmbracoForms.config file inside the App_Plugins\UmbracoForms folder. At this point I suspect that I may have to replicate this file (or its json equivalent) somewhere in the v13 app, along with all the other stuff that comes from the App_Plugins\UmbracoForms folder, but I don't really know where to put these files in the v13 version of the app and what exactly is needed, and this may or may not be the actual issue that is causing the problem.

Hi all 🙂 I am pretty new to Umbraco and definitely when it comes to using it headless with their API. I posted following question on Stackoverflow which I hope you could help me answer: https://stackoverflow.com/questions/78910978/integrating-vue-3-as-frontend-with-umbraco-cms. Basically I am wondering about the general workflow when using it with Vue and also how I should handle the preview before publishing feature when using the API. Right now I just get an error when pressing preview since I am not rendering with Umbraco but on the frontend.

Hi, i could really use a hand on this. With such code:

cs
var culture = HttpContext.Features.Get<IRequestCultureFeature>()!.RequestCulture.Culture;
using var umbracoContext = _umbracoContextFactory.EnsureUmbracoContext().UmbracoContext;

var blog = (Blog)umbracoContext.Content!.GetByRoute("/blog", culture: culture.Name)!;

var response = MapBlogToResponse(blog, culture.Name);
return Ok(response);

When looking into the debugger, i only get one child one, but that child node has a list of cultures, which has two elements? https://cdn.discordapp.com/attachments/1264204453129752576/1264204453305647104/image.png?ex=669d05a5&is=669bb425&hm=fe3c9ead22043e309c73ee85ae65ff5d1889209a4fbc55253c04e81eee473c17&

Umbraco 8.17.1, site is running fine but it seems to be racking up hundreds or even thousands of these Errors a day. Am I looking for illegal characters in an image name? Or where else should I be looking?

System.ArgumentException: Illegal characters in path.
   at System.Security.Permissions.FileIOPermission.CheckIllegalCharacters(String[] str, Boolean onlyCheckExtras)
   at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, AccessControlActions control, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
   at System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String path)
   at System.Web.InternalSecurityPermissions.PathDiscovery(String path)
   at System.Web.Hosting.HostingEnvironment.MapPath(VirtualPath virtualPath)
   at ImageProcessor.Web.HttpModules.ImageProcessingModule.<ProcessImageAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   ----trimming----
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

While typing this message this afternoon I actually got 2 like this :

ImageProcessor.Common.Exceptions.ImageProcessingException: ProcessImageAsync 558 : The request /media/ykmlwb44/4-outlet-130l-red-low-res.jpg?fbclid=IwZXh0bgNhZW0CMTEAAR3fQ0xZ6tLYX6DrAtZbk4-zEUELr0Ukz3Ynt_XTvNmFkJZda55U0ZIbZ0Q_aem_9_jcDQogLzo7hF1E_uButQ could not be understood by the server due to malformed syntax.

I'm wondering if it's just someone spamming ImageProcessor along the lines of this: https://dev.to/skttl/stop-spammers-from-abusing-imageprocessor-to-flood-your-umbraco-8-logs-2c5m and if I'm safe enough to just filter them out of the logs. The site seems fine.

Version: Umbraco 14.1 With Macros being removed, we are switching over to utilizing Blocks/Elements to handle the ability for authors to add forms to their pages. We have created the form, the element (form and theme pickers) and render them out in a partial view with the proper name. If we just print out a tag, it does render, so we know the view is functional. When we try to output using the tag helper

<div><umb-forms-render form-id="@Model.Content.Form.Value" theme="@Model.Content.Theme" exclude-scripts="true" /></div>

It doesn't render anything. When we try to render out with the Component.InvokeAsync:

@(await Component.InvokeAsync("RenderForm", new { formId = Model.Content.Form, includeScripts = true }))

We get a system.stackoverflowexception error. We've also tried to hard code these values in

@(await Component.InvokeAsync("RenderForm", new { formId = new Guid("c875c7ff-1789-422c-8688-a1abae5bd707"), theme = "themename", ThemeincludeScripts = true }))

We get the same stackoverflowexception error. Has anyone run into this or is there a way to get a better/more informative error? The current documentation (https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/rte-blocks) seems to be a clone of v12/13 which still references Macros (which should be gone now).

I've been following the "create a basic website" tutorial for v13 (I'm running 13.3.1 and .NET 8)and on the section where I insert the properties that I've created in the document type, when I save and run the page I get the following error: RuntimeBinderException: 'Umbraco.Cms.Core.Models.ContentModel' does not contain a definition for 'Value' I've followed the tutorial closely, and the only thing that's different is my template. https://cdn.discordapp.com/attachments/1246106579489656983/1246106580177649846/Screenshot_2024-05-31_171913.png?ex=665b2eb0&is=6659dd30&hm=022939fb63e57696f03a08fc4208ab3db8545a929a409eeee99c573e7576c53e&

Is there a way to get the available language codes for the current node tree? This is what i got currently but it gives me all configured languages in the backoffice

C#
    public bool DoesLanguageExist(string isoCode)
    {
        var languages = _localizationService.GetAllLanguages();
        return languages.Any(language => language.IsoCode == isoCode);
    }
}

Anyone got any tips on setting up AzureBlob storage on clean install of Umbraco 8.18.13 ? What i have done - Install umbraco (

install-pacakge UmbracoCms

) - Build and run through install - Install Azureblob (

NuGet\Install-Package UmbracoFileSystemProviders.Azure.Media -Version 3.1.0

) - Update web.config - Fix newtonsoft so it will boot (update web.config dependency from 12.0.0. to 13.0.0) get a boot failed error with

Could not load file or assembly 'System.Diagnostics.DiagnosticSource

now this is similar to the newtonsoft error, and i can continue to wade through this treacle, but just hopeing someone has a 'oh yeah, just do this' answer to help out.