• Content Deployment – Best Practices

He is another Stefan Goßner post that is also very interesting

• Pimp My Content Deployment Job

The post MOSS Content Deployment MUST READ appeared first on Blog IT.

For some reason if you need to install a Publishing Site, developed in a SharePoint 2007 with infrastructure update, in a SharePoint 2007 with only SP1 o you can :).

You just need to use stsadm -backup and stsadm -restore to do the job.

Sorry, but can't be done, i was wrong, i used two SharePoint 2007 Server VM but both where with Infrastructure Update 🙁 my bad.

Backup a Site Collection

1.Open a console windows
2.In the cmd window navigate to the “C:\Program files\common files\microsoft shared\web server extensions\12\bin” directory.
3.Type stsadm -o backup -url “http://YOURSITE” -filename “C:\BACKUP.bak” -overwrite
4.Press Enter

At this point you can copy the file to the other server, or just perform the restore on the same server by following the steps below.

Note before restoring ensure that the target site collection you are restoring onto is a BLANK site. This will allow you to avoid some potential issues with duplicate names and ID’s.

To Restore a Site Collection

1.Open a console windows
2.In the cmd window navigate to the “C:\Program files\common files\microsoft shared\web server extensions\12\bin” directory.
3.Type stsadm -o restore -url “http://YOURSITE” -filename “C:\BACKUP.bak” -overwrite
4.Press Enter

The post SharePoint Infrastructure Update and SharePoint SP1 environments appeared first on Blog IT.

To do that o need to add this to the url of you current site _layouts/savetmpl.aspx.

You can to this in the root site or in a sub site.

When you put that url in your web browser you are redirected to the following page.

Insert the name and title for the file and click on the OK button.

Now you have your site save as a template, to be possible to use this template you need to allow it, so you need to go Site Settings and click on the "Page layout and site template" under Look and Feel.

The template will appear on the left lisbox, choose and click on "Add >" then "Ok" button.

Now you can go to the Site Actions and Create Site.

Saving a site as template will have all pages and lists but no subsite.

The post WCM – Save Site as Template appeared first on Blog IT.

 But there is a very nice and clean trick:

Add a new calculated field to the content type that you are using on the page layout with the following formula:

=TEXT(DATEFIELD,"DATEFORMAT")

In the date format you can put "dddd, d mmmm yyyy" or "mmmm d-mm-yyyy" …

On your page layout add the html code behind:

<PublishingWebControls:EditModePanel runat=server id="EditModePanel2">
      <SharePointWebControls:DateTimeField ID="DateTimeField1" FieldName="DataPublicacao" runat="server"></SharePointWebControls:DateTimeField>
</PublishingWebControls:EditModePanel>
<PublishingWebControls:EditModePanel runat=server id="EditModePanel3" PageDisplayMode="Display">
      <SharePointWebControls:CalculatedField ID="CalculatedField1" FieldName="CustomDateField" runat="server"></SharePointWebControls:CalculatedField>
</PublishingWebControls:EditModePanel>

This will show on edit mode the datefield and on display mode the calculated field. 

You can use this trick on any list to show on your views different date formats.

The post DateTime SharePoint Field Format appeared first on Blog IT.

The out-of-the-box styles for the editor are located on the Web front-end server at %systemdrive%:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\STYLES\HtmlEditorCustomStyles.css. There are three main styles which are accessed from the rich text editor style drop-down: .ms-rteCustom-Article; .ms-rteCustom-ArticleByline; .ms-rteCustom-ArticleHeadLine. Note that the styles all include the named parameter ‘rteCustom’.

To add a new style and have that style available from the style drop-down selection in the rich text editor, create a new css file and then create a new class, for example:

.ms-rteCustom-SharePointRusSpecialStyle

{

Font-family: verdana;

Font-style: italic;

Font-size: 18pt;

Color: fuchsia;

}

Then save the file and upload it to the root site’s Style Library, i.e. http://site_server/Style%20Library/Forms/AllItems.aspx.

Next, using the browser, navigate to the Site Master Page Settings page (from Site Settings, Look and Feel, Master Page) and in the Alternate CSS URL section select the radio button ‘Specify a CSS file to be used by this publishing site and all sites that inherit from it’. Then Browse to the Style Library where you uploaded the custom CSS file and select that file. Click OK.

Note, here we’ve simply added an override for a custom CSS class specifically for the rich text editor. But, you could just as easily bundle this additional class into your main CSS override file, remembering to specify the ‘rteCustom’ attribute in the class name.

Then go use the rich text editor to access the new style.

The post MOSS Rich Text Editor Styles – modify and add new styles appeared first on Blog IT.

But using API and getting the object weparts using the GetLimitedWebPartManager there is only the correct webpart.

Then when i was trying to find the reason for this problem, the SharePoint Designer gave me the solution.

He automatically added to the <%@ Page this information meta:webpartpageexpansion="full".

So i've changed the page on my feature, deleted the page from my site, deactivate the feature, activate the feature and voiala my page is working.

By the way i've used a feature to add pages to my site because the page will exist on every sites and subsites of my site.

CHANGED: Don't use this option, please see the comment to this post

The post Duplicated WebPart added to a Page on WCM appeared first on Blog IT.

 So how can i delete this Page Layout ?

What i did to delete it is very simple, create a new folder on SharePoint Designer drag or cut and page the Page Layout file into the new folder. Then delete the folder.

Simple isn't it :).

The post Deleting Page Layouts on Microsoft Office SharePoint Server WCM appeared first on Blog IT.

Today i found a new reason to provoke this error. If we define two files with the same name and in the same folder on the feature.xml, elementmanifest.xml and on solution.ddf the wsp file created will have two files with the same and that will also cause this error.

The post Failed to extract the cab file in the solution appeared first on Blog IT.

Customizing and Branding Web Content Management-Enabled SharePoint Sites (Part 1 of 3): Understanding Web Content Management and the Default Features – This article discusses topics that you should understand before you use Microsoft Office SharePoint Server 2007 to create sites that support Web content management (WCM) and gives a general overview of the various artifacts that are available in the product. (11 printed pages)

Customizing and Branding Web Content Management-Enabled SharePoint Sites (Part 2 of 3): Extending WCM – This article explains the structure of master pages, the steps to create a custom master page, the underlying mechanisms of navigation in WCM-enabled sites, the creation of custom field controls, and how to customize the Page Editing toolbar. (19 printed pages)

Customizing and Branding Web Content Management-Enabled SharePoint Sites (Part 3 of 3): Creating and Configuring WCM-Enabled Sites – This article examines the Web content management (WCM) features of Microsoft Office SharePoint Server 2007 from an administrative perspective: creating a Publishing Portal site, configuring a site for anonymous access and forms authentication, and using site variations. (9 printed pages)

The post Customizing and Branding Web Content Management-Enabled SharePoint Sites appeared first on Blog IT.