I'm in the process of moving a site away from Umbraco Cloud to a regular .NET Framework 4.8 site. It's an old Umbraco 8 and the code and structure is 100% the same on both sites. But, on the new site the code fails when I ask for specific properties in my MVC files. When I look at the document types, I can see that the properties are in fact missing, on both sites I've also looked in the generated models, they are missing here as well. But on Umbraco Cloud it just doesn't fail. Could it be possible that Umbraco Cloud could be configured to be more forgiving to errors ? If so, which configuration could that be ?

That or its likely that your deploys to cloud has not been properly deployed, then it will be running the last running build.

The cloud solution have been running for several years, so I don't think it's a deploy issue.

It's possible that Cloud is running in PureLive models builder mode, meaning that if the properties exist on the doc type in the back office, then they are available when the site is running. Alternatively, the if the properties aren't on the doc types, it's possible the Cloud site has a DLL in it that has old models compiled in it.

Both sites are running in PureLive mode. I've looked in the generated files, on both sites, and the properties are missing on both sites. This is really weird.

Could it be the

umbracoSettings.config

macroerror

setting that is masking errors?

<!-- How Umbraco should handle errors during macro execution. Can be one of the following values:
         - inline - show an inline error within the macro but allow the page to continue rendering. Historial Umbraco behaviour.
         - silent - Silently suppress the error and do not render the offending macro.
         - throw  - Throw an exception which can be caught by the global error handler defined in Application_OnError. If no such
                    error handler is defined then you'll see the Yellow Screen Of Death (YSOD) error page.
         Note the error can also be handled by the umbraco.macro.Error event, where you can log/alarm with your own code and change the behaviour per event. -->
    <MacroErrors>throw</MacroErrors>

Nope, I figured it out. Stupid me 🙂 The site is using the Igloo Theme builder, and since it's an Umbraco 8 solution I had to install it from the marketplace on the new site. And of course the partials had been updated to a newer version, than was used on the live site when installing. As soon as copied over the old partials, everything was working. Thanks for rubberducking 🙂