I have been trying to get the default Search box in Umbraco back end to work. It is currently complaining that there is no search index. However I am not sure how do you reindex the Lucene index file. I have tried the following url "http://<my-website>/umbraco/reindex.aspx" but i think it is obsolete and it throws me the following error
Server Error in '/' Application.
Parser Error
Description:An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message:Could not load type 'umbraco.cms.presentation.reindex'.
Source Error:
Line 1: <%@ Page language="c#" Codebehind="republish.aspx.cs" AutoEventWireup="True" Inherits="umbraco.cms.presentation.reindex" %> Line 2: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > Line 3: <HTML>
Source File:/umbraco/reindex.aspx Line:1
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
Could someone please point out how I can reindex the file?
Lucene Reindexer for Umbraco 4.1 RC
Hi,
I have been trying to get the default Search box in Umbraco back end to work. It is currently complaining that there is no search index. However I am not sure how do you reindex the Lucene index file. I have tried the following url "http://<my-website>/umbraco/reindex.aspx" but i think it is obsolete and it throws me the following error
Server Error in '/' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'umbraco.cms.presentation.reindex'.
Source Error:
Source File: /umbraco/reindex.aspx Line: 1
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
Could someone please point out how I can reindex the file?
Thanks,
Steven
Does anyone knows?
Hi, I'm facing the same problem. Did you resolve it?
is working on a reply...