Sharepoint ItemStyle.xsl for CQWP using images from a content type

cqwpsharepointxslt

I'm building a custom Content Query Web Part to display rollup information from an employee content type. This content type has a Publishing Image site column called EmpPhoto. My CQWP is working great and all the site columns I need are available.

I am now creating a custom xsl template to render the information correctly but am stuck using the EmpPhoto image.

If I use the code:

<xsl:value-of select="@EmpPhoto" disable-output-escaping="yes" />

… I get a correctly rendered image which is great. However I want to build an onmouseover event for this image and this approach will not work.

I thought to create an xsl variable to grab the actual image URL then build my own html img and write the onmouseover into that e.g.

<xsl:variable name="EmpPhotoUrl">
    <xsl:call-template name="OuterTemplate.GetSafeStaticUrl">
        <xsl:with-param name="UrlColumnName" select="@EmpPhoto"/>
    </xsl:call-template>
</xsl:variable>

…

<img src="{$EmpPhotoUrl}" onmouseover="" alt="test" />

This doesn't get the URL from the EmpPhoto site column however. I am new to xsl so I might well be missing an obvious solution!

Any help much appreciated,

Jonny

Best Answer

This is cheating... and it's making assumptions about the src attribute. But here it is!

<xsl:variable name="EmpPhotoUrl" select="substring-before(substring-after(@EmpPhoto, 'src=&quot;'), '&quot;')" />

Related Solutions

R – SharePoint Form Library: Programmatically or Stsadm command to change content type to custom form template

Here is some code I have used to do set the content types for a list.

 void AddContentTypes(SPWeb web)
    {
        //get a reference to content types previously installed
        SPContentType CompanyAContentPage = web.AvailableContentTypes["CompanyA Content Page"];
        SPContentType CompanyAWelcomePage = web.AvailableContentTypes["CompanyA Welcome Page"];

        //get list to mess with
        SPList spList = web.Lists["Pages"];

        //enable management of content types
        spList.ContentTypesEnabled = true;

        //get the content types added to the list (different from the web ones)
        SPContentType newCompanyAPageContentType = spList.ContentTypes.Add(CompanyAContentPage);
        SPContentType newCompanyAWelcomePageContentType = spList.ContentTypes.Add(CompanyAWelcomePage);
        //update list
        spList.Update();

        //get a list of content types for the "new" drop down on the list
        List<SPContentType> contentTypeList = new List<SPContentType>();
        contentTypeList.Add(newCompanyAPageContentType);
        contentTypeList.Add(newCompanyAWelcomePageContentType);

        //set the content types for the "new" drop down list
        spList.RootFolder.UniqueContentTypeOrder = contentTypeList;
        spList.RootFolder.Update();
    }

Not exactly the same as your problem, but I hope it helps.

XSLT – Adding Elements dynamically

What would happen if more job roles, other than Dev and QA got added? Would your stylesheet be able to cope? Maybe you can make use of Muenchian Grouping to get all possible roles in the stylesheet, and then generate columns for each possible role dynamically?

<xsl:key name="roles" match="role" use="."/>

<xsl:template match="/projectteam">
 <table border="1">
  <tr>
   <td>Name</td>
   <td>Role</td>
   <xsl:for-each select="member[generate-id(role) = generate-id(key('roles', role)[1])]">
    <td>
     <xsl:value-of select="role"/>
    </td>
   </xsl:for-each>
  </tr>
  <xsl:apply-templates select="member"/>
 </table>
</xsl:template>

<xsl:template match="member">
 <xsl:variable name="currentrole" select="role"/>
 <xsl:variable name="currenthrs" select="hrs"/>
 <tr>
  <td>
   <xsl:value-of select="name"/>
  </td>
  <td>
   <xsl:value-of select="role"/>
  </td>
  <xsl:for-each select="/projectteam/member[generate-id(role) = generate-id(key('roles', role)[1])]">
   <td>
    <xsl:choose>
     <xsl:when test="$currentrole = role">
      <xsl:value-of select="$currenthrs"/>
     </xsl:when>
    </xsl:choose>
   </td>
  </xsl:for-each>
 </tr>
</xsl:template>

I've outputted as HTML, not XSL-FO, but maybe this gives you the general idea.

Related Topic