生成器安装/更新

专业技术支持

Our team install Site.pro builder for free for new clients with a paid license. Just let us know by creating a ticket and providing us needed login details.

You can find login details which will be needed for builder installation below.

• If using cPanel:
  • preferrably ROOT access to server https://[your-cpanel-host]:2087 (where username = "root").
  • Access to cPanel account https://[your-cpanel-host]:2083 where you want site builder to be installed. It can be a separate clean account or already used account — then builder can be installed on sub-domain or addon domain.
• If using Plesk:
  • preferrably ROOT or Admin access to server https://[your-plesk-host]:8443.
  • Access to Plesk account where you want site builder to be installed.
• Other:
  • ROOT access to server. It can also be a clean server — then our team will install all required software (Apache, PHP, MySQL) as well.

Server

Requirements:

• Apache 2.2 (or newer) (modules: rewrite (rewriting from .htaccess must be enabled), headers)
• PHP 5.3.6 (or newer) (extensions: gd (version 2+), exif, sqlite, pdo, pdo_mysql, pdo_sqlite, json, curl, mbstring, iconv, xml, openssl, zlib, zip)
  Note: Published websites require PHP 5.3.6 (or newer) and Apache 2.2 (or newer) too.
• MySQL 5.5 (or newer)
• ionCube Loader (newest version possible) ionCube install instructions can be found at ionCube site: http://www.ioncube.com/loaders.php
  The recommended way of installing ionCube loader is by downloading loader wizard loader-wizard.zip, extracting it to web-servers document root and opening it via browser and then just following install instructions from there.
• Web accessibility through domain (sub-domain). Local builder installations are not supported. Make sure that you specified correct domain (sub-domain) for builder. It must be accessible publicly on the WEB.

Recommendations for builder server:

[Hardware]
CPU: 2GHz
RAM: 2048MB
Storage (HDD or SSD): 20 GB (it can vary depending on number of customers using site builder) (see how the space can be optimized).
(This is recommended hardware requirements, depending on concurrent user count you might be OK with half or even less)

[OS]
Ubuntu / Debian / CentOS / Windows (should work on any other operating system)

Nginx if used instead of Apache

... # click to expand

listen       80;
server_name  some.builder.domain;

charset utf-8;
root /home/builder/public_html;

index  index.php;

location ~ /(\.ht|error_log|php_errors\.log|config\.json|config\.json\.backup)|^/(vendor/|src/) {
	deny  all;
}

location ~ \.php$ {
	fastcgi_pass   127.0.0.1:9000;
	fastcgi_index  index.php;
	fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
	include        fastcgi_params;
}

location ~ ^((?:/v3|)/data/[^/]+/[^/]+/(?:[^/]+/)?(?:out|preview)/)(.*)$ {
	try_files $uri $uri/ $1/sitepro/$2 $1/sitepro/$2/ $1/sitepro/index.php?$args;
}

# For installer config test.
location /installer/rewrite_test/ { return 200 'OK'; }

location /v3/ {
	try_files $uri $uri/ /v3/index.php?$args;
}

location / {
	try_files $uri $uri/ /index.php?$args;
}

... # click to expand

listen       80;
server_name  some.site.domain;

charset utf-8;
root /home/site/public_html;

index  index.php;

location ~ /(\.ht|error_log|php_errors\.log)|^/sitepro/(vendor/|src/) {
	deny  all;
}

location ~ \.php$ {
	fastcgi_pass   127.0.0.1:9000;
	fastcgi_index  index.php;
	fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
	include        fastcgi_params;
}

location / {
	try_files /sitepro$uri /sitepro$uri/ /sitepro/index.php?$args;
}

安装

1. Download site builder archive and extract it to your virtual host www folder:
   
   • for PHP 5.3.6 - 5.5.x — SitePro_Builder_v4.tar.gz
   • for PHP 5.6.0 - 7.0.x — SitePro_Builder_v4_php7.tar.gz
   • for PHP 7.1.0 - 7.4.x — SitePro_Builder_v4_php71.tar.gz
2. Open link in your browser (ex.: http://your-builder-domain.com/installer/) and follow instructions from there.
   Installation script can also be executed using CLI for automated installs (without requiring user interaction):
   php installer/index.php "/installer?host=[builder-hostname]&dbHost=[database-host]&dbName=[database-name]&dbUser=[database-user]&dbPass=[database-password]&cfgApiUser=[API Username from brand]&cfgApiPass=[API Password from brand]&cfgBrandId=[Brand ID]"
   Note:
   When running CLI installer will verify PHP CLI configuration and not the actual PHP configuration that will be used for running builder. Make sure they match.
3. When installation completes, delete folder installer.
4. Setup builder CRON. This will help you to optimize builder used space and keep builder up-to-date.

影片指南

更新

1. Login to builder server console per SSH.
2. Run the following command:
   cd [BUILDER_DIR] && php index.php /api/update-builder
   where replace "[BUILDER_DIR]" with a real path where you have builder installed.
Note:
If you have multiple PHP versions on server and PHP CLI version differs from PHP WEB version used by builder then specify correct PHP executable in CRON command. For example:
cd [BUILDER_DIR] && /usr/bin/php7 index.php /api/update-builder

迁移到版本4.x.x

In order to migrate your current builder installation which is of version 3.x.x you need to execute manual update with builder archive of version 4.x.x. (Make sure you execute all steps).

After migration to version 4.x.x the new builder will become default for all clients but the client will always be able to return back to builder v3. After switching to old builder it will be loaded with URL:
"http://your-builder-domain.com/v3/".

For those who had custom templates and/or custom plugins

After migration all custom templates and plugins will be moved to new builder and will automatically be converted so that their structure correspond to new builder version. After that custom templates and plugins will no longer be available on version v3. In order to bring them back to old builder you need to:

• copy all folders of your custom templates from "templates" to "v3/templates"
• copy all folders of your custom plugins from "plugins" to "v3/plugins"

HTTPS

In order to run builder under HTTPS protocol you need to take the following steps:

• Update builder domain in your brand from "your-builder-domain.com" to "https://your-builder-domain.com".
• Open file "config.json" located in your builder web-root directory and update parameter "siteProApiUrl" to be also with "https://".

额外配置

• String disabledHostingPlans — Plans separated by comma for which builder will not work default: -
• String enabledHostingPlans — Opposite to "disabledHostingPlans". If specified "disabledHostingPlans" will be ignored default: -
• String disabledHostingPlansMessage — Message to show when hosting plan matches the one from specified in "disabledHostingPlans" option or when hosting plan is not included in plans specified in "enabledHostingPlans" option (used together with "disabledHostingPlans" or "enabledHostingPlans" accordingly). The value is multilingual.* default: default sentence(1)
• String yandexMetrikaCode — Yandex Metrika ID for builder default: -
• Boolean yandexMetrikaCodeDemoOnly — Use Yandex Metrika ID only in public demo builder default: false
• Object ui — Object adding extra buttons to builder toolbar - default: example below(2)
• Boolean useSecureFtp — Defines whether to use FTP with SSL encryption during publishing. default: false
• String theme — Builder UI theme ID to use (currently only "modern" is available). Will be ignored if "themeUrl" is set. default: -
• String themeUrl — URL to css file to change builder UI style. default: -
• String googleMapsApiKey — Google.com Maps API key. Required to enable Google Maps plugin (get it from here). default: -
• String googleFontsApiKey — Google.com Fonts API key. Required to enable Google Fonts feature (get it from here). Note: Google Fonts also works with parameter "googleMapsApiKey" if set. default: -
• Boolean logTemplateUsage — If true template usage statistics will be logged to database (enable only if you are using automated builder updates). default: false
• Boolean enableForcedHttpsPort — If true will show forced HTTPS port option in builder settings dialog. default: false
• Boolean noUrlRewrite — If true will disable URL rewriting for published websites. default: false
• Boolean defaultForcedHttpsEnabled — If true then forced HTTPS option will be enabled in new websites by default. default: false
• Boolean defaultForcedRedirEnabled — If true then forced redirection option will be enabled in new websites by default. default: false
• Boolean defaultForcedRedirOption — Forced redirection option chosen by default (1 - redirect from www to non-www, 2 - redirect from non-www to www). default: 1

• (1) — "The software is not available for your hosting plan."
• (2) — example shows how to add two extra buttons in builder toolbar:

  "ui" : {
      "toolbars" : {
          "control-toolbar-cont" : {
              "items" : [
                  {
                      "name" : "Prices",
                      "img" : "/path/or/url/to/prices.png",
                      "url" : "http://yoursite.com/prices",
                      "order" : 21
                  },
                  {
                      "name" : "Domains",
                      "img" : "/path/or/url/to/domains.png",
                      "url" : "http://yoursite.com/sign-up",
                      "order" : 22
                  }
              ]
          }
      }
  }

  All default builder buttons have orders multiple to 20, that is 20, 40, 60 etc.
  Parameters "name" and "url" are multilingual (please see explanation below).
• * — Multilingual value can be either a string like:

  "disabledHostingPlansMessage": "My message"

  or an object containing values for multiple languages like:

  "disabledHostingPlansMessage": {
      "en": "My message",
      "it": "Il mio messaggio"
  }

CRON available since version 3.7.280

Setup CRON to be executed automatically every minute:

1. Run command crontab -e to open CRON editor.
2. Append this line at the end:
   * * * * * cd [BUILDER_DIR] && php cron.php
   where replace "[BUILDER_DIR]" with a real path where you have builder installed.
3. Save new CRON.

Currently CRON includes the following tasks:

• builder update (run once per day) — This cron task keeps builder always up-to-date.
• temporary/old files cleanup (run twice per day) — during builder work it accumulates some garbage (temporary/old files) which can take a lot of space with time. This cron task keeps builder clean and space optimized.
• free disk space checking (run every 5 minutes) — This cron task checks free disk space the builder is running on. Once the disk is full it disables builder and shows corresponding message for clients. This is important because during lack of free space builder can work unpredictably and even damage clients' site data used by builder. We recommend to sometimes check free disk space on builder server and ensure that there are at least 2 GB available.

Cleanup available since version 3.7.263

During normal use of builder, temporary files are being created, and after some time they might start using a lot of disk space.
You can use this CRON to regularly (ex. daily) cleanup those files:

1. Run command crontab -e to open CRON editor.
2. Append this line at the end:
   0 0 * * * cd [BUILDER_DIR] && php index.php /cron/cleanup/temp-files
   where replace "[BUILDER_DIR]" with a real path where you have builder installed.
3. Save new CRON.

自动更新

Setup CRON to be executed automatically in specific periods of time (ex. every day):

1. Run command crontab -e to open CRON editor.
2. Append this line at the end:
   0 0 * * * cd [BUILDER_DIR] && php index.php /api/update-builder
   where replace "[BUILDER_DIR]" with a real path where you have builder installed.
3. Save new CRON.

手动更新

1. Download site builder archive and extract it to builder installation folder overwriting all files.
   Important! Do not delete files before extraction:
   
   • for builder version 4.x.x (new)
     • for PHP 5.3.6 - 5.5.x — SitePro_Builder_v4.tar.gz
     • for PHP 5.6.0 - 7.0.x — SitePro_Builder_v4_php7.tar.gz
     • for PHP 7.1.0 - 7.4.x — SitePro_Builder_v4_php71.tar.gz
   • for builder version 3.x.x (legacy)
     • for PHP 5.3.6 - 5.5.x — SitePro_Builder.tar.gz
     • for PHP 5.6.0 - 7.0.x — SitePro_Builder_php7.tar.gz
     • for PHP 7.1.0 - 7.4.x — SitePro_Builder_php71.tar.gz
2. Execute command:
   cd [BUILDER_DIR] && php index.php "/api/update-builder?skip_extract=1"
   where replace "[BUILDER_DIR]" with a real path where you have builder installed.
   
   Note:
   If you have multiple PHP versions on server and PHP CLI version differs from PHP WEB version used by builder then specify correct PHP executable in when executing this command.
   For example:
   cd [BUILDER_DIR] && /usr/bin/php7 index.php "/api/update-builder?skip_extract=1"
   
3. Delete installer folder (if it exists).

更改PHP版本

If you change PHP version with already installed builder then you will need to manually update builder afterwards (see documentation) in case if PHP version changed range (from the list of PHP versions ranges specified above).