Use logs and maintenance utilities

Archived instructions for existing Fusion Owned installations; labels and available controls depend on the installed build.

Find the matching log

- **Utilities > API Log** searches past API responses and supports print/export.

- **Utilities > Gateway Log** searches by **Transaction Id**, **Client name**, **Date** and **Payment Status**; its description records what happened during gateway processing.

- **Utilities > System Log** contains errors reported by system files.

- **Utilities > SMS Log** shows delivery states and errors.

- **Utilities > Download Log** records the user, IP, date and filename.

- **Utilities > Activity Log** records events such as profile or service changes, the updating user, IP and date/time.

For a failed payment or API action, find the record matching its reference and time. Share only a relevant redacted excerpt rather than a full log export.

Database status and cleanup

Open **Utilities > Database Status** to review table names and sizes. The archived page provides optimization and indexing controls, including indexing needed by some historical database updates. Back up the database and identify the affected tables before using them.

**Utilities > System Cleanup** removes unwanted log data. Preserve records needed for a support investigation or accounting before cleanup; clearing a log does not fix the underlying error.

Import data from another system

Open **Utilities > Import Script**. The legacy import can transfer supported users, orders and invoices. Its documented fields are:

- **Transfer from**: the source script or server type.

- **Host**: the source database host.

- **DB name**, **DB user** and **DB password**: the source database connection.

Confirm source and destination, back up both sides and test against a separate copy first. Enter the connection details only in the protected import form; never paste them into a support message.

Online users, IPs and legacy lists

- **Utilities > Online User** separates system users from guests.

- **Utilities > IP Manager > Blocked IP** accepts entries or ranges such as `192.168.*.*` and `192.168.1.*`; the source's reason format is `192.168.1.1#Reason`. Select the country and save the intended rule.

- **Utilities > IP Manager > White List IP** manages allowed-IP entries.

- **Utilities > IP Manager > CloudFlare API** has **ZONE ID**, **Email** and **API KEY** connection fields.

- **Utilities > Email Black List** and **Utilities > Blacklist IMEI** manage the site's existing email or IMEI lists.

The archived **Utilities > Fraud Cage** page contains a shared-report list and submission controls. Review authority and privacy obligations before sharing account information. Do not change a block or allow rule without checking which visitors or administrators it affects.

Other operational tools

- **Utilities > SEO Functions** generates an XML sitemap from selected fields and includes **Google Base Generator**.

- **Utilities > Language Editor** edits administrator/client wording and supports multiple languages; its archived integration uses a Google API for translation.

- **Utilities > Messenger Notification** contains Telegram or Slack notification connections where the feature is installed.

These menus describe the old build; provider integrations and optional features still depend on the site's configuration.

Legacy payment aggregation

Under **Utilities > Payment Aggregation**, enter the **aggregator name**, select the **gateway**, enter the **monthly limit** and click **Add**. The archive calls the generated identifier **UIID**.

On the site using another Fusion administrator's gateway, open **Settings > Payment Gateway**, activate **Payment aggregator** and enter the gateway-owning site's UIID in that gateway configuration. Review the agreement, monthly limit and payment records on both sites before using this historical workflow.