As far as I know, it's not possible — but take a look at the ezSearch package which was created as kind of a replacement, using Razor etc. I'm almost certain that it'll be possible with that.
There's not a lot of use in searching unpublished content... what would be gained by showing it in search results? If an unpublished result were clicked by a website visitor it wouldn't go anywhere.
Having said that, XSLTsearch will only search within published content and there's no way to change that behaviour. ezSearch (definitely recommended these days instead of XSLTsearch because it's even faster than XSLTsearch and is built with Razor that people find easier to modify) uses the Examine/Lucene indexes and thus it would be possible to get to unpublished content if you have a reason to do so, but you'd have to modify the code slightly to do that.
Tnx, the need for searching in unpublished content is due to a unique identifier (a custom property) located on each subsite in our solution (we have 500+ subsites in the nodetree), and some of these await approval and such, and are therefore not published, but still it would be a good feature for the contenteditor to locate unpublished content via search and the unique identifier, due to the big amount of subsites/data, and not browsing through all nodes to find the needed subsite.
And again tnx for ezSearch, never a big fan of XSLT, so I will def. dig into that.
You know you can search from within the Umbraco backoffice, right? That will search within unpublished content so maybe that's the solution for the content editors to find pages without having to scroll through the node tree?
Yup, but for some DARN reason, the quicksearch and the ashx service behind it will not serve content with our unique identifier.
We have 2 types of identifiers (Both available in the lucene index, I checked with "Luke" :-) ) : one which is a straight forward integer, this is searchable with the wildcard search, f.i : "*102420". But the second identifier is often prefixed with 1 - many chars and will NOT appear in the quick search or search.aspx, f.i "DK10240", even though it IS available in the Lucene index.
So due to a nearby (as in due) deadline, I had to find a plugin that quickly could solve our problem.
Possible to search for unpublished content?
Hey,
Is it possible in some way to force xsltsearch to search in unpublished content?
/Stef
Hi Stef,
As far as I know, it's not possible — but take a look at the ezSearch package which was created as kind of a replacement, using Razor etc. I'm almost certain that it'll be possible with that.
/Chriztian
Awesome, tnx Chriztian, will take a peek.
/Stef
Hi, Stef,
There's not a lot of use in searching unpublished content... what would be gained by showing it in search results? If an unpublished result were clicked by a website visitor it wouldn't go anywhere.
Having said that, XSLTsearch will only search within published content and there's no way to change that behaviour. ezSearch (definitely recommended these days instead of XSLTsearch because it's even faster than XSLTsearch and is built with Razor that people find easier to modify) uses the Examine/Lucene indexes and thus it would be possible to get to unpublished content if you have a reason to do so, but you'd have to modify the code slightly to do that.
cheers,
doug.
Hi Douglas,
Tnx, the need for searching in unpublished content is due to a unique identifier (a custom property) located on each subsite in our solution (we have 500+ subsites in the nodetree), and some of these await approval and such, and are therefore not published, but still it would be a good feature for the contenteditor to locate unpublished content via search and the unique identifier, due to the big amount of subsites/data, and not browsing through all nodes to find the needed subsite.
And again tnx for ezSearch, never a big fan of XSLT, so I will def. dig into that.
cheers,
Stef
You know you can search from within the Umbraco backoffice, right? That will search within unpublished content so maybe that's the solution for the content editors to find pages without having to scroll through the node tree?
Just an idea.
cheers,
doug.
Yup, but for some DARN reason, the quicksearch and the ashx service behind it will not serve content with our unique identifier.
We have 2 types of identifiers (Both available in the lucene index, I checked with "Luke" :-) ) : one which is a straight forward integer, this is searchable with the wildcard search, f.i : "*102420". But the second identifier is often prefixed with 1 - many chars and will NOT appear in the quick search or search.aspx, f.i "DK10240", even though it IS available in the Lucene index.
So due to a nearby (as in due) deadline, I had to find a plugin that quickly could solve our problem.
is working on a reply...