Search

Englando's Blog

SharePoint and more!

SharePoint 2010 Users Unable to Edit Page Content and Add Web Parts

Ok, so found a strange “feature” with SharePoint 2010.

The scenario goes like this:

You have a new Intranet, setup your Intranet Owners (who have full control from Site Collection Level down) and created some new SharePoint groups for content managers.

You then give the Content Managers groups Read Access to the top site collection and the Design permission level to the relevant pages (or folder in the Pages library) that you want them to be able to edit.  (incidentally, a major change from SharePoint 2007 here – you can now only have ONE Pages library in a publishing site).

You then find the users in those groups cannot actually edit their page content or add web parts.

What you need to do is create a new Permission Level at the top site collection, that only has “Add and Customise Pages” (plus the other required permissions that get added when you enable that one).

Then give the Content Managers groups this Permission Level to the Top Site Collection.  You can also restrict their permissions to the pages you do not want them to access in the Pages library.

Advertisements

People Matches not Showing on FAST SharePoint 2010 Search Page

So, if you have ever thought you did not need certain profile properties in SharePoint 2010 and decided to delete them you may find that some things no longer work as expected.

The properties you SHOULD NOT delete all have internal names starting with “SPS-“.  So if you deleted SPS-Location for instance, you may find your People Matches web part on the search results page no longer works.  You will also find the Profile pages no longer load.

There is a way to rectify this though and you need to start by following a post at this link which details how to recreate SPS-Location.  If that link no longer exists then the details are bulleted below:

  • Create a new Property with name like “SPSLocation” (leafe the ‘-‘ after ‘SPS’). In this way the propertyname will be accepted. Now just start your SQL-Server Management Studio, select and edit the appropriate record in you profile database. In my case I used the following SQL:
  • Using this SQL to select the appropriate record (Ensure that you only get 1 result-line!!!): SELECT * FROM PropertyList WHERE PropertyName=’SPSLocation’;
  • Using this SQL to edit the appropriate record: UPDATE PropertyList SET PropertyName=’SPS-Location’ WHERE PropertyName=’SPSLocation’;

Now you will still find People Matches does not work, until you add a metadata property and perform a full crawl…

Go to Central Admin, Application Management, Manage Service Applications.

Click on your FAST search query service.

Click on Metadata Properties from the left hand side

Click New Managed Property

Enter BaseOfficeLocation as the Property Name

Add a new mapping to People:SPS-Location(Text)

Leave everything else as is and click OK

Now edit ContentsHidden and add the same mapping

Start a full crawl

when the crawl has finished you should now see People Matches working as it should be.

Note to self – disable propeties, do not delete them!

SharePoint 2010 Tag Cloud Font Size Problem

Are you finding that when you use the out of the box tag cloud to show tags for all users there is no variation in font size between the various keywords?

I have found the solution to this.  There is a CSS stle sheet for social data which is what the My Site uses when displaying tags there.  The thing that is stopping these styles from being used within the main SharePoint site collection is either your theme css if you are using one out of the box, or the style sheet within the style library.  If you use the default SharePoint theme this will be nightandday.css.

The styles being used within those CSSs will be something like:

.ms-TagCloud
{
 padding: 0;
}
.ms-TagCloud a:active
{
 font-size: 11pt;
 text-decoration: none;
}
.ms-TagCloud a:visited
{
 font-size: 11pt;
 text-decoration: none;
}
.ms-TagCloud a:link
{
 font-size: 11pt;
 text-decoration: none;
}
.ms-TagCloud a
{
 font-size: 11pt;
 text-decoration: none;
}
.ms-TagCloud a:hover{
 text-decoration: none;
}

So the way I solved this was simply to remove any reference to the TagCloud in the out of the box CSSs that I am using.  Now my Tag Cloud web part shows the variation in font sizes wherever I place it in the site collection.

“fpdatasources” Missing in SharePoint Designer 2007?

If you cannot see the fpdatasources folder in SharePoint Designer 2007 and are sure you have Site Collection/Owner permissions then perform this step …

Go to “Data View” on the SharePoint Designer 2007 menu and then click on “Manage Data Sources”

Now expand “_catalogs” in SharePoint Designer 2007 and you should see fpdatasources. 

I needed to change the permissions on this folder so that everyone had read access (as a standard contribute level user could not access the site without elevating their permissions to approver level).  If you are unsure how to change permissions on fpdatasources then right click on it and select “Properties”.

Then click on the “Security” tab then click on the link “Manage permissions using the browser”.  Add the relevant groups that require read access and then save.

Script to Install SharePoint 2010 on Windows 7

In order to do some development work using Visual Studio you can install Visual Studio on a development server with SharePoint installed.   However, there is an alternative method which is to install SharePoint and Visual Studio locally on Windows 7!

so I have just installed SharePoint 2010 on my Macbook Pro (running Windows 7) using a PowerShell script at the following link …

Script to Install SharePoint 2010 on Windows 7.

Couple of things to note …

If you are using the ISO version of the SharePoint files then you will not need to extract the files from OfficeSetup.exe so this line within function ExtractSP2010SetupExe can be changed.  I changed it to setup.exe.

You will need to set up IIS in Windows 7 prior to configuration of SharePoint, so you can follow step 9 from here for the correct settings: http://msdn.microsoft.com/en-us/library/ee554869.aspx

I also downloaded the prerequisites prior to installation as I did not have internet access on my Macbook at the time.  You can use the links from the script (then delete the download links from the script before running it):

I received an error when trying to run the “SharePoint 2010 Products Configuration Wizard” – “Failed to create the configuration database”, and the problem was to do with the Microsoft Identity Model.  You will need to download the latest version (Windows Identity Foundation) from microsoft here: http://msdn.microsoft.com/en-us/evalcenter/dd440951

If you installed the Geneva version of WIF then you will need to uninstall it and reboot prior to installing the latest version.

I restarted the Macbook and ran the wizard again which went through no problem.  SharePoint is now installed and running very well.

Project Server 2010 Navigation Bug

I have found a bug in Project Server 2010 that will automatically show all subsites on the left hand navigation when you manually enter a link or heading in the Navigation settings for the server.

How to replicate:

  1. Go to Project Server 2010 home page
  2. Go to Site Actions
  3. Go to Site Settings
  4. Go To Navigation
  5. Under Current Navigation ensure there is no tick in Show subsites
  6. Click OK
  7. Go to Site Actions
  8. Click on New Site
  9. Select Microsoft Project Site
  10. Enter the new sites details and complete
  11. Go back to Project Server 2010 home
  12. NB: The new site should not appear in the Quick Links on the left hand side
  13. Go to Site Actions
  14. Go to Site Settings
  15. Go to Navigation
  16. Under Navigation Editing and Sorting click on Current Navigation
  17. Click on Add Link
  18. Enter details for any link and click OK
  19. Click OK to save the navigation
  20. You should now see the new link on the Quick Links as well as the existing site you created earlier.  This should not happen.

I have replicated this issue on a vanilla VM as well as our production server.  I have also tried the December SharePoint cumulative updates but I get the same issue.

I have raised a support call with Microsoft and will update this blog post in due course.

UPDATE:

Apparently this is normal behaviour as Project Server works differently to how you might think it should based on the mindset of how SharePoint works.  However, instead of modifying the navigation in the normal SharePoint manner you need to use the “Quick Launch” setting in “Server Settings”.  To stop subsites from showing remove the tick from

TIP: Change Sort Order in People Matches SharePoint 2010 Web Part

The People Matches web part in SharePoint 2010 defaults to a sort order that you may not find intuitive.  So in order to change it to something more user friendly you will need to edit the web part and modify the XSL.

  • Edit the People Matches web part
  • Expand Display Properties
  • Click on the XSL Editor button
  • I would recommend you select all of the text and paste into Notepad etc as a backup
  • Locate the section that starts <xsl:template match=”/”>
  • Below the line that reads <xsl:for-each select=”$results”> add the following line … <xsl:sort data-type=”text” order=”ascending” select=”preferredname”/>
  • You can change the sort field (preferredname) for another should you so desire – dont forget to change the data type if the field you choose is not text
  • Save the XSL and apply the changes
  • When you now do a search and see the results page that includes the People Matches web part you should see people showing in the order you have set

Hope this helps some people out.

Want More Details in SharePoint 2010 “People Matches” Web Part?

The People Matches web part on search results pages can be very effective, however the default setting is to show only the persons name, job title and department.

What if you want more information in there such as the phone number so people that perform a search for someone in the organisation can see at a glance what number to phone for that particular person.

So to add the phone number you need to first edit the search results page (typically located as Results.aspx within Search Centre), then edit the People Matches web part.

Untick the box for “Use Location Visualization”.

Now click on the XSL Editor.

Add a new variable name …

<xsl:variable name=”haswp”        select=”string-length(workphone) &gt; 0″/>

Then add the following code at the end of the “ContactInfo” section:

      <xsl:if test="$haswp">
        <li id="WorkPhoneField">
          <xsl:apply-templates select="hithighlightedproperties/workphone" />
        </li>
      </xsl:if>

So that the “CoontactInfo” section looks like this:

  <div id="ContactInfo">
    <ul id="MiniContactCard">
      <li id="NameField">
        <xsl:if test="$haspn">
          <a href="{ddwrt:EnsureAllowedProtocol(string($url))}" id="{concat($currentId, '_CSR')}">
            <xsl:apply-templates select="hithighlightedproperties/preferredname" />
          </a>
        </xsl:if>
      </li>
      <xsl:if test="$hasydn">
        <li id="YomiField">
          <xsl:apply-templates select="hithighlightedproperties/yomidisplayname" />
        </li>
      </xsl:if>
      <xsl:if test="$hasjt">
        <li id="JobTitleField">
          <xsl:apply-templates select="hithighlightedproperties/jobtitle" />
        </li>
      </xsl:if>
      <xsl:if test="$hasdp">
        <li id="DepartmentField">
          <xsl:apply-templates select="hithighlightedproperties/department" />
        </li>
      </xsl:if>
      <xsl:if test="$haswp">
        <li id="WorkPhoneField">
          <xsl:apply-templates select="hithighlightedproperties/workphone" />
        </li>
      </xsl:if>
    </ul>   
  </div> 
 
Save and publish the page and the work phone details should appear when you perform a new search for someone in the organisation.

To add any other user profile data it should be a simple case of making up a variable as above and copying (and changing) the new part of the ContactInfo section with the correct name for the field in the user profile.



Project Server 2010 RAG Indicator Does not Show in Browser

Found another glitch with Project Server 2010.  Graphical Indicators are not showing in the Project Web App (2010).

If you add an Enterprise Column to Project Server 2010 that is calculated to show different icons depending on values etc then add the new column to a tasks view such as Tasks Summary, and then publish your project via the Web App the indicator will not show.

In order for the indicator to show you need to publish the project from Project Professional 2010.  If you then subsequently re-publish via Project Web App the indicator will dissapear.

The only way to get indicators to show in Project Web App is to publish the project from Project Professional 2010.

Blog at WordPress.com.

Up ↑