Hiding pages in EditTree
A problem for some of our customers with globalized websites is that the EditTree gets cluttered with pages only existing in one or a few languages.
The pages get displayed in italics and this, I take it, is a feature making it easy to get an overview of pages not having a language version in the selected language and also making it easy to create that version. This is fine when working with languages as intended by EPiServer, that is where all pages exists in all languages in a 1:1 relationship. This is however not the reality for several of our customers since they need to have different content in different market areas leading to a different page structure with different page types.
One of the new features of CMS 6 is the ability to assign access rights on languages. While this is a great improvement like many other things in the new release I was hoping for an option to hide pages that does not exist in a language accessible by the editor. This would solve the problem for editors only editing one language. When i couldn’t find this opiton I asked the EPiServer support team if this could be achieved in any way. They pointed me to a useful forum post that helped to get me started.
The goal of this post is a walk through of making a httpModule that hides pages in the EditTree based on
- Access rights on language
- Access rights in page structure
- The selected language in the drop down under the EditTree
First, we need to define a class that inherits from IHttpModule and hook into the DataFactorys FinishedLoadingChildren event.
public class PageExcluder: IHttpModule {
public void Dispose() {}
public void Init(HttpApplication context) {
EPiServer.DataFactory.Instance.FinishedLoadingChildren += new EPiServer.ChildrenEventHandler(Instance_FinishedLoadingChildren);
}
void Instance_FinishedLoadingChildren(object sender, EPiServer.ChildrenEventArgs e) {
}
}
This method gets called each time children is loaded so we need to make sure we only hide pages when actually loading the EditTree
if (HttpContext.Current.Request.Url.AbsolutePath.EndsWith("EditTree.aspx")) {
Now we need to iterate over the pages that has been loaded from the data factory
for (int i = 0; i < e.Children.Count; i++) {
While doing this we want to remove any pages that:
- Is not editable by the user based on access rights set on the language
// get the languages the user has access to edit
StringCollection languageAccess = new StringCollection();
foreach (LanguageBranch language in LanguageBranch.ListAll()) {
if (language.ACL.QueryDistinctAccess(EPiServer.Security.AccessLevel.Edit)) {
languageAccess.Add(language.LanguageID);
}
}
// remove pages that the user has no access to edit
if (!languageAccess.Contains(e.Children[i].LanguageID)) {
e.Children.RemoveAt(i);
i--;
continue;
}
- Is not editable by the user based on access rights set in the page structure
if (!e.Children[i].QueryDistinctAccess(EPiServer.Security.AccessLevel.Edit)) {
e.Children.RemoveAt(i);
i--;
continue;
}
- Does not have a language version in the language selected by the user in the drop down under the edit tree.
string selectedEditLang;
if (HttpContext.Current.Request.Cookies["editlanguagebranch"] != null)
selectedEditLang = HttpContext.Current.Request.Cookies["editlanguagebranch"].Value;
else
selectedEditLang = CultureInfo.CurrentUICulture.TwoLetterISOLanguageName;
if (e.Children[i].LanguageID != selectedEditLang) {
e.Children.RemoveAt(i);
i--;
continue;
}
In the complete version of this module you can specify which one(s) of these checks you want to do by adding entries to your appSettings. You can download the complete project here.
This is my first blog post here on EPiServer world and i hope you found it useful. I appreciate any feedback, improvements or suggestions.
Comments