Symphony.

I have an Age-range field where data is stored like this '20-35'. I am using substring-before/after to extract two new fields: 'age-range-starts' and 'age-range-ends'.

Now, I am building a search form where there are two input boxes where people can enter age rage. I set up datasource with two filters:

{$url-age-range-start:0} to 100

and

100 to {$url-age-range-end:0} 

This should work, right? In theory this should give me the correct results, but data source filters doesn't seem to work correctly on Reflection field. It doesn't find any entries and there is no error.

I've also tried

greater than {$url-age-range-start:0}

and

less than {$url-age-range-end:100}

Only thing that has worked so far is if I just filter the datasource by static value

{$url-age-range-start}

But this is not useful since it only returns entries that have age-range-start while I want those who have 20 or greater.

Is it a reflection field bug or am I missing something?

Is it a reflection field bug or am I missing something?

Looking at the code it appears range filtering is not supported in this field.

was just thinking out loud today about a new fieldtype ('slugfield'?) that is somewhat like a reflectionfield: … works with textfields (only). E.g. 'linked' to a Title field. … 'handl-izes' values (Foo & Bar => foo-and-bar) of linked textfield … only auto-populates on first save (of linked text-field)

@davidhund It will be great

@bambocci yes, I still feel this could be worth-while. Might look into it myself (later when life's less busy, ahem…).

Does this field allow the usage of general parameters like $root or $workspace?

Looking through the code briefly, nope.

This is not working with xpath attributes. Like photo[@id]

Because your xPath is wrong...

photo/@id

will get the @id value, what you we're trying was a predicate, that would check that photo had an attribute of @id, not get it's value.

Hmm. ok. Thank you very much. Sorry for that!