Upgrading Umbraco and Umbraco Forms from 12.almost-latest to 13.latest worked fine in development, but in the production environment we get "Invalid column name NodeId" in the Forms backoffice UI and in the logs when forms are being indexed. There was nothing in the version-specific upgrade documentation for Forms to 13. What should be done in this case? Is this a Forms SQL migration that didn't run?

I have an Umbraco Document Type and a template with the same name. I create a page in Umbraco and can view the page with the details entered. On this page i now would like to build a form so it can be submitted. As soon as i declare the model in the top of my cshtml file, i get an error about the ViewData (ViewDataDictionary) is of type X but this method requires Y. How am i supposed to set this up so both the content from Umbraco work and my custom form would work?

Hey everyone. Today i was wondering what the future of umbraco could look like. I've read posts about using nextjs and other frameworks, but am i right, that then cshtml would be obsolete? Is the future more and more heading towards headless cms and moving away from cshtml and all that comes with it? OR is it still future proof and will it someday maybe go to blazor? What would be a good way to implement client side rendering together with cshtml? As you can see there is a lot of things that i'm unsure about. Maybe someone could help me out what a future proof stack could look like and what umbraco itself is targeting for the future. I've found this post regarding .net Core / MVC https://stackoverflow.com/questions/51390971/im-lost-what-happened-to-asp-net-mvc-5

I am currently trying to load vtt files for video subtitles from umbraco media section in our frontend. We use an NextJs Frontend, so the domain of the frontend is not the same as the Umbraco instance. I now get cors errors when i try to load the vtt files. the images and videos are loaded without a problem. Did anyone else have the same problem?

In Umbraco 13, is there an way, (possibly via the Content API?) to get a list of all published nodes? For example (1003,1008,1018,1019) etc.

Hi all, has anyone tried using Redis Cache (or another distributed cache) to store the Memory Cahce/NuCache when auto scaling out? One of the issues with scaling out an Umbraco Azure web app instance is that each new instance will slam the database as it builds it's Memory/NuCache, so moving the memory cache into a distributed cache would hopefully alleviate this issue. (at least in theory lol) Has anyone tried this or something similar? Also posted on Our: https://our.umbraco.com/forum/using-umbraco-and-getting-started//112967-nucache-plus-redis-cache-for-automatic-scale-out

Exceeding 260 character limit for paths in Windows

This is obviously not ideal, but I'm working with a situation where, rather than building out a whole Angular UI for a backoffice custom page, we're looking into just using an existing .net core set of controller/view/model code to render a custom page. This page should only be accessible to users who are authenticated in backoffice, but since there's no way to 'inject' a standard model/view/controller action into the backoffice UI, we're thinking we just put it on the frontend, but in the action verify that the user is logged in and has the proper Group in the backend. In Umbraco 9, I see references to people doing things like this: https://our.umbraco.com/forum/umbraco-9/106857-how-do-i-determine-if-a-backoffice-user-is-logged-in-from-a-razor-view#comment-334423 They seem to be manually checking the cookies. I believe you'd have to be on a route of /umbraco/backoffice/* in order to see those? Not sure. In any case, the question is: To do the above, what changes in Umbraco 13? https://github.com/umbraco-community/Our-Umbraco-TagHelpers/blob/dee84a4726e3db60b77fb0187a76f8ec0c86e003/Our.Umbraco.TagHelpers/Services/BackofficeUserAccessor.cs There's even a Tag Helper written for Umbraco 9 that does almost what I want (I want to gate the entire Action, not just a part of it), I just need to understand what's different for 13, or if there's a better way to do this.

Hey, i have issues deploying app to the server. I'm frustreted cause i've been doing it for 7 hours now. I've played with all the settings' variations as well as with connection string and in some scenarios it shows "Umbraco boot failed" in other "error 500.30" and "403 forbidden". I've noticed that after publishing there's no ASP.NET section in my app. Only IIS and Managmeent whereas in other app there's section ASP.NET. Has anyone got any experience with deploying umbraco 13? https://cdn.discordapp.com/attachments/1252588067865493514/1252588068255436830/MicrosoftTeams-image_1.png?ex=6672c30b&is=6671718b&hm=d1b911af13f45af7e8587ca54066a1cc652a4e899811eb24ae8557b5cb1610ce& https://cdn.discordapp.com/attachments/1252588067865493514/1252588068805021816/MicrosoftTeams-image.png?ex=6672c30b&is=6671718b&hm=f3f6c9ac40c8dd19b65929871f11e680c1ce57fb10c7ad7e73530194128b28c6&

My team and I have attempted an umbraco upgrade to the latest stable 13.x.x on a production environment (at the time of work sign-off). We maintain three deployment environments for our client: - An internal test and a prep-prod/UAT environment. - Production All of these umbraco applications are hosted in Azure in the form of Azure Web Apps. Pre-Prod and Prod are the closes architecturally speaking as each have two app web apps: 1) An Administrative instance for the umbraco backoffice 2) A public facing instance of the website An upgrade on all environments prior to production has been relatively painless - allowing Umbraco to applicate the necessary changes to facilitate the upgrade to 13.0.3. Unfortunately, the same can be said about production: The production database contains significantly more content that that of the non-prod environments and could be a contributing factor to the SQL timeout exceptions observed in the installation splash screen and in the trace logs *Troubleshooting * There was two key issues that we resolved together on pre-prod: Ensuring that the .NET stack version on the Azure Web app was updated to v8 (which I did) Adding and increasing the **DistributedLockingReadLockDefaultTimeOut **values in the appsettings. I also came across one example of the issues with an Umbraco 13 upgrade as described in this Umbraco forms thread. The suggested remediation steps didn’t resolve my issue. If you have any ideas for next steps, I’d be appreciative. https://cdn.discordapp.com/attachments/1219659453012639856/1219659453155250196/fe0d208e-9f4d-4ae2-99b5-28a59d8d9fa0.png?ex=660c1b61&is=65f9a661&hm=a1dbe9908a72a51961dcb7b998f104e523489b853719e20c37f0b78a8229f598&