Often when you are setting up a new site you might want to use a 3rd party JavaScript library. This article shows you how you are able to upload unlimited external files and have them embedded in your site's files.

You will need to have access to the Developer module in your Funraisin platform for this. If when you login you don't see the Developer module on the left nav then you may need to request access or enable it yourself in Funraisin > User Admin.

Upload Assets

Once you get access to the Developer module, simply go into Developer > Upload Assets and you will see a screen like the screenshot below that let's you upload your external files. Note all files must be zipped prior to uploading.

screen-shot-2017-01-05-at-6-20-00-pm

Once you have uploaded your zip file you should see it listed like the screenshot below.

screen-shot-2017-01-05-at-6-24-05-pm

Add to your Site's Views

Once you have uploaded all of your assets you can now add them to your site's view files. Note that this is best performed by a web developer as if you make any changes to your site's views you can detrimentally affect your site if not careful.

Still within the Developer module, choose "Edit Theme" from the left hand menu.

On the right hand side you should see a list of all the site's desktop and mobile views and clicking on any view file will load up that file in the code editor.

The view called "_meta" is a global file that is loaded within each page's. If your external library requires to be loaded in the head then you should use this view. Otherwise you can also use the "_footer" view and providing that you check that the files are loaded, this would be the best location for loading any 3rd party library.

screen-shot-2017-01-05-at-6-40-22-pm

Back on the list of Assets, you will notice that each asset is given a directory such as "http://yourcause.funraisin.co/assets/external/fancybox/". You can use this path to load up your library, though we strongly recommend that you lose the "http://" and just use "/yourcause.funraisin.co/etc" to make sure that it will be compatible with the site when viewed over https.