What Information to Collect Before Asking for Joomla Technical Support

A useful Joomla support request gives the technician enough evidence to reproduce or narrow the problem without first asking for basic environment details. Collect the exact symptom, reproducible steps, software versions, recent changes, and relevant logs while keeping passwords, tokens, and private data out of the ticket.

Describe the exact problem and expected result

State what you were trying to do, what you expected Joomla to do, and what actually happened. Include the frontend URL or Administrator path when safe, the user role involved, whether the issue is constant or intermittent, and the exact error text. Screenshots can help with layout or visual problems, but copyable error text is more useful for technical diagnosis.

Provide reproducible steps

Write the shortest sequence that triggers the problem from a known starting point. A good reproduction might say: log in as an Editor, open a specific article, change the category, click Save, and observe the error. If you cannot reproduce the issue reliably, provide timestamps and conditions from the occurrences you have seen rather than presenting a theory as fact.

Collect Joomla, PHP, database, and server details

Use Joomla System Information to record the Joomla version and relevant PHP, database, web-server, and environment details. Include the active template and the version of the component, module, plugin, or package involved. For compatibility problems, support needs the actual runtime used by the website, which can differ from command-line PHP.

Do not include database passwords, secret keys, API tokens, session cookies, private keys, or other credentials in screenshots or pasted configuration files.

Create a short timeline of recent changes

List changes shortly before the issue began: Joomla or extension updates, PHP changes, migrations, DNS/CDN changes, template edits, new plugins, configuration changes, security rules, or backup restores. Include approximate dates or times. A clear change timeline often reduces a large troubleshooting space to one or two likely areas.

Attach the relevant evidence

Collect Joomla log entries, PHP or hosting error-log entries, browser console errors, failed network requests, and timestamps that match the failure. Include only the relevant section rather than an enormous unfiltered log when possible. Redact personal data, credentials, tokens, filesystem details that should remain private, and unrelated customer information.

Explain what you already tested

List troubleshooting already performed and the result of each test. Say whether clearing cache changed anything, whether the problem reproduces on staging, whether disabling a specific extension fixed it, or whether a PHP change had no effect. Also state whether you have a current backup and a rollback path. This prevents support from repeating risky work and helps distinguish evidence from guesses.

Package access safely if support needs it

Provide temporary Administrator, hosting, SFTP, or other access only through the support provider's approved secure method and only when it is genuinely required. Use a dedicated temporary account with the minimum necessary permissions, record what was granted, and remove or rotate it when the case is complete. Never post credentials in a public forum or public ticket attachment.


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.

Open a Support Ticket