Nope! 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.
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 fullpage.extensions.min.js file from the github project.
No activation key is necessary for localhost and 127.0.0.1 domains.
Any other staging domains will require a license (Professional or Business) that allows to generate a new key for those.
Note that you can still use the Hobby license if the different environments are subdomains of the same domain. For example: apple.com and dev.apple.com
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?
Sure! But you'll have to purchase the Business license for that. The Hobby or Professional licenses use a different activation key per domain.
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.
The most probable thing is that you a missing some of the required steps.
Notice you'll have replace (not add!) the usual fullPage.js file (fullpage.js or fullpage.min.js) for the file fullpage.extensions.min.js.
I do! As long as:
Contact me for more information.
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: