Hi Nick

Could you double check that the search-node in your content tree has a template selcted?

/Kim A

Hi Kim,

I have made sure that correct template was selected all the way though (and republished the entire site just to be certain) and the issues is still there. What is the best way to debug these sort of things?

Thanks,

Nick Goloborodko @ Xorbit

Hi Nick,

Have you tried doing this in your Search Template ?

<form method="get" action="search.aspx?">
         <umbraco:Macro source="-1" searchFields="@nodeName,bodyText,metaDescription" previewFields=" " searchBoxLocation="None" previewType="Beginning" resultsPerPage="5" previewChars="225" showPageRange="1" showOrdinals="1" showScores="0" showStats="0" Alias="XSLTsearch" runat="server"></umbraco:Macro>
</form>

It works for me under Umbraco V 4.7

//fuji

Hi again Nick

Can you check the umbraco.config-file, to make sure that the node is actually written to the XML? Try opening up the file, and search for "search" to check if it's there.

Does this only happen on the search.aspx or does it occour on other nodes as well?

/Kim A

Hi Kim,

I have this entry in the umbraco.config file:

<XSLTsearch id="1266" parentID="1252" level="2" writerID="0" creatorID="0" nodeType="1262" template="1265" sortOrder="4" createDate="2011-05-13T02:39:53" updateDate="2011-05-13T02:53:03" nodeName="Search" urlName="search" writerName="Nick Goloborodko" creatorName="Nick Goloborodko" path="-1,1252,1266" isDoc="">

      <umbracoNaviHide>1</umbracoNaviHide>

    </XSLTsearch>

All of the other pages work fine... it's just the search (which I've installed from Umbraco packages repository - v3.0.1 I believe)

I'll check to see if all of the files have appropriate permissions (I'm currently assuming they do - since umbraco installed them it self)

Once again, thank you very much for trying to help me - I really appreciate it!

Nick Goloborodko @ Xorbit 

I've finally figured this out - I've made a bit of a mess with content place tags in the template. It is a bit unfortinate that this mistake gives such an ambigous error message.

Thanks again for all of your help!

Nick Goloborodko @ Xorbit 

Hmm.. sounds weird. Could you show us the code that caused it to fail? Could be interesting to see what happened for further reference.

/Kim A

So the code below was in a template that was used for the search page. (Note the nester asp:content tags...) I removed the top-level asp:content tag and the page started working as expected.

<%@ Master Language="C#" MasterPageFile="~/masterpages/Page.master" AutoEventWireup="true" %>
<asp:content ContentPlaceHolderId="mainContentPlaceHolder" runat="server>

<asp:content ContentPlaceHolderId="scriptsContent" runat="server">
  <link href="/css/colorbox.css" rel="stylesheet" type="text/css" media="screen" />
</asp:content>

<asp:content ContentPlaceHolderId="pageContent" runat="server">
  <!-- BEGIN OF CONTENT -->
        <div id="content">
          <div class="maincontent">
              
                <!-- begin of content fullwidth -->
              <div id="content-fullwidth">

                   
    <umbraco:Macro runat="server" Alias="XSLTsearch"
      macroAlias="XSLTsearch"
      source="-1"
      searchFields="@nodeName,metaKeywords,metaDescription,bodyText"
      previewFields="bodyText,metaDescription"
      previewType="beginning"
      searchBoxLocation="bottom"
      resultsPerPage="5"
      previewChars="255"
      showPageRange="0"
      showOrdinals="0"
      showScores="0"
      showStats="1">
    </umbraco:Macro>  
                </div>
                <!-- end of content fullwidth -->         
                
            </div>
        </div>        
        <!-- END OF CONTENT -->
</asp:content>
</asp:content>

Hi Nick

Thanks for sharing this. It's a classic when something goes wrong and sometimes one can stare himself blind on something like this - good to hear you got it all solved.

/Jan

Cool that you shared this Nick. But I still think it's weird that this gives a 404 instead og a YSOD. But well, glad you got your problem solved :)

/Kim A

is working on a reply...