> > Why this is done After the search performed? As I know, ACL check could be > specified directly in Lucene query (filed named "rigth")?
No , because what is stored in the index is only the right id. We must retrieve the Acl instance for this id and perform permissions check for the current user. Acl permissions are not stored in the search index but in db table. Khue ----- Original Message ----- From: "Khue Nguyen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 18, 2004 3:03 PM Subject: Re: search again > Hi, > > a lot of conditions are added to the search query 'transparently' > i.e : the current language, the current workflow mode ( live/staging ) as > well as right check, > so that you don't have to worry about it. > > But it would be nice if this default behavior can be changed by additionnal > search parameters ( one to skip right check... ). > > Regards, > Khue > > > ----- Original Message ----- > From: "Mokrinsky Alexey" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, June 18, 2004 11:39 AM > Subject: search again > > > > > > Hi Jahia team! > > Thank you for your replies, they do help me in proceeding with my search > routine! > > > > But, as usual :) I have an additional question -> > > After the search is performed in SearchEngine, the results are built in > JahiaSearchResultHandlerImpl.buildSearchResult() -> There fields are checked > for their ACLs and, as I understand, unsuitable are not added to the result > list. > > Why this is done After the search performed? As I know, ACL check could be > specified directly in Lucene query (filed named "rigth")? > > > > Thnak you in advance > > Alex > > > > > > __________ > > www.newmail.ru -- Новая Почта для нового поколения. > >
