SuperBranding

New Post: Cannot use a leading .. to exit above the top directory.

jstorry — Wed, 18 Jun 2008 18:51:36 GMT

I am trying to install 'SuperBranding' on my SP site as this is exactly what I was looking for!

I can install the feature no problem, but when I try to access the /_layouts/SuperBrand/BrandManagement.aspx page from my 'Site Actions' menu, I get the following error:

Cannot use a leading .. to exit above the top directory.   at System.Web.Util.UrlPath.ReduceVirtualPath(String path)
   at System.Web.Util.UrlPath.Reduce(String path)
   at System.Web.Util.UrlPath.Combine(String appPath, String basepath, String relative)
   at System.Web.UI.Control.ResolveClientUrl(String relativeUrl)
   at System.Web.UI.HtmlControls.HtmlLink.RenderAttributes(HtmlTextWriter writer)
   at System.Web.UI.HtmlControls.HtmlLink.Render(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
   at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)
   at System.Web.UI.HtmlControls.HtmlHead.RenderChildren(HtmlTextWriter writer)
   at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
   at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)
   at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
   at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)
   at System.Web.UI.Control.Render(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
   at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)
   at Microsoft.SharePoint.WebControls.UnsecuredLayoutsPageBase.RenderChildren(HtmlTextWriter writer)
   at System.Web.UI.Page.Render(HtmlTextWriter writer)
   at Microsoft.SharePoint.WebControls.UnsecuredLayoutsPageBase.Render(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

And I can't seem to find the text '..' anywhere in the vs project release.

Any ideas?

Thanks,
Jesse

UPDATED RELEASE: SuperBranding (v.91)

Thu, 01 Nov 2007 18:06:11 GMT

Source Code (Visual Studio)

UPDATED RELEASE: SuperBranding (v.91)

Thu, 01 Nov 2007 18:05:04 GMT

Source Code (Visual Studio)

UPDATED RELEASE: SuperBranding (v0.90)

Thu, 01 Nov 2007 18:04:39 GMT

Source Code (Visual Studio)

UPDATED WIKI: Home

TedPattison — Mon, 29 Oct 2007 14:49:55 GMT

feature named SuperBranding
feature named SuperBrandingChildSiteInitializer
feature named SuperBrandingFarm
ASP.NET module named SuperBrandingModule
custom application page named BrandManagement.aspx

NOTE: This is a proof-of-concept code sample about how to switch out the master page for built-in application pages such as settings.aspx and it uses a technique involving an HttpModule that is not supported by Microsoft.

Currently, you should extract the zip file with the source code and expand it into a directory named SuperBranding. If you development machine is a single-server farm with WSS 3.0 or MOSS installed, you should just be able to build the project which will run install.bat and install the 3 features and install SuperBranding.dll in the GAC.

The SuperBranding feature can be actviated within any site collection. We have tested it on Blank sites and Team sites. Once you have actviated it within a site collection, you can navigate to the application page named BrandManagement.aspx from a menu item added to the Site Actions menu by a Custom Action. Once you have navigated to the Brand Management page, you can select between one of several different brands (TPG, Litware, Minimal).

The installation of SuperBrandingFarm forces activation which runs an event handler which updates the web.config file to configure an HttpModule module named SuperBrandingModule. This module is what is used to force application pages (e.g. settings.aspx) to use the same custom master page that is used by site pages.

The SuperBranding uses feature stapling to automatically activate the SuperBrandingChildSiteInitializer feature within any child site created within a site collection in which the SuperBranding feature has been actviated. The SuperBrandingChildSiteInitializer feature provides a FeatureActivated event handler that determines what branding settings to set up while a child site is being provisioned.

Once you run install.bat, then you should be able to test the code out. Go to any site collection and navigate to the site collection feature page. Activate the feature with the title of A Sample Feature: Super Branding. Once you activate this feature, the site settings menu should provide a new menu item with a title of Brand Magement. Select this menu item to navigate to BrandManagement.aspx. This page allows you to switch between several available brands.

UPDATED WIKI: Home

TedPattison — Mon, 29 Oct 2007 14:41:15 GMT

feature named SuperBranding
feature named SuperBrandingFarm
ASP.NET module named SuperBrandingModule
custom application page named BrandManagement.aspx

CREATED RELEASE: SuperBranding (v0.90)

Tue, 17 Jul 2007 20:46:43 GMT

Source Code (Visual Studio)

UPDATED WIKI: Home

TedPattison — Fri, 06 Jul 2007 20:40:17 GMT

feature named SuperBranding
feature named SuperBrandingFarm
ASP.NET module named SuperBrandingModule
custom application page named BrandManagement.aspx

Currently, you should extract the zip file with the source code and expand it into a directory named SuperBranding. If you development machine is a single-server farm with WSS v3 or MOSS installed, you should just be able to build the project which will run install.bat and install the 2 features and install SuperBranding.dll in the GAC.

Note that installation of SuperBrandingFarm forces activation which runs an event handler which updates the web.config file to configure an HttpModule module named SuperBrandingModule. This module is what is used to force application pages (e.g. settings.aspx) to use the same custom master page that is used by site pages.

Once you run install.bat, then you should be able to test the code out. Go to any site collection and navigate to the site collection feature page. Activate the feature with the title of A Sample Feature: Super Branding. Once you activate this feature, the site settings menu should provide a new menu item with a title of Brand Magement. Select this menu item to navigate to BrandManagement.aspx. This page allows you to switch between several available brands.

UPDATED WIKI: Home

TedPattison — Fri, 06 Jul 2007 20:39:47 GMT

Project Description
This is Visual Studio project that provides end-to-end branding of sites running in Windows SharePoint Services 3.0 (WSS) and Microsoft Office SharePoint Server 2007 (MOSS).

The SuperBranding project contains several different components
*feature named SuperBranding
*feature named SuperBrandingFarm
*ASP.NET module named SuperBrandingModule
*custom application page named BrandManagement.aspx

Currently, you should extract the zip file with the source code and expand it into a directory named SuperBranding. If you development machine is a single-server farm with WSS v3 or MOSS installed, you should just be able to build the project which will run install.bat and install the 2 features and install SuperBranding.dll in the GAC.

Note that installation of SuperBrandingFarm forces activation which runs an event handler which updates the web.config file to configure an HttpModule module named SuperBrandingModule. This module is what is used to force application pages (e.g. settings.aspx) to use the same custom master page that is used by site pages.

Once you run install.bat, then you should be able to test the code out. Go to any site collection and navigate to the site collection feature page. Activate the feature with the title of A Sample Feature: Super Branding. Once you activate this feature, the site settings menu should provide a new menu item with a title of Brand Magement. Select this menu item to navigate to BrandManagement.aspx. This page allows you to switch between several available brands.