When getResources Starts to Hurt: Moving MODX Pagination to pdoPage
getResources struggles on deep MODX resource trees. Here's how to migrate paginated listings to pdoPage, with a worked example, verification steps, and the real trade-offs.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
getResources struggles on deep MODX resource trees. Here's how to migrate paginated listings to pdoPage, with a worked example, verification steps, and the real trade-offs.
Guide comparing TVs, MIGX TVs, and custom xPDO tables for storing repeatable data in MODX, with step‑by‑step implementation of a custom events table.
MODX Revolution uses Contexts as its multi-tenancy primitive—one installation, multiple isolated sites. This architecture note covers the minimal viable design, trust boundaries, operational verification, failure modes, and the triggers that force a move to separate installations.
Learn how to build and run a custom database query with MODX Revolution’s xPDO ORM. This guide covers prerequisites, building the query, verification steps, and recovery options so you can safely fetch data without raw SQL.
MODX contexts let one core serve multiple sites, but they share a database, manager, and codebase. This guide covers the minimal design, routing pitfalls, trust boundaries, ACL patterns, cache issues, and conditions that signal you need separate installations instead.
Learn how MODX caches parsed resources, when to mark them uncacheable, and how to verify cache hits to improve performance without serving stale content.
Learn how to use MODX Revolution Snippets to bridge the gap between static templates and dynamic data using PHP, script properties, and the MODX API.
A MODX white screen is a hidden PHP fatal error, not a mystery. This guide walks through surfacing the real message, matching it to extras, cache, config, or permissions, and verifying the fix.
Learn how to create and apply custom permissions in MODX Revolution, bind them to roles, scope them to specific resources, and verify the setup—ensuring least‑privilege access for your content team.