PanelAlpha Documentation
Back Home
Live Demo Get Started

Predefined WordPress Template

Documentation
    Introduction FAQ Automatic Tester
Getting Started
    Requirements Installation Update Guide SSL Configuration Resetting Admin Password Translations Health Check Diagnostic Mode Additional Configuration
Background Billing
    Introduction Billing System Quick Registration Social Media Login Client Area
Admin Area
    Dashboard Instances Services Users Logs Migrations
Onboarding Methods
    Quick Onboarding Super Quick Onboarding Standard Onboarding
System Configuration
    General Configuration Branding Hosting Servers DNS Servers Email Servers Remote Backups Plans Notifications Automatic SSL Themes, Plugins and Packages
Hosting Server Connections
    Hosting Scenarios PanelAlpha Engine for Docker cPanel Plesk DirectAdmin WP Cloud
Email Server Connections
    Mailcow cPanel
DNS Server Connections
    Cloudflare cPanel DNS Only PowerDNS
Billing Systems Integrations
    WHMCS
Billing Scenarios
    Introduction Single WordPress Instance Predefined WordPress Template Multiple WordPress Instances Cross-Selling Paid Plugins and Themes Cross-Selling Domains Plan Upgrade
Integrations
    Integrated Solutions Matomo Google Analytics Let's Encrypt Google PageSpeed Insights DB-IP Extendify WithoutDNS
Client Area - Instances
    List of Instances Creating New Instance Importing Existing Instance Instance Details Changing Domain Sharing Instances Monitoring Backups Plugins Advanced Settings
Client Area - Hosting
    Summary Domains FTP Accounts MySQL Databases Cron Jobs File Manager DNS Zone Editor Email Addresses Email Forwarders

# Predefined WordPress Template

  • Offering a predefined WordPress Template
  • Workflow illustration
  • Configuration in PanelAlpha
  • Configuration in WHMCS

Before proceeding further to find the gist, please ensure that you are already familiar with the "Introduction" article. This article discusses the necessary steps that must be completed prior to utilizing the information provided in this section.

*Go back to "Introduction" now.

# Offering a predefined WordPress Template

This is a similar workflow as offering a single instance, in this case, however, the customer will have their WordPress automatically installed when the service is activated. This is a recommended configuration for companies offering their own instance templates.

For example: Site with predefined plugins, theme and configuration that works perfectly for a dental clinic business.

# Workflow illustration

  1. End-customer orders a new service in a billing system, for example WHMCS, in our example that will be: "Dental Clinic"
  2. They go through the standard ordering process.
  1. After the payment for the ordered product is complete:
    • The end-customer will receive an email message with details about their service
    • From the client area in WHMCS they can directly proceed to the new PanelAlpha user page. Simply use the "WordPress Management" section in the menu - it uses SSO to automatically authenticate them into PanelAlpha
    • Alternatively, they can go to their service page and click "Log In To PanelAlpha" - it uses SSO to automatically authenticate them into PanelAlpha as well
  1. Once they are redirected to PanelAlpha, again SSO is used to for automatic authentication.
  2. The first page that they see is the information on the process of the instance installation. Wait a moment until the process is complete.
  1. The new site is ready for the client to manage! The end-customer, after opening the dashboard, can access their new site.

# Configuration in PanelAlpha

Underneath, you will find steps describing exactly what to do in your PanelAlpha admin area to achieve the above scenario.

  1. To start using instance templates, you must first create them. Navigate to Admin Area → Instances → Instance Details and locate the action button labeled Save as Template. Provide a name for the template and confirm by pressing Save. Currently, saving an existing instance as a template is the only method available for creating them.
  1. The created template will appear on the list of Instance Templates, make sure its status is active, as only then you will be allowed to assign it to a plan.

  1. Let's proceed to the configuration of a plan that allows creating instances from templates. For demonstration purposes, we will show how it works using the recommended Quick Onboarding method.

  2. Create a new plan, fill in the details section by providing the plan name - we have set it to 'Dental Clinic - Predefined Template', define the instances limit (1), and fill out the remaining options according to your preferences.

  1. In Onboarding tab, make sure to select the instance template that will be used by default for creating the new website. In our case, we are leaving the "Allow to choose themes" and "Ask for domain" unselected and "Force installation for new users after login" selected. This way, after being logged in to PanelAlpha client area, the end user will simply have the website installed automatically without being asked any questions and steps to complete.

  1. Define the Hosting, DNS and Email servers details to establish the connection.

  2. Define the Domains creation rules. Skip the "Plugins&Themes" section as in our case you are going to offer a predefined instance template with already installed plugins and themes.

  3. Enable automatic backups and set up the frequency. You may skip the "Other" section. Save the changes to confirm creating the plan.

# Configuration in WHMCS

Here are prompts on how to set up and configure a product in the billing system (WHMCS) that will be offered for sale to your end-customers.

  1. Before you proceed to your WHMCS and start server and product configuration, you must previously generate your API Token, you will need it in further steps.

  2. Once you enable the API Token, you will get a one time access to it. Keep in mind that this is the only moment when you see it, so please copy it and keep in a safe place!

  3. Proceed to your PanelAlpha admin area → Configuration → Admins → API Token.

Once ready, move to your WHMCS platform and begin the configuration.

  1. Under System Settings → Products/Services → Servers create a new server. Fields that must be filled out are:
    • Name - any name for your server.
    • IP Address - provide the IP address with a port number where your PanelAlpha is located. The Hostname field may be lefty empty, after saving the changes, it will be filled in automatically.
    • API Token - PanelAlpha token generated as described in the steps above.
  1. Under System Settings → Products/Services → Servers create a new group of servers and assign the just created server to this group.
  1. Next, proceed to System Settings → Products/Services and create a new group of products.
  1. Once you have the group, you may finally create your PanelAlpha product.
    • Product Type - set it to "Shared Hosting"
    • Product Group - select the just created group
    • Product Name - in our example that is: "Dental Clinic"
    • Module - please select "PanelAlpha" from the dropdown menu
      Press "Continue" to move to the next step.
  1. Now, go to Module Settings section. As the module name has been already selected, find the server group where the server you need to connect with is assigned in the dropdown menu. Once selected, all the module configuration settings will appear.
    • PanelAlpha Plan - select the plan you wish to assign to this product In the described now example, that will be "Dental Clinic - Predefined Template"
    • Based on the selected plan, all the further settings will be automatically filled in. Save the changes once the settings configuration is ready.
  1. Finally, set the pricing details for your product, you may do that in the "Pricing" tab.