Config info

JEM Settings: Config Info

Inspect installed JEM extensions, server capabilities, logs and bundled libraries.

Navigation

ComponentsJEMSettingsConfig Info

Purpose

Config Info is a read-only diagnostic tab. It does not change JEM settings. Use it to establish the exact environment before updating, debugging or requesting support.

Support workflow

  1. Confirm component, package, module and plugin versions are aligned.
  2. Check enabled status and PHP/GD capabilities.
  3. Note the active JEM log level and reproduce the problem once.
  4. Review the relevant log. Remove personal data, filesystem paths, tokens and credentials before sharing it.
  5. Return production logging to a normal level after diagnosis.

What Config Info does not prove

An enabled extension can still be misconfigured; an available library does not guarantee every output is valid; and Super User success does not prove ACL works for contributors. Combine this page with role-based testing and the Update Check screen.

Information and actions

SectionContentHow to use it
JEM extensions Package, component, modules and plugins with version/date and enabled status. Detect mixed package versions, missing integrations and disabled extensions before reporting a fault.
Server capabilities PHP version, legacy PHP flags and GD availability. Compare the server with JEM/Joomla requirements and image-processing needs.
Log level Current JEM logging level. Confirm whether the expected error/warning/debug records can be produced.
Log files Component, module and plugin log files, source and activation condition. View or download a log for support. Review it for personal data or secrets before sharing.
Bundled libraries Library name, version, licence, scope, location and notes. Audit third-party runtime/bundled dependencies, including PDF support.

Saving and verification

  1. Select Save and review any validation or permission warning.
  2. Open the affected frontend view in a private browser window and as each relevant user group.
  3. Test a representative event and venue with images, attachments, access restrictions and empty optional fields.
  4. If the setting changes layout or assets, test desktop and mobile widths and clear Joomla and browser caches.
  5. Record non-default values in the site's maintenance notes before an update or migration.

Code sources

  • admin/views/settings/tmpl/default_configinfo.php
  • admin/views/settings/view.html.php

This article documents the current JEM 5 source tree and relevant behaviour introduced or corrected in the JEM 4.4, 4.5 and 5.0 milestones. Menu-item options can override some global display defaults. Record-level values and Joomla ACL continue to apply independently.

Related reading and implementation history