In the 4.0 versions you need to manually add the extensions to the /config/xsltextensions.config file I believe.

cheers,
doug. 

I already added the extension there. It works in normal XSLT files, but not in this XSLT file which is in the Umbraco backoffice. Also tried Umbraco XSLT extensions and those also don't work.

Jeroen

Ahhh... sorry, missed that. Those are different and not handled the same way. You might need to put the code in your xslt file directly, but someone who is better with the source of the back office might know better.

Here's how to do it: http://blog.percipientstudios.com/2009/9/21/advanced-xslt-with-net-namespaces.aspx. Read the comments too about debug mode.

cheers,
doug. 

I'm now trying in-line C# like you mentioned in your blog, but it gives me this error:

Error creating control 
System.Xml.Xsl.XsltCompileException: XSLT compile error at C:\SVN\PrismaIntranet\trunk\site\umbraco\xslt\searchResult.xslt(30,58). See InnerException for details. ---> System.Xml.Xsl.XsltException: The 'msxsl:script' element cannot be empty. at System.Xml.Xsl.XsltOld.ContainerAction.AddScript(Compiler compiler) at System.Xml.Xsl.XsltOld.ContainerAction.CompileTopLevelElements(Compiler compiler) at System.Xml.Xsl.XsltOld.ContainerAction.CompileDocument(Compiler compiler, Boolean inInclude) at System.Xml.Xsl.XsltOld.RootAction.Compile(Compiler compiler) at System.Xml.Xsl.XsltOld.Compiler.CreateRootAction() at System.Xml.Xsl.XsltOld.Compiler.Compile(NavigatorInput input, XmlResolver xmlResolver, Evidence evidence) --- End of inner exception stack trace --- at System.Xml.Xsl.XsltOld.Compiler.Compile(NavigatorInput input, XmlResolver xmlResolver, Evidence evidence) at System.Xml.Xsl.XslTransform.Compile(XPathNavigator stylesheet, XmlResolver resolver, Evidence evidence) at System.Xml.Xsl.XslTransform.Load(XPathNavigator stylesheet, XmlResolver resolver) at System.Xml.Xsl.XslTransform.Load(IXPathNavigable stylesheet, XmlResolver resolver) at System.Xml.Xsl.XslTransform.Load(XmlReader stylesheet) at System.Web.UI.WebControls.Xml.LoadTransformFromSource() at System.Web.UI.WebControls.Xml.Render(HtmlTextWriter output) at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) at System.Web.UI.Control.RenderControl(HtmlTextWriter writer) at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) at umbraco.uicontrols.Pane.Render(HtmlTextWriter writer) in d:\TeamCity\buildAgent\work\7380c184e9fcd3ea\components\umbraco.controls\pane.cs:line 99

The element is not empty. If I remove the complete msxsl:script part it doesn't give an error.

Jeroen

I wonder if it just isn't possible in the back office context? I've never tried it but it sure seems it ought to work.

Can you post a trimmed down version of your searchResult.xslt file? Perhaps a second set of eyes might spot something.

cheers,
doug. 

The xslt in my first post is the complete search result file. Here is how the file is loaded in the Umbraco backoffice:

search.aspx

<%@ Page Language="C#" MasterPageFile="../masterpages/umbracoDialog.Master" AutoEventWireup="true"
    CodeBehind="search.aspx.cs" Inherits="umbraco.presentation.dialogs.search" %>

<%@ Register TagPrefix="cc1" Namespace="umbraco.uicontrols" Assembly="controls" %>
<asp:Content ID="header1" ContentPlaceHolderID="head" runat="server">
<script type="text/javascript">
    function openItem(url) {
        parent.right.document.location.href = "../" + url;
        parent.closeModal();
    }
</script>
</asp:Content>
<asp:Content ID="Content1" ContentPlaceHolderID="body" runat="server">
    <cc1:Pane ID="Wizard" runat="server">
        <h3>Search</h3>
        <p>
        <asp:TextBox ID="keyword" runat="server" Width="500" CssClass="bigInput"></asp:TextBox> 
            <asp:Button ID="searchButton" runat="server" Text="Search" onclick="search_Click" /><br />
        </p>
        <asp:Xml ID="searchResult" runat="server" TransformSource="../xslt/searchResult.xslt"></asp:Xml>
    </cc1:Pane>
</asp:Content>
<asp:Content ID="footer1" ContentPlaceHolderID="footer" runat="server">
<script type="text/javascript">
    document.getElementById("ctl00_body_keyword").focus();
</script>
</asp:Content>

using System;
using System.Collections.Generic;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

using umbraco.cms.businesslogic.index;

namespace umbraco.presentation.dialogs
{
    public partial class search : BasePages.UmbracoEnsuredPage
    {
        protected void Page_Load(object sender, EventArgs e)
        {
            this.Page.Form.DefaultButton = this.searchButton.UniqueID;

            if (!IsPostBack && helper.Request("search") != "")
            {
                keyword.Text = helper.Request("search");
                doSearch();

            }
        }

        protected void search_Click(object sender, EventArgs e)
        {
            doSearch();


        }

        private void doSearch()
        {
            string query = keyword.Text;
            query = query.Trim();

            // Check for fulltext or title search
            string prefix = "";
            /*            if (query.Length > 0 && query.Substring(0, 1) != "*")
                            prefix = "Text:";
                        else
                            query = query.Substring(1, query.Length - 1);
                        */

            // Check for spaces
            if (query.IndexOf("\"") == -1 && query.Trim().IndexOf(" ") > 0)
            {
                string[] queries = query.Split(" ".ToCharArray());
                query = "";
                for (int i = 0; i < queries.Length; i++)
                    query += prefix + queries[i] + "* AND ";
                query = query.Substring(0, query.Length - 5);
            }
            else
                query = prefix + query + "*";

            searchResult.XPathNavigator = cms.businesslogic.index.searcher.SearchAsXml(
cms.businesslogic.web.Document._objectType, query, 100).CreateNavigator();

        }
    }
}

Hmm that would cause all these issues :p. Haven't looked at a way to register extensions yet, but if it's possible I'm afraid that I'll need to change something in the Umbraco source and that's what I've been trying to avoid here. If I need to change the Umbraco source anyways there are easier ways to extend the search results page.

Jeroen

*cough* You could use XSLTsearch *cough*

Now I'm using Simple Search for Umbraco. It replaces searching in the Umbraco backoffice and I modified it to show the extra info I needed. This way I still didn't need to modify the Umbraco source.

Jeroen

is working on a reply...