tag:blogger.com,1999:blog-18939862.post4655559457117189384..comments2023-07-25T01:20:13.916-07:00Comments on Sitecore CMS Blog by Alex Shyba: Updated: Standalone apps under Sitecore web rootAnonymoushttp://www.blogger.com/profile/09553655443086620502noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-18939862.post-80370682722502996392013-07-25T03:44:28.589-07:002013-07-25T03:44:28.589-07:00You'll have a problem related to cache manager...You'll have a problem related to cache manager, /sitecore/admin/cache.aspx if you sepcifay location and not inheritance in main web.config - cache manager won't functioning.Sergejs Kravcenkohttps://www.blogger.com/profile/08631971620677834363noreply@blogger.comtag:blogger.com,1999:blog-18939862.post-23572520998146937902011-09-11T18:15:56.999-07:002011-09-11T18:15:56.999-07:00This is great, but one caveat emptor is that you m...This is great, but one caveat emptor is that you may find that some of the Sitecore functionality may break as a result of this. For instance we had rich text editor control fail to load. Which is a Telerik control and I assume is also a child application which in this case need to inherit Sitecore settings.Andrewhttps://www.blogger.com/profile/09204748131269313072noreply@blogger.comtag:blogger.com,1999:blog-18939862.post-60514626200876298052009-05-13T01:03:00.000-07:002009-05-13T01:03:00.000-07:00Alex, thinking a bit more about it gave me an idea...Alex, thinking a bit more about it gave me an idea that using <clear /> is more preferable than a number of <remove /> elements. There might be not "sitecore" specified as default provider, but also "switcher", or anything else.Yan Sklyarenkohttps://www.blogger.com/profile/02915083843106544026noreply@blogger.comtag:blogger.com,1999:blog-18939862.post-70195807081883487532009-05-13T00:52:00.000-07:002009-05-13T00:52:00.000-07:00Nice article, Alex!
To Alexander: I believe it is...Nice article, Alex!<br /><br />To Alexander: I believe it is just as doing the same things in a bit different way.<br />Adding inheritInChildApplications="false" to the parent config should affect any child application, but apart from this does the same job. <br />Regarding membership/roles/profile changes, a number of <remove/> entries is the same as one <clear/> element in each provider group (which is how YAF is configured).Yan Sklyarenkohttps://www.blogger.com/profile/02915083843106544026noreply@blogger.comtag:blogger.com,1999:blog-18939862.post-68342119624983937602009-05-13T00:10:00.000-07:002009-05-13T00:10:00.000-07:00Hi Alexander! I was just editing the YAF integrati...Hi Alexander! I was just editing the YAF integration document, and it mentions a standalone application setup as well:<br />http://trac.sitecore.net/SitecoreYAF/browser/Trunk/Yet_Another_Forum_Integration.pdf?format=raw<br /><br />The approach given in the doc is different. Does it have any pros or cons compared to yours one?Alexander Kokoshynhttps://www.blogger.com/profile/05259659098745453594noreply@blogger.com