FAQ

Subdomain should be created in the hosting panel, then your clients will have access to the builder for a new subdomain via their hosting panel.

If you don’t have a brand:

• Click "Add brand";
• Choose Cloud or On-Premises and press save;
• Follow the steps below.

If you have a brand:

• Click "Manage" button next to your domain;
• Fill in the information about your website builder;
• Select "Install plugin";
• Choose required panel and press install;
• Follow the installation guide or create a ticket and we will help you install with the installation.

The publication process is the process which starts when the client presses button "Publish" in builder toolbar. The process can be divided into several parts which are executed one after another in specified order:

• saving draft — this step saves website draft — the same action which is triggered when pressing button "Save Draft". This step takes <1 second; when it completes the state "preparing..." is displayed;
• website generation — during this step builder generates final website files which will be published to client's hosting. They consist mostly of .php, .js, .css and different media files. During this step the state "building website..." is displayed;
• connection to hosting FTP server — this is the 1st step of deploying part. The builder tries to establish FTP connection with hosting server where it will publish website. The connection is made with 3 different IPs in specified order until it finally connects (when it connects with some of them it does not try the rest):
  • IP address which was passed by hosting control panel API to builder plugin when builder was opened (in case if "Custom (API)" is used then it is defined by parameter "apiUrl");
  • IP address of domain which was opened (in case if "Custom (API)" is used then it is defined by parameter "baseDomain" [or "domain" if "baseDomain" is not provided]);
  • remote IP address of server which made API call to builder during opening;
  During this step the state "connecting..." is displayed;
• logging to hosting FTP account — this is the 2nd step of deploying part. After successful connection to FTP server builder tries to log in with username and password of FTP account. Builder gets FTP data from builder plugin on hosting control panel (API) (in case if "Custom (API)" is used then FTP details are defined by parameters "username" and "password");
• files uploading — this is the 3rd step of deploying part. During this step website files are uploaded to hosting. Note that only changed files are uploaded from last publication. This is usually the longest part. It can take from few seconds to few minutes (depending on website size and connection speed between builder and hosting servers);
• verification — this is the 4th step of deploying part. After successfully uploaded website files (only changed) to hosting then builder makes verification whose purpose is to check if all required website files are on hosting and they are all correct. During this step builder connects to website hosting on port 80 or 443. The connection is made also with different IPs in the same order and same IPs as during builder connection to FTP server with one difference — firstly it tries IP address which could successful establish connection to FTP server. During this step the state "verifying..." is displayed;
• files re-uploading (full) (optional) — this step is taken only in the case if verification returned negative result, that is some website file on hosting was removed or changed since last publication. During files re-uploading the connection to FTP is made again as described in step (3). When the uploading ends then no second verification is made.

Note that practically all these steps are executed quite quickly and usually client does not see them all in publication process bar.

For Cloud brand: Unfortunately the limit of restorable backup files cannot be changed if you use premium brand. For backup file restoration which exceeds builder limit please create ticket on tickets page and specify us website domain and external link to backup file which you want to restore. Our team will restore it and we will notify you.

For On-Premises brand: The builder limit parameter directly depends on PHP parameters post_max_size and upload_max_filesize on server where builder is installed. So the limit is a smaller value of these 2 parameters. Just update values of these parameters in PHP settings and the limit in builder will automatically change.

Important! If you have your on-premises builder domain configured with CloudFlare (or use different proxy service), then specified PHP parameters must also be raised in that service (by default it uses 128M).

If you want to run builder domain under HTTPS protocol you need to do the following steps:

For Cloud brand:
Open licenses page, expand your Cloud brand and click button "Add SSL". Wait until the process is finished, and then site builder will start working with HTTPS protocol having a valid SSL certificate.

For On-Premises brand:.

• Open your On-Premises brand and change builder domain by adding "https://" at the beginning of it (e.x. "builder.yourdomain.com" -> "https://builder.yourdomain.com");
• Open file "config.json" in your builder web root directory and update parameter "siteProApiUrl" by changing "http://" part to "https://";
• Go to Site.pro licenses page, open On-Premises brand and click "Apply" button.

After license upgrade, Site.pro badge is still displayed on websites. Your logo is starting to be displayed only on newly created websites.

Documentation page — https://site.pro/docs/builder/

Benefits of website builder v4:

• 100% responsive website;
• New website builder features;
• Live preview.

Note: Cusotmers have opportunity to switch back (if needed).
Possibly it will need one-time manual correction (~5 min).

Website Builder upgrade from v3 to v4:

• Open license page;
• Choose a Brand that you need to migrate;
• Click “Manage”;
• Choose “Customize builder”;
• In “New Builder Version (v4)” block – mark checkbox “Enabled”;
• If your builder version is (3.x.xxx) – please follow migration instructions to update to the new builder version (On-premise only).

Your customers will be able to implement migration from v3 to v4 in the website builder by themselves.

Mass Websites migration from v3 to v4:

• Open license page;
• Choose a Brand that you need to migrate;
• Click “Manage”;
• Choose “Mass migration”;
• Click on “Add Websites to queue“;
• Specify domains that you need to migrate;
• Click “Add”.

If you want to have website builder and mail server on the same domain, you need to add MX records to that domain (pointing to your mail server IP address).

The Site.pro website builder accessible only via your Hosting Panel or Site.pro account.