[2.0.1] Using placeholders inside &filter

66 Posts

bkvernst Reply #1, 19 years, 3 months ago

Hi,

I seem to be having problems using a placeholder in the filter clause.
Here’s my filter call: &filter=`content,[+searchword+],7`

What I’m trying to do here is to make Ditto my very own search engine, which crawls the document content for whatever [+searchword+] tells it to look for.

Now, I’ve tried replacing "[+searchword+]" with "55 000", which worked like a charm. That listed up all the pages with 55 000 in their content.

[+searchword+] is set by fetching a GET variable, and works everywhere else. I’ve even used it in the &noResults-paramenter just to check that everything’s fine with the searchword value.

So is Ditto having trouble handling [+ +]’s (what’s their name again?) in a filter clause, or have I done something wrong? Is there any way to make this work by using custom filtering instad, maybe?

Thanks!

66 Posts

bkvernst Reply #2, 19 years, 3 months ago

I’ve been trying to figure this out, but from what I’ve understood this seems to be a bug. I’ll post it in the Bug Tracker now...

3,250 Posts

MARKSVIRTUALDESK Reply #3, 19 years, 3 months ago

Depending on your MODx version, your placeholder [+searchword+] might not be replaced with its value before Ditto receives it. Thus, a workaround would be to create a pre-parsed filter in a new extender like so:

$filters["parsed"][] = array('getFilter' => array("source"=>"content","value"=>$_GET['YOUR_FIELD_GOES_HERE'],"mode"=>"7"));
	// Variable: $filters["parsed"][]
	// Add the pre-parsed filter to the parsed filters list where YOUR_FIELD_GOES_HERE is the name of your get field.