☆ A M B ☆
'displayed' => array('*'),
☆ A M B ☆
Ok...&parents=`not in:64,84` works for me too!! That is wonderful, thanks. I did not know about that parameter.
Had no luck with &filter seems like it doesn't see the parent of the resource.
But this works:
AjaxSearch snippet call on search page:
[!AjaxSearch? ... &parents=`not in:64,84` ... !]
[!AjaxSearch? &showInputForm=`0` &ajaxSearch=`0` &showIntro=`0` &pagingType=`0` &highlightResult=`0` &grabMax=`20` &minChars=`2` &rank=`pagetitle:80,introtext:60,description:40` &whereSearch=`content:null` &advSearch=`oneword` &parents=`not in:64,84` &tplInput=`as-tpl-searchboxP` &tplGrpResult=`as-tpl-grpResult` &tplResult=`as-tpl-result` &tplResults=`as-tpl-results` &tplPaging0=`as-tpl-paging0` !]
Thanks for this suggestion also. I am not sure if that is feasible because the resources should to be searchable when they are published to the main folder on approval from the staff. I think &parents=`not in:64,84` overcomes the problem for now. Many thanks.
// + As you use front-end pubKit you could also go the route of creating resources with searchable off.
$fields = array( "searchable" => 0,
Re setting Searchable off when creating PubKit items - a good idea for previews, and should be possible to build in in a similar way to the &showinmenu setting. Some code adjustment is needed to switch searchability back on when you publish an item, of course, unless you specify otherwise via the new parameter.Sounds great Keith, I can see how this would come in handy.
@kp52: The hideMenu problem is not caused by this. It should work as as expected.I experience the same problem Jako - putting hidemenu directly in the snippet call does not seem to have any effect in my testing.
Thanks Jako, that is what I will use for this. [ed. note: nickf08 last edited this post 12 years, 3 months ago.]
&parents=`not in:64,84` is the better option for sure, because this will create a where clause in ajaxSearch that will narrow the result array during request.
☆ A M B ☆
☆ A M B ☆
Try to change line 243 in snippet.ajaxSearch.php@kp52: The hideMenu problem is not caused by this. It should work as as expected.I experience the same problem Jako - putting hidemenu directly in the snippet call does not seem to have any effect in my testing.
$cfg['hideMenu'] = isset($hideMenu) ? intval($hideMenu) : (isset($__hideMenu) ? intval($__hideMenu) : $dcfg['hideMenu']);
Try:Hey Jako, You are a genius.
&where=`parent NOT IN (64,84)`
Quote from: nickf08 at Jul 01, 2014, 04:36 AMThanks Jako.Try to change line 243 in snippet.ajaxSearch.php@kp52: The hideMenu problem is not caused by this. It should work as as expected.I experience the same problem Jako - putting hidemenu directly in the snippet call does not seem to have any effect in my testing.
$cfg['hideMenu'] = isset($hideMenu) ? intval($hideMenu) : (isset($__hideMenu) ? intval($__hideMenu) : $dcfg['hideMenu']);