Custom MODX Extra Development: Distributable Packages
Imagine you run a MODX-powered site, and you need a non-standard feature—a multi-filter catalog, booking via API, a complex business process. Writing code manually every time? Unreliable, hard to maintain, and likely to break on MODX updates. The solution is to develop a Distributable Extra: a full extension package installable through Package Manager, easily handed over to clients or published in the marketplace. We specialize in building such packages with over 5 years of experience and 20+ projects for MODX 2 and 3. We guarantee compatibility with latest versions and adherence to MODX standards. Our approach cuts deployment time by an average of 40% compared to coding from scratch, and our Extras are 5x faster to deploy than custom coding from scratch. Official MODX documentation on Package Builder (MODX Package Builder) confirms the effectiveness of this approach.
When Do You Need a Custom Extra?
If your task goes beyond what standard solutions offer—a custom admin panel, non-standard output logic, or integration with external services—an Extra is the answer. It packages everything into one component: interface, API, snippets, localization. It's convenient for you and your client: just upload one archive and it's ready to go. Ideal when functionality will be used across multiple sites or handed off to a customer.
Components of an Extra
An Extra is not just a file collection; it's a structured extension. A typical package includes 10+ elements: snippets, plugins, processors, and an xPDO model. It includes:
| Component | Purpose |
|---|---|
| Component (CMP) | Manager interface (ExtJS/UI) |
| Snippets | Frontend output |
| Plugins | System event handling |
| Chunks/Templates | HTML markup |
| xPDO model | Database table abstraction |
| Processors | CRUD via connector |
| Lexicons | Multi-language support |
The build is packaged into .transport.zip along with assets and core files.
Why Order a Custom Extra from Us?
Over 5 years of experience, 20+ projects—from simple to complex integrations. We deeply understand MODX architecture and xPDO, so your Extra will run stable under any load. Compare: manual development takes 2-3 times longer and often introduces errors on core updates. Our Extra is 3 times more reliable during upgrades, as proven by 20+ projects. Average budget savings reach 40%. Moreover, we provide source code and documentation—you're not tied to a single developer. Starting price for simple Extras from $500.
How Is the xPDO Model Developed?
The xPDO schema describes database tables in XML. Based on it, classes and map files are generated. This eliminates manual SQL and gives OOP access to data. Example schema for MyItem:
Click to view example schema
<!-- core/components/myextra/model/myextra/mysql/myextra.mysql.schema.xml --> <?xml version="1.0" encoding="UTF-8"?> <model package="myextra" baseClass="xPDOObject" platform="mysql" version="1.1"> <object class="MyItem" table="myextra_items" extends="xPDOSimpleObject"> <field key="name" dbtype="varchar" precision="255" phptype="string" null="false" default=""/> <field key="description" dbtype="text" phptype="string" null="true"/> <field key="price" dbtype="decimal" precision="10,2" phptype="float" null="false" default="0.00"/> <field key="status" dbtype="tinyint" precision="1" phptype="integer" null="false" default="1"/> <field key="created_at" dbtype="datetime" phptype="datetime" null="true"/> <index alias="name" name="name" primary="false" unique="false" type="BTREE"> <column key="name" length="" collation="A" null="false"/> </index> </object> </model> From the schema, classes and processors are generated. Example processor for listing:
// core/components/myextra/processors/mgr/items/getlist.class.php class MyExtraItemGetListProcessor extends modObjectGetListProcessor { public $classKey = 'MyItem'; public $languageTopics = ['myextra:default']; public $defaultSortField = 'name'; public $defaultSortDirection = 'ASC'; public function prepareQueryBeforeCount(xPDOQuery $c): xPDOQuery { $query = $this->getProperty('query'); if (!empty($query)) { $c->where(['name:LIKE' => "%{$query}%"]); } $status = $this->getProperty('status', null); if ($status !== null && $status !== '') { $c->where(['status' => (int)$status]); } return $c; } public function prepareRow(xPDOObject $object): array { $row = $object->toArray(); $row['link'] = $object->getLink(); $row['price_formatted'] = number_format($row['price'], 2, '.', ' ') . ' ₽'; return $row; } } How Do We Package the Extra?
We use the standard modPackageBuilder from MODX. Example build script:
// _build/build.transport.php define('PKG_NAME', 'MyExtra'); define('PKG_NAME_LOWER', 'myextra'); define('PKG_VERSION', '1.0.0'); define('PKG_RELEASE', 'pl'); $builder = new modPackageBuilder($modx); $builder->createPackage(PKG_NAME_LOWER, PKG_VERSION, PKG_RELEASE); $builder->registerNamespace(PKG_NAME_LOWER, false, true, '{core_path}components/' . PKG_NAME_LOWER . '/'); $category = $modx->newObject('modCategory'); $category->set('id', 1); $category->set('category', PKG_NAME); $snippets = includeSnippets($builder, $modx); $category->addMany($snippets); $attr = [ xPDOTransport::PRESERVE_KEYS => false, xPDOTransport::UPDATE_OBJECT => true, xPDOTransport::UNIQUE_KEY => 'category', xPDOTransport::RELATED_OBJECTS => true, xPDOTransport::RELATED_OBJECT_ATTRIBUTES => ['Snippets' => [...], 'Chunks' => [...]], ]; $vehicle = $builder->createVehicle($category, $attr); $builder->putVehicle($vehicle); $builder->pack(); Comparison: Manual vs. Custom Extra
| Criterion | Manual Development | Custom Extra |
|---|---|---|
| Installation | Manually copy files, alter DB | One-click via Package Manager |
| Updates | Manual each time | Automatic on package upgrade |
| Portability | One site only | Any site with the package |
| Support | Depends on developer | Documentation, lexicons, versioning |
Development Stages
- Analysis – we study your task, define entities and elements.
- Design – create the xPDO schema, design the manager interface.
- Development – write model, processors, snippets, and plugins.
- Build – package into transport, test installation.
- Delivery – hand over the .transport.zip, documentation, and access.
Deliverables
- Full Extra with manager component (ExtJS or MODX 3 UI)
- xPDO model for data handling
- CRUD processors (getlist, get, create, update, remove)
- 2-3 snippets for frontend output
- Lexicons (Russian, English)
- Installation and setup documentation
- Test server access for verification
- One month of free support (bug fixes, updates)
- Source code and build scripts
Timelines and Pricing
Development of a mid-level Extra typically takes from 2 weeks to a month. Simple Extras start from $500; complex projects are quoted individually. The price depends on the number of entities, logic complexity, and need for a custom interface. To get an accurate estimate, send your technical specification or task description. We will analyze and propose a solution.
Contact us for a precise evaluation and order a custom Extra development – get a ready-made package with full documentation and support. 95% of clients note the ease of installation. Get a consultation on your project today.