As of MODX Revolution 2.2, developers are handed class-based processors to speed up development of the back-end components. These are great, and I have blogged about Class Based Processors in general before with some quick examples, but in this article we'll dive into a particularly awesome one: modObjectGetListProcessor.
The modObjectGetList processor is mostly used for populating grids through the modExt Grid implementation, but you could also use it for any other widget that uses a JSON Data Store. And processors aren't limited to being used by connectors for back-end components.. they're also great to keep your code DRY (Don't Repeat Yourself) for use in Snippets!
For this article we'll assume a simple grid though. The techniques displayed can be used to point you in the right direction for other implementations.
Here's basically the minimum processor file you can use:
.. and the reason they're so awesome. Brief, super awesome, working code!
The most important thing to note is the public variable
$classKey, this is the class name of the object you are going to retrieve. Furthermore you'll see we define the
$defaultSortField to the "initiatedon" date field from the schema, and with
$defaultSortDirection we make sure we get the latest on top. The
$objectType variable is not necessarily required, but allows you to use prefix (lexicon) error messages for some default sanity checks. For example in the update processor it will use the objectType to prefix _err_ns if the primary key is not specified.
We also make sure we return the name of our extended class in the end, as that is used to instantiate the processor when it's called. While you're free to name it whatever you want, I'd advise you to keep it the same as your classKey. That way, when adding a new processor, you can just copy/paste another one and find/replace the old classKey for the new one and you're good to go.
Exploring the Processor Process
Just like an earlier post, dealing with the modObjectUpdateProcessor class based processor, I have created a list of what happens in the processor that you will find below.
- Processor instantiated, properties being set.
- Using checkPermissions() the processor decides if the user is allowed to access it.
- The processor finds lexicon topics to load via getLanguageTopics, which gets its data from the languageTopics variable (as an array).
- initialize() is called on the processor, which sets a number of default properties including sort to the defaultSortField (default: name) class variable, and the direction to the defaultSortDirection variable (default: ASC).
- process() is called.
- beforeQuery() is triggered by process(), and if the result is not a boolean TRUE it will consider the processor to have failed and cancel further execution.
- getData() is triggered by process().
- The getData() method builds an xPDOQuery object for the classKey type.
- The getData() method calls prepareQueryBeforeCount(xPDOQuery
$c) allowing you to add additional conditions to the queries. After calling that, it fetches the total amount of results using modX.getCount.
$c) is called by getData().
- The query is sorted with help of the getSortClassKey() method, and the sortAlias, sort and dir properties.
- If the limit property is larger than 0 it limits the query and sets an offset.
- modX.getCollection is called with your data, it's been retrieved.
- Every row is iterated over using the iterate(array
$data) method. iterate calls beforeIteration(array
$list), and starts looping over the rows.
- If the checkListPermission variable is true, the object extends modAccessibleObject and checkPolicy('list') is false, it skips the row.
$object) is called which needs to return an array with the objects' fields. Great method to customize the retrieved data. The array is added to the list.
- After iteration over the entire result set afterIteration(array
$list) is called.
- The data is returned.
Defining Constraints (where field X has value Y)
When adding constraints, we will take our minimum processor and add (actually override) a new function called prepareQueryBeforeCount. This function takes in the xPDOQuery object as parameter, and expects it to be returned as well.
Easy enough we first get the "reservation" value using $this->getProperty(). By specifying a second value we are assigned a default instead of NULL. In this case I'm setting the default value to zero, which makes sure that if there is no reservation passed, it will not return any results - but no results instead (as all rows have a reservation set to > 0).
After getting the reservation variable, we just interact with the xPDOQuery
$c as we would in a normal processor (or script) and pass our where condition.
In the end we return the xPDOQuery (this is important!) and we've limited our query to just that reservation.
Modifying the way row data is returned
In some cases, your database set up may not completely match how you want to display that data in the front end. For example, you may have an array (which is stored serialized), which you want returned as one line of text per array key=>value, for rending in a textarea for example.
You will also see that instead of calling simply $object->toArray(), I am passing some additional parameters.
Specifically selecting fields
You could also join tables in the prepareQueryBeforeCount processor, add additional constraints etc.
Are there any more examples you would like to see, or have some to share yourself? Let me know in the comments!
Read 7 comments and share your own thoughts!