This post on the SharePoint 2010 forums also mentions this issue.

You can off course use powershell to get rid of this problem:

$site = Get-SPSite "http://sitecollectionurl"

$web = $site.OpenWeb("/weburl")

$web.AlternateHeader = ""

$web.Update()

Update:
The post on the forums got answered and according to that it has to do with the publishing feature that was activated before saving the site as a template. However in my case that feature wasn’t activated, because we’re aware that such a scenario isn’t officially supported by Microsoft.

Bookmark to:

CSS contents showing in settings page for site based on custom template is a post from: Peter Gerritsen's blog

For instance if you would like to filter on a date, you could use the following query:

LastModifiedTime>=01/06/2010

The actual format of the date depends on your regional settings (I’m using Dutch (nl-NL) in this case).

To search within a range of dates you can use the following query syntax:

LastModifiedTime:28/06/2010..30/06/2010

To exclude items you could use the following syntax:

LastModifiedTime<>28/06/2010

More info from MSDN about keyword syntax kan be found here: http://msdn.microsoft.com/en-us/library/ee558911.aspx

Bookmark to:

SharePoint 2010 Search: Property Restriction in Keyword Queries is a post from: Peter Gerritsen's blog

SPList list = SPContext.Current.List;
SPField field = list.Fields["Thema"];

string value = field.GetValidatedString(SPContext.Current.ListItem[field.Id]);

When you use the resulting value as the default value on the field, everything should be okay. When you set an invalid default value, you will not be able to create new items anymore or set the default value through the UI. You can get around this by setting the default value back to an empty string.

Bookmark to:

Set default value on a Managed Metadata field through code is a post from: Peter Gerritsen's blog

A hidden web application feature is probably not activated. You can activate it through PowerShell or stsadm:

Enable-SPFeature -id “73EF14B1-13A9-416b-A9B5-ECECA2B0604C” -Url <Site-URL>

stsadm -o activatefeature -id 73EF14B1-13A9-416b-A9B5-ECECA2B0604C -url http://<url> -force

Bookmark to:

Term Store management option missing in Site Collection settings is a post from: Peter Gerritsen's blog

Sadly this version has some integration issues. Main ones I’ve noticed is not being able to use the “Edit in SharePoint designer” link in the context menu and not being able to edit page layouts in SharePoint Designer.

64-bit Office also has some integration issues. So unless you need 64 bit for working with really large Excel Sheets, I would stick with 32-bit for now.

Bookmark to:

Issues with SharePoint Designer 64 bit is a post from: Peter Gerritsen's blog

When the button is clicked a modal Dialog is shown that will allow the user to specify the options used for conversion:

When the Ok button is clicked the selected files will be added to a conversion job and the job will be started.

The dialog is launched by some javascript that is specified in the CommandUIHandler section of the ribbon button definition.

<commandUIHandler
Command="SP2010WA_Convert_Button"
CommandAction="javascript:function convertDocument() {
Sys.loadScripts(['/_layouts/SP2010WordAutomation.UI/SP2010WordAutomation.UI.js'], function() {
SP2010WordAutomation.UI.ConvertDocument();
});
}
convertDocument();"
EnabledScript="javascript:function oneOrMoreEnable() {
var items = SP.ListOperation.Selection.getSelectedItems();
var ci = CountDictionary(items);
return (ci > 0);
}
oneOrMoreEnable();" />

I’ve decided to use the beta version of the ASP.Net 4.0 AJAX client library to load the required scriptfile when it is actually needed. While this is not completely necessary in this case, because the amount of script in there is quite little, it could provide a speedboost because the browser won’t load and interpret the script when the page loads.

The definition also contains some script to enable the button only when one or more files are selected.

The following lists the script that is loaded and called when the button is clicked:

Type.registerNamespace("SP2010WordAutomation.UI");

SP2010WordAutomation.UI.ConvertDocument = function () {
var items = SP.ListOperation.Selection.getSelectedItems();
var selectedItems = '';
var k;

for (k in items) {
selectedItems += '|' + items[k].id;
}

var options = {
url: '/_layouts/SP2010WordAutomation.UI/ConvertDocument.aspx?items=' + selectedItems + '&source=' + SP.ListOperation.Selection.getSelectedList(),
title: 'Convert Documents',
allowMaximize: false,
showClose: true,
width: 600,
height: 480,
dialogReturnValueCallback: SP2010WordAutomation.UI.ConvertCallback
};

SP.UI.ModalDialog.showModalDialog(options);
}

SP2010WordAutomation.UI.ConvertCallback = function(result, target) {
SP.UI.Notify.addNotification(target, false);

SP.UI.ModalDialog.RefreshPage(result);
}

First I use the Type.registerNamespace method that is provided by the standard SharePoint scriptlibrary to make sure I don’t override other methods with the same names.

In the ConvertDocument function we then launch a SharePoint dialog that will load an ApplicationPage which provides the user with the options they can choose. The ConvertCallback function which is called when the dialog passes a result will add a notification message to the main screen.

To see how this mechanism can be used, please refer to this post by Vesa Juvonen

Bookmark to:

New sample project for SP2010 Word Automation: UI is a post from: Peter Gerritsen's blog

Because you can’t associate workflows created with SharePoint designer to libraries or folders, these actions won’t use the current item from the context, so you need to specify the input and output library or folder by url. To use the activities you can run the workflow on a other item or document. The activities locate the libraries or folders relative to the current web, so you don’t have to specify a full url:

You can download the latest release and source code from the CodePlex project site

Bookmark to:

2 new worflow activities added to SP2010 Word Automation is a post from: Peter Gerritsen's blog

Bookmark to:

SP2010 Installation – Error creating configuration database is a post from: Peter Gerritsen's blog

Word Automation Services allow you to convert document to and from different formats.

File formats the service can read:

• Office Open XML (DOCX, DOCM, DOTX, DOTM)
• Word 97-2003 Document (DOC) and Word 97-2003 Template (DOT)
• Rich Text Format (RTF)
• Single File Web Page (MHTML)
• HTML
• Word 2003 XML
• Word 2007/2010 XML

File formats the service can write:

• PDF
• XPS
• Office Open XML (DOCX, DOCM)
• Word 97-2003 Document (DOC)
• Rich Text Format (RTF)
• Single File Web Page (MHTML)
• Word 2007/2010 XML

(source)

As far as I’ve found out, there are no UI features available out-of-the-box to use these services, so I’ve decided to create some. The first one is a custom workflow action you can use in SharePoint Designer to convert a document to many of the supported
formats.

In the workflow designer you can add the “Convert Document” action:

The action is inserted into the workflow step where you can specify the url of the output file, select the output format and save options and select a variable for storing the conversion job id (which you can use later to retrieve the status, as the job runs asynchronous):

The job id is also logged into the Workflo w History Log (the second entry is from a second workflow action that logs the returned conversion job id variable):

After the job has run, which can take up to a few minutes (depending on the word automation services settings), the converted document appears in the library:

The custom workflow action is one of the first features for Word Automation in SharePoint 2010 I’ve planned to release. Other features will be a Ribbon and Item context menu extension and more Workflow actions.

Let me know if you have any suggestions for improvement or other functionality you would like to see.

Bookmark to:

CodePlex project for Word Automation Services is a post from: Peter Gerritsen's blog

But when I was working on a project with custom workflow actions, the SafeControl entry that is needed for making it work was not added to the generated manifest.xml file.

Fortunately the package designer allows you to modify the template file it uses for generating this file. So open up the package designer, switch to the “Manifest” tab and add the assembly reference in the template yourself, but this time, include the SafeControl entry:

You can safely use the SharePoint project tokens in there as well, but only for the SafeControl entry. When you put it into the Assembly entry, the package generator won’t understand it and will add another assembly reference for the project output:

Bookmark to:

Force Visual Studio 2010 to add a SafeControl Entry is a post from: Peter Gerritsen's blog