Install WordPress in UAPP
Create a WordPress site with eligible domain, version, language, PHP and administrator settings, including update policies and queued installation recovery.
Open WordPress Toolkit → Install WordPress.
Installation fields
| Field | Requirement |
|---|---|
| Domain mode | Select an existing eligible domain or create a subdomain. |
| Domain | Required offered domain in existing mode. |
| Parent domain / Subdomain name | Required in create mode; name up to 63 characters, validated without wildcards or underscores. |
| Site title | Required single-line title, maximum 200 characters. |
| Admin username | Required, 1–60 characters: letters, digits, underscore, @, dot or hyphen. |
| Admin password | Required nonblank value without line breaks or null characters. Retain it securely. |
| Admin email | Required valid address, maximum 254 characters. |
| WordPress version | Offered release from the available catalog. |
| Language | Offered language for the selected release. |
| PHP version | Domain Default or an offered installed version when PHP selection is permitted; must meet release requirements. |
| WordPress automatic updates | No, minor only, or minor and major. Initially minor only. |
| Plugin / theme updates | Defined individually or Forced; initially individual. |
An empty eligible website directory is required. The Toolkit checks MySQL availability and the hosting database allowance; an unavailable/stale version catalog can block installation.
Install and verify
- Choose the domain mode and target, then version, language and compatible PHP.
- Enter the title and administrator credentials.
- Review update policies and submit.
- Follow the queued job through completion.
- Verify the website, administrator login, HTTPS and application behavior.
Creating a subdomain checks ownership, feature and capacity. Subdomain creation or PHP changes can occur before WordPress is queued. If the subdomain was created but installation was not queued, reload and select it as an existing domain rather than creating it again.
The form uses a request identity to recover an already-queued installation after an uncertain response. Follow its retry/status guidance; do not open multiple fresh forms to duplicate the request. Busy resources and queue limits can delay or reject submission.
Do not install over existing content
Use Discover WordPress for an existing site. Preserve current files and data rather than clearing a directory merely to pass the empty-directory check.
Demo mode blocks installation. A submitted or queued response does not mean provisioning finished. Review failed/partial job details and actual website state before retrying.