Fullpage.js: Licence Key error in console

Created on 12 Mar 2019  ·  10Comments  ·  Source: alvarotrigo/fullPage.js

Hi!
I just bought fullPage.js and placed the licence number as described in the documentation (licenseKey: 'xxx-xxx-xxx')., but I have this error in console:
Fullpage.js version 3 has changed its license to GPLv3 and it requires a licenseKey option. Read about it here

Is maybe only because I'm working in localhost or I must do something to activate my licence?

Thanks a lot
Barbara

question

All 10 comments

As detailed in the the fullpage.js documentation all you need to do is add the licenseKey option in your fullpage.js initialization with the value you got:

new fullpage({
    licenseKey: 'YOUR_KEY_HERE'
});

Make sure not to initialise fullpage.js more than once.

If you still getting the error, it means you are not doing it properly for some reason.

I'm having the same issue

Then apply the same suggested solution:
https://github.com/alvarotrigo/fullPage.js/issues/3596#issuecomment-472030367

your answers are fucking awesome!

Well, you didn't provide any information at all. So if you get the error is basically because you didn't add the licenseKey option properly :)

Hello I was having the same issue. I was about to comment before I figured it out.
I am using vue fullpage and fullpage.

Just commenting here in case anyone makes the same mistake.
It really Helps if you look at the demos.

My issue was I was initializing it more than once as was mentioned above.
I did vue.use on fullpage and vuefullpage
[fullpage, VueFullPage].forEach((plugin) => Vue.use(plugin))

What worked for me was not calling fullpage and just doing VueFullPage
I still installed both ofc.

[VueFullPage].forEach((plugin) => Vue.use(plugin))
or Vue.use(VueFullPage).

VueFullPage adds the wrapper and also initializes fullpage which wasn't super clear to me at first.

Here is a link to the demo I used.
https://github.com/alvarotrigo/vue-fullpage.js/blob/master/demos/webpack/src/main.js
There are a ton more demos there which is nice :)

Glad you managed to find a solution @hothit43 !

Having same issue with licenseKey option written as specified in docs.

@krispind two possible options:

  • Your key is incorrect
  • You have typed the option licenseKey incorrectly or all in lower cases.
Was this page helpful?
0 / 5 - 0 ratings

Related issues

meceware picture meceware  ·  3Comments

cavias picture cavias  ·  3Comments

pepi3 picture pepi3  ·  4Comments

lunaandyou picture lunaandyou  ·  4Comments

villain2 picture villain2  ·  3Comments