Page not found
Uh oh, you've reached a page that does not exist.
It may have gotten lost on the new documentation platform or it was removed because it was no longer relevant. It could also be a really old link from two (or more) documentation systems ago, which is not part of the 2000+ automatic redirects currently in place.
Based on your request, this may be what you're looking for:
-
Contributing to xPDO
xPDO is an object-oriented framework on which MODX Revolution is built. It is maintained in a separate git repository from revolution and contributing to the xPDO core of MODX requires some additional work. xPDO contributors should follow the same ba...
-
Database Connections
xPDO Database Connections¶ Database connectivity in xPDO is done in the constructor. The xPDO object can only hold one database connection per instance, but you are free to instantiate as many xPDO instances as you need. The syntax of the constructor...
-
Creating xPDO Instance
When using xPDO within MODX, the modX class (typically available as $modx or $this->modx) is an instance of xPDO so you do not need to create a separate instance. When using xPDO standalone, or if you want to create additional instances, use the i...
-
Custom Users
Intended Audience¶ This article is for developers who are looking to add additional data to their MODX users and functionality to the related classes. Although this is possible via a less integrated approach by simply adding a database table that inc...
-
xPDO
xPDO is the object-relational-bridge that is built into MODX. Simply put, it's how MODX connects to the database, and how it interacts with different tables. In MODX 2.x, the modX class directly extends xPDO. While in hindsight that's not the best de...