In STS 1.0 the items listed in the Quick Launch section were generated from the database. They were links to (only) those lists that had been defined in the User Interface when adding or amending a list as "Yes, I want this in the Quick Launch list".

 

There was one Quick Launch list per main web or per subweb.

If you wanted to add your own links (for instance to sites outside the STS site or to pages within the STS site that were not main List pages), you had to add some (<A> </A>) HTML code just above or just below the code for the generated Quick Launch links.

 

In WSS there are several different Quick Launch sections. The initial information they contain is generated as before from the database.

 

However if you now want to add additional links (external or internal) *within* the "normal" links this is now possible through the use of Front Page 2003 by selecting first the Quick Launch section; and then either using "Add a Link" or right-clicking and adding a link after selecting 'Link Bar Properties'.

See

 

IV.2.1 General Customization of the main section

 

and

 

IV.2.2 Customizing the look of Document Libraries in the main section

In STS 1.0 the only customization of this section of the main page that could be done in the User Interface was the definition of which Document Libraries and Lists would appear in this section. (Sites and Settings / Customize Home Page Layout)

 

Using FrontPage XP or using even an HTML editor allowed to do other changes such as re-sizing columns; changing colours etc. (see also IV.2.2)

 

In WSS you can also move into position onto the main page the Document Libraries and Lists as before, but you can also move in a selection of Web Parts (both actions done by Modify Page / Add Web Part - the Doc Libs and Lists are also called Web Parts in this version).

 

In addition most of the changing of the look of the page can as before be done in Front Page 2003 or by amending the page in an HTML editor. (see also IV.2.2)

In STS 1.0, the default look of a document library when made available in the main section of the front page was that it consisted of three fields Icon; FileName and Modified By. The default number of documents was 20. Both these settings could be changed by entering the site in FrontPage XP; accessing the default.htm file; selecting the List; right-clicking and then by 'View Properties' followed by amending (for the above two cases) the Files and Options settings.

 

(Note that the View Properties box was centered on the screen)

 

In WSS the default look is the same and the View Properties box is accessed in the same way but is now a new right-hand column (in the same sort of location as the clipboard for instance) rather than a centered box. The items listed are roughly the same with the same use of 'Fields' to change the fields used on the default page and the Use of Style followed by Options (rather than just 'Options') to amend the default number of documents (which unfortunately still has the same default of 20).

STS 1.0 came with a small set of icons for the main Office applications. When a document from one of these applications was listed in a document library, the special icon for this document type was shown otherwise all documents used a general icon. It was possible to add icons (from a selection available on a private website) by amendments to the templates (by amending an .xml file and adding the .gif of the icon to a specfic directory).

 

These icons were then valid for all sites and subwebs created after this template change was made. A further amendment to the templates was needed for the icon to become available to existing sites and subwebs.

 

The official word in the beta newsgroups was that WSS comes with a slightly increased number of icons with icons for Visio and Project (probably) available in addition to the previously available icons for Word, Excel, and PowerPoint.

 

However tests have shown that more icons are available than this (stored at ...60/TEMPLATE/IMAGES - as the usual IC???.GIF - there are almost 100 images including everything under the sun *except* for .pdf).

Images are chosen slightly differently than before.

 

Icons for a small group of standard MS document types (Word, Excel etc.) are chosen on the basis of the document type. Other icons are chosen on the basis of the file type (.xxx). Priority is given to the MS document type before the file type, thus if you save a MS Word document but give it a .mht file name, you will see in WSS the icon for MS Word not for .mht files. The file used for the above is DOCICON.XML which you will find in ...60/TEMPLATE/XML.

 

As with STS 1.0 in order for a newly added icon (amendments to both the IMAGES folder and to DOCICON.XML) to work you need to Restart IIS. ((IIS Manager / local computer + right click / All Tasks(Restart IIS).)

 

Unlike STS 1.0, following these actions the new icon is available for ALL document libraries - not just those in subwebs created after the change.

 

 

In STS 1.0 customization with Images was done either through using HTML code directly or by generating HTML code through the use of FrontPage. Most often images were not added to the centre and right-hand columns, although the default home page included the STS logo at the top of the right-hand column.

(From where I always removed it as it took up unnecessary space)

In WSS the same customization possibilities are available as above. However in addition it is possible through the use of Web Parts to add images at suitable positions in the centre and right-hand columns. This process is not as easy as it looks at first glance and therefore this section deals with a recommended procedure.

First create a Picture Library which will contain all the images that you want to use on the web site. Then use standard WSS techniques to upload images to that library. (This initial step is essential as a means of getting a web address for the images so that they can also be accessed at that address from other PCs apart from the server).

Secondly go into the web page and select "Modify My Page" or "Modify Shared Page" (or "Modify My Page" followed by "Shared View" followed by "Modify Shared Page"). Select "Add Web Parts" / Browse and choose "Image Web Part" now either Drag and Drop or use the Center/Right + Add button. Close the Add Web Parts window.

Go to the new web part on your page and click on "open the tool pane". Enter here the full address of the image that you earlier entered into your Picture Library for Web site images (you did do a Ctrl-C so you can now do Ctrl-V didn't you). OK (to have defaults for everything else) and you now have an image visible in that part of the column whenever you (if done in Personal View) or anyone (if done in Shared View) accesses the web site from any location.

Note the following peculiarities in the way these Web Parts work.

a. If you create an Image Web Part in Shared View it is immediately also present in the Personal View.

b. If you create an Image Web Part in Personal View it is only present in Personal View

c. An Image Web Part created in Shared View can be closed in Shared View. In this case it are still present in Personal View *if it has been subsequently amended in Personal View* otherwise it is removed from Personal View too.

d. An Image Web Part created in Shared View can be deleted in Shared View (Delete is only available in "Design This Page" mode). In this case the Image Web Part is no longer present in Personal View.

e. Image Web Parts created in Shared View can be amended only in a limited way when in Personal View. For instance the URL of the image can not be amended in this case. This also applies to Image Web Parts when the Image Web Part has been closed in the Shared View.

f. The default view of an Image Web Part includes a Title Bar and Frame. This can be easily changed to None (no Title Bar or Frame) which is in my opinion a much more sensible option for an Image. (Modify Web Part / Appearance Section / Frame Style)

g. Watch also out for "Reset Page Content" when in the Personal View. This will make your Personal View a copy of the Shared View.

 

 

"make sure your picture library has reader permissions for everyone"

 

 

In STS 1.0 it was possible to customize the _layout files.

 

In WSS it is no longer possible because these _layout files are per server.

 

In order to make a change of look valid for the whole site you can either use one of the ready-made themes MS include or create your own.

 

Here are some instructions for how to create your own.

 

Open your site in Front Page 2003

Format | Theme

 

At the very bottom of the theme task pane select "Create new Theme"

 

You'll get the "Customize" theme window

 

Click on "Text"

Click on "More Text Styles"

 

From the list, choose the selector you want

 

Modify (modify the attribute(s) you are interested in for that selector)

 

Repeat for each selector you want to modify

| OK | OK

 

Save as "MyTheme" |OK

 

Apply "MyTheme" to your SharePoint site

 

When you select customize a theme, goto the Text panel and click on "More Styles" - there you can edit all class styles (ie .ms-xxxxx).

 

This information comes from Gabe Bratton who also pointed out that the theme does not replace the existing (ows.css on an WSS site) style sheet, but instead acts as a modifier for it.

 

Daniel Prior comments (slightly edited) that there is a non-Front Page alternative.
 
You can duplicate a theme folder

 

(default location C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\TEMPLATE\THEMES\)

 

by making changes to (renaming files, replacing text in CSS and other text files) and updating the SPTHEMES.XML file

 

(located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\TEMPLATE\LAYOUTS\1033\).

 

Thumbnail images for the theme should be placed in the appropriate directory

 

(C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\TEMPLATE\IMAGES\).
 

Thank you Daniel.
 

 
 

Amend your site as you wish (using FP etc.), then go to Site Settings / Site Administration / Save Site As Template

Go to Site Settings / Site Administration /Manage list template catalog

 

You will see the list of list template fwp files. You can hover over the link for the fwp, right click and save the file to disk.

 

a) You could save the file directly to \program files\common files\microsoft shared\webserver extensions\60\bin.

 

To add to the global catalog, you would run the command line:

 

 

or

 

b) You could save the file locally (to C:\ say) (Rohit Puri)

 

in this case you would run the command line

 

 

Udaysinh Patil adds
 
If you are creating a site from this template with code then you need to specify wild card inclusion with this command

 

stsadm -o addpath -url http://SERVERNAME/* -type wildcardinclusion

 

Thanks, Udaysinh!
 

run the command line:

 

 

This will provide output such as:

 

Custom Template - Language: 1033 - Site Template: _GLOBAL_#1

run:

 

 

(One line)

You can't.

 

Roles are not preserved as part of the template in this (first) release of WSS.

The maximum size for a site template is 10MB.

 

If you create a site larger than that you will normally get the error message "This site is too large to save as a template".

 

Another possible effect is that you will get a time-out. This tends to happen when you have both more than 10 MB of data AND a large list with substantial list data.

 

(Thanks to Gabe Bratton - the text is mine)

 

Gabe also later confirmed that this 10MB limit is hard-coded and it is not possible to change it.

The maximum site for a list template is (like the maximum list for a site template) 10MB.

 

Again this is hard-coded and can't be changed.

 

Please see also the item VI.7 "How to save a Document Library as a template that with content is greater than 10 MB in size (and not lose data)" in the Tutorial section for a way of moving lists via the "Save as List Template" function that are greater than 10MB in size. 

If you created the templates by going through the WSS UI and selecting 'Save List as Template', you can remove them as follows:-

 

Site Settings / Site Administration

 

In 'Site Collection Galleries' click on “Manage List Template Gallery”

 

Edit (the Template you want to remove) + Delete

 

(based on a reply by Jerry Orman)

 

 

 

Go to Webtemp.xml in templates\1033\XML

 

There you can change the HIDDEN property of a particular configuration ("Team Site" "Blank Page" etc.) for it not to show up when you create a
site.

 

This needs an IISRESET.

 

Ian Morrish points out that sites that include Data View Web Parts (DVWPs) store a hard coded link to the list.

 

This means that when trying to create a new site from a template saved from such a site you will get error messages such as

 

List does not exist
The page you selected contains a list that does not exist.  It may have been deleted by another user.  Click "Home" at the top of the page to return to your Web site.
Troubleshoot issues with Windows SharePoint Services.

 

Ian's suggestion is to add ?contents=1 to the page url

 

This will disable any DVWPs and you can then edit the data connection with the correct link details.

 

In STS 1.0 this required coding. Specifically because (for instance) an asp-based web site required a different pre-processor to that used by STS, it was necessary to add code containing a so-called IFrame into the STS page where the contents of the other web site should appear.

 

In WSS this no longer requires coding. A Web Part "Page Viewer Web Part" is available that can be dragged and dropped into the Web page and details of the site to be accessed along with size in this page etc. are specified in the fill-in box that appears at the right-hand of the screen.

 

Adam Macaulay came up with this suggestion for the direction to take to achieve this.

 

He described it as "cloggy" or in other words "a technique used to get the job done in the wierdest way possible, not the norm".

 

-----------

 

Create an entry ASPX Page which the user will authenicate to and then will redirected to the site in question. You will not be able to create your own login box but the SharePoint/Browser Authenication box should be good enough. Bascially what you are doing is catching the authentication error that can occur if the user does not have access. If they have access to the first they will get redireted accordingly, if not then they'll get the second redirect.

 

The code below is not real so you will need to look to the SDK for WSS to get the correct syntax but I just wanted to give you an idea.

 

Try

{
    Set your site object to open a site SPWeb objWeb =
SPControl.GetContextSite(Site).AllWebs
    objWeb.CatchAccessIsDenied = true;
    Redirect the user to the site url Page.Redirect(objWeb.URL)
}
catch
{
}

try
{
    Set your site object to open a site SPSite objSite =
SPControl.GetContextSite(Site).AllWebs
    objWeb.CatchAccessIsDenied = true;
    Redirect the user to the site url Page.Redirect(objSite.URL)
}
catch
{
}

-----------

 

 

 

Open the SCHEMA file for the announcements list type found in in the ANNOUNCE dir of the template root.

 

at the top of the file find:

 

<MetaData>
        <Fields>
            <Field Type="Note" RichText="TRUE" Name="Body"
DisplayName="Body" Sortable="FALSE" ></Field>
            <Field Type="DateTime" Name="Expires" DisplayName="Expires"
Format="DateOnly" FromBaseType="TRUE" ></Field>

 

in the FIELD definition for Body add in AllowHyperlink="TRUE"

 

 

IISreset and you should be all set. You should have a button that lets you add HyperLinks.

Add this just before the closing </head> element:

 

 

 

 

Look for the line in the doclib's schema.xml starting with 

 

 

and change it to

 

Also look for the line starting with

 

 

and change it to

 

 

John Jansen suggested the following (edited)

 

Create a Data View Web Part (using FrontPage) and hand-code the XSLT to select unique values.

 

This is **possibly** the relevant section of the XSLT Developer's Guide

 

 

Thanks, John!

 

[The top-level of the XSLT Developer's Guide is at

 

 

as far as I know there is no download available (2 April 2004 status)]

 

 

 

 

This is covered in the following article

 

 

at the FrontPage Customization site.

 

To save you time, please note that the technique there only works when transfering to a web part page.

 

1. I you create or use a web part package without dwps, then the virtual server gallery is not populated on installation of the package. (It is if the package contains dwps)

 

2. If the web part package has already been installed with dwps - i.e. you already have an entry in the virtual server gallery - you can delete the dwps from the wpcatalog folder (\inetpub\wwwroot\wpcatalog)

 

3. If you manually install a web part then you will place the assembly where you want to place it and you will add the appropriate SafeControl markup. In this case you just won't add dwps to the wpcatalog folder.

 

 

1. Insert a Data View of some WSS list (for instance the Announcements list although the source doesn't matter as long as you have at least one piece of data in it).

 

2. Create a conditional formatting rule on this to show items when Created By == [Current User]

 

(Having selected Conditional Formatting, you'll have to select the contents of any one of the fields from this custom list in order to be able to "Create" a conditional rule.)

 

3. Do a Find in the Code View in Front Page 2003 for

xsl:value-of select="@Title"/>

 

4. Replace this with

 

<p>Hello, <xsl:value-of select="$UserID"/<<p>

 

He notes a couple of things

 

a) he does 2. above to make sure the parameter is in scope for the XSLT template.

 

(If it isn't, then on switching back to Design (View) you see a long message saying that 'a reference to variable or parameter "UserID cannot be resolved" etc. I hope to be able to add here what you do then)

 

b) it might be easier to create a custom list that has one item in it rather than to use Announcements

 

c) you have to make sure that this code is not within a "FOR EACH" because then you will have "Hello Joe" for each record.

 

(You nicely avoid this by following b) and creating a custom list specially for this with one record only)

 

------------

 

maritza commented that

 

 

 

-------------

 

 

If you do this, $UserID is only in scope for the web part you do it on.  If you want to pull back the name of the user, and also display all records, I used "Created By Equals [Current User] Or CreatedBy Not Equal [Current User]"

 

 

 

 

 

Here - from John P. Grieb - is the answer to how you remove it *from sight* ("It just disables the "Multiple Upload" functionality on the Web page because it thinks that it thinks that the appropriate browser isn't running or a required control isn't installed").

 

Edit the file upload page in FrontPage.
Switch to Code view.
Modify the function EnsureUploadCtl to return 0;.
 
The only problem with this method is that you have to do it for each document library you want to disable multiple file upload for.

 

Thanks John !

 

 

Jim Duncan provided the solution

 

Make a backup copy of \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\TEMPLATE\1033\XML\WEBTEMP.XML and then open WEBTEMP.XML

and then change the Hidden attribut to equal "TRUE" for the Configurations you don't want to appear in the list.

 

 

e.g.

 

<Configuration ID="1" Title="Blank Site" Hidden="TRUE"
ImageUrl="/_layouts/images/stsprev.png" Description="This template creates a Windows SharePoint Services-enabled Web site with a blank home page. You can use a Windows SharePoint Services-compatible Web page editor to add
interactive lists or any other Windows SharePoint Services features.">
</Configuration>

 

You must restart IIS for changes to take effect:

Start>Run>iisreset

 

 

 

1. Save a backup of the searchresults.aspx file found in the program
files/common files/microsoft shared/webextensions/layouts folder on the server.

 

2. Edit the searchresults.aspx, file. 

 

3. Comment out the tables

that reference the 'list' results.

 

4. DO NOT comment out the place holders - this causes errors.

 

5. Save the file.

 

 

(Ed's aside: So far the only page I've found where I could add a form was one default.aspx page (another one didn't let me))

 

Boris Gomiunik came up with the following workaround.

 

1. Make a html form in a new page, say "newsletter.htm".

 

2. Then in the page you want to include the subscription form use page viewer web part to view the "newsletter.htm" in the page.

 

 

You have two options:

 

1. If it's a top level site collection connected to a portal you can configure it in the site settings to not show the link.

2. Edit default.aspx with FP2003, select the link and delete it.

 

 

1. Create a custom theme for the site, copying an existing one

 

2. Modify the CSS class for the navbar

 

(There is info in the SDK on which class to use and how to create a custom theme).

 

You'll want to modify the a:hover property which tells you what color/style to use when the mouse hovers over the item.

 

The number of lines the Announcements web part displays is a property which can be manipulated from FrontPage.

 

Open your site in Frontpage, expand the Lists folder, right click on Announcements and get properties.  In the resulting window, click the "Fields" tab.  In the scrolling list of fields, double-click the "Body" field.
 
There's nothing for you to change on the next window pane, but if you click "next", you'll see a field where you can change the number of lines displayed.

 

If you want a better description, MS had a Knowledgebase article on a similiar topic - adding a Hyperlink button to the Announcements text editor, which is an ultra-handy feature. 

 

The article is at http://support.microsoft.com/default.aspx?
scid=kb;EN-US;839944. 

 

The title indicates the technique applies to SPS, but it actually works fine with WSS...

 

 

 

 

and unfortunately. he's right.

 

 

 

 

 

 

See www.wssfaq.com for an example of this before you proceed.

 

The steps using FP 2003 are easy but not particularly easy to find so here they are

 

- Open the site in FP 2003

 

- Open default.aspx

 

- In Design View select a suitable central position
(high up / above the web parts)

 

- Insert (FP menu line) + Navigation

 

- Select Link Bars (already default)

 

- Select Bar with custom lists

 

- Select a theme

 

- Choose an orientation (horizontal)

 

So far so good, but the next step while simple isn't so obvious.

 

- Amend the "choose existing drop-down" to Lists

 

- Remove the ones you don't want

 

- OK

 

- Look in Preview to see if it's where and how you want it to look.

 

- Save

 

Check again in a browser and then go back to FP 2003 to remove the entire original Quick Launch code.

 

 

 

If you look at the code in default.aspx you'll find that there are two <TR> lines for each of the major items (Pictures, Surveys etc.) listed. The first line contains the name (e.g. Surveys) and the second doesn't ...

 

Amend both (starter) <TR> statements so that they contain style="visibility:hidden" - i.e. so that they look like this

 

<TR style="visibility:hidden">

 

save the new version and the Surveys heading no longer appears.

 

 

Nobody Special (sic!) commented

 

 

The cSmartLaunch product from Collutions has an option to automatically hide the section headings (Pictures, Surveys, etc.) if the sections  are empty.

 

 

http://www.collutions.com/Lists/Solutions/DispForm.aspx?ID=15
 

Thanks for that !

 

 

 

I tried the last solution and what it did was move the link to the beginning of the list instead of hiding it.

 

 

 

I opened up the default.aspx file and just commented out the Surveys table row.  It removes it from the Quick Launch, but doesn't prevent you from creating a survey if you need to. You can then easily just go back in and uncomment out that row if you needed to "readd" the heading. 
 
Thanks, Steve! 

 

"You'll need FrontPage 2003. Just load the site up and use the FP tab component and insert it onto the page then create new pages (tabs) and hook them up to each tab. You can optionally set the style of the tabs to match the rest of your site."

 

 

You'll find a full description of the process at Bil's blog

 

 

Jesslyn Hendrix commented that 
 
"I found that it was easier for my users to implement the Multipage meeting as a model for a tabbed template.  It was easier to manage and does not require users to have or use Frontpage."

 

Thanks Jesslyn! 
 

The usual default is that links sent by e-mail to documents in WSS Document Libraries are opened in the browser as read-only.

 

Ian Morrish has code on his web site

 

(at http://www.wssdemo.com/Pages/DocEdit.aspx)

 

that makes a link sent by e-mail to documents in WSS Document Libraries open in Word so it can be edited.

 

It consists of two sets of code

 

a) in the AllItems.aspx page, he adds a client side script to add a menuitem to the dropdown list to generate an email

 

b) in a web page (possibly but not necessarily AllItems.aspx) he adds a second set of client side code

 

For the code itself, please go to the above web page.

Rodi Williams wanted in a Survey page to move the normal 'Save and Close' button from the top of a page to the end of the Survey.

 

 

 

The problem is that the whole input form, including the toolbar that contains the Save And Close linik, is a compiled Web Part, and therefore not someting you can edit.

 

So, although this may seem a bit (or way) crude, I would add a button like this to the bottom of the page.

 

<input type="button" value="Save and Close"
onclick="document.forms[0].diidIOSaveItem.click();">

 

where diidIOSaveItem is the ID of the Save And Click hyperlink at the top of the page.

 

 

You can also clone the entire toolbar to the bottom of the page as shown here:

 

 

 

(Any more Jims want to comment)

 

Jason Fortner commented
 
"You can hide the items on the toolbar by using the style of the item you would like to hide. "

 

Thanks, Jason! 
 

This is taken from the blogs of both Patrick Tisseghem and Bil Simser (both SPS MVPs) - at the end you'll find links to the original blog items.
 
Q: I would like to run a CAML query where a WSS column as datetime has to be compared to the present time.
 
A: Sharepoint works with dates in the ISO8601 format: yyyy-mm-ddThh:mm:ssZ
 
So your CAML query should look like this

<Query>
<Where>
<Gt>
<FieldRef Name="EventDate" />
<Value Type="DateTime">2005-5-27T00:00:00Z</Value>
</Gt>
</Where>
</Query> 
 
Bil Simser added this
 
You can add a time to the date as well if you want to a query for a particular time. For dates with time the format of the query has to be:
 
<Query>
<Where>
<Leq>
<FieldRef Name="EventDate" />
<Value Type="DateTime">2005-05-27T16:00:00Z</Value>
</Leq>
</Where>
</Query>
 
So this would return all items in a list that has a field called EventDate with a value before 4:00PM on Friday, May 27, 2005.
 
 
Now the blog addresses:
 
Patrick: http://blog.u2u.info/DottextWeb/patrick/archive/2005/05/27/3010.aspx
 
Bil:
http://weblogs.asp.net/bsimser/archive/2005/05/27/409243.aspx

Bil Simser has a detailed blog item on this at

 

 

which I suggest you read in full.

 

The main insights he has there are that WSS fields often (see there for the details he has uncovered) use a field length of 50 characters irrespective of the real length and that there is a DisplaySize parameter that can be used in SCHEMA.XML but which is not listed in the SDK.

 

Adding this to suitable fields in SCHEMA.XML like this

 

   <Field Name="City" DisplayName="City" Type="Text" DisplaySize="20" />

 

allows you to adjust the display size of your fields.

 

But look at the blog item for the details !

Chandima Kulathilake posted this in his blog (http://digitalmelon.com/default.aspx) and kindly gave me permission to re-use the text of the blog item here.

 

---------

 

Recently a project that I was working on had a specific requirement that the client did not want it to be possible to create "Folders" in Document Libraries.

 

At the same time they did not want to modify the site definition files.

 

[You can modify the site definition's SCHEMA.XML to remove the code which applies the Folder icon.

(SCHEMA.XML is at
“\$\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\1033\STS\LISTS\DOCLIB\SCHEMA.XML“)]

 

You can also do this without editing SCHEMA.XML by using a style element that's applied to the code.

 

The New Folder icon is created by using some simple HTML. This code can be found by viewing the source of the page:
Look for: <a tabindex="2" ID="diidNewFolder"...

 

So all I did was to add the following to OWS.CSS

 

(OWS.CSS is in:
$\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\LAYOUTS\1033\STYLES\)

/* Hide Folders */
#diidNewFolder

{
visibility:hidden;
margin: 0 0 0 0;
}

 

Note: This change will also apply to all WSS sites created in a Portal Server 2003 system.

 

[Mike: I've edited the text and any error in the edited text is mine - I didn't edit the OWS.CSS addition though.]

Chandima Kulathilake