See http://platform.xwiki.org/xwiki/bin/view/DevGuide/velocityHqlExamples
Thanks -Vincent On May 19, 2008, at 7:32 PM, [EMAIL PROTECTED] wrote: > I am not sure of why the search requires programming rights but I'm > putting a wild guess on the fact that if you would use normal rights > check, you might need to check if the user that performs the search > has > view rights on each page that might result in the search, which of > course > it's almost impossible. > > However, what I want you to understand is that using the programming > rights from a page saved by an admin is not a "workaround", but an > intended feature of xwiki. Many applications use this. > > If you still want to use the search from wherever you want, you > might need > to write your own plugin. However, i suggest you have a good look at > the > lucene plugin first. > > Cristian > >> >> Hi Cristian, >> This information does help me understand things better. Probably I >> can use >> this feature as a workaround to always execute search. However I >> would >> still >> like to know the rationale of why search is restricted to programming >> rights >> only. I think if any user has view rights then he should be able to >> use >> the >> search apis. >> >> What do others say? >> >> Thanks >> Sachin >> >> >> >> cristian.vrabie wrote: >>> >>> Hi Sachin, >>> The programming rights work a bit different. The check is not if the >>> current logged user has programming rights, but if the person that >>> saved >>> the page(document) last time has them. For example, if the page that >>> executes the search is created/saved by an admin that has >>> programming >>> rights, inside it you can execute scripts that require programming >>> rights >>> even though the current user doesn't have them. >>> >>> Hope this helps, >>> Cristian >>> _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
