Joomla account cleanup
This integration connects a Joomla website to a Tickessa project. You review and control an approved operation from its ticket. Joomla performs the supported steps locally; the ticket system receives an internal completion note and a separate reply draft.
The settings area requires Tickessa 0.15.4 or later. Joomla extension 0.4.0-beta.2 is a beta with restricted download access. This guide describes existing functions and does not authorize a production cleanup operation.
Prerequisites
- Administrator access to Joomla and the ticket system.
- Plugin entitlement and a released Joomla ZIP in your customer account.
- Reachable HTTPS base addresses for both systems.
- An existing active support project.
- A backup of the Joomla database and files before cleanup.
The tested Joomla baseline includes Joomla 6.1.3, Kunena 7.0.8 and JomSocial 5.0.1. Other component versions may block execution. Community Builder is not supported in this beta. Additional data and unknown integrations are not automatically considered empty or cleaned.
1. Install the Joomla extension
Download the Joomla ZIP released for your account and verify its checksum. Install it in Joomla through System → Install → Extensions, then open Components → Tickessa account cleanup → Connection.
The Tickessa integration ships with the normal support package. No additional connection ZIP needs installing there. Joomla uses its existing database connection; no new database credentials are required.
2. Create the connection in the customer portal
Open My plugins → Joomla plugin and create a connection with a name, Joomla address and ticket system address. Enter the Joomla setup key in Joomla. Use the other key only in the ticket system. Both keys belong to the same connection and allow initial pairing within 24 hours.
3. Select the project in the ticket system
- Open Settings → Plugins.
- Select Open settings on Joomla account cleanup.
- Open Connect another Joomla website. This section is already expanded when no connection exists.
- Select an active Assigned project.
- Enter the Ticket system setup key from your customer account.
- Choose Set up connection.
Setup does not require an existing ticket. After pairing, the website appears in the list. The project ID and name are confirmed in the customer portal, where the chosen project name replaces an unexplained internal number.
Existing connection settings
| Field or action | Purpose |
|---|---|
| Joomla website | Shows the connected website. |
| Connection status | Result of the last test, not continuous live monitoring. |
| Last check | Time of the last test attempt. |
| Last successful check | Most recent confirmed connection; retained after later failures. |
| Test connection | Uses the customer portal to verify a signed response from Joomla. Does not start cleanup. |
| Assigned project | Selects an active project from this Tickessa installation. |
| Save and sync project | Saves the assignment and sends its ID and name to the customer portal. |
| Manage in customer portal | Opens plugin details for downloads, update periods and connection management. |
After renaming a project, save its assignment again to update the name in the customer portal. A project change applies to new operations. Existing tickets and completed records keep their original project. An unfinished cleanup blocks changes; continue it in the current project first.
Understanding connection tests
| Result | Next step |
|---|---|
| Connection confirmed at last check | The test succeeded at the displayed time. |
| Connection set up, not checked yet | Choose Test connection. |
| Setup incomplete | Check that both systems were paired using their respective keys. |
| Check in progress | Wait at least 30 seconds before testing again. |
| Connection unavailable or no longer authorized | Check HTTPS availability, plugin activation and possible revocation in the customer portal. |
| Joomla website response could not be verified | Check the plugin version, paired website and system clock. Do not immediately create a second operation. |
Testing sends no ticket text and starts no deletion. A successful result confirms connectivity, not complete cleanup or approval of a target account.
Handle an operation in a ticket
- Open a ticket in the assigned project and verify the request and target account.
- Select the website and confirmed Joomla user ID in the Joomla section.
- Choose Request preview. Review the identity, data, blockers and proposed mode.
- Review remaining posts, quotations, files and other data stores. Confirm only checks actually completed.
- Then choose Approve and clean up. Use Resume cleanup for further steps.
- For an interrupted request, choose Retry interrupted request in the same ticket. Do not create another cleanup request for the same unfinished operation.
- After confirmed completion, the audit appears as an internal note. Use in reply field copies only the short customer draft into the normal reply editor.
- Review and edit the text before sending. Setup, testing and completed cleanup do not automatically send a customer reply.
Beta cleanup scope
Without Kunena posts, the integration can remove the Joomla account and supported profile data. When posts exist, it blocks and anonymizes the account while preserving posts. Supported JomSocial profile data and clearly assigned local images are included. Shared files are not removed.
Unsupported content and dependencies may block execution. Kunena avatars, attachments, private content and additional JomSocial data must be reviewed separately before approval. External storage, additional extensions, quotations, backups and old unassigned files also require separate review. The extension does not promise complete cleanup of every data store.
Update, disconnect and restore
Update Tickessa through its regular updater and Joomla using its released package, then test the connection again. An expired update period alone does not revoke acquired usage.
Revoke the connection in the customer portal to stop further remote commands. This does not remove existing tickets. Uninstalling the Joomla extension does not restore deleted data and retains operation records for traceability. Handle unfinished operations before a planned uninstall and manage backups separately.