No announcement yet.

What happens during an upload?

  • Filter
  • Time
  • Show
Clear All
new posts

  • What happens during an upload?

    When "Web|Update Website" is requested the following actions are performed in sequence.

    Checking Catalog...
    All the .cat (section information) and most of the .fil (configuration information) files are generated at this time. The generated files are saved to the site directory.

    Checking HTML pages...
    SellerDeck goes section by section and generates the HTML files for all the sections. The HTML templates used for the cart or checkout, search page, site map, etc. are also generated at this time. The generated pages are saved to SiteHTML folder.

    Checking brochure pages...
    If brochure is enabled the related HTML files are generated at this phase. The generated pages are saved to SiteHTML folder.

    Checking search indices...
    SellerDeck generates the index file for online search at this phase. The search index is saved to the site directory.

    Reviewing files...
    SellerDeck checks if there were a previous upload and if so determines which files have changed and should be uploaded (by using the file dates). This does not happen if you use 'Web | Refresh Website'.

    Sending base files...
    SellerDeck creates an ftp connection and uploads the base files (perl scripts) to the server. When the upload is done a new ftp session is created and the file permissions are adjusted as required.

    Purging files...
    SellerDeck investigates the folders on the server to find any files uploaded previously but not required at the moment. If such a file found on the server the file is removed.

    Sending catalog files...
    The content of the acatalog directory (and the applet files) are uploaded at this phase. All the HTML files (catalog and brochure), BLOBs, images and other files are uploaded to the acatalog directory via ftp (by default).

    Uploading Digital Download Files...
    If Digital Download is enabled then the DD files are uploaded in this separate phase. The methods mentioned above (Sending catalog files) apply here.

    Merging incremental updates at the web site
    There are a few large data files (search index, customer account details) used in SellerDeck Ecommerce. It would be quite ineffective to upload them in case of any small change. Therefore SellerDeck keeps a copy of these files from the previous upload (if there were any) and compares to the current one - making updates as necessary. assembles these files.

    PLEASE NOTE: With the introduction of version 9.0.3 SellerDeck now uses multiple threads for uploading, so uploading takes place at the same time as generation. This dramatically decreases upload time for large stores