If you are finding that a script you don't need is being enqueued and causing confilcts, you can deregister it.
See the codex here - http://codex.wordpress.org/Function_...egister_script
Find the line that is registering it in the theme or plugin. You'll see something like `wp_register_script` or 'wp_enqueue_script', along with the name of the script as an argument. This will usually be in a function that is used as a callback within an action hook.
Here is the code I use to register Modernizr in my framework:
Code:
wp_enqueue_script(
'modernizr', // < -- this is the name
get_template_directory_uri() .
'/includes/template/js/modernizr.min.js'
);
Once you have the name of the script, you can deregister it from a new plugin file or in your theme/child theme functions file. You need to do this from the `wp_enqueue_scripts` action, preferably with a late priority, like so.
Code:
add_action( 'wp_enqueue_scripts', function() { wp_deregister_script( 'SCRIPT_NAME' ); }, 999 );

Originally Posted by
Ecommerce web design
One quick point plugins can increase the possibility of hacking etc, so ensure you keep updating as much as possible.
Plugins don't increast the possibility of hacking. Poorly written plugins ( and themes ) increase the chance of hacking.