FAQs

Can I test extensions before buying them?

Nop! You can not. You need to purchase them in order to try them.

But remember you have a 30 days money back guarantee as long as you do not generate any activation key. Pleas read the fullPage.js Refund Terms of the license.

Where do I get the files for fullpage.js extensions?

Once you purchase the extension you'll get a confirmation message on the screen in which you'll be able to download the file.

Additionally, on the purchase confirmation email you'll see a link to download the extension file. (For example: fullpage.scrollHorizontally.min.js)

You can get the jquery.fullpage.extensions.min.js file from the github project.

Can I get an invoice?

Sure you can! You'll find a link to generate the invoice in the purchase confirmation email.

More info in here.

If you have any question or problem regarding invoices and billing, please contact [email protected] to reach the company that deals with the payment.

What to do with dev/staging domains?

As detailed on the extensions page: Upon request new activation keys can be provided for staging or developing domains to a maximum of 3. No activation key is necessary for `localhost` and `127.0.0.1`.

You can get the activation for your staging domain and then ask me for a new one whenever you want to move it to the production one.

Just send me the URL and the name of the extension together with the email you used for the purchase.

Can I be refunded?

Sure! As detailed on the extensions page, there's 30-days money back guaranteed for any purchase under the conditions detailed in the License Agreement: read the fullPage.js Refund Terms.

Notice that you won't be elegible for a refund if you generated an activation key for your extension.

I get an "Unlicensed extension" message

That means you are not using the right key for your extension!

Make sure to read how to activate a fullPage.js extension and how to use fullPage.js extensions.
Notice you'll have replace (not add!) the usual fullPage.js file (jquery.fullpage.js or jquery.fullpage.min.js) for the file jquery.fullpage.extensions.min.js.

Can I upgrade from one license to another?

Sure! It is in fact very easy!

Please proceed to purchase the upgraded license (Professional or Business license). Then contact me and let me know that you want to upgrade. I'll then proceed to refund you the previous purchase. Easy uh?

Can I use a common activation key for all my domains?

Sure! But you'll have to purchase the Business license for that. The Hobby or Professional licenses use a different activation key per domain.

I lost my activation key, how can I find it?

The activation key was sent to the email used for the purchase when you generated it for a domain. If it is not on the inbox, please look into the SPAM folder.

My extension is not working

The most probable thing is that you a missing some of the required steps.

Make sure to read in the documentation how to use your extension as well as how to activate a fullPage.js extension and how to use fullPage.js extensions.

Notice you'll have replace (not add!) the usual fullPage.js file (jquery.fullpage.js or jquery.fullpage.min.js) for the file jquery.fullpage.extensions.min.js.

Do you offer any kind of discounts?

I do! As long as:

  • - You purchase all extensions
  • - You purchase more than 2 extensions under the Professional license
  • - You purchase more than 3 extensions under the Hobby license

Contact me for more information.

Not an extensions issue?

If you are having problems with fullPage.js, please make sure to first check the documentation and the fullPage.js FAQs to look for a solution.

If you do not find a solution in there and it is a fullPage.js, multiScroll.js or pagePiling.js issue, please make sure to create an isolated reproduction of the issue in jsfiddle, codepen or your own hosting. It should not contain CSS or JS files external to my libraries (unless strictly required). It should also use empty sections if possible to have as less HTML code as possible.

Then, please proceed to create an issue in the github project's forum: