link javascript and css correct.

Hardly idiot proof, but maybe a proper example will help. This enqueues one style and one script, expand on it as needed.

function my_scripts_callback() {
	wp_enqueue_script('my_handle', get_stylesheet_directory_uri() . '/js/jquery.fullPage.js', array('jquery'), null);
	wp_enqueue_style('my_style', get_stylesheet_directory_uri() . '/js/jquery.fullPage.css', false, null );
}
add_action( 'wp_enqueue_scripts', 'my_scripts_callback' );

This goes in your theme’s functions.php. You do not want to load jquery and jquery-ui from outside sources unless you have very good reasons to use that version. WP has its own version local on your server and already registered, the outside versions will conflict with it.

Since they are registered, you just need to specify it as a dependency and it will be loaded along with the script you are enqueuing. I showed an example dependency, I don’t know the actual dependencies, you need to verify those. See this list for proper handles of registered scripts. Also check the scripts you are enqueuing, if they use the $ shortcut instead of the explicit jQuery, they will need to be wrapped in a no conflict wrapper.

Thanks for the reply. Still can’t get this to function. I do need to load the external scripts it seems to make the plugin I’m using to work.

Stupid question, but do i need to call the function/action in my header to make the scripts work?

No, that’s too late. I mentioned placing it in your theme’s functions.php which is silly since you are dealing with a plugin. It works just as well and makes infinitely more sense in your plugin’s code. I go a bit confused because you scripts were in your theme’s folders, apologies. If your files are really in your plugin folder, get_stylesheet_directory_uri() is the wrong function, you need the plugin folder equivalent.

There’s lots of reasons jQuery might not work, but you can easily verify at least the enqueue part is working by inspecting the page’s head section for the necessary meta links. You should roughly be seeing what you had as hardcode, but this time the correct libraries are referenced and dependencies properly resolved. Check the referenced paths carefully, it’s not too hard to get them wrong.

If you really need the external versions, you need to de-register the WP versions to prevent conflicts. I thought there was something in the Codex about this, but I cannot locate it at the moment. You can probably search as well as I can.

One other thing that can go wrong is using the wrong hook. There’s different hooks to enqueue for different parts of WP.

Thanks again for the reply. Not following though, theres no plugin except the scripts and the function to activate them. Probably sound dumb here, sorry for that. The script I’m using is this, placed in my js folder:

https://github.com/alvarotrigo/fullPage.js#fullpagejs

Im not really sure i need the external versions, but i can’t make it work without them, so far at least.

I guess I’m picking up on the wrong cues, but no matter. You need to put some PHP code somewhere. It can be in any activated plugin code actually, but you shouldn’t be editing plugins that are not yours. It’s actually useful to create a simple site specific plugin for the sole purpose of containing random bits of custom code site admins often come up with.

The other place to place PHP code is your theme’s functions.php file. It’s best to create a child theme for this so your code is protected from theme updates.

As I mentioned, there’s many things that can cause code to not work. It’d be good to really confirm there’s a version issue involved. Try reverting to the hardcoded functional version. Change the external reference, one file at a time, to the equivalent WP version and test for functionality. If things work under this condition then we know the local WP version can work, something else is amiss. Apologies if this is what you did, once again, it wasn’t clear to me :/