We have moved to GitHub Issues
Created by Tom Fulton 24 Jun 2015, 02:49:05 Updated by Shannon Deminick 26 Jun 2017, 07:13:12
''Disclaimer: This might not be an "issue", but thought I'd bring to your attention just in case as it requires a change in behavior.''
Typically when we want to run another application underneath an Umbraco site, we'll:
<location>tags to Umbraco's web.config to prevent Umbraco's settings from trickling down (otherwise, sub-app gets YSOD trying to load Umbraco stuff) (refs: [http://codeblog.shawson.co.uk/stop-the-web-config-being-inherited-by-child-applications-in-sub-folders/ 1] [https://our.umbraco.org/forum/getting-started/installing-umbraco/6825-web-application-inside-umbraco-site-in-iis 2] [https://our.umbraco.org/forum/getting-started/installing-umbraco/16868-Non-Umbraco-Virtual-Directory?p=0 3])
This process doesn't seem to work starting in Umbraco ~7.2.6, it causes a server error when trying to access the Umbraco backoffice (attached):
HTTP Error 500.22 - Internal Server Error An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
The cause seems to be the new [https://github.com/umbraco/Umbraco-CMS/commit/0df0b78b908e505e47452eb5cd31528004350021
This might not be an Umbraco issue per se, maybe it just requires a change in the way we (+ others?) usually configure sub-applications. I think there are other ways to make it work, but thought I'd flag it here just in case :)
'''Forum posts of people having this issue:''' https://our.umbraco.org/forum/getting-started/installing-umbraco/66756-problem-running-separate-app-in-umbraco-site#comment-222428
'''Steps to reproduce:'''
myapp, add an
index.htmlfile with contents: Hello World
<location>tags, to allow your sub application to work and not inherit Umbraco's web.config
Got this issue after an upgrade from 7.1.4 to 7.2.2 As soon as I remove the
We also ran into this today, it turns out you can just add
Instead of removing the whole section, I think it happens when wrapping the whole system.webserver section, so umbraco doesn't know to not validate the integrated config. Adding it back in tells Umbraco to behave ;)
Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/
Backwards Compatible: True
Affected versions: 7.2.6
Due in version: