Support Forum
Well hopefully you followed the advice and made your own theme. If you didn't then it's not too late. And it IS simple and worth it. See http://codex.simple-press.com/.....g-a-theme/
YELLOW
SWORDFISH
|
Yellow Swordfish said
This should do it - commenting out the following lines of code://wp_deregister_script('jquery'); //wp_register_script('jquery', ''.get_template_directory_uri().'/scripts/js/jquery.min.js', 'jquery'); wp_enqueue_script( 'jquery' ); //wp_register_script('jqueryui', ''.get_template_directory_uri().'/scripts/js/jquery-ui.min.js', 'jquery'); wp_enqueue_script( 'jqueryui' );See if that helps.
Hi Guys,
I have come back to this to find that this solution gets the login jquery drop down functioning but breaks all other uses of jquery on the site. Any ideas?
Thx
I thought that might be the case and found the following file: custom.js (attached) This has a lot of javascript using the $ notation I have tried simply doing a find and replace in this document, swapping out the $ for jQuery but this did not work.
However, I did manage to get the slider on the homepage working as there is a single javascript for this that I amended as below...
<script type="text/javascript">
var jQuery = jQuery.noConflict();
jQuery(window).load(function() {
jQuery('.flexslider').flexslider();
});
</script>
instead of...
<script type="text/javascript">
$(window).load(function() {
$('.flexslider').flexslider();
});
</script>
the second one (jquery ui), should be:
wp_enqueue_script('jquery-ui-core');
wp_enqueue_script('jquery-ui-widget');
the second one might not be needed, but I always put it in since it used to be jquery ui core...
Visit Cruise Talk Central and Mr Papa's World
Ok, tried adding the above but still no good, forum works fine, rest of the site doesn't.
Below the calling of jquery are all of the following, some of these are the ones that are now not working:
wp_register_script('superfish', ''.get_template_directory_uri().'/scripts/js/superfish.js', 'jquery');
wp_enqueue_script('superfish');
wp_register_script('custom', ''.get_template_directory_uri().'/scripts/js/custom.js', 'jquery');
wp_enqueue_script('custom');
wp_register_script('tabs', ''.get_template_directory_uri().'/scripts/js/tabs.js', 'jquery');
wp_enqueue_script('tabs');
wp_register_script('prettyphoto', ''.get_template_directory_uri().'/scripts/js/jquery.prettyPhoto.js', 'jquery');
wp_enqueue_script('prettyphoto');
wp_register_script('opacityrollover', ''.get_template_directory_uri().'/scripts/js/jquery.opacityrollover.js', 'jquery');
wp_enqueue_script('opacityrollover');
wp_register_script('galleriffic', ''.get_template_directory_uri().'/scripts/js/jquery.galleriffic.js', 'jquery');
wp_enqueue_script('galleriffic');
wp_register_script('flexslider', ''.get_template_directory_uri().'/scripts/js/jquery.flexslider-min.js', 'jquery');
wp_enqueue_script('flexslider');
wp_register_script('jcarousel', ''.get_template_directory_uri().'/scripts/js/jquery.jcarousel.js', 'jquery');
wp_enqueue_script('jcarousel');
wp_register_script('photogallery', ''.get_template_directory_uri().'/scripts/js/slides.min.jquery.js', 'jquery');
wp_enqueue_script('photogallery');
wp_register_script('easing', 'http://gsgd.co.uk/sandbox/jquery/easing/jquery.easing.1.3.js', 'jquery');
wp_enqueue_script('easing');
Mr Papa said
the second one (jquery ui), should be:wp_enqueue_script('jquery-ui-core');
wp_enqueue_script('jquery-ui-widget');the second one might not be needed, but I always put it in since it used to be jquery ui core...
Ok, tried Mr Papas suggestion adding the above but still no good, forum works fine, rest of the site doesn't.
Below the queing of jquery are all of the rest of the scripts being called from within the theme, some of these are the ones that are now not working for example:
wp_register_script('prettyphoto', ''.get_template_directory_uri().'/scripts/js/jquery.prettyPhoto.js', 'jquery');
wp_enqueue_script('prettyphoto');
Do these need to be edited?
Well the prettyphoto script is commonly used and I encounter it often on our users sites. Just because it does not work now does not necessarily mean the problem is in there.
I do wish that theme and plugin authors would take into account that their stuff needs to work with the widest possible array of other plugins. It is so easy to do things properly!
You need to go about this in a methodical manner and that means determining exactly what piece of code is at fault. The only way to do this is by using a script console. By far the best is the Firebug extension for Firefox but if tyou do niot want to install that then the Firefox error console will do. Open it - clear it out - run a page. Look at the console report (please ONLY the errors tab) and it should point to the place of failure if all is well.
YELLOW
SWORDFISH
|
1 Guest(s)