Are you enjoying the extensions? Did you like the support? Help others decide.
Leave a reviewRemove jQuery conflicts on Joomla websites overloaded with javascript libraries.
jQuery Easy re-orders scripts, fixes potential javascript issues and fine-tunes your pages for better performance.
Go even further with jQuery Easy Profiles (the pro version for jQuery Easy) and only target the pages that need special attention.
Fixing javascript/jQuery issues on a page is a process that usually requires several iterations (although most users will find that using the basic options will fix their issues). Start your investigations by setting the basic options of the plugin and if errors remain, proceed to the more advanced options in order to control the work that is done internally.
For terminology and questions you may have, please check the Frequently Asked Questions section.
jQuery Easy cannot analyze and fix issues on aggregated or zipped code.
Some tools or templates perform high levels of optimizations that render scripts unidentifiable (the plugin looks for file names but not the content of those files), therefore if a file is a compilation of library scripts, it won't find those scripts). Use one or the other. In this case, identify issues with jQuery Easy on non-aggregated code, fix the code internally (or by requesting support for the faulty extension(s)), disable jQuery Easy and finally optimize the code before putting the site into production.
Plugins are executed in the order in which they appear in the Ordering column of the Plugin Manager.
The jQuery Easy plugin needs to be called last. In most cases, the ordering doesn’t matter. However, in some cases, where you have more than one plugin triggered from the same event, and where the results of one plugin can affect the processing of jQuery Easy, the order can be important. In this case, you can change the order in the Plugin Manager by adjusting the Ordering values to control the execution order.
Install the plugin through the Extension Manager
of the Joomla administrator's console.
Note You can download and install the plugin directly from the Install from Web
tab of your website. Type simplifyyourweb in the search box and select jQuery Easy.
Install the package through the Extension Manager
of the Joomla administrator's console. It will install the jQuery Easy Profile module, the jQuery Easy Profiles and quickicon plugins and the Simplify Your Web Extensions library.
Note The Profiles
version can only be downloaded from this website, once you are logged in and if your license is valid.
Starting with version 2.3.3, you can now use the new download id that is associated with the extension. This will allow you to make one-click updates through the Joomla installer, without the need to download the updates manually.
Go to Extensions -> Plugins and select the Installer type.
Enter the download id (found on the site under 'My purchased licenses' once you are logged in) in the enabled jQuery Easy Profiles installer plugin.
If, for any reason, the external library, packaged with the extension, fails to install or update, please download and install manually.
Before updating, make sure you read the change logs and are aware of potential backward compatibility issues.
The upgrade is seamless and no side effects have been reported so far. If you have the latest version installed under Joomla 4.4, no update is necessary when upgrading to Joomla 5.
The extension works properly without the Compatibility plugin enabled.
There have been many under-the-hood modifications in Joomla 4, which means that the changes you made under Joomla 3 through the plugin to fix javascript issues will need to be re-evaluated.
Therefore, disable the plugin when moving your site to Joomla 4. Install the specific Joomla 4 version and re-enable only if needed under your new configuration. The plugin's parameters are reset on install unless you are using the pro version.
For general instructions on moving from Joomla 3.10 to Joomla 4, please check this tutorial out!
Must read: specific instructions about the migration for this extension.
Joomla 4 This version supports all Joomla versions 4.1 and over.
It's a bug fix release with additional support for Bootstrap 5.3.
It's a bug fix release with additional support for Bootstrap 5.2.
Profiles The main feature in this release is the possible addition of defer attributes for all scripts.
This version either adds more options or replace old ones. In any case, it does not change anything in the behavior of your pages (unless you select any of the new options). All old parameters are automatically replaced with the newer counterparts and parameter values are moved over to the new parameters on update.
There are no potential issues to look for.
The noConflict regular expression has been improved and when stripping 'noConflict' code, the option 'Yes, ignore variable declarations' now catches ALL declarations, eliminating errors that could result from falsely removing 'must keep' variable declarations. If you compensated the removal of needed variables declarations by adding them again in 'Add script declarations' ('scripts' tab), you will need to remove those extra declarations to avoid variable declaration duplicates.
There have been some internal code improvements, but they won't affect your settings.
There is no backward incompatibility introduced in this major version but the extensions went through a major code re-factoring and many under-the-hood improvements.
Therefore it is of the most importance that you test the update before installing it on your production site.
The plugin's 'engine' may also catch more issues than before, potentially hidden in your previous installation.
Profiles Core overrides options have moved to the plugin. If you have enabled the options disable tooltips and disable caption in the global configuration section, you will need to reset them in the plugin (the new option is Yes, by overload)
Profiles Regular expressions (regexp) have been modified internally. If you are replacing the extension's regexp with your own, you may need to modify them as well. The internal regexp no longer include src="
and href="
. The attributes src="
and href="
are re-injected into the regexp only when lookups are made on the whole page.
The extension is now packaged as a component, with a brand new dashboard packed with information.
Other than the revamped user interface, there have been a few fixes that may affect your page's output.
1 Some regular expressions would not take into account the -
and instead would mistakenly refer to it as the range indicator.
What does it imply practically? Some scripts or stylesheets may get removed, while they were not removed before the update.
For instance, the script /js/sub-directory/jquery.js
was not removed in v1.x. It is now removed in v2.x.
2 The stripping of scripts and stylesheets (options strip remaining...
) is now independent from the jQuery fixes, allowing you to use those options even though no fixes are made on a page.
Starting with jQuery Easy Profiles
v2.2, it becomes extremely easy to upgrade from the free plugin jQuery Easy
.
Due to the way the profiles version works, when you upgrade and if jQuery Easy
is enabled, you will end up with:
jQuery Easysettings transferred to the jQuery Easy Profiles plugin (only if the free plugin was used site-wide),
jQuery Easysettings transferred to a published jQuery Easy Profile module instance (only if the free plugin was used in specific areas of the site),
jQuery Easy Profilesplugin enabled,
jQuery Easyplugin disabled.
The transfer should be seamless, and you should not have any disturbance on the public side of the site.
Note that there is no direct path to upgrade from the free plugin prior to jQuery Easy Profiles
v2.2.
In that case, make sure the free plugin jQuery Easy
is disabled and that the new plugin jQuery Easy Profiles
is enabled. You can use the free plugin as reference of the previous implementation.
These are the steps to follow specifically for jQuery Easy or jQuery Easy Profiles to experience the smoothest migration possible.
There is no migration path from the free version under Joomla 3.10 to the pro version in Joomla 4. Migrate the free version from Joomla 3.10 to Joomla 4 first, then under Joomla 4, upgrade to the pro version.
Go to Extensions -> Plugins.
Type 'jQuery Easy' in the search box.
Disable the plugins, if enabled:
This will remove potential update issue warnings and prevent issues once under Joomla 4 until the extension is re-installed.
Go to Components -> Joomla! Update. Click on Check for Updates. You will see update pre-checks.
Pro The SimplifyYourWeb Extensions Library will be updated automatically. Ignore warnings about the library, if any.
Download the free version of the extension for Joomla 4 or the pro version and all add-ons (information types) you need for your design(s).
Go to System -> Install section. Click on Extensions.
Install the free package jQuery Easy or the pro package jQuery Easy Profiles for Joomla 4.
Go to System -> Manage section. Click on Plugins.
Type 'jQuery Easy' in the search box.
Re-enable the plugins ONLY if you have remaining javascript issues in your pages or want to use cloud versions of the libraries:
The free plugin's parameters are reset on install.
Pro The plugin and module instances are remained untouched.
Go to Extensions -> Manage -> Manage. Type 'jQuery Easy' in the search box.
Select the 'System - jQuery Easy' plugin and click on Uninstall.
Select the component ONLY and click on Uninstall. This will remove all extensions at once. If it does not, remove them one by one.
Joomla 3.10 You may see an additional Package called 'jQuery Easy Profiles'. Remove the package instead of the component (all extensions tied to the package can't be removed individually).
Go to System. In the Manage section, go to Extensions.
Type 'jQuery Easy' in the search box.
Select the 'jQuery Easy' package and click on Uninstall.
Select the 'jQuery Easy Profiles' package then click on Uninstall. This will remove all extensions installed through that package.
Warning There will be no conflict resolution until jQuery is enabled.
Enabling jQuery will trigger several actions. By default (before enabling/modifying advanced options), the plugin will:
no conflict
scripts and declarations,no conflict
code script,Enable jQuery |
|
Version |
Profiles slimversions are available. |
Sub-version | When using versions 1.9 and over, the Google CDN asks we specify which release of that milestone is actually requested. Prior to v1.9, the latest release of each milestone is used by default. But one can still specify a sub-version. Example |
Local path | The path to the local file when using the local version option.
Example |
Migrate version | Use in conjunction with jQuery libraries v1.9 and over. It garanties older scripts created for jQuery remain compatible with the latest versions of the library.
|
New Sub-version |
Starting version 3.0, you need to specify the Migrate sub-version (x)
Example |
Migrate local path | The local path to the jQuery Migrate plugin
Example |
Version |
|
Sub-version | When using versions 1.9 and over, the Google CDN asks we specify which release of that milestone is actually requested. Prior to v1.9, the latest release of each milestone is used by default. But one can still specify a sub-version. Example |
Custom/Local path | The path to the local or custom file when using the custom/local option. The jQuery UI file can be the full blown UI library or a custom one created at the jQuery UI website. Example |
Theme | Set the UI theme (or skin) that will be used in conjunction with the jQuery UI library. Themes are not always required.
Warning Since jQuery UI v1.10.2, the base theme is not available anymore. Use another skin or you will end up with errors on the page. It has been re-introduced in jQuery UI v1.12.0. |
Custom/local theme path | The path to the custom or local CSS file. Get or customize skins at the ![]() Note Images are usually associated with a skin. Wherever the path of your file is, add a images/ folder containing those images.
Example |
Version |
|
Local javascript path | When using the localoption, set the path to the local javascript (.js) file Example |
Local stylesheet path | When using the localoption, set the path to the local stylesheet (.css) file Example |
Theme | Set the mobile theme that will be used in conjunction with jQuery Mobile.
|
Custom theme path(s) | The path to the custom skin stylesheet(s). Customize skins at the ![]() Example |
Protocol | Set the protocol that will be used to load the libraries.
|
Compression | Load the libraries compressed or not. The ‘minified’ option is selected by default (best loading times). The un-compressed libraries would be mostly used for jQuery debugging (perfect if you want to see Migrate logs). |
Note Using sub-versions is useful for caching the library files for a year and therefore optimize website loading times. Find more information at the BucketSoft blog.
Note The plugin will sometimes remove the wrong scripts when looking for jQuery libraries. For instance:
…searchtools.jquery.min.js
will be removed, wrongly identified as a jQuery library,…jquery.searchtools.min.js
will not be removed, rightly assuming this is a jQuery plugin.When a library has been wrongly deleted (easily identified if you are using the reporting tool or comparing the source code before and after enabling the plugin), use the Ignore scripts
advanced option to force the plugin to ignore the script in its search for jQuery libraries.
My life would suck without jQuery Easy Profiles. I’ve got complex, messy sites. jQuery Easy Profiles makes them work. The support is first rate. Olivier is one of the smartest, nicest, most helpful people I’ve had the pleasure of ever working with. Thank you!
This product is not affiliated with or endorsed by The Joomla! Project™. It is not supported or warranted by The Joomla! Project or Open Source Matters.
The Joomla!® name and logo is used under a limited license granted by Open Source Matters the trademark holder in the United States and other countries.