Archive for category Configuration

SharePoint 2010 Site Search Drop Down Mode

This post has moved to my new blog located at: http://www.sharepointanalysthq.com/2010/06/08/sharepoint-2010-site-search-drop-down-mode/

Enjoy!

No Comments

SharePoint 2010 Claims Based Authentication Resources

This post has moved to my new blog located at: http://www.sharepointanalysthq.com/2010/05/04/sharepoint-2010-claims-based-authentication-resources/

Enjoy!

    No Comments

    SharePoint 2010 inline list editing

    In line list editing is another cool new feature that can be offered to your users in order to speed up data entry. The most accurate description is that its kind of like the next evolution of the datasheet view except its a little more user friendly to use but doesn’t offer the ability to edit multiple records at one time.

    In order to enable in line editing, which isn’t enabled on lists by default, firstly modify the default view by going to List Tools -> List -> Modify View

    Modify View

    Modify View

    Then expand the Inline Editing option and select the ‘Allow inline editing‘ checkbox, then press OK to save the changes to the current view

    Inline Editing

    Now you have a new little icon on the far left side of the list view  as shown below, click on it and you can see the inline editing experience which is pretty cool actually!

    Inline editing in action

    Inline editing in action

    You can see that you have access to drop downs, text fielsd and related links. Unfortunately for calendar controls looks like you can only enter in a text date and that you can’t have links to look up lists but I am sure that this might change in the RTM version.

    Enjoy :)

    No Comments

    Creating an RSS reader using a Federated Search Web Part

    Overview

    WSS 3.0 comes with a number of web parts but one that is missing, and is oft wanted, is an RSS reader that comes with MOSS. Where is it you say? Well its not there but if you install Search Server Express 2008 on top of WSS 3.0 or standalone you get access to a whole collection of search web parts.

    Collection of search web parts when SSE2008 is installed

    Collection of search web parts when SSE2008 is installed

    Federated Results Web Part

    So what does the Federated Results web part actually do. In essence it take a URL string with a parameter for search results that returns back well formatted XML in the form of ATOM or RSS and then renders that to display it to the user.If this sounds familar well it is, its virtually identical to the RSS Web Part that comes with MOSS but the Federated Results Web Part has a few more configuration options: allowing you to specify credentials, having parameters in the URL to access amongst others.

    But we can fool this web part into acting like an RSS reader by simply not specifying the {searchterms} parameter in the URL string and a couple of other configuration options as listed below.

    We will be using an RSS Feed from news.com.au with the url http://feeds.news.com.au/public/rss/2.0/news_mostpopular_travel_406.xml which will retrieve the latest popular travel stories.

    1. Create a new Federated Location

    First we have to create a new Federated Search Location since the Federated Results Web Part only allows you to choose from a drop down list of options. So go to Central Admin->SSP->Search Administration->Federated Location->New Location and you should see the screen below:

    Federated Location Configuration Page

    Federated Location Configuration Page

    Fill in the following fields (we will get to Location Information, Display Information and Restrictions and Credentials information below).

    • Location Name: This is an unique ID that is only visible to Administrators of Sharepoint so most likely a short identifier can be used, we are using ‘RSS-News-Travel’.
    • Display Name: This is the name that will be visible when a user adds a Federated Results Web Part to a page, so in our case we are going to call it ‘Popular Travel Stories Feed‘.
    • Description: This is the description that is shown once again when a user selects an option from the web part so something useful shoule reside here like ‘Latest travel stories RSS Feed from news.com.au‘.
    • Author and Version: Self explanatory, we are going to leave these out.
    • Trigger: This is important as it specifies if the web part will fire on certain queries, in our case we are going to set it for always.

    2. Location Information Configuration

    Location Information

    Location Information

    This is really where the magic happens, instead of specifying a search string using the {searchterms} parameter we leave it out and add out rss feed location:

    • Location Type: This has to be set to OpenSearch 1.0/1.1
    • Query Template: Now in here we specify the URL of the RSS feed, we dont need to add the {searchterms} parameter since we wont be using it.
    • More Results Link Template: We don’t need this for our use so just leave it blank.

    3. Display Information

    Display Information Section

    Display Information Section

    In this section you can specify the XSL transform to use to transform the returned XML into HTML for rendering. We won’t be discussing it here but it is very useful to grab other fields from the feed if need be.

    4. Restrictions and Credential Information

    Restrictions and Credentials Information

    Restrictions and Credentials Information

    There are a couple of interesting sections here that I will go through.

    • Restrict  Usage: You can restrict where this feed can be used which is really useful if you have a lot of Federated options that you don’t necessarily want your user to have access to.
    • Specify Credentials: I love this section! Now you can choose different types of authentication for your feeds. So say you subscribe to a site that requires authentication through a user name and password log in page this can now be done within SharePoint and you can view your subscribed feeds easily.

    So once you have all of this set, click on the OK button and you should see the new feed displayed in your Manage Federated Locations page.

    So we now have this all set up, lets put it on the page and see how it works.

    Adding your new Federated RSS News Feed to a page

    Now we need to add the Federated web part to a page and see our results so lets do that! Now we don’t need to add this web part to a search results page since for an RSS feed we probably want it somewhere more prominent, like the home page of the site. So lets add it there.

    1. Choose the Federated Search Web Part to add to the page

    Federated Search Web Part option

    Federated Search Web Part option

    2. Choose our feed to display on the page

    Choice of Federated Locations

    Choice of Federated Locations

    Click OK and we should be good to go….

    3. Where the hell is my feed??

    So as you can see there is nothing displayed on any page that is not a search results page. So why is that? Well if you ever look at the search results pages you can see that the search parameter is passed as a query string with the format of k={searchterm}.

    k parameter

    k parameter

    It is this query string that causes all the other search results web parts to fire, wether this be search core results, best bets or federated results. So in order to get any page that contains our Federated Results XML feed to work we need to add the k={searchterm} to the URL. What I usually do is modify the navigation so that the home tab is changed from Default.aspx to Default.aspx?k=feed this will then fire the Federated Results web part and we have a nice RSS reader for our users to use!

    Nothing is displayed with the K parameter

    Nothing is displayed with the K parameter

    Now with the k parameter we get our feed

    Now with the k parameter we get our feed

    Remember that you can also adjust the XSL to render this whatever way you like. Enjoy :)

    3 Comments

    SharePoint Branding: Themes vs Style Sheets vs Relative CSS

    Introduction

    In order to apply CSS to a SharePoint site (this includes WSS 3.0) there are a number of options. This article will discuss the pro’s and con’s of each and I am really interested to see what other people might be using, since we often have this discussion at work.

    The three basic methods are:

    1. Creating a SharePoint theme and embedding the CSS that you would like to use in the theme so that it may be selected by users from the Site Settings on each site, see below
      Users can select from a number of themes

      Users can select from a number of themes

    2. Creating a style sheet (anything with a .css extension) and then specifying it as the Alternate CSS URL in Site Settings->Site Master Page settings,see below:

    Specifying an alternate CSS file

    Specifying an alternate CSS file

  • Specifying a relative link to file within either a Page Layout or more commonly a master page with the code:
  • <link rel="stylesheet" type="text/css" href="/_layouts/styles/mystyle.css"/>
    
    

    Comparing the Approaches

    So which approach should you use, well lets look at the advantages and disadvantages of each.

    Creating a Theme

    Advantages

    1. Allows users to easily select the theme in a familiar interface regardless if they are on a site with the Publishing Infrastructure enabled (such as the out of the box Collaboration Portal) or not enabled (such as a team site)
    2. Can quickly and easily change themes if a user requires.
    3. Can use the Alternate CSS URL for any quick fixes if need be.

    Disadvantages

    1. Added programming effort of creating a theme,(have to create an XML file and requires an IIS Reset)
    2. Themes are NOT automatically propagated to sub sites when a new sub site is created. So if I have a Site Collection with a number of sites that already have my theme applied any new site will NOT have that theme automatically applied, a user will have to configure it themselves.

    Specifying an Alternate CSS URL

    Advantages

    1. All sub sites created will inherit the Alternate CSS URL, hence they will have the CSS applied automatically. This is in direct contrast to the theme which will have to be configured.
    2. Users can easily change the .css file through SPD or the front end of SharePoint and see these changes propagated.

    Disadvantages

    1. In sites without the Publishing Infrastructure enabled there is no way through the SharePoint interface to specify an alternate CSS URL so for things such as Team Sites you have to enable the Publishing Infrastructure feature to allow users to do this from the user interface. Of course this creates a lot of overhead and document libraries which you don’t necessarily want.

    Relative CSS

    Advantages

    1. In order to change the CSS a user can simply change the CSS on the document library where it is stored.

    Disadvantages

    1. Real pain to have all these references in Master Pages and then in Page Layouts. Could be a real mess when you try to trace the css to see what is going on.
    2. Cannot easily change the CSS file or add a new CSS file unless you redo every single Master Page or Page Layout that the link resides on…this could be time consuming and undoubtably will lead to errors.

    Some tips!

    In my mind branding should always be implemented in themes. For starters a user can quickly and easily change the theme if the want to..especially in team sites. By having an alternatve CSS specified you force your team site users, which will far outnumber publishing sites, to place extra overhead simply to specify a CSS file.

    So thats my opinion but I am sure that it will differ from people but hopefully this has outlined some of the issues that you could face.

    2 Comments

    Technical Preview Information for SharePoint 2010

    Microsoft SharePoint 2010 team has released a download for SharePoint 2010 developer documentation which contains white papers and help files.

    To review your copy, Please download zip file from Microsoft.com

    http://www.microsoft.com/downloads/details.aspx?FamilyID=94afe886-3b20-4bc9-9a0d-acd8cd232c24&displaylang=en

    Also there is the Microsoft Technologies Product and Technologies Protocol Documentation:

    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5e94ad07-902c-422f-aadd-ff2bba9e540a

    And finally the Sneak Peak which contains videos and other stuff that is guaranteed to get the mouth watering:

    http://sharepoint.microsoft.com/2010/Sneak_Peek/Pages/default.aspx

    No Comments

    When to use look up columns instead of the choice column in SharePoint

    This post has moved to my new blog located at: http://www.sharepointanalysthq.com/2010/06/06/sharepoint-2007-when-to-use-look-up-columns-instead-of-the-choice-column-in-sharepoint/

    Enjoy!

    6 Comments

    Listing of all default placeholders on master pages

    I had an issue with a Master Page that I developed. The Master Page worked fine but when an Wiki was used they couldn’t see the Edit Button for the page, as detailed below.

    Edit Wiki Button

    Edit Wiki Button

    Turns out that since we were using a custom master page, in order for the thing to work we do what a lot of people do, that is create the Master Page with all the placeholders but then put a whole bunch into a hidden panel to not mess up the HTML.

    Well of course this works in the majority of cases but for a wiki, which needs the PlaceHolderMiniConsole control, it wasn’t the best.

    Then I came to this fantastic post by Tom from SharePointForEndUsers.com that has a great listing and pictures of all the default placeholders. Its also one of the better SharePoint blog sites out there having a whole range of great content.

    No Comments

    Removing the Restricted Readers Group

    Just a tip. I’m always a fan of removing the seemingly number of strange and superfluous groups in an standard SharePoint installation. One caveat with this is that if you remove the “Restricted Readers” group all users that are  NOT Site Collection administrators that have the ability to create pages will see the create page button under site action but then get an Unknown Error.

    The cryptic reason is that the Restricted Readers group includes everyone and this group has access to the Master Page gallery which allows users to view Master Pages. When you remove the group for some reason (and if anyone has the definitive answer please tell me) user can still view Master Pages but when they go to createPage.aspx

    So be careful and when this happens check that your users have access to the Master Page gallery.

    No Comments

    Things to remember when branding SharePoint

    I’m really new to branding SharePoint, my artistic skills being comparable to that of a ferret with a paintbrush, but I have had to do some tweaking of branding that have caused me some pain.

    Firstly let me say that I think that the world of SharePoint branding would be in dire straits (not the band) if it wasn’t for Heather Solomon and her blog located here.

    She has some fantastic items in the blog, the most frequently of which I use is the CSS Reference Chart for SharePoint 2007 (Microsoft Office SharePoint Server 2007 and Windows SharePoint Services v3) which details the CSS reference for all those pesky things that you want to branding in SharePoint and WSS.

    So for some tips, I’m going to add to this as we go along and if anyone has any suggestions then please let me know and I can add them here as well!

    Branding Tools

    • SharePoint Designer: Used to edit CSS, Master Pages and add images
    • IE Developer ToolBar: Indispensable tool to work out what the hell is going on when a page is rendered. Comes out of the box with IE 8 and some added features.
    • FireBug: Once again this another tool to view CSS but I really think that the features of FireBug are a lot better than that of IE Dev Toolbar. For instance the “View Style Information” feature:
    • firebug-style-information
      and also the “HTML View
      firebug-html-view

    Collaboration Site Branding

    • Collaboration Sites cannot have their Master Page changed out of the box, the only changes that can be made are CSS changes through themes.
    • If you do want Collaboration sites to have branding features  such as custom master pages then you must enable the “Office SharePoint Server Publishing Infrastructure” feature to be able to change the Master page.

    Publishing Site Branding

    • Try to use page layouts and publishing fields as much as possible.  Andrew OConnell gives the definitive explanation here
    • If a Page Layout is not checked in that the default.aspx page is based on, published and approved as a major version then the user will see the link to the site in the menu (if applicable), can visit all of the other content in the site but will get a “File Not Found” error, which is useless for all intensive purposes.

    Internet Branding

    • Be prepared for some real fun when testing on other browsers apart from IE!!!

    Branding Tips

    • Anything in the /_layouts pages is not branded using the Site or System master pages but in another Master page that resides on the file system called “Application.Master“. Now you can in theory change this but like always you should never touch any file directly in the [12] Hive. You can achieve a certain amount of customization with CSS only but usually most organizations don’t even bother have any branding on these pages.
    • If only one placeholder is missing from a Master Page you will get an error that will be difficult to track down unless you have debugging turned on for the Web Application.
    • The navigation does not persist across site collections. Be careful how you structure your sites otherwise you will need to write your own Navigation Provider, although MOSS comes with quite a few (listed here in Shantha Kumar’s blog, or create you own ASP.NET menu which you can also do.

    Economics of Branding

    • Branding  is finicky, time consuming and costs money. For smaller SharePoint products branding can really drive up the cost of the total implementation. Some more cost effective branding can be achieved by the following:
      • Don’t use custom master pages but create a theme or CSS file instead.
      • Always change the logo of the client by changing the site logo. There are a number of ways to do this (change the Master, change the logo in the database..ouch) or the easiest is simply to “Title, Description and Icon” page in Site Settings->Title, Description and Icon and point to a new logo that you have uploaded to the [12] hive.site-logo-change
      • Try to get the client to focus on functionality instead.
      • Make sure that you tell the client that branding SharePoint takes much, much longer than branding other Internet Platforms whose main purpose is static content.
      • If you are using a branding company you have to be very clear and specific, with both them and the client, what is possible out of the box and what is needed from the branding company. Many times an outside graphic design company comes up with an amazing Intranet design which will have to be tweaked because the cost in implementing it is too much. If money was no object we could do this, but in these times….

    No Comments