Table of Contents
- In this video, I am going to show you How to Install WordPress in cPanel Manually Step by Step in 2021. Hope this will be very helpful to you all.
- CPanel can be classified as a tool in the 'Server Configuration and Automation' category, while WordPress is grouped under 'Self-Hosted Blogging / CMS'. WordPress is an open source tool with 12.7K GitHub stars and 7.78K GitHub forks. Here's a link to WordPress's open source repository on GitHub.
- Overview
- Create a WordPress site backup
- Clear a WordPress installation cache
- Clear the WordPress Toolkit cache
- Display the WordPress Toolkit help documentation
- Clone a WordPress site to a domain and/or subdirectory
- Manage WordPress Toolkit configuration settings
- Copy file and database table data from one WordPress site to another
- Detach a WordPress site from WordPress Toolkit
- Display information about a WordPress installation
- Install a new WordPress site on a domain
- Display the available locales for a version of WordPress
- Display information for all WordPress installations
- Manage your available WordPress plugins
- Add a WordPress installation to the WordPress Toolkit
- Manage WordPress plugin and theme sets
- Manage WordPress Toolkit Smart Updates for a WordPress site
- Manage your available WordPress themes
- Update a WordPress site URL
- List all available WordPress versions for WordPress Toolkit
- Execute a wp-cli command to the given WordPress installation
- Update the wp-config.php file settings
- Install a WordPress Toolkit license
- Update the operation system type and version
CPanel & WHM® has introduced a revolutionary new way to manage WordPress sites. The WordPress Toolkit (WPTK) empowers web hosting providers and site owners to install, secure, and configure multiple websites in a single easy-to-use interface.
Table of Contents
- Overview
- Create a WordPress site backup
- Clear a WordPress installation cache
- Clear the WordPress Toolkit cache
- Display the WordPress Toolkit help documentation
- Clone a WordPress site to a domain and/or subdirectory
- Manage WordPress Toolkit configuration settings
- Copy file and database table data from one WordPress site to another
- Detach a WordPress site from WordPress Toolkit
- Display information about a WordPress installation
- Install a new WordPress site on a domain
- Display the available locales for a version of WordPress
- Display information for all WordPress installations
- Manage your available WordPress plugins
- Add a WordPress installation to the WordPress Toolkit
- Manage WordPress plugin and theme sets
- Manage WordPress Toolkit Smart Updates for a WordPress site
- Manage your available WordPress themes
- Update a WordPress site URL
- List all available WordPress versions for WordPress Toolkit
- Execute a wp-cli command to the given WordPress installation
- Update the wp-config.php file settings
- Install a WordPress Toolkit license
- Update the operation system type and version
WordPress® Toolkit Command Line Interface
Valid for versions 92 through the latest version
Last modified: April 21, 2021
Overview
This document lists all of the commands available via the WordPress® Toolkit command line interface.
Create a WordPress site backup
Options
This command accepts the following options:
Description | |
---|---|
-instance-id | The WordPress installation’s ID. |
-domain-name | The domain name. |
-path | The relative filepath from the domain’s document root directory. For example: /subdirectory |
-operation | The action to perform:
|
-filename | The backup file’s name. |
-format | Output the data in a specific format:
raw data output. |
Example
Clear a WordPress installation cache
Options
This command accepts the following options:
Option | Description |
---|---|
-instance-id | Required The WordPress installation’s ID. |
-domain-name | Required The domain name. |
-path | Required The relative filepath from the domain’s document root directory. For example: /subdirectory |
-format | Output the data in a specific format:
raw data output. |
Example
Clear the WordPress Toolkit cache
Display the WordPress Toolkit help documentation
Options
This command accepts the following options:
Option | Description |
---|---|
-command | Display a WordPress Toolkit command’s help documentation. |
Example
Clone a WordPress site to a domain and/or subdirectory
Options
This command accepts the following options:
Option | Description |
---|---|
-source-instance-id | Required The source WordPress site ID to clone. |
-target-domain-name | The target domain name to clone the WordPress site ID to. |
-target-path | The path inside the target domain’s document root for cloning the WordPress site. This option defaults to the domain root. |
-target-db-name | The target database name. If you do not use this option, the command automatically creates the database’s name. |
-target-db-user-login | The username of the target database user. To specify a password for the database user, use the TARGET_DB_USER_PASSWORD environment variable. If you do not use this option, the command automatically creates the username. |
-force-overwrite | Whether WordPress Toolkit will overwrite data on the target domain and path, ignoring any existing WordPress installations and other site data.
no . |
-format | Output the data in a specific format:
raw data output. |
-show-progress | Whether to display the operation’s progress:
json output format. |
Example
Manage WordPress Toolkit configuration settings
Options
This command accepts the following options:
Description | |
---|---|
-operation | Required The action to perform:
|
-option-name | The configuration setting’s name. The setting’s name is case-sensitive and cannot be a read-only configuration setting. |
-option-value | The new configuration setting value. |
-format | Output the data in a specific format:
raw data output. |
Example
Copy file and database table data from one WordPress site to another
Options
This command accepts the following options:
Option | Description |
---|---|
-source-instance-id | Required The source WordPress site’s installation ID. |
-target-instance-id | Required The target WordPress site’s installation ID. |
-data-to-copy | The data to copy:
|
-files-replace-modified | Whether to replace the target WordPress site’s files with the source WordPress site’s files, even if the source site’s files are older:
yes . |
-files-remove-missing | Whether to remove any files that exist on the target WordPress site but do not exist on the source site:
|
-db-tables-copy-mode | The database tables to copy:
|
-db-tables | A comma-separated list of database tables to copy. |
-exclude-db-tables | A comma-separated list of database tables to exclude from copying. |
-create-restore-point | Create a restore point you can use to revert any changes:
yes . |
-show-progress | Whether to display the operation’s progress:
json output format. |
Example
Detach a WordPress site from WordPress Toolkit
This command does not uninstall the cPanel account’s WordPress site.
Options
This command accepts the following options:
Description | |
---|---|
-instance-id | Required The WordPress installation’s ID. |
-domain-name | Required The domain name. |
-path | Required The relative filepath from the domain’s document root directory. For example: /subdirectory |
Example
Display information about a WordPress installation
Options
This command accepts the following options:
Option | Description |
---|---|
-instance-id | Required The WordPress installation’s ID. |
-domain-name | Required The domain name. |
-path | Required The relative filepath from the domain’s document root directory. For example: /subdirectory |
-format | Output the data in a specific format:
raw data output. |
Example
Install a new WordPress site on a domain
Options
This command accepts the following options:
Description | |
---|---|
-domain-name | Required The domain name. |
-username | The WordPress site administrator’s username. To set its password, use the ADMIN_PASSWORD environment variable. If you do not specify this value, the system generates an admin_ account with a randomized suffix value. For example: admin_jzsfbt4l |
-admin-email | The WordPress site administrator’s email address. If you do not specify this value, the system creates the admin email account. For example: admin@example.com |
-protocol | The WordPress site’s protocol:
https . |
-path | A relative filepath from the domain’s document root directory. For example: /subdirectory This option defaults to the cPanel account’s home directory. |
-version | The WordPress version number. For a list of available versions, use the --versions command. This option defaults to the most recent version of WordPress. |
-language | The WordPress site’s locale. For a list of available locales, use the --languages command. This option defaults to en_US . |
-db-name | The database’s name. If you do not specify this value, the system generates a database name using the cPanel account’s username. For example: username_wp_f0ehk |
-db-user | The database user’s username. To specify a password for the database user, use the DB_PASSWORD environment variable. If you do not specify this value, the system generates a username using the cPanel account’s username. For example: username_wp_vfcf4 |
-table-prefix | The database table’s prefix. If you do not specify this value, the system generates a prefix. |
-site-title | The WordPress site’s title, surrounded by quotes. If you do not specify this value, the system generates a random site title. |
-auto-updates | Whether to enable automatic security updates for the new Wordpress site:
true . |
-plugins-auto-updates | Whether to enable automatic updates for Wordpress plugins:
false . |
-themes-auto-updates | Whether to enable automatic updates for Wordpress themes:
false . |
-show-progress | Whether to display the operation’s progress:
json output format. |
-format | Output the data in a specific format:
raw data output. |
Example
Display the available locales for a version of WordPress
Options
This command accepts the following options:
Option | Description |
---|---|
-version | Required The WordPress version number. |
-format | Output the data in a specific format:
raw data output. |
Example
Display information for all WordPress installations
Options
This command accepts the following options:
Option | Description |
---|---|
-domain-name | The domain name. |
-plugins | Also display each WordPress installation’s number of installed plugins. |
-themes | Also display each WordPress installation’s number of installed themes. |
-format | Output the data in a specific format:
raw data output. |
Example
Manage your available WordPress plugins
Options
This command accepts the following options:
Option | Description |
---|---|
-operation | Required The action to perform:
|
-id | The WordPress plugin’s ID. |
-version | The WordPress version number. |
-source-url | The plugin’s URL. |
-path | The relative filepath from the domain’s document root directory. For example: /subdirectory |
-format | Output the data in a specific format:
raw data output. |
Example
Add a WordPress installation to the WordPress Toolkit
Options
This command accepts the following options:
Description | |
---|---|
-domain-name | Required The domain name. |
-path | Required The relative filepath from the domain’s document root directory. For example: /subdirectory |
-format | Output the data in a specific format:
raw data output. |
Example
Manage WordPress plugin and theme sets
Options
This command accepts the following options:
Option | Description |
---|---|
-operation | Required The action to perform:
|
-instance-id | The WordPress installation’s ID. |
-plugin-id | The WordPress plugin’s ID. |
-plugin-slug | The WordPress plugin’s slug name. |
-set-id | The WordPress set’s ID. |
-name | The WordPress set’s name. |
-theme-id | The WordPress theme’s ID. |
-theme-slug | The WordPress theme’s slug name. |
-format | Output the data in a specific format:
raw data output. |
Example
Manage WordPress Toolkit Smart Updates for a WordPress site
Options
This command accepts the following options:
Description | |
---|---|
-instance-id | The WordPress installation’s ID. |
-domain-name | The domain name. |
-path | The relative filepath from the domain’s document root directory. For example: /subdirectory |
-operation | Required The action to perform:
|
-format | Output the data in a specific format:
raw data output. |
Example
Manage your available WordPress themes
Options
This command accepts the following options:
Option | Description |
---|---|
-operation | Required The action to perform:
|
-id | The theme’s ID. |
-version | The WordPress version number. |
-source-url | The theme’s source URL. |
-path | The relative filepath from the domain’s document root directory. For example: /subdirectory |
-format | Output the data in a specific format:
raw data output. |
Example
Update a WordPress site URL
Options
This command accepts the following options:
Description | |
---|---|
-instance-id | Required The WordPress installation’s ID. |
-domain-name | Required The domain name. |
-path | Required The relative filepath from the domain’s document root directory. For example: /subdirectory |
-format | Output the data in a specific format:
raw data output. |
Example
List all available WordPress versions for WordPress Toolkit
Options
This command accepts the following options:
Option | Description |
---|---|
-format | Output the data in a specific format:
raw data output. |
Example
Execute a wp-cli command to the given WordPress installation
For a list of available commands and their subcommands, read WordPress’ wp-cli
documentation.
Options
This command accepts the following options:
Description | |
---|---|
-instance-id | Required The WordPress installation’s ID. |
-domain-name | Required The domain name. |
-path | Required The relative filepath from the domain’s document root directory. For example: /subdirectory |
Example
Update the wp-config.php file settings
- You can pass all
wp-config.php
file settings through environment variables. To do this, you must specify an empty parameter value. - For information about the
wp-config.php
file and its settings, read WordPress’ Editingwp-config.php
documentation.
Options
This command accepts the following options:
Description | |
---|---|
-instance-id | Required The WordPress installation’s ID. |
-domain-name | Required The domain name. |
-path | Required The relative filepath from the domain’s document root directory. For example: /subdirectory |
Example
Install a WordPress Toolkit license
Update the operation system type and version
This command may be required after converting your system from CentOS to CloudLinux™.
Additional Documentation
Table of Contents
- Overview
- Install WordPress
- Install WordPress from WordPress Toolkit
- Install WordPress from WordPress Manager
- Install WordPress as Site Software
- Install WordPress Manually
Table of Contents
- Overview
- Install WordPress
- Install WordPress from WordPress Toolkit
- Install WordPress from WordPress Manager
- Install WordPress as Site Software
- Install WordPress Manually
Last modified: October 28, 2020
Overview
WordPress®, a web-based content management system, allows users to easily create a website or blog. This document describes how to install WordPress on your cPanel account.
Install WordPress
Install WordPress from WordPress Toolkit
In cPanel & WHM version 92 and newer, users can install WordPress through the WordPress Toolkit interface.
For instructions on how to install WordPress through WordPress Toolkit, read Plesk’s WordPress Toolkit documentation.
Install WordPress from WordPress Manager
In cPanel & WHM version 70 through 90, users can install WordPress through the WordPress Manager interface.
For instructions on how to install WordPress through WordPress Manager interface, read our WordPress Manager documentation.
Install WordPress as Site Software
In cPanel & WHM version 90 and earlier, users can install WordPress as a cPAddon with cPanel’s Site Software interface (cPanel >> Home >> Software >> Site Software).
To install WordPress as a cPAddon, perform the following steps:
Navigate to cPanel’s Site Software interface (cPanel >> Home >> Software >> Site Software).
To receive a notice via email when the hosting provider installs WordPress, click here after the You currently are set to receive a notice when updates for your installs are available text.
Click WordPress.
Enter the requested information.
- To install WordPress directly into a domain’s document root, leave the installation URL’s path blank. This may overwrite any files already in the document root.
Click Install.
- If your hosting provider moderates requests for WordPress installation, click Submit Moderation Request.
- Enter a note for your hosting provider, and click Submit Request.
When the WordPress installation finishes, use your web browser to view the location that you entered in Step 4.
- For example, if you installed WordPress in the
http://example.com/wordpress/
directory, browse to thehttp://example.com/wordpress/
URL.
- For example, if you installed WordPress in the
If WordPress is not available as a cPAddon, users can ask their hosting provider to add it, or they install WordPress directly themselves. For more information, read the User installs WordPress Manually section below.
The WordPress Manager interface (cPanel >> Home >> Applications >> WordPress Manager) allows you to manage the WordPress installations on your cPanel account. The WordPress Manager interface only manages WordPress installations that you create with the RPM-based WordPress cPAddon.
Install WordPress Manually
If your hosting provider does not offer WordPress as a cPAddon, you can manually download WordPress from the WordPress website and install it on your site.
For more information, read installation instructions from WordPress and their cPanel-specific instructions on how to create a database for WordPress.
Manual installations may encounter issues due to conflicting .htaccess
files or database connection errors:
In the following examples, the following statements are true:
example.com
represents the domain name.example
represents the account name.subdomain
represents a subdomain’s directory.addon.com
represents an addon domain name.
Document root issues
Due to potential conflicts in the .htaccess
file, do not configure multiple WordPress installations to share a single document root. If you experience difficulties with WordPress, check the following requirements:
Each cPanel account user can host only one installation of WordPress in the document root directory.
The following are examples of document root directories:
/home/example/public_html/
/home/example/public_html/addon.com
/home/example/public_html/subdomain
Each directory may only contain one WordPress installation.
If the subdirectories are not a document root, cPanel account users can install additional WordPress installations in subdirectories under the domain’s home/example/public_html directory.
The following examples demonstrate installations that use the wordpress subdirectory:
Under the document root for the main domain:
/home/example/public_html/wordpress
Under a subdomain:
/home/example/public_html/subdomain/wordpress
Under an addon domain:
/home/example/public_html/addon.com/wordpress
For more information, visit the WordPress website.
Database connection errors
If WordPress returns a database connection error, ensure that the database’s name and password in the wp-config.php
file are identical to the database credentials in your account.
For a document root installation, the wp-config
file exists in the /home/username/public_html
directory, where username
represents the cPanel account name.
Cpanel Wordpress Dns
To change the database’s username or password, use cPanel’s MySQL Databases interface (cPanel >> Home >> Databases >> MySQL Databases).
To test a username and password combination, run the following command (where db_user
represents the database’s authorized username):
Cpanel Wordpress Toolkit Install
After you enter the command, enter the user’s password. The system will respond with a success or failure message.