Hey guys,

if you are trying to restrict special sites for the extranet\anonymous user, so only authenticated users (doesn’t matter if it’s a virtual user or a real user account) can view that content.

You can restrict the read right for the anonymous user and add an (undocumentated - the reason I write about it ) attribute to your site in the web.config. The default one will be website I think.

loginPage=“/sitecore/content/home/Registration/Login.aspx“

It can also be a sitecore Item and you refer to the virtual path. So after Sitecore sees that the user is not autenticated, it redirects the user to your login page. Unfortunately it passes own query string parameters, and none of them is “returnUrl”. In my case I hooked into the httpRequest pipeline right before the ExecuteRequest processor and created my own SecurityResolver.

[updated]

    public class SecurityResolver : HttpRequestProcessor 
    {     
 
        public override void Process(HttpRequestArgs args) 
        { 
            // Get the site context 
            // [CW] 
            SiteContext site = Sitecore.Context.Site;          
 
            // Check if the current user has sufficient rights to enter this page 
            // [CW] 
            if (SiteManager.CanEnter(site.Name, Sitecore.Context.User)) 
            { 
                string prefix = args.StartPath;          
 
                if(args.LocalPath.Contains("/sitecore/content/home")) 
                    prefix = String.Empty;          
 
                if (Sitecore.Context.Database != null) 
                { 
                    Database contextDatabase = Sitecore.Context.Database;          
 
                    Item contextItem = null;          
 
                    // Get the item using securityDisabler for restricted items 
                    // [CW] 
                    using (new SecurityDisabler()) 
                    { 
                        contextItem = contextDatabase.SelectSingleItem(String.Concat(prefix, args.LocalPath)); 
                    }          
 
                    // Check if a loginPage is given 
                    // (Should be for this website) 
                    // [CW] 
                    if ((contextItem != null) && (contextItem.Access.CanRead() == false) && (site != null) && (site.LoginPage.Length > 0)) 
                    { 
                        // Redirect the user 
                        // [CW] 
                        WebUtil.Redirect(String.Format("{0}?returnUrl={1}", 
                            site.LoginPage, 
                            HttpContext.Current.Server.HtmlEncode(HttpContext.Current.Request.RawUrl))); 
                    } 
                } 
            } 
        } 
    }

Hope it’s helpful for you - You may also post questions or interests. I’m looking forward to develop a sitecore client application with xaml, and can manage to documentate the steps I do.

cheers chris

Hey guys,

as a Developer in a the german area, I’m creating solutions in the german language more than in english. If you have seen the already the issue that in another website language some buttons aren’t translated you  can resolve it yourself, I will also create a support ticket at the Sitecore support; but then you have to wait until the next release.

The “self-doing-way”:
Go into the Core Database (you can switch the databases by clicking on the icon left beside the clock) . Open the content editor and then you have two solutions:

• Set the field called “Header” in the “WebEdit Button” data template to shared
• Add new versions to the languages in the “Header” fields under the path: /sitecore/content/Applications/WebEdit/Buttons/Associated Controls/*

You have to be aware of the way to change a template field and set it to shared that other language versions are being lost, and it’s also a heavy change in the Sitecore core database, but in order to point out all ways I have to mention that as well. I would go for the new language versions on content items.

Another issue is that you have to rename the language to the same item name / key as it is in the Sitecore core database. For example: I have created a language called “de-DE” for german, but in the core database is only the “de” language item. So I have to rename the language from “de-DE” to “de”. (Also you can go the other way round, but changing the core database should only be the last solution!)

That’s it for today I guess. I will update my post if the Sitecore support has answered.

Thanks to Steen Pedersen, who a really nice guy and pointed me to the items having the header field. It has been a pleasure to meet you guys.

cheers chris