If you are changing your site or just purchased your extension and you are getting an "Unlicensed extension" message, then check out How To Fix Unlicensed Extension Message.

If, however, you have not changed anything on your site and you are suddenly getting this message, here's probably why.

The problem

You are probably a CDN like https://unpkg.com/ to load the JS and CSS files for fullPage.js.

For example:

<!-- Loading the fullpage.js CSS file -->
<link rel="stylesheet" type="text/css" href="https://unpkg.com/fullpage.js/dist/fullpage.min.css" />

<!-- Loading the fullPage.js JS file (Only when not using extensions) -->
<script type="text/javascript" src="https://unpkg.com/fullpage.js/dist/fullpage.min.js"></script>

<!-- Loading the fullPage.js extensions JS file (instead of fullpage.min.js) -->
<script type="text/javascript" src="https://unpkg.com/fullpage.js/dist/fullpage.extensions.min.js"></script>

The problem with this kind of CND link is that they do not specify the version of the script they are trying to load, so the CDN assumes you want to load the latest version of the script.

You can check this by yourself by accessing (https://unpkg.com/fullpage.js/dist/fullpage.min.css) in your browser. Notice how you get redirected to another URL containing the version number on it. Something like this: https://unpkg.com/[email protected]/dist/fullpage.min.css

This is where the problem is and the main reason why it's not usually recommended to use this kind of CDN links.

You usually want a CDN link for a specific version of the library because future versions might introduce breaking changes. Specially when switching a major version like 3.1.2 to 4.0.5. (Major versions tend to reflect breaking changes following the Semantic Versioning guidelines).

The solution

If you were using fullPage.js version 3, for example. Then make sure to specify the latest version 3 on the CDN URL.

The latest version 3 is 3.1.2 (You can check this from the fullPage.js releases page). 

So the links you would need to use would be the following ones:

<!-- Loading the fullpage.js CSS file -->
<link rel="stylesheet" type="text/css" href="https://unpkg.com/[email protected]/dist/fullpage.min.css" />

<!-- Loading the fullPage.js JS file (Only when not using extensions) -->
<script type="text/javascript" src="https://unpkg.com/[email protected]/dist/fullpage.min.js"></script>

<!-- Loading the fullPage.js extensions JS file (instead of fullpage.min.js) -->
<script type="text/javascript" src="https://unpkg.com/[email protected]/dist/fullpage.extensions.min.js"></script>

But... I want to update to version 4?

Version 4 is a major update and therefore it's not free to update from version 3. 

If you want to update to version 4 you must first check the breaking changes introduced in version 4 to see if any affect you.

If you are not sure what version you are using, check out how to find out what version of fullPage.js you are using.

Then, you will have to:

  • Purchase a new license for fullPage.js version 4 from the pricing page.
  • Re-purchase any of your current extensions for version 3, but this time, for version 4 from here.
  • Active those extensions for the specific domains (You'll get the instructions by email)

Why update to version 4?

New versions usually mean fewer bugs and more features, and this is exactly the case.

Version 4 has fixed 10 bugs and added more than 10 enhancements and new features. You can check this out in the fullPage.js changelog for version 4.

Not only that. 

fullPage.js version 3 will no longer receive any updates and the support for it will be limited to answering questions of usage. 

Is up to you to decide if you can still run your pages using version 3 or version 4. 

You might also find these articles relevant: