If your builder version is (3.x.xxx) – please follow migration instructions to update to the new builder version (On-premise only).In “New Builder Version (v4)” block – mark checkbox “Enabled”.Choose a Brand that you need to migrate.Possibly it will need one-time manual correction (~5 min). Note: Cusotmers have opportunity to switch back (if needed). Note that practically all these steps are executed quite quickly and usually client does not see them all in publication process bar. When the uploading ends then no second verification is made. During files re-uploading the connection to FTP is made again as described in step (3). 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 this step the state "verifying." is displayed 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 builder connects to website hosting on port 80 or 443. 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. verification - this is the 4th step of deploying part.It can take from few seconds to few minutes (depending on website size and connection speed between builder and hosting servers) Note that only changed files are uploaded from last publication. During this step website files are uploaded to hosting. files uploading - this is the 3rd step of deploying part.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") After successful connection to FTP server builder tries to log in with username and password of FTP account. logging to hosting FTP account - this is the 2nd step of deploying part.remote IP address of server which made API call to builder during opening ĭuring this step the state "connecting." is displayed.IP address of domain which was opened (in case if "Custom (API)" is used then it is defined by parameter "baseDomain" ).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").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): The builder tries to establish FTP connection with hosting server where it will publish website. connection to hosting FTP server - this is the 1st step of deploying part.During this step the state "building website." is displayed website generation - during this step builder generates final website files which will be published to client's hosting.This step takes <1 second when it completes the state "preparing." is displayed ![]() saving draft - this step saves website draft - the same action which is triggered when pressing button "Save Draft". ![]() The process can be divided into several parts which are executed one after another in specified order: The publication process is the process which starts when the client presses button "Publish" in builder toolbar.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |