![\"pgwSlideshow](\"http:\/\/sgcustomwebsolutions.com\/blog\/wp-content\/uploads\/2015\/09\/slideshow-screenshot-1024x737.jpg\")
<\/p>\n
Our plugin contains the following CSS and JQuery files:<\/p>\n
- \n
- pgwslideshow.css<\/li>\n
- pgwslideshow.min.css<\/li>\n
- pgwslideshow_light.css<\/li>\n
- pgwslideshow_light.min.css<\/li>\n
- pgwslideshow.js<\/li>\n
- pgwslideshow.min.js<\/li>\n<\/ul>\n
The files with the “.min” extension are “minified” versions of the css and js files. A minified file is simply one that has been stripped of all extra space. They are virtually impossible to read, but they’re also smaller in size, so they load faster on your page.<\/p>\n
A jQuery plugin typically provides both regular and minified versions of the plugin files, but you should only load the min versions on your site for performance reasons. In this tutorial we will be loading pgwslideshow.min.js<\/em> and pgwslideshow.min.css<\/em>.<\/p>\n
The Prep<\/h3>\n
This tutorial makes a few important assumptions:<\/p>\n
- \n
- You’re using a child theme<\/strong>. This is strongly recommended because it protects your changes from being overwritten by future theme upgrades.<\/li>\n
- You have a functions.php<\/em> file in your child theme.<\/strong> If you don’t, you’ll need to learn a little about this file<\/a> and create one before proceeding.<\/li>\n
- You’ve created folders in your child theme directory called js<\/em>, css<\/em>, and images<\/em>.<\/strong> If you like to organize your files differently, just be sure to adjust the file paths in this tutorial accordingly.<\/li>\n<\/ul>\n
Okay, ready to make this happen? Let’s roll.<\/p>\n
1. Make the Code Compatible with WordPress<\/h3>\n
First we need to tweak our jQuery file so it will work in the WordPress environment. WordPress comes loaded with the latest jQuery library, which is set to ‘No Conflict’ mode to prevent clashes with other Javascript libraries you may be using. Consequently, jQuery scripts using the “$” symbol won’t work in WordPress.<\/p>\n
To fix the problem we’ll simply replace every occurrence of “$” with “jQuery” in pgwslideshow.min.js<\/em> using the find\/replace function of a standard text editor. For example, this bit of code in our script:<\/p>\n
$(this).addClass('elt_' + element.id);<\/pre>\nwill become:<\/p>\n
jQuery(this).addClass('elt_' + element.id);<\/pre>\nAfter saving the changes to pgwslideshow.min.js<\/em>, we’ll place our plugin files at the following locations within WordPress:<\/p>\n
pgwslideshow.min.js\u00a0<\/em> <\/i>\u00a0 <child-theme-directory>\/js\/pgwslideshow.min.js. <\/em><\/p>\n
pgwslideshow.min.css\u00a0<\/em> <\/i> <child-theme-directory>\/css\/pgwslideshow.min.css.<\/em><\/p>\n
2. Enqueue the Code in WordPress<\/h3>\n
Next we’ll add some code to functions.php<\/em> that will tell WordPress to load our two plugin files. This code hooks into the ‘wp_enqueue_scripts’ action that WordPress automatically executes whenever you load a page.<\/p>\n
Since the slideshow will be on a page entitled “My Photography,” our function only needs to load the plugin files when that page is accessed. Note that you could also use a blog post title within the is_page()<\/a> check below:<\/p>\n
function load_slideshow_scripts() {\r\n\r\n if(is_page('My Photography')) {\r\n wp_register_style( 'slideshowstyle', get_stylesheet_directory_uri() . '\/css\/pgwslideshow.min.css', false, 0.1 ); \r\n wp_enqueue_style( 'slideshowstyle' ); \r\n wp_register_script( 'theslideshow', get_stylesheet_directory_uri() . '\/js\/pgwslideshow.js', array('jquery'), false, true );\r\n wp_enqueue_script( 'theslideshow' ); \r\n }\r\n}\r\nadd_action( 'wp_enqueue_scripts', 'load_slideshow_scripts' );<\/pre>\nIf you should later run into problems getting the slideshow to work, the code below can be temporarily added to the function above for debugging purposes. Just place these lines right after that last wp_enqueue_script()<\/em> call:<\/p>\n
if(wp_script_is( 'theslideshow', 'enqueued' )) { echo \"<BR>Slideshow script enqueued successfully!\"; }\r\nif(wp_style_is( 'slideshowstyle', 'enqueued' )) { echo \"<BR>Slideshow style enqueued successfully!\"; }<\/pre>\nThis will display two success messages at the very top of the slideshow page upon successfully loading the plugin files. If those messages don’t<\/em> appear when you hit the page, you’ve got a script loading problem on your hands.<\/p>\n
3. Call the Script on a WordPress Page<\/h3>\n
Lastly, it’s time to place the necessary jQuery and HTML on our slideshow page. The PgwSlideshow plugin documentation provides the following example for calling the jQuery plugin on your web page:<\/p>\n
$(document).ready(function() {\r\n $('.pgwSlideshow').pgwSlideshow();\r\n});<\/pre>\nWe’ll tweak this a bit to make it compatible with WordPress. First, navigate to the page where you want to put your slideshow, open it in edit mode, and click on the WordPress “text” editor tab. Then copy and paste the code below into the editor.<\/p>\n
Notice that we have replaced the “$” with “jQuery” for the reasons explained in step one. A few optional parameters have also been added in the function call to configure the slideshow. These can be modified or added to as desired. And below the jQuery function call is a sample template for the unordered list of slides that the plugin will need:<\/p>\n
<script type=\"text\/javascript\">\r\njQuery(document).ready(function() {\r\n jQuery('.pgwSlideshow').pgwSlideshow({\r\n transitionEffect: \"fading\", \r\n transitionDuration: 650,\r\n maxHeight: 700, \r\n displayControls: true\r\n });\r\n});\r\n<\/script>\r\n<ul class=\"pgwSlideshow\">\r\n <li><img src='..\/wp-content\/themes\/your-child-theme-here\/images\/your-image-1.jpg' alt='Somewhere, USA' data-description='Some Description'><\/li>\r\n <li><img src='..\/wp-content\/themes\/your-child-theme-here\/images\/your-img-2.jpg' alt='Somewhere, USA' data-description='Some Description'><\/li>\r\n <li><img src='..\/wp-content\/themes\/your-child-theme-here\/images\/your-image-3.jpg' alt='Somewhere, USA' data-description='Some Description'><\/li> \r\n<\/ul>\r\n<\/pre>\nNow we have one final issue to address. WordPress automatically adds paragraph tags to your markup, which will actually prevent the jQuery call as formatted above from working. One way to fix the issue is to place the entire script call onto one single line like this:<\/p>\n
<script type=\"text\/javascript\">jQuery(document).ready(function() { jQuery('.pgwSlideshow').pgwSlideshow({transitionEffect: \"fading\", transitionDuration: 650, maxHeight: 700, displayControls: true});});<\/script><\/pre>\nHowever, the line is now more difficult to read. If you prefer to keep the original formatting you can disable the auto paragraphs instead with a handy little WordPress plugin called Raw HTML. This plugin adds a widget on the WP page editor that allows us to switch off auto paragraphs for a given page as shown below:<\/p>\n
![\"Raw](\"http:\/\/sgcustomwebsolutions.com\/blog\/wp-content\/uploads\/2015\/09\/raw-html1-300x191.jpg\")
<\/a><\/p>\n<\/h3>\n
Save your changes to the slideshow page, and that’s all there is to it. Mission accomplished!<\/p>\n
Conclusion<\/h3>\n
As we’ve seen, loading a jQuery plugin in WordPress is relatively painless when you’re armed with the right information. And the principles discussed here apply to any jQuery plugin you may want to install on WordPress. Check out my live demo of this slideshow plugin – and enjoy a few nature photos while you’re at it – on my photography page<\/a>. Please note that I have adjusted the css and used Adobe Photoshop Elements to create uniformly-sized slides for optimal viewing.<\/p>\n
Good luck, and happy plugging!<\/p>\n
Did you find this post helpful? Say thanks by clicking the Facebook “like” button below!<\/em><\/p>\n
Resources<\/h3>\n
jQuery Documentation on ‘No Conflict’ Mode<\/a><\/p>\n
WordPress Codex: Child Themes and functions.php<\/a><\/p>\n
WordPress Codex: Enqueing Scripts<\/a><\/p>\n
- You have a functions.php<\/em> file in your child theme.<\/strong> If you don’t, you’ll need to learn a little about this file<\/a> and create one before proceeding.<\/li>\n
- You’re using a child theme<\/strong>. This is strongly recommended because it protects your changes from being overwritten by future theme upgrades.<\/li>\n