Eigil M

Web part zone adapter

eigilm — Tue, 07 Oct 2008 15:27:00 GMT

A lot of people working with public facing web sites and SharePoint 2007 have discovered that the web part zone makes it virtually impossible to have a WCAG complient site, in other words to have a page layout which doesn't use HTML tables for layout purposes. The only possible way to change this is to make a web part zone adapter which renders the web part zone in a DIV based layout instead. The only downside to this approach is that this will break the javascript the zone uses to drag and drop web parts. This downside can be minimized if you only apply the adapter when the page is rendered to the end user, which means when the page is not rendered in edit mode. By doing this the javascript is only broken for the end user, so if the end user shouldn't mess around with web parts, then nothing is lost and the page will be compliant according to WCAG 2.0 (of course you would have to make sure the rest of the HTML is also compliant).

The below attachment is source code for the adapter with a little instruction in the readme file.

Allow http in Custom and Orders Manager

eigilm — Fri, 04 Apr 2008 11:55:00 GMT

This is a little trick to use in your development environment, so you don't have to use SelfSSL to isuue and setup a certificate. Go to %ProgramFiles%\Microsoft Commerce Server 2007\Business User Applications\.

Go inside the "CustomerandOrdersManager.exe.config" file.

Find this entry
<setting name="AllowHTTP" serializeAs="String">
<value>False</value>
</setting>

Change the value to "True" and save the file. Now http is allowed and you don't have to worry about the certificate. This is of course not recommended in a production environment.

Inherit Content Types

eigilm — Tue, 04 Sep 2007 13:26:00 GMT

Introduction

This document describes the content types' hierarchy and how to inherit existing content types. The main reason for making this document is that the standard documentation doesn't contain such a description and it is a part of the SharePoint 2007 server which will be used in any ECM scenario.

Hierarchy

Content types are ordered in a hierarchy (See attachment below for the whole content type inheritance tree - "Appendix A - ContentTypes hierarchy.pdf") to enable reuse and to make maintenance easier. This means that all content types inherit from the same base system content type.

The default content types which are already present in the SharePoint server is found in an XML file which resides in the feature folder: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ctypes\ctypeswss.xml. If you want to find the publishing content types they are found here: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\PublishingResources\PublishingContentTypes.xml. To most important thing to understand when working with content types is that the ID of a content type reveals its base content types and when making your own content type you must provide a unique ID which includes the base content type you wish to inherit from.

An ID of a content type can be composed in two different ways:

•1. baseID + 00 + [GUID] (Ex. 0x010100b6ca00b0b50411db96e9005056c00008)

•2. baseID + two hexadecimal values (Ex. 0x0101AA)

In the first case you must remove the hyphens (-) from the GUID. In the second case you must make sure that the ID you give is unique within the site collection. Both above examples inherit from the document content type which has ID 0x0101. From the ID of the document content type you can see that it inherits from 0x01 = Item, which inherits from System = 0x, which is the base of all content types.

The complete hierarchy of content types is found in the appendix A (see attachment). If a content type can't be inherited it is marked as "SEALED = TRUE" in the diagram. Some of the content types shown in the inheritance diagram cannot be found in the SharePoint UI because they have their "Group" attribute set to "_Hidden".

Best practice

When making your own content types follow this best practice: When you make a content type that directly inherits from one of the predefined content types, the use the first approach e.g. base + 00 + GUID, when inheriting from one of your own custom types, then use the second approach, because now you already have made certain that your own branch is unique and the second approach is much easier to read and thereby makes the inheritance tree structure more transparent.

Tip

If you want to see a content types ID, without opening the xml document, then go to the content type gallery, the link to each content type contains a "ctype" parameter which contains the ID.