CompositeC1Contrib Wiki Rss Feed

Updated Wiki: Home

burningice — Fri, 16 Mar 2012 16:10:31 GMT

Project Description
User contributions, hacks and optimization to Composite C1 CMS.

Download from the Source Code tab

Code is also hosted on BitBucket https://bitbucket.org/burningice/compositec1contrib

Find documentation of how to use under Documentation

Updated Wiki: Home

burningice — Fri, 16 Mar 2012 16:10:23 GMT

Project Description
User contributions, hacks and optimization to Composite C1 CMS.

Download from the Source Code tab

Code is also hosted on BitBuckethttps://bitbucket.org/burningice/compositec1contrib

Find documentation of how to use under Documentation

Updated Wiki: SiteMapProvider

burningice — Fri, 16 Mar 2012 10:33:23 GMT

SiteMapProvider

Enabling in web.config

Add the following section inside <system.web>

<siteMap defaultProvider="CompositeC1">
   <providers>
      <add name="CompositeC1" type="CompositeC1Contrib.Web.CompositeC1SiteMapProvider, CompositeC1Contrib.SiteMapProvider"/>
   </providers>
</siteMap>

Updated Wiki: UserControl functions

burningice — Fri, 16 Mar 2012 10:32:36 GMT

See documentation here: http://docs.composite.net/ASP-NET/Web-Forms/User-Control-Functions

Updated Wiki: Documentation

burningice — Fri, 16 Mar 2012 10:32:10 GMT

Updated Wiki: Sitemap Protocol

burningice — Fri, 16 Mar 2012 10:31:35 GMT

Sitemap Protocol

To deliver a compliant sitemap according to the Sitemap Protocol standard (http://sitemaps.org), we provider a handler that will generate it for you based on the configured SiteMapProvider. This means of course that the SiteMapProvider has to be enabled, but other than that this only requires two small changes to web.config

web.config

Depending on what webserver and mode you're using you add the handler to <system.web/httpHandlers> or <system.webServer/handlers> like this

<httpHandlers>
    <add verb="GET" path="sitemap.xml" type="CompositeC1Contrib.Web.SiteMapHandler, CompositeC1Contrib.SiteMapProvider"/>

<handlers>
    <add name="SitemapProtocol" verb="GET" path="sitemap.xml" type="CompositeC1Contrib.Web.SiteMapHandler, CompositeC1Contrib.SiteMapProvider"/>
</handlers>

and the module to <system.web/httpModules> or <system.webServer/modules> like this

<httpModules>
    <add name="Globalization" type="CompositeC1Contrib.Web.GlobalizationModule, CompositeC1Contrib.Core"/>
</httpModules>

<modules>
    <add name="Globalization" type="CompositeC1Contrib.Web.GlobalizationModule, CompositeC1Contrib.Core"/>
</modules>

The Globalization module is required to be able to request a sitemap in any language we want.

Viewing the sitemap

When configured we can view the sitemap browsing the url /sitemap.xml. This will show the sitemap for the default language, If there is several languages installed, it will generate a list with urls to sitemaps for each of the different languages.

Do we want to see the sitemap for ie. English or Danish we can use the urls /en-US/sitemap.xml and /da-DK/sitemap.xml

Updated Wiki: Sitemap Protocol

burningice — Fri, 16 Mar 2012 10:30:00 GMT

Sitemap Protocol

web.config

Depending on what webserver and mode you're using you add the handler to <system.web/httpHandlers> or <system.webServer/handlers> like this

<httpHandlers>
    <add verb="GET" path="sitemap.xml" type="CompositeC1Contrib.Web.SiteMapHandler, CompositeC1Contrib.SiteMapProvider"/>

<handlers>
    <add name="SitemapProtocol" verb="GET" path="sitemap.xml" type="CompositeC1Contrib.Web.SiteMapHandler, CompositeC1Contrib.SiteMapProvider"/>
</handlers>

and the module to <system.web/httpModules> or <system.webServer/modules> like this

<httpModules>
    <add name="Globalization" type="CompositeC1Contrib.Web.GlobalizationModule, CompositeC1Contrib.Core"/>
</httpModules>

<modules>
    <add name="Globalization" type="CompositeC1Contrib.Web.GlobalizationModule, CompositeC1Contrib.Core"/>
</modules>

The Globalization module is required to be able to request a sitemap in any language we want.

Viewing the sitemap

When configured we can view the sitemap browsing the url /sitemap.axd. This will show the sitemap for the default language configured in web.config. Do we want to see the sitemap for ie. English or Danish we can use the urls /en-US/sitemap.axd and /da-DK/sitemap.axd

Updated Wiki: SiteMapProvider

burningice — Fri, 16 Mar 2012 10:28:15 GMT

SiteMapProvider

The user of the SiteMapProvider for Composite C1 has no special dependencies and can be used immediately after enabling it in web.config. So far its only for use with .Net binding, if you're creating your markup with XSLT there are no functions for providing urls and titles provided by the SiteMapProvider yet

Note: To get pretty urls when creating markup in XSLT you can use the Nicer Urls which will replace raw content of the generated html. Also when using SiteMapProvider for printing out urls with the SiteMapNode.Url property, they will always be in the format of Nicer Urls.

Enabling in web.config

Add the following section inside <system.web>

<siteMap defaultProvider="CompositeC1">
   <providers>
      <add name="CompositeC1" type="CompositeC1Contrib.Web.CompositeC1SiteMapProvider, CompositeC1Contrib.SiteMapProvider"/>
   </providers>
</siteMap>

Updated Wiki: Masterpages

burningice — Fri, 16 Mar 2012 10:27:14 GMT

See documentation here http://docs.composite.net/ASP-NET/Web-Forms/Web-Form-Master-Pages

Updated Wiki: Razor functions

burningice — Fri, 16 Mar 2012 10:26:57 GMT

See documentation here: http://docs.composite.net/ASP-NET/Razor

Updated Wiki: Masterpages

burningice — Mon, 24 Oct 2011 16:30:38 GMT

See documentation here http://docs.composite.net/C1/ASP-NET/Web-Form-Master-Pages1.aspx

Updated Wiki: Razor functions

burningice — Mon, 24 Oct 2011 16:30:06 GMT

See documentation here: http://docs.composite.net/C1/ASP-NET/Razor-Functions.aspx

Updated Wiki: Razor functions

burningice — Mon, 24 Oct 2011 16:29:53 GMT

See documentation here: http://docs.composite.net/C1/ASP-NET/Razor-Functions.aspxhttp://docs.composite.net/C1/ASP-NET/Razor-Functions.aspx

Updated Wiki: Razor functions

burningice — Mon, 24 Oct 2011 16:29:22 GMT

See documentation here: http://docs.composite.net/C1/ASP-NET/Razor-Functions.aspx

Updated Wiki: Documentation

burningice — Mon, 24 Oct 2011 16:29:02 GMT

Updated Wiki: SiteMapProvider

burningice — Mon, 02 May 2011 10:33:47 GMT

SiteMapProvider

Enabling in web.config

Add the following section inside <system.web>

<siteMap defaultProvider="CompositeC1">
    <providers>
        <add name="CompositeC1" type="CompositeC1Contrib.Web.CompositeC1SiteMapProvider, CompositeC1Contrib" />
    </providers>
</siteMap>

Updated Wiki: Masterpages

burningice — Fri, 01 Apr 2011 01:07:21 GMT

Masterpages

Using Masterpages in Composite C1 has many advantages over default xlst templates. Mainly its what normal asp.net developers are used to, there is full support for it in Visual Studio and its a lot easier to insert UserControls and normal asp.net controls into a Master Page than in xslt templates. It only requires a simple change to web.config and the creation of the masterpages of course.

web.config

Depending on what webserver and mode you're using you add the handler to <system.web/httpHandlers> or <system.webServer/handlers> like this

<httpHandlers>
    <add verb="*" path="Renderers/Page.aspx" type="CompositeC1Contrib.Web.UI.CompositeC1Page, CompositeC1Contrib"/>
</handlers>

<handlers>
    <add name="CompositePage" verb="*" path="Renderers/Page.aspx" type="CompositeC1Contrib.Web.UI.CompositeC1Page, CompositeC1Contrib"/>
</handlers>

and register the rendering controls prefix to <system.web/pages/controls> like this

<controls>
    <add tagPrefix="rendering" namespace="CompositeC1Contrib.Web.UI.Rendering" assembly="CompositeC1Contrib" />
</controls>

Creating masterpages

The convention for using masterpages is that you have a masterpage for each Layout created in Composite C1. The masterpages are named the same as the Layout and stored in same folder as the C1 xml templates which is ~/AppData/PageTemplates. So say you have a Layout named Frontpage you would create the following masterpage: ~/AppData/PageTemplates/Frontpage.master. If there is no master found for the page's layout normal XSLT rendering will be used.

For putting content into the master you copy the <rendering placeholder /> from the Layout Markup and add a runat="server" to the tag. You can have as many Rendering placeholders as you need and masterpages can of course inherit from each other like you're used to in normal asp.net. For writing out the page's title and description you use <rendering:title /> and <rendering:description />

Using C1 functions in your masterpage

It is possible to use normal C1 functions directly on your master page as well. For this you use the <rendering:function /> control and just write the markup as content to the control. Example:

<rendering:function runat="server">
   <f:function name="Composite.Navigation.Path" xmlns:f="http://www.composite.net/ns/function/1.0"> 
     <f:param name="Level" value="0" /> 
   </f:function>
</rendering>

Updated Wiki: Nicer Urls

burningice — Thu, 31 Mar 2011 22:38:30 GMT

Nicer Urls

Nicer Urls enables Composite C1 to use extensionsless urls plus guaranteeing its all lowercase. It will also use _ as word separator instead of -.

To be able to use Nicer Urls SiteMapProvider has to be enabled as well.

For using Nicer Urls with Composite C1 you enable the UrlFilter which will find all links in the raw html and replace them with Nicer Urls. It will also intercept requests and rewrite them into Composite C1's own format. Note that when using SiteMapProvider for printing out urls with the SiteMapNode.Url property, they will always be in the format of Nicer Urls.

Rules for generating url

When there is only one site, the site-part is removed from the url
- If there is more than one site, but each is using seperate hostnames the site-part is also removed
All urls are lowecase
spaces and - is replaced with _
all non-allowed characters are replaced with _
.aspx is removed from url

Web.config

Depending on what webserver and mode you're using you add the module to <system.web/httpModules> or <system.webServer/modules> like this

<httpModules>
    <add name="UrlFilter" type="CompositeC1Contrib.Web.UrlFilterModule, CompositeC1Contrib" />
</httpModules>

<modules>
    <add name="UrlFilter" type="CompositeC1Contrib.Web.UrlFilterModule, CompositeC1Contrib" />
</modules>

It is very important that this module is added before any Composite C1 module

Updated Wiki: Nicer Urls

burningice — Thu, 31 Mar 2011 22:36:32 GMT

Nicer Urls

Rules for generating url

When in a multilingual site we can get rid of the first url-part referencing the homepage-node, by setting the url-title to the same as defined under Languages (ie. en, da, kl)
All urls are lowecase
spaces and - is replaced with _
all non-allowed characters are replaced with _

Web.config

Depending on what webserver and mode you're using you add the module to <system.web/httpModules> or <system.webServer/modules> like this

<httpModules>
    <add name="UrlFilter" type="CompositeC1Contrib.Web.UrlFilterModule, CompositeC1Contrib" />
</httpModules>

<modules>
    <add name="UrlFilter" type="CompositeC1Contrib.Web.UrlFilterModule, CompositeC1Contrib" />
</modules>

It is very important that this module is added before any Composite C1 module

Updated Wiki: Masterpages

burningice — Thu, 31 Mar 2011 22:35:51 GMT

Masterpages

web.config

Depending on what webserver and mode you're using you add the handler to <system.web/httpHandlers> or <system.webServer/handlers> like this

<httpHandlers>
    <add verb="*" path="Renderers/Page.aspx" type="CompositeC1Contrib.Web.UI.CompositeC1Page, CompositeC1Contrib"/>
</handlers>

<handlers>
    <add name="CompositePage" verb="*" path="Renderers/Page.aspx" type="CompositeC1Contrib.Web.UI.CompositeC1Page, CompositeC1Contrib"/>
</handlers>

and register the rendering controls prefix to <system.web/pages/controls> like this

<controls>
    <add tagPrefix="rendering" namespace="CompositeC1Contrib.Web.UI.Rendering" assembly="CompositeC1Contrib" />
</controls>

Creating masterpages

The convention for using masterpages is that you have a masterpage for each Layout created in Composite C1. The masterpages are named the same as the Layout and stored in same folder as the C1 xml templates which is ~/AppData/PageTemplates. So say you have a Layout named Frontpage you would create the following masterpage: ~/AppData/PageTemplates/Frontpage.master. If there is no master found for the page's layout normal XSLT rendering will be used.

For putting content into the master you copy the <rendering placeholder /> from the Layout Markup and add a runat="server" to the tag. You can have as many Rendering placeholders as you need and masterpages can of course inherit from each other like you're used to in normal asp.net. For writing out the page's title and description you use <rendering:title /> and <rendering:description />

Using C1 functions in your masterpage

It is possible to use normal C1 functions directly on your master page as well. For this you use the <rendering:function /> control and just write the markup as content to the control. Example:

<rendering:function runat="server">
   <f:function name="Composite.Navigation.Path" xmlns:f="http://www.composite.net/ns/function/1.0"> 
     <f:param name="Level" value="0" /> 
   </f:function>
</rendering>