Input filters in Revo

I haven’t been able to find any information about input filters in Revo and my trial-and-error attempts to use one have gotten nowhere, so I’m asking.

What’s the syntax for input filters?

I know that they modify the element before it’s processed, but what exactly does that mean--anything in a MODx tag is left alone?

By default, Input/Output Filters in Revolution simply mimic PHx behavior; the input filters in this case simply parse/collect data from the tag name into variables later used by the output filters to operate upon, modifying the output. You can currently programmatically override the input/output filters for any Element, and in 2.1 (or possibly before) this is something you will be able to specify per Element when you edit it.

Do we have list of filters somewhere? and their usage syntax.

Quote from: zi at Jul 10, 2009, 05:16 PM

Do we have list of filters somewhere? and their usage syntax.

Not yet, but should essentially be the same as PHx, except custom modifiers as snippets do not require a phx: prefix.

Quote from: OpenGeek at Jul 10, 2009, 05:20 PM

Quote from: zi at Jul 10, 2009, 05:16 PM

Do we have list of filters somewhere? and their usage syntax.

Not yet, but should essentially be the same as PHx, except custom modifiers as snippets do not require a phx: prefix.

Slight correction, we do have a list of Output Filters and their syntax:

http://svn.modxcms.com/docs/display/revolution/Input+and+Output+Filters

We don’t have documentation on Input Filters yet, however.

I understand output filters.

If I’m understanding you correctly, input filters are used internally and there’s no case where a user would want to specify an input filter in the tag (and no way to do it).

Is that correct?

If not, I need an example.

Input Filters + Output Filters == PHx. Input Filters filter the tag name and set the modifiers indicating to the output filters what they are supposed to do; it’s all tied together.

Thanks guys!

Quote from: OpenGeek at Jul 11, 2009, 11:45 AM

Input Filters + Output Filters == PHx. Input Filters filter the tag name and set the modifiers indicating to the output filters what they are supposed to do; it’s all tied together.

1. Right, but I don’t see a direct answer to my question about whether this is a correct statement:

Input filters are used internally and there’s no case where a user would want to specify an input filter in a tag (and no way to do it).

I’ve tested most of the output filters listed on the page splittingRed refers to and I didn’t, to my knowledge, need to mess with input filters to do it.

So, hypothetically, if someone were writing about this in a book on MODx :

2. Should there be any information on input filters?
3. If so, what would it include?

Without the input filters, output filters would be meaningless because the input filter is responsible for defining how the tag name is parsed. When you use PHx style tags, you are using Input/Output Filters, both, not just Output Filters. Input filters will allow developers to define new ways to specify what/how custom output filters are are going to be applied.

So yes, it should be included, no it’s not internal (though there are default input/output filters that act like PHx), and what is said about it is what I’m trying to describe.