Upgrading Rapido

There are two types of Rapido releases – majors and minors:

  • A major release is from Rapido i.e 2.* to 3.*. May contain breaking changes.
  • A minor release is from i.e. 2.01 to 2.1.

Upgrading from one major to another is a handheld process, and we cannot guarantee a simple and problem-free experience. Upgrading from one minor to another is a straight-forward and low-risk procedure, as described below.

Upgrades must always be applied to a test environment before a live solution is upgraded. 

Since Rapido is FREE to use, please find below some limitations:

If an upgrade fails, Dynamicweb cannot be held responsible - and is not responsible for investigating why the upgrade fails, as this can be a result of custom implementation. We will however, accept bug reports and change Rapido implementation in such a way that minor updates can be conducted if the error is in Rapido solution and is not coming from any kind of customisation.

New versions of Rapido can contain new content (Pages, feeds, products, settings etc.) that will not be part of an update, minor or major, and these have to be added manually upon upgrades. This is done by looking at a new standard Rapido and make the same configuration on the solution being upgraded. If you want to include select features from a major release in an older project, it is often possible to manually merge the feature to an older project.

Updates are a manual process conducted by the partner. Dynamicweb does not cover the costs of upgrading.

When upgrading your Rapido 3.2 solution to a Rapido 3.3 your old content pages and paragraphs will not magically be using on the new column/row grid system for Visual editor. Your content will still be presented and up and running. But you will get a mix of new/old pages and paragraphs types. Also, read the release notes here

However, it is possible to change all your old pages to the new content model if needed, but this is a manually process. Or you can leave the old pages as it is and only create the new content pages with the new visual editor.

Follow this upgrade guide

  1. Backup your solution
  2. Export the website settings on the existing solution
  3. Download the Rapido upgrade zip package
  4. Unzip upgrade file
  5. Copy the Files folder from the upgrade zip and overwrite the existing Files folder on your solution
  6. IIS recycle
  7. Import your old website settings - the ones you exported during step 2
  8. Save and close
  9. In Settings/Itemtypes click Update in the ribbon bar
  10. In Settings/Web and HTTP/Security. Enable checkbox “Activate antispam functionality”
  11. In Settings/Ecommerce/Advanced configuration/Shopping cart. Enable checkbox “Do not delete carts with 0 orderlines “. (If you want to use Order draft functionality)

Convert Old pages in Rapido 3.2 to Rapido 3.3 manually to support Visual editor

(The Rapido 3.3 full packages consist only of the new pages and paragraphs types, which is supported by the visual editor, set up from scratch. On this packages you can see how we have set the pages up with the new content page)

Optional: If you decide to convert all your old pages to the new content pages manually to support visual editor please follow this To-do-list. Be aware that this will be a time consuming process.

Convert these pages

  1. Content pages e.g. landing page, about page, contact
  2. Log in/log out/Create account pages
  3. Customer center pages e.g.
    • Dashboard, My profile, My addresses, My orders, My favorites, My Quotes etc.
  4. Cart/empty cart page
  5. These pages do not support the new content pages:
    • Dynamic articles, Newsletter emails, Printable papers, Content in the Feeds folder

Example: Setting up e.g. the Sign in page

  1. Create page select Content page (supported by visual editor)
  2. Click visual editor on the ribbon bar, this will redirect you to the visual editor mode
  3. On the Panel on the left. Click on the Row tab, find section Empty rows.
    • Select either a Full row or 1-2-1 split row and drag it to the area.
    • Set height to auto.
  4. On the panel select Column tab, go to section empty columns
    • Select the App column item type and drag it to the empty row you just applied earlier
    • A modal will appear
    • click on App in the ribbon bar select Extranet App and fill in the usual information and selected template needed for the Sign in page

Now repeat the same process for the rest of the pages that needs to be converted. If you need more general introduction to the Visual editor please read it here.

Are you still using the old News -, Blog-, Events- list?

Go to Website settings on ribbon bar select Layout tab, select Item page layouts. Insert Page.cshtml for the list that is needed e.g. on Event list

Hide old Page and paragraph options & check restrictions

After converting all the pages to the new content page. There are some settings and permission to setup that can be a benefit, in order not to confuse the end user by displaying both old and new page and paragraphs.

  1. In Settings/Editing/Interface settings enable checkboxes
    • “Disable Remove standard paragraphs”.
    • “Disable standard page”.
  2. Go to website setting on ribbon bar select tab Layout select Rapido: ContentPage.cshtml
  3. Go to website settings on ribbon bar select tab Website and Item type: Now select Content page properties on Page settings
    • Important!: You need to go through all your new pages and “save & close” you Page properties to get rid of the template error
  4. In Settings/Itemtype/Content folder/Content page select restrictions on the ribbon bar ensure that these checkboxes are enabled.
    • Allow in websites – “All”
    • Allowed parents – “Allow in root of website” & “Allow under a regular page”
    • Allowed children – “App”, “Breadcrumb”, “Buttons” “Card paragraphs”, “Carousel”, “Content page”, “Cover row”, “Image” , “Navigation”, “Quote”, “Search paragraphs”, “Seperation line”, “Simple map”, “Standard paragraph one”, “Standard paragraph three” , “Standard paragraph two”, “Video”.

To upgrade from one minor to another minor within the same major:

  • Keep in mind that if you have made custom changes to the standard Rapido files then be they may be overwritten, so make sure to follow these bullets
  • If you have changed the standard website settings, be sure to export the website settings on your existing solution, so that you can import them again later
  • Backup your /Files folder and the solution database
    • These include your GlobalSettings.aspx file in which you've entered your database information when you first installed Rapido - this will be used later
    • In /System/Items/WebsiteSettings/ you can find your exported website settings
  • Download the new Rapido release (Use the 'Upgrade file' Rapido version)
  • Extract the /Files folder from the new release on top of the old /Files folder (this should merge the two folders, but if not, you have a backup of e.g. the /Images folder)
  • These files are removed from the 'Upgrade file' Rapido version, so it should not overwrite your custom changes. However if it does, then copy them over from your backup:
    • Copy the CSS/Ignite files and custom.js  from the backup to the updated /Files folder
    • Copy the repositories from the backup to the updated /Files/System/Repositiories folder
  • Do not update the database! Open the new /Files folder and locate the new GlobalSettings.aspx. Using the old file, re-enter the the Database information and recycle the application pool
  • Now go to your solution frontend and go through the Rapido website settings and ensure that any new setting are properly configured and selected - Very important!
  • In backend go to Settings/Itemtypes and click 'Refresh' in the ribbonbar
  • Delete browser cache
  • Go through the solution and verify that everything is fine:
    • Content pages
    • Product lists
    • Product page
    • Customer Center
    • Etc.
  • Only on Rapido 2.0 to Rapido 2.1 version
    • If you are using PageNoEcom Template on your existing solution then change it to Rapido Page.cshtml template.
    • Go to website settings/Layout and select Page.cshtml template  (imp. when upgrading to Rapido 2.1)
    • Check that the file Placerholder.gif is in the folder Files/Images (imp. when upgrading to Rapido 2.1)
    • Copy the folders Payment and SocialIcons and place it as a subfolder under Files/Images (imp. when upgrading to Rapido Beta to Rapido 2.1)

Please be aware, that any changes to Rapido code outside of the Ignite.css and custom.js files means you cannot upgrade in the manner described above. Instead, you can often manually merge features from the new release to the solution.

Be sure that you select all the options in website settings or import our default JSON website settings.

If you want to include features from a new major release, or if you have made customizations to the Rapido code outside of the ignite.css and custom.js files, you cannot upgrade in the manner outlined above.

However, it will often be possible to manually merge the feature. This is a frontend-developer task, and requires code knowledge:

  • Backup your /Files folder
  • Locate the code related to feature you want to merge in the Rapido template set
  • Copy it
  • Check if the feature is dependent on JavaScript – this is the case if an element has a class with the ’js-’ prefix. Copy the corresponding JavaScript.
  • Check if the feature uses any new CSS – this can easily be checked by simply having a look, or searching for class names. Copy the corresponding .less code

This is the recommended approach – if it fails, don’t hesitate to contact us on the forum.

Upgrading from Rapido 3.1.X to 3.2 has some extra 

  1. Backup your solution
  2. Export the website settings on the existing solution
  3. Download the Rapido upgrade zip package
  4. Unzip upgrade file
  5. Copy the Files folder from the upgrade zip and overwrite the existing Files folder on your solution
  6. IIS recycle
  7. Import your old website settings - the ones you exported during step 2
  8. Save and close

Required on Rapido 3.2

  1. Set the settings in Settings/Ecommerce/advanced configuration/shopping cart enable Do not render user address loop & enable Copy customer info to delivery fields if empty
  2. Create a subpage under cart called AddressForCheckout
    1. Create a paragraph and select the extranet
      1. In Section SHOW Select toggle Manage addresses
      2. Select template AddressesList.cshtml
      3. Select template AddressForm.cshtml
    2. On the ribbon bar use the template Default.cshtml
    3. On the page AddressesForCheckout go to Properties in the ribbonbar
      1. Select the Option tab and click on Navigation in the ribbon bar , insert Navigation tag AddressesForCheckout
      2. Select the Layout tab And select the Rapido:clean template
  3. Go to website settings /Ecommerce tab/Checkout and enable toggle e.g. Static addresses
  4. Empty cache
Figure 5.1 Settings/Ecommerce/advanced configuration/shopping cart enable these settings

Page Setup for AddressesForCheckout 

Figure 5.2 AddressesForCheckout setup

Upgrading from Rapido 3.0.X to 3.X is a handheld process because 3.X uses the color swatch item type instead of the color field item type.

  1. Backup your solution
  2. Export the website settings on the existing solution
  3. Download the Rapido upgrade zip package
  4. Unzip upgrade file
  5. Copy the Files folder from the upgrade zip and overwrite the existing Files folder on your solution (Needs to be a 3.0/3.0.X)
  6. IIS recycle
  7. Import your old website settings - the ones you exported during step 2
  8. Save and close
  9. Go to website settings and find the pencil icon besides the color swatches
  10. Set brand colors in new brand color swatch by editing Brand color 1,2,3,4,5 and set your brand colors. You can take the hex codes from the rounded custom color swatch button and insert when you edit each brand color (Figure 6.1)
Figure 6.1 Copy the hex code into the color swatches
  1. Select the new color swatches for brand color one-five (Figure 6.2)
  2. (Go through your entire website settings)
  3. Save and close  website settings
  4. Empty your cache and IIS recyle

And that’s all folks :)

Figure 6.2 Select the new swatch colors

Upgrading from Rapido 2.X to 3.0 is a handheld process since we move from one long page of website settings to website settings in tabs, and we cannot guarantee a simple and problem-free experience.

That said, if you have made no changes to the standard Rapido templates the process is as follows:

  1. First, backup or screenshot the existing website settings
  2. Download the new Rapido 3 Files folder and extract it
  3. Backup the existing Files folder
  4. Overwrite the old Files folder with the new Files folder
  5. Copy the <Database> section from the old GlobalSettings.aspx file to the new one – you may have to recycle the application pool afterwards

You now have the new templates & item types installed – next they must be applied:

  1. Login to the backend
  2. Open the Website settings for the English (Master) website
  3. In the toolbar click Item types
  4. Select the new Website settings tabs as the website properties item
  5. Save the website settings

This applies the updated, tabbed website settings to the solution.You can now manually transfer settings from the old setup to the new setup - or use the converter tool as decribed below.

If you simply want to load the new default layout:

  1. Click Import settings
  2. Select the ENG-BIKES-Websitesettings.json file and click LOAD
  3. Save the website settings

If your settings still does not appear on frontend check your less.config files

  1. Go to Files/Template
  2. Open e.g. Less_1.config 
  3. Ensure that this line is place below OutputPath
  4. Go to your website settings and save your settings again

And that’s all folks :)

Convert Rapido 2.x settings to Rapido 3.x settings

Since the format for website settings changed between Rapido 2.x and 3.x, with Rapido 3.x employing the item tab item type, a simple export and import between versions is not possible.

To solve this issue, we have developed a small tool for converting Rapido 2.x settings to the Rapido 3.x format.

Here's how to use it:

  1. Download the Rapido Settings Converter
  2. Create a folder on your Desktop call it Mapping
  3. Insert the RapidoSettingsConverter.exe that you have downloaded in the Mapping folder
  4. Go to your Rapido 21 solution and export the website settings call it e.g. Mysite2-1
  5. Find your json file under File/System/Items/Websitesettings, copy Mysite2-1.json
  6. Insert the Mysite2-1.json file  in the Mapping folder
  7. Open your command line
  8. Write cd Desktop in the command line
  9. Write cd Mapping in the command line
  10. Write RapidoSettingsConverter.exe to run it
  11. Write Mysite2-1.json to select the file you need to convert to fit a Rapido 3.0 website settings
  12. Now in the Mapping folder you get a file called Mysite2-1.json(Rapido30).json
  13. Insert the new json fil in your solution under File/System/Items/Websitesettings
  14. Go to website settings and import Mysite2-1.json(Rapido30).json and click save