Choosing Between Template Variables, MIGX TVs, and Custom xPDO Tables in MODX Revolution
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.
Loading…
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
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.
Learn how to define a custom table with MODX Revolution’s xPDO schema, query it using typed objects, and paginate results efficiently—all without writing raw SQL.
Goal is to bound large resource result sets in ModX Revolution using xPDO limit/offset and present them via the getResources snippet pagination controls. Assumptions are ModX Revolution with xPDO ORM and MySQL. getResources builds xPDO queries from limit, offset and page parameters. Offset-based paging is simple to configure but database scans skipped rows a
The goal is to decide whether MODX should expose administrator‑configurable xPDO connection pool parameters, such as an idle timeout or maximum pool size, to mitigate intermittent 'Too many connections' errors observed under high traffic. In MODX Revolution 3.x the default connection mode switched to persistent PDO connections when the driver supports them,
Goal: Determine the appropriate PHP-FPM pm.max_children value that prevents intermittent MySQL 'Too many connections' errors when MODX Revolution's xPDO persistent_connection system setting is enabled. Constraints/uncertainty: xPDO reuses a single PDO instance per request but does not share persistent connections across separate PHP-FPM workers; idle persist