What Information to Collect Before Asking for Joomla Technical Support
Record the exact symptom
Write down what you expected to happen, what actually happened, and the exact page or Administrator action that triggers the problem. Copy the complete error message instead of paraphrasing it. Note whether the failure is constant or intermittent and whether it affects guests, logged-in users, administrators, or only a particular account.
Collect Joomla and server versions
In Administrator, use System → Information Panel → System Information to collect the Joomla version plus PHP, database, web-server, and operating-environment details. Joomla documentation identifies System Information as a troubleshooting source for host, PHP, database, configuration, and directory information. Do not post secrets such as database passwords or private keys.
List relevant extensions and recent changes
Identify the component, module, plugin, template, or package involved and record its version. Include changes made shortly before the issue began: Joomla or extension updates, PHP changes, migrations, DNS or CDN changes, new plugins, configuration edits, or restored backups. A short change timeline often narrows the investigation dramatically.
Capture reproducible steps
Write the smallest sequence that reproduces the problem from a known starting point. Include the URL or menu path, login role, button or action used, and the result. If the problem cannot be reproduced reliably, record when it occurs and what conditions appear to be present rather than presenting a guess as a confirmed cause.
Gather logs and diagnostic evidence safely
Collect relevant Joomla log entries, hosting error logs, browser console errors, failed network requests, and timestamps. Joomla Debug System can provide diagnostic and SQL information, but official documentation warns against leaving debug mode enabled on a live site. Use it briefly and redact credentials, tokens, personal data, and filesystem details that should not be shared publicly.
Explain what you already tested
List the troubleshooting steps already attempted and their results, including cache clearing, extension isolation on staging, PHP changes, or rollback tests. State whether a current backup exists. This prevents support from repeating risky experiments and distinguishes changes that genuinely affected the symptom from changes that made no difference.
Package the request so someone else can act on it
A useful support request contains the exact symptom, reproduction steps, environment versions, relevant extension versions, recent changes, logs with timestamps, and previous test results. Provide temporary access only through the support provider’s approved secure method and only when needed. Never place passwords, API keys, session tokens, or private credentials in a public ticket or forum post.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.