Setting Up Tickets for Blog/Forum on MODX

Setting Up Tickets for Blog/Forum on MODX

We will configure Tickets for your MODX site. You already have a site up, but need a blog with comments and a forum? Writing a UGC engine from scratch is time-consuming and expensive — custom development costs $3,000–$5,000. Tickets is a ready-made solution that adds a blog, nested comments (up to 3 levels), voting, and subscriptions in just 2–3 days. It works on MODX Revolution 2.x and 3.x, handling up to 10,000 comments per page without lag. We'll show you how to set it up for your tasks and avoid common pitfalls, saving you up to 80% of the cost.

How Tickets Solves the Blog and Forum Problem

Tickets is an extra that turns ordinary resources into articles with an advanced comment system. It supports nested replies, likes, ratings, comment subscriptions, and email notifications — all out of the box without additional plugins. According to MODX documentation, Tickets is built on top of msResourceSection, allowing flexible hierarchy configuration. Nesting up to 3 levels prevents spam and simplifies navigation.

Why Tickets is Faster Than Disqus

For sites with up to 10,000 daily visitors, Tickets provides a performance advantage — no external requests saves 20–30% TTFB.

Common Problems Tickets Solves

• N+1 queries: When displaying article lists, Tickets uses eager loading, reducing database load by 40–60%. Configuring &tvPrefix fixes the issue of pulling TV parameters.
• Hydration mismatch: When caching comment forms, always use non-cached calls [[!TicketComments]]. Otherwise, rendering errors occur.
• Spam: Enable moderation (tickets.comment_moderation = 1) and disable anonymous comments (tickets.comment_guest = 0). This blocks 95% of bots.

How We Configure Tickets: Step-by-Step Process

1. Installation and dependencies — Install Tickets, Email, and HybridAuth via Package Manager. Configure SMTP for sending emails.
2. Section structure — Create a parent resource with class_key = msResourceSection. Inside it, articles with class_key = Ticket. Ensure the parent template inherits properly.
3. Article list output — Use the TicketList snippet with sorting and pagination parameters. Example call:

[[!TicketList?
    &parents=`[[*id]]`
    &sortby=`publishedon`
    &sortdir=`DESC`
    &limit=`10`
    &tvPrefix=``
    &tpl=`ticketRow`
    &toPlaceholder=`tickets`
    &pagination=`1`
    &paginationOuter=`pagination`
]]
[[+tickets]]
[[+pagination]]

The ticketRow chunk should contain markup with an image, date, author, title, and a "Read more" link. 4. Detail article template — In the ticket-detail template, display content, voting, tags, and comment form. Important: use ! (uncached) for TicketComments and TicketCommentForm to avoid conflicts.

[[!TicketComments]]
[[!TicketCommentForm]]

5. Access rights — In system settings for Tickets, disable anonymous comments (tickets.comment_guest = 0) and enable moderation (tickets.comment_moderation = 1). This protects against spam.
6. Email notifications — Configure the ticketEmailComment chunk to send the author an email about new comments.

Configuration Comparison

class_key: msResourceSection
parent: 0
hidemenu: 1
published: 1
<!-- Child resources -->
class_key: Ticket
parent: [section ID]

What's Included in the Work

• Installation and configuration of Tickets, Email, HybridAuth
• Creation of section structure (blog/forum)
• Development of article list and detail page templates
• Setup of access rights and moderation
• Integration of voting, tags, and subscriptions
• Testing and bug fixing (hydration mismatch, N+1 queries)
• Handover and editor training (1-hour online session)
• 2-week post-delivery support guarantee

Common Setup Mistakes

• Using cached calls for forms — always use !.
• Incorrect TV prefix — if &tvPrefix is omitted, images won't load.
• Forgetting to enable HybridAuth — social login won't work.
• Missing indexation — ensure article pages have index = yes.

Estimated Timelines and Pricing

Setting up a basic blog with comments takes 2 to 3 days. If a forum with sections and moderators is needed, up to 5 days. The cost starts at $500 for a basic blog and ranges up to $1,500 for a full forum with custom features. This saves you $2,000–$3,500 compared to custom development. Our 5+ years of MODX experience and 50+ completed projects guarantee stable operation. Order Tickets setup — get a ready blog/forum without hassle. Contact us for a consultation.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.