I've encountered an issue with protecting pages and results being displayed.
Search was working perfectly fine, with no roles based protection on the site, once I added it things started going a little strange. I have active directory sign on working, it is allowing me to view all the pages, as I have full access, but when I search from any page it won't find anything.
On the local development copy I removed the role based protection, rebuild indexes and republished the site, it worked again. Reapplied the roles based protection and it kept working still.
I'm not sure what is the correct process to use, if there is one, so any advice / help much appreciated.
We gave the site and the AppPool a stop and start to make sure changes kicked in (may not be needed), rebuilt the ExternalIndexer from the Examine Management tab in the Developer section and the Indexer picked up all our protected nodes. ezSearch then was able to return results as expected.
ezSearch and protected pages issues
Hi all,
I've encountered an issue with protecting pages and results being displayed.
Search was working perfectly fine, with no roles based protection on the site, once I added it things started going a little strange. I have active directory sign on working, it is allowing me to view all the pages, as I have full access, but when I search from any page it won't find anything.
On the local development copy I removed the role based protection, rebuild indexes and republished the site, it worked again. Reapplied the roles based protection and it kept working still.
I'm not sure what is the correct process to use, if there is one, so any advice / help much appreciated.
Ian
Hi Ian,
We're building an intranet and faced the same issue.
The solution is to allow the ExternalIndexer, on which ezSearch relies, to index protected nodes.
In your \Config\ExamineSettings.config change this:
to this:
We gave the site and the AppPool a stop and start to make sure changes kicked in (may not be needed), rebuilt the ExternalIndexer from the Examine Management tab in the Developer section and the Indexer picked up all our protected nodes. ezSearch then was able to return results as expected.
For reference: http://umbraco.com/follow-us/blog-archive/2011/9/16/examining-examine.aspx
Hope this helps!
EDITED: tidying up the formatted code.
is working on a reply...