How to upgrade from the trial version
Requirements
Acquiring a license
When upgrading from a trial license to a commercial, the first step is to purchase the commercial license. This can be done from our pricing page among other areas of our website. If you are still looking for which license to choose or if you have any questions, let us know! We are here to help!
Assigning the license to the developer
After the purhcase of the commercial license, it should be assigned to the developer, who will do the development. This can be done immediately after the purchase, or later from the licenses page. When the buyer and the developer is the same person, the license can be self-assigned as well.
Upgrading the library in your project
If you are building a web application with module loaders and bundlers (like webpack or rollup) and you installed the trial with the Mobiscroll CLI, then you have two options how to upgrade. Depending on how did you install the trial in your project and what type of license did you purchase, you can:
If you are developing a web page and you installed the trial without the Mobiscroll CLI, you can:
Upgrading to the full package
This method will include a Mobiscroll package into your project from NPM. In order for this to work, you will need a license from the following types of licenses with an active maintenance:
- Date & Time picking
- Scheduling & Calendaring
- Complete
- Enterprise (SaaS)
The package installed will contain all the components of the framework, except for the Date & Time license. In that case only the associated components will be included in the package. Check out the pricing page for more details on which components are included in the Date & Time picking license.
To upgrade the trial package in your project, the commercial license needs to be assigned to your account. If you are the developer, but somebody else purchased the license, then the buyer can assign the license to your account. You should instruct the buyer to log in to his account and proceed to the licenses page. From there, he can assign the license to you account.
After the license is assigned to your account, run the following commands in your project root directory to upgrade the package:
1. Log in to your account
If you are using the same account for the commercial license that you were using with the trial, then you can skip this step.
mobiscroll login
When you are asked, please provide your credentials. If you haven't set a password yet, you can set one from your account page.
2. Configure the project
mobiscroll config javascript
At this point the trial package should be replaced with the commercial package, and building and running your project should work.
After upgrading to the commercial package, components that auto-initialize need to be registered for the auto-initialization to work. Check out the register components section to learn how to enable auto-initialization in ESM bundles.
Upgrading to a Component license
With this method, you will download a package from our website, then you will use the Mobiscroll CLI to install that package to your project.
If you don't have access to the Full Framework, or if you want to customize your package to only contain specific components, this is the way to go.
1. Download your package
Access the download page, by logging in to your account. The commercial license needs to be assigned to your account. If you are the developer, but somebody else purchased the license, then the buyer can assign the license to your account. You can instruct the buyer to loggin into his account and proceed to the licenses page.
After selecting the components, themes, custom themes and font icon packs that you need, hit the download button and download your package. If you have multiple licenses and have access to multiple frameworks, you might need to select the framework as well.
2. Copy the library to your project
Extract the zip file you just downloaded, then grab the js, src and css folders and copy it into the src/lib/mobiscroll folder of your project. If there is no such folder available, you should create it.
3. Configure the project
Run the config command in your project's root folder with the --no-npm flag to proceed with the upgrade.
mobiscroll config javascript --no-npm
The Mobiscroll CLI under the hood will create and install a local NPM package from the lib folder. After the installation is complete, your package.json file should have an entry for a dependency like this:
"@mobiscroll/javascript": "file:./src/lib/mobiscroll-package/mobiscroll-javascript-5.27.1.tgz",
The .tgz file referenced here is the Mobiscroll package and it should be added to your repository too.
At this point the trial package should be replaced with the commercial package, and building and running your project should work.
Upgrade to a custom package by replacing the trial
With this method, you will download a package from our website, then you will replace the existing trial files in your project with the downloaded commercial ones.
If you included the Mobiscroll library to your project without the Mobiscroll CLI by copying the files over, then this is how you should proceed if you want to upgrade to commercial.
1. Download your package
Access the download page, by logging in to your account. The commercial license needs to be assigned to your account. If you are the developer, but somebody else purchased the license, then the buyer can assign the license to your account. You can instruct the buyer to loggin into his account and proceed to the licenses page.
After selecting the components, themes, custom themes and font icon packs that you need, hit the download button and download your package. If you have multiple licenses and have access to multiple frameworks, you might need to select the framework as well.
2. Replace the trial files in your project
Extract the downloaded zip file to a folder on your machine. There will be several folders inside the package. You will need the js and css folder contents. Locate the same files in your project, then copy and replace them with the ones you extracted from the downloaded package.
Browsers cache the loaded scripts and stylesheets by their names. When the filenames don't change, even though you replace the file contents, it might happen that you will still see the trial package in use.
Try to clear the browsers cache by hard-reloading your page to use the replaced files!
