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.
Upgrading From 2.X to 3.X
Upgrading from Rapido 2.X to 3.X is a handheld process, 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:
- First, backup or screenshot the existing website settings
- Download the new Rapido 3 Files folder and extract it
- Backup the existing Files folder
- Overwrite the old Files folder with the new Files folder
- 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:
- Login to the backend
- Open the Website settings for the English (Master) website
- In the toolbar click Item types
- Select the new Website settings tabs as the website properties item
- 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:
- Click Import settings
- Select the ENG-BIKES-Websitesettings.json file and click LOAD
- Save the website settings
If your settings still does not appear on frontend check your less.config files
- Go to Files/Template
- Open e.g. Less_1.config
- Ensure that this line is place below OutputPath
- 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:
- Download the Rapido Settings Converter
- Create a folder on your Desktop call it Mapping
- Insert the RapidoSettingsConverter.exe that you have downloaded in the Mapping folder
- Go to your Rapido 21 solution and export the website settings call it e.g. Mysite2-1
- Find your json file under File/System/Items/Websitesettings, copy Mysite2-1.json
- Insert the Mysite2-1.json file in the Mapping folder
- Open your command line
- Write cd Desktop in the command line
- Write cd Mapping in the command line
- Write RapidoSettingsConverter.exe to run it
- Write Mysite2-1.json to select the file you need to convert to fit a Rapido 3.0 website settings
- Now in the Mapping folder you get a file called Mysite2-1.json(Rapido30).json
- Insert the new json fil in your solution under File/System/Items/Websitesettings
- Go to website settings and import Mysite2-1.json(Rapido30).json and click save
Upgrading to a new minor
To upgrade from one minor to another minor within the same major:
- Keep in mind that if you have made custom changes to these standard Rapido files then be they may be overwritten
- Backup your /Files folder and the solution database
- Download the new Rapido release (Use the Empty Rapido version)
- Extract the /Files folder from the new release on top of the old /Files folder
- 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!
- 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 2.1)
- Go through the Rapido website settings and ensure that any new setting are properly configured and selected - Very important!
- 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)
- Go through the solution and verify that everything is fine:
- Content pages
- Product lists
- Customer Center
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.
Merging features manually
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 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.