Profiles
The plugin is the core engine of jQuery Easy Profiles. It looks for any created module instance (profile) and use the profile's parameter settings to act on a specific area of a site.
Go to Extensions -> Plugins.
Select the system type to narrow down the list of available plugins.
Enable the System - jQuery Easy Profiles
plugin.
Position | The custom position the module instances of jQuery Easy Profile need to have to be recognized by the plugin. The default is jqeprofile . |
CDN of choice | The Content Delivery Network to be used by the plugin.
|
v2.0 Head-only modifications |
Limit the plugin processing to the <head> area of the page (off by default) Note Use when there is no need to check the <body> area. It will improve performance and limit server resources consumption. |
v2.0 Strip blank lines |
Removes the blank lines created by the plugin’s cleaning. Note Disabled by default because it may slow down the loading of long pages. |
All libraries | |
---|---|
v2.0 Protocol |
Set the protocol that will be used to load the libraries.
|
v2.0 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). |
Reporting | |
Report | Show a report of the changes made through-out by the plugin.
Reporting Toolfor more information |
Note All of these options are global settings for the jQuery Easy Profile
module instances.
jQuery, Bootstrap and MooTools
Starting with v2.2, the plugin can set jQuery, Bootstrap and MooTools options site-wide, removing the need to create a module instance of jQuery Easy Profile
for site-wide use.
By default, the plugin settings are used, but if a module instance exists and targets specific pages, the module instance settings will be used instead.
v2.0Scripts and Styles
Starting with v2.0, the plugin allows you to strip or add scripts and stylesheets site-wide, regardless of profiles being setup.
Note Scripts and styles have precedence over the module instances' ones.
v2.2Regular Expressions
Site-wide free-style regular expressions will be used on all pages EXCEPT when a module instance exists for a page, in which case the free-style regular expressions usable in all profiles will be used instead.