Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesdnn 7.1 search modulednn 7.1 search module
Previous
 
Next
New Post
9/10/2013 2:29 PM
 

@Jurgen2 - I believe what you are seeing is recorded in this bug https://dnntracker.atlassian.net/browse/DNN-3556 

Does the problem go away after app pool recycle, I am thinking a caching issue?


Ash Prasad
Director of Engineering
DNN Corp.
 
New Post
9/10/2013 2:32 PM
 
@Guess - Here is how the Permission string can be used

"!Translator (en-US);![0];[1];;Administrators; ContentEditorRole;"

! -- identifies denied permission
[n] -- identifies userId

In the above example, role "Translator (en-US)" does not have view permission whereas Administrators and ContentEditorRole do.

UserId 0 does not have have permission, whereas 1 has.


Ash Prasad
Director of Engineering
DNN Corp.
 
New Post
9/10/2013 6:13 PM
 
Great, tx Ash.

So "[1];[5];[10];Administrators"

User 1, 5, 10 and Admins has permission..... what about 2,3,4, 6,7,8,9 and all the other 1000's of users. do I explicitly have to deny them ? or choosing a role like "!Register Users;" to deny the rest (I assume if your current userid is in at least ONE match that CAN VIEW, then you can view and all the the other (! denied) 's does not matter?
 
New Post
9/10/2013 6:36 PM
 

@Guess -- Permission is done identical to how it's done in the Core, with one difference that if you don't specify this value then the SearchDocument is searchable by anyone. However tab and module permissions are always respected. For e.g. if you have a page / module with permission to specific role and then all you want to do is restrict search to this role, you don't have to do anything extra. However, if you want granular permission, e.g. Forums module where non-moderated comments can only be searched by admins, in this case you'd use this property. You set [Moderators] as Permission for items that are in moderation. Once item is no longer in moderation you should update the corresponding SearchDocument in index.


Ash Prasad
Director of Engineering
DNN Corp.
 
New Post
9/11/2013 5:46 AM
 
@ash: Got passed the previous error by recycling my app pool but now I get this error:

2013-09-11 11:42:56,510 [Jurgen][Thread:18][ERROR] DotNetNuke.Services.Exceptions.Exceptions - Lucene.Net.Search.BooleanQuery+TooManyClauses: maxClauseCount is set to 1024
at Lucene.Net.Search.BooleanQuery.Add(BooleanClause clause)
at Lucene.Net.Search.BooleanQuery.Add(Query query, Occur occur)
at DotNetNuke.Services.Search.Controllers.SearchControllerImpl.ApplySearchTypeIdFilter(BooleanQuery query, SearchQuery searchQuery)
at DotNetNuke.Services.Search.Controllers.SearchControllerImpl.GetResults(SearchQuery searchQuery, Int32& totalHits)
at DotNetNuke.Services.Search.Controllers.SearchControllerImpl.SiteSearch(SearchQuery searchQuery)
at DotNetNuke.Web.InternalServices.SearchServiceController.GetBasicViews(SearchQuery searchQuery, Int32& totalHits)
at DotNetNuke.Web.InternalServices.SearchServiceController.Preview(String keywords, String culture, Int32 forceWild, Int32 portal)

What does this mean?
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesdnn 7.1 search modulednn 7.1 search module


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out