Remember the Core Design Chili Code plugin extension? We used it to reformat some code, as we can see in the next image:

This plugin required the jQuery library, but as the plugin itself doesn't have the library included, another plugin from the same developers was needed—the Core Design Scriptegrator plugin. You can check it in Extensions | Plugin Manager:

This plugins works much like the SC jQuery plugin, but for the extensions of the Core Design Chili Code plugin developers. This plugin loads the jQuery library, and some others that we don't need, in order for the other extensions to use it.

As we are using the SC jQuery plugin, we can disable the Scriptegrator plugin:

But hey, then the Core Design Chili Code plugin stops working. Why? We have said that the Chili Code plugin needs the jQuery library, but we are using the SC jQuery plugin to provide it. At this point we need to check the Chili Code plugin source code, so just open plugins/content/cdchilicode.php. Here we can see the following piece of code:

// define language
                        if (!defined('_JSCRIPTEGRATOR'))
                        {
                        Error::raiseNotice('', JText::_('CHILICODE_ENABLE_SCRIPTEGRATOR'));
                        return;
                        }
                        // require Scriptegrator version 1.3.4 or higher
                        $version = '1.3.4';
                        if (!JScriptegrator::versionRequire($version))
                        {
                        JError::raiseNotice('', JText::sprintf('CHILICODE_SCRIPTEGRATOR_REQUIREVERSION', $version));
                        return;
                        }
                        if (!JScriptegrator::checkLibrary('jquery', 'site'))
                        {
                        JError::raiseNotice('', JText::_('CHILICODE_MISSING_JQUERY'));
                        return;
                        }
                    

What does all this code do? It checks for the Core Design Scriptegrator plugin. If it doesn't find any evidence of the plugin, it raises some errors and returns.

We know that jQuery will be loaded. So we can comment the code mentioned, and the Chili Code plugin will work again.

That's it; we have just reduced one jQuery library load; ready for the next one?

Remember our gallery plugin? Surely you do; we used it to create an interesting image gallery in our home page:

This is our next objective. This plugin also uses the jQuery library, as we can see by checking the source code of our site:

<script type="text/javascript" src="/plugins/content/ppgallery/res/jquery.js" charset="utf-8"></script>
                        <script type="text/javascript" src="/plugins/content/ppgallery/res/jquery.prettyPhoto.js" charset="utf-8"></script>
                    

The prettyPhoto library will be loaded as required, but loading the jQuery library needs some work. This time we will be working with the plugins/content/ppgallery.php file. Here we need to find the following line:

$doc->addScript($relpath.'/plugins/content/ppgallery/res /jquery.js" charset="utf-8'),
                    

As we can see, this is where the plugin loads the jQuery library. We will modify this line to:

$app =& JFactory::getApplication();
                        if( !$app->get('jquery') ){
                        $doc->addScript($relpath.'/plugins/content/ppgallery/res /jquery.js" charset="utf-8'),
                        }
                    

As in the previous instances, we use the variable set by the SC jQuery plugin to decide whether the jQuery library needs to be loaded or not.

Once we have done so, the pPgallery plugin won't load the jQuery library if it is present, thus saving us another load. We are almost done now, just keep up the good work.

This time we need to think twice about this extension. Looking at the source code of our site we see the following:

<script type="text/javascript" src="http://wayofthewebninja.com/modules/mod_ninja_shadowbox/ ninja_shadowbox/js/adapter/shadowbox-jquery.js"></script>
                        <script type="text/javascript" src="http://wayofthewebninja.com/modules/mod_ninja_shadowbox/ ninja_shadowbox/js/shadowbox.js"></script>
                    

We can see two library loads here:

However, though we may think the first one is a jQuery instance, it isn't. Does this mean we weren't using jQuery for this library? Not exactly; go to the administrator screen, then to Extensions | Module Manager | Ninja Shadowbox. There look for the Parameters zone; it will be more or less as follows:

Here we can see that when we first used the library we decided not to include the core JavaScript library. If we had included it, our source code would look as follows:

<script type="text/javascript" src="http://wayofthewebninja.com/modules/mod_ninja_shadowbox/ ninja_shadowbox/js/lib/jquery.js"></script>
                        <script type="text/javascript" src="http://wayofthewebninja.com/modules/mod_ninja_shadowbox/ ninja_shadowbox/js/adapter/shadowbox-jquery.js"></script>
                        <script type="text/javascript" src="http://wayofthewebninja.com/modules/mod_ninja_shadowbox/ ninja_shadowbox/js/shadowbox.js"></script>
                    

Here we can now see how the jQuery library is being loaded. This way, by selecting Don't Include in the module's parameters, our work will be done with this library.

This extension has been easy, as it includes a parameter that lets us select whether we want to load the jQuery library or not. But don't worry; only some extensions are left, and before we finish off the chapter we will see some very interesting things, just keep up with us!

This was one of the first extensions we used, and is one of the most visible parts of our site. Do you remember it? Look at the following screenshot:

This extension works a bit differently than the others that we have seen. As you may have noticed, we haven't seen its library load on the header section of our site. That's because this library loads its necessary libraries within the body part of our site.

Why don't we look at this more closely? Open the modules/mod_jw_ajaxhr/mod_jw_ajaxhr.php file, and search for the following code:

<script type="text/javascript" src="modules/mod_jw_ajaxhr/jquery.js"></script>
                        <script type="text/javascript">jQuery.noConflict();</script>
                        <script type="text/javascript" src="modules/mod_jw_ajaxhr/jquery.innerfade.js"></script>
                    

In this way scripts are included just in the body section of our site. In the previous extensions we saw the following code:

$document->addscript
                    

This code snippet added scripts to the head section of our site.

Does this change the way in which we can detect if the jQuery library has been loaded? No, we can detect it the same way as we have done before, as follows:

<?php
                        $app =& JFactory::getApplication();
                        if( !$app->get('jquery') ){
                        ?>
                        <script type="text/javascript" src="modules/mod_jw_ajaxhr/jquery.js"></script>
                        <script type="text/javascript">jQuery.noConflict();</script>
                        <?php
                        }
                        ?>
                        <script type="text/javascript" src="modules/mod_jw_ajaxhr/jquery.innerfade.js"></script>
                    

Done, just as we have been doing previously. Easy, isn't it?

This is another of the easy ones, as there's a parameter in the module's admin screen that lets us define if we want to load, or not load, the jQuery library.

Just go to the administrator screen of our site, then go to Extensions | Module Manager | Content Slider Module. Look for the Assume jQuery already loaded parameter, as seen in the following screenshot:

When we worked with this extension we set the parameter to Yes, as we knew we had already loaded jQuery. We will keep this parameter set to Yes, just so that we don't unnecessarily load another jQuery library. The next two extensions will be a bit different, but keep reading!