Here is the client side JavaScript that will allow you to open any page within a dialog box-

//Handle the DialogCallback callback
function DialogCallback(dialogResult, returnValue){
    window.location = window.location;
}

//Open the Dialog
function OpenEditDialog(link){
    var options = {
        url:link + '&IsDlg=1',
        width: 700,
        height: 700,
        dialogReturnValueCallback: DialogCallback};
    SP.UI.ModalDialog.showModalDialog(options);
}

To invoke the dialog, simply call the OpenEditDialog function with the target URL.

Notice that the IsDlg=1 query string parameter is appended within the OpenEditDialog function. The presence of “IsDlg” dynamically loads the "/_layouts/styles/dlgframe.css” file which applies “display:none” to all items using the “s4-notdlg” css class. This effectively hides items of this class in a dialog box. For example, v4.master uses the “s4-notdlg” class for the Ribbon control to hide the ribbon within dialogs.

ThmxTheme.SetThemeUrlForWeb(newWeb, ThmxTheme.GetThemeUrlForWeb(newWeb.Site.RootWeb));

Do you know of a nicer way to inherit site themes? Please post a comment below.

<ContentType ID="0x010092E61E2438E84353B7211741448DE18A"
             Name="Example"
             Inherits="TRUE"
             Version="0">
  <FieldRefs>
    <RemoveFieldRef ID="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" Name="Title" />
    <FieldRef ID="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" Name="Title" Required="FALSE" />

Workaround

Attach a feature receiver to your content type and use the object model to modify the Title field-

SPContentType contentType =
     site.RootWeb.ContentTypes[
             new SPContentTypeId(contentTypeId)];
SPFieldLink title = contentType.FieldLinks["Title"];
title.Required = false;
contentType.Update(true);

Discussion

This is a ‘cheap’ solution so to speak because modifying the content type via the object model disconnects it from the XML definition thus making future updates messier (Read More).

I’m a strong advocate of doing things declaratively and this solution clearly violates that rule. A colleague of mine made a case for writing content types completely non-declaratively using the object model.

What best practices do you follow when writing content types?

Error occurred in deployment step ‘Activate Features’

Workaround 1
Use the “No Activation” deployment configuration and use Post-deployment command-line operations to manually activate your features since the retraction process will deactivate your features regardless.

Workaround 2
Deploy using default configuration until you see error message. Then manually Enable/Disable problem features and then RE-DEPLOY using default configuration-
1) Enable-SPFeature -identity "FeatureTitle" -Url http://localhost
2) Disable-SPFeature -identity "FeatureTitle" -Url http://localhost

Solution
When you upload a list template (STP) using a feature to the list template gallery ( _catalogs/lt ), you must set some attributes in order for the template to show up on the create.aspx page-

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
    <Module Url="_catalogs/lt" Name="PS.AACP.Stp" Path="">
        <File Url="StpTest.stp" Type="GhostableInLibrary" IgnoreIfAlreadyExists="TRUE">
           <Property Name="Title" Value="StpTest" />
           <Property Name="Language" Value="1033" />
           <Property Name="FeatureID" Value="{D90095AD-86D4-4e55-AE28-119E21530552}" />
        </File>
    </Module>
</Elements>

The default top navigation bar in SharePoint 2010 uses ‘Accent 1’ from the site theme to determine the background color for each one of the navigation items. However, SharePoint doesn’t directly use the user-provided hex code for this accent. Instead, there seems to be some sort of a ‘normalizing’ algorithm that generates a new hex code.

1) Let us set the Accent 1 color for our site theme to Red (#FF0000):

2) Now inspect the global top navigation bar and what you’ll notice is that the background color is NOT what you would have expected. SharePoint interpreted the red accent and generated its own hex code: #FFA5A5

Conclusion
SharePoint doesn’t directly use ‘Site Themes’ but instead seems to generate its own interpretations based upon it. Therefore, designers looking for some discreet control over the branding of a SharePoint site need to still write custom CSS in 2010.

http://server/results.aspx?k=sharepoint&u=http%3A%2F%2Fserver%2Flists

Problem
The above will return zero results if you have a server name mapping configured in your search settings-

Solution
Removing the server name mapping will resolve this issue and site specific search works as expected

Tip: Adding a query string url restriction is equivalent to the following-
 

Workaround
Modify one of the Kwizcom javascript files (“12\TEMPLATE\LAYOUTS\KWizCom_KSCP\KSCP.js”) to comment out the drag drop functionality (See lines 13, 21 & 22) -

   1:  function kwiz_cal_DragDropOnLoad(q)

   2:  {

   3:      g_WPQ = q;

   4:   

   5:      // attach onscroll event (needed for recalculating table cells positions)

   6:      window.onscroll = kwiz_cal_Scroll;

   7:      

   8:      if(browseris.ie || browseris.safari)

   9:      {

  10:          kwiz_cal_Calculate_Cells();

  11:          

  12:          // disable text selection for ie, safari

  13:          //document.onselectstart = function(event) {return false};

  14:      }

  15:      else

  16:      {

  17:          // firefox does not execute this function when assigning to onscroll event, but IE & Chrome do

  18:          kwiz_cal_Scroll(); 

  19:          

  20:          // disable text selection for firefox

  21:          //if (typeof document.body.style.MozUserSelect != "undefined") 

  22:          //    document.body.style.MozUserSelect = "none";

  23:      }

  24:  }

More Info

The official word from Kwizcom Support on this issue is as follows:

“The issue is caused by dragdrop functionality. The new release version 3.3.00 will allow the users to disable drag drop through settings.  Currently there is no exact timeline for release.”

Boot up was under 15 seconds on all attempts with a VMware configured with 256MB RAM and 1 Processor at 2.4 GHz. From login screen to home screen took under 5 seconds on all attempts.

2) Inside the OS
Upon the first login, Chrome OS opens up 2 tabs that would be most commonly used: Mail & Calendar. However after resetting the machine chromium only displayed the Google home screen. The homepages are configurable (See configuration options below)

There is a button on the top left that seems to be the equivalent of a “Start” button in windows. However you need a “@google.com” account to access any “Google Short Links” here. Neither my Gmail account nor my Google Apps account worked here.

3) Configuration Options
Configuration options can be accessed from the top right drop down menu. Looks like Google is planning on supporting other browsers besides just chrome based upon the second configuration screen.

Turns out that if you already have an existing alert setup on the list then even if you switch the list to use a different alert template, sharepoint sends you alert emails using the template that was assigned to the list when you ORIGINALLY setup the alert.

So the SOLUTION is to delete your existing alert and re-subscribe to the list.

If you would like to know more on how to customize the alert email templates in sharepoint then this is a great resource: Customizing Alert Notifications and Alert Templates in Windows SharePoint Services 3.0