[solved] Exclude children of known parents from AjaxSearch (and Ditto) results

Hello,

I am using Evo 1.0.14 with the inbuilt AjaxSearch 1.10.1 and I am trying to exclude the children resources of known parents from the search results.

The 2 parent folders I am targeting are 64 and 84. The parents are unpublished and not shown in menus.

The children documents are all published and show in menus. Children documents get added quite regularly to these 2 folders by public users that submit pubKit forms in the front end. So manually listing each child document, and manually changing to show in menu / unpublished, is not feasible because they change all the time.

I have tried the following in the AjaxSearch snippet call on the search page:
&hideMenu=`0` (hoping this might hide children if parents are hidden - but does not seem to behave that way)
&filter=`parent,64,2` (I understand AjaxSearch filtering works like ditto filtering but not sure how to do it)
&documents=`not in:64,84` (hoping this would cover 64 and 85 and all their children - but I think it only covers the 2 specific resources)

These are my AjaxSearch snippet calls...

AjaxSearch snippet call in header (the form):


AjaxSearch snippet call on search page:


Any ideas on how to exclude children of known parents from AjaxSearch results?

Thanks in advance. [ed. note: nickf08 last edited this post 12 years, 3 months ago.]

I know this is tricky but maybe someone out there knows how to do it?

Have you unchecked "Searchable" for the resources?

That link you sent through in the first reply was really interesting:
https://forums.modx.com/thread/3221/parents-parameter---for-a-more-convenient-way-to-specify-the-documents-ids

Something like that would be perfect - but the above applies to Revo (perhaps why you removed).
&documents=`-c64,-c84` would be sensational.
I wish!

Checking the Searchable box is not an option unfortunately because of the public forms being submitted - we'd need to manually change the Searchable checkbox so I need a more dynamic solution to exclude children of know parents. It's tricky.

I deleted it as the code is for REVO.

I'm testing to see if I can figure this out and will post answer here

// I think you've found a bug as filtering by id works fine... [ed. note: mrhaw last edited this post 12 years, 3 months ago.]

Ok...

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:


// + As you use front-end pubKit you could also go the route of creating resources with searchable off.

[ed. note: mrhaw last edited this post 12 years, 3 months ago.]

I tried out both &hideMenu and &filter parameters in AjaxSearch 1.10.1, both in MODX 1.0.14 and Clipper 1.2.7. They didn't work in either. For instance, using &hideMenu=`1` and &hideMenu=`0`, which ought to be mutually exclusive, produced exactly the same result.

What did work, though, was setting the parameters via the config file (ajaxSearch/configs/default.config.php), e.g. to exclude items under parent with id of 3, or .
So it looks as if some parameters set in the snippet call don't get through to the main part of the snippet.

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.

:) KP

@KP Thanks for the clearification on this. Yes searchable option would be great for pubKit!

&filter=`parent,x,y` would work. But since 'parent' is not in the list of the displayed fields of &whereSearch=`content` it could not be filtered by this column.

This could be solved by changing line 97 of ajaxSearchRequest.class.inc.php to

or in my opinion better


The second change will return a larger array than the first one and it uses more memory but I don't think that the impact is that high.

Should that be changed in AjaxSearch code?

@kp52: The hideMenu problem is not caused by this. It should work as as expected. [ed. note: Jako last edited this post 12 years, 3 months ago.]

Option 2: Cool to have the full arsenal using &filter and most columns are just TINYINT or INT (1-20) (pic)

Option 1 (add parent column): We're NOT using count(*) but it's interesting how that affects
different queries

> http://www.mysqlperformanceblog.com/2007/04/10/count-vs-countcol/
> http://stackoverflow.com/questions/65512/which-is-faster-best-select-or-select-column1-colum2-column3-etc

AND &parents=`not in:64,84` is a solid method for AjaxSearch...

// I'm neutral. [ed. note: mrhaw last edited this post 12 years, 3 months ago.]