'style.display' is null or not an object error

As you create pages you may see the following error:



If you do, it is probably because you have copied and pasted from one content editor web part into another. If you see this error you will need to check your content for any WebPartID that is being referenced. The copy paste will copy this into the new content, breaking the content, if you remove the DIV tags that contain that reference, it will fix the page.

If you want to avoid this you should copy the text out of the original web part, paste it into a word document and then copy the word document content and paste it into the new web part, this reformats and removes the WebPartID.

Thanks to egghead cafe for the discussion that is summarized in this solution.

Some helpful Links for MOSS Administrators

Administrator Guides
· MOSS 2007 - Administrator Guide
· WSS 3.0 - SDK
· WSS 3.0 - Technical Library
· MOSS 2007 - Newly published content
· WSS 3.0 - Newly published content
· WSS 3.0 - SharePoint Server 2007 Developer Portal
· WSS 3.0/MOSS 2007 - Office SharePoint Server 2007 Administrator's Companion
· Complete reference of all PSCONFIG operations


Best Practices
· Before You Begin with SharePoint Server 2007
· Best Practices Analyzer for WSS 3.0 and MOSS2007
· Writing SQL Syntax Queries for Relevant Results in MOSS2007
· Backing Up and Restoring Web Sites w/ Stsadm
· MOSS 2007 - Planning and Architecture for Office SharePoint Server 2007


Search
· Configure the Office SharePoint Server Search service
· Configure Office SharePoint Server Search to crawl Lotus Notes
· Security considerations for search
· Overview: Plan search
· White paper: Evaluation guide for search in Office SharePoint Server
· Plan to deploy index and query servers

STSADM Commands
· Jose Barreto's Blog Complete reference of all STSADM operations (with parameters) in MOSS 2007 SP1

Publishing Templates

When you are working with MOSS 2007 there are two different templates you need to be able to deploy; application templates (WSP files) and site templates (STP files).

While creating an STP file from a site is easy and it makes it available within SharePoint for use, if you script any of your actions, you need to deploy your STP file globally. To do that you are going to need to download the STP file from the site Gallery and then delete it for the gallery. If you don't delete it you will have duplicate templates when we are done.

Once you have the file downloaded you will need to copy it to your web front end server. Once copied we will do the following from the command line using stsadm:

1. Check if the template already exists:
stsadm -o enumtemplates
2. If the template exists, you will need to delete the current copy:
stsadm -o deletetemplate -title {template title}
3. Now you can add the template:
stsadm -o addtemplate -filename {template filename & location} -title {template title} -description {template description}

It will prompt you that an IIS reset is needed at each of these steps, but in reality it is not required and can wait until a time that works for your environment.

The other deployment that you will need to be able to perform is a GAC deployment of an application template. This is also done on the web front end server using stsadm.

1. Add the application template to the solutions list:
stsadm.exe -o addsolution -filename {template filename & location}
2. Deploy the solution to the GAC:
stsadm.exe -o deploysolution -name {template filename} -immediate -allowgacdeployment
3. Copy the Binary Content:
stsadm -o copyappbincontent


So now you know how to deploy global site templates and applicaion template solutions.

Turn off New Folder option in MOSS as default

Have you ever wanted to have the New folder disabled by default in MOSS 2007?

You can manually disable it by choosing the Document Library Settings and choosing Advanced Settings, but if you are like me, you have far too many sites to worry about let alone changing this with each Document Library.

I have a solution for you, why not disable it in the template? It is pretty easy, just go to your hive 12 folder, TEMPLATE\FEATURES\DocumentLibrary\DocLib\ and edit your schema.xml. In the file, disable the folders by adding the highlighted setting to your List XML as follows:

List xmlns:ows="Microsoft SharePoint" Title="$Resources:shareddocuments_Title;" FolderCreation="FALSE" Direction="$Resources:Direction;" Url="Shared Documents" BaseType="1"

The FolderCreation option, simply chooses the No folder option in the advanced settings by default, allowing you to enable it if needed.

Once the change has been made and saved, you will need to restart IIS for the change to take effect.

Hope this helps someone out there, it took me forever to find a solution and I thought I should share it.