Read Joomla Module and Menu Item Data with QCDR Tokens

QCDR Max/All Access Joomla data Tokens can read selected stored properties from a specific frontend module or menu item. You identify the record by its Joomla ID, and QCDR resolves the value at request time for the current visitor.

These are record lookups, not rendering commands. In particular, a module-content Token reads the module's stored content field; it does not execute or recursively render the module.

Specific Module Sources

Under Specific Joomla module, choose:

  • Module title by ID
  • Stored module content by ID

Enter the numeric frontend Module ID. The record must be a published site module (client_id = 0), be within its publication dates, and use an Access level available to the current visitor.

QCDR reads the stored module record directly. It does not invoke the module's PHP, module layout, plugin events, or recursive Joomla module rendering. For non-Custom modules, the database content field may therefore be empty or may not represent what the rendered module normally displays.

Specific Menu Item Sources

Under Specific Joomla menu item, choose:

  • Menu item title by ID
  • Menu item alias by ID
  • Menu item link by ID

Enter the numeric frontend Menu Item ID. QCDR requires a published site menu record within its publication dates and accessible to the current visitor. The link provider returns a site-relative Joomla Itemid route for that record.

Create the Token

  1. Create or edit a Token and choose Joomla content / dynamic data.
  2. Select the desired Specific Joomla module or Specific Joomla menu item source.
  3. Enter the corresponding Module ID or Menu Item ID.
  4. Leave Output handling on Automatic unless you have a specific formatting requirement.
  5. Save and test the Token with the visitor Access levels that matter.

Automatic Output Handling

Automatic mode treats module titles and menu titles/aliases as escaped text. Stored module content is an HTML-capable source and is returned as stored markup. Menu links use URL-safe handling.

If you need a module's stored content to appear as literal text, explicitly choose Plain text. If you choose HTML, remember that QCDR is trusting stored module markup rather than executing the module.

Module Assignment Is Not a Rendering Check

The specific-module provider validates the module record's publication dates and Access level, but it is not asking Joomla whether that module is assigned to the current menu item or position. Use QCDR's own Token targeting when the dynamic value should appear only on selected pages.

Unavailable Records Fail Non-Destructively

If the selected module/menu record is missing, unpublished, outside its publication window, or inaccessible to the visitor, the source does not resolve. QCDR leaves a standalone placeholder or a dependent Rule's original match intact.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.