📌 Purpose & Quick Summary

Once deployed, all applications appear in the Installed Applications manager. From here, you can launch 1-Click Admin Auto-Login (direct SSO into WordPress /wp-admin without entering passwords), perform automated core upgrades, take snapshot backups, and safely uninstall applications.


🖥️ Interface Tour & Elements

  1. Installed Applications Tab: Displays a ledger of all active CMS installations.
  2. Installation Details: Shows Application Name, Version, Domain URL, Installation Path, and Connected Database.
  3. Action Toolbar:
    • Admin Login (SSO): Direct 1-click login into application administrative backends.
    • Snapshot Backup: Creates an instantaneous backup of the application files and database.
    • Upgrade Core: Updates CMS core to the latest stable release.
    • Uninstall (Purge): Completely removes the application and drops the connected database.

🛠️ Step-by-Step Instructions

Step 1: 1-Click Admin Auto-Login

  1. In 1 Click Install, click the Installed tab.
  2. Locate your WordPress installation.
  3. Click the Admin Login button (key icon).
  4. The system generates an authenticated session and opens https://yourdomain.com/wp-admin/ directly in a new tab.

Step 2: Uninstalling an Application Safely

  1. In the Installed tab, locate the application to remove.
  2. Click the Uninstall button (trash icon).
  3. Check Purge Database if you also want the connected database dropped.
  4. Click Confirm Uninstallation.

⚙️ Complete Field & Parameter Reference Table

Action Function Safety Guarantee
Admin Login One-time passwordless authentication token Safe access even if you forget your admin password.
Snapshot Full backup of files and DB Creates recovery point before major plugin/theme upgrades.
Uninstall Unlinks files and drops schema Leaves parent directory clean for future deployments.

❓ Troubleshooting & Common Errors

1. Admin Auto-Login Fails (Redirects to Login Screen)

  • Cause: Security plugins (such as Wordfence or iThemes) blocking programmatic authentication.
  • Solution: Log in manually using the admin credentials generated during deployment, or temporarily disable the security plugin via File Manager.