Description of the plugin, can be changed should you have more than one copy.

Refers to the complete URL to the software. It should look something like this http://www.yourdomain.com/software

This refers to the path of the integration installation on your server. It shall look something like this /home/my_account_name/my_domain_name/integration or /var/www/httpdocs/integration depending on your server setup. To help you determine the path you need for this integration jFusion has filled in the path to the Joomla installation.

The setting comes into play when the Master software does not support usernames but allows the use of only email addresses for authetication and logging in. One such software supported at the moment by JFusion is Magento. In case you happen to use Magento as the Master, set this setting to 'E-mail'. Otherwise leave it as 'Username'.

If SEF mode is enabled, what should the URLs look like?

Database Type (ie mysql)::The type of database. mysql, mysqli etc. are among the various options.

The database host. Most hosts use 'localhost' to connect to their databases but certain provide specific URLs to access their databases like 'db.yourdomain.com'. Remote MYSQL is possible too. Choose accordingly

The name of your Database used to install and run the integration

The username required to access the database

The password used to access the database for the above mentioned username.”

The table prefix for Moodle tables in the Database.

Character set of the database.

Here you may have two options for usergroup management, simple and advanced. If plugin is set as the master, then you can only use simple mode. Simple mode will allow for a single selection of a Default Usergroup that each new user created by JFusion is assigned to (after they have been activated if activation is enabled). Once the group is assigned, it is never changed by JFusion. However, you have the option to enable the advanced mode if plugin is set as a slave. In advanced mode, you can assign a groups in plugin corresponding to various possible groups in Joomla!. If the group is changed in the master, JFusion will automatically update the groups of plugin to that which is paired to the master group when the user logs in. So for example, you let's say you have plugin's group Registered Users paired with Joomla's Registered and plugin's Administrator paired with Joomla's Administrator. If a user is in Joomla's Registered group and is changed to an Administrator, they will automatically be made part of the Administrator group in plugin.

If set to yes and plugin is set as slave, plugin's user's activation status will automatically be updated to that of the masters.

If set to yes and plugin is set as slave, plugin's user's email will automatically be updated to that of the masters.

If set to yes and plugin is set as slave, plugin's user's ban status will automatically be updated to that of the masters.

When in slave mode should a new user be created for inactive users in the master?

When in slave mode should a new user be created for blocked users in the master?

If set to yes, the user will be deleted from plugin if deleted from Joomla!

Cookie Name

Should be set the same as the cookies generated by the integration. (dot)domain.com eg .domain.com will work best.

Usually / works fine. However, this item should be set the same as in the integration. If using a path, put a slash at the end, like in /joomla/

Cookie expiry time (secs). Set to 0 to set the cookie as a session cookie.

Cookie on Secure connection only

Should we use a HTTP-only cookie? This depends on the settings in Joomla and integration software. If they use HTTP-only cookies, this should be set to yes.

Type 0 makes Curl use one session for reading the loginpage and posting. Type 1 makes Curl use seperate sessions. Type 2: use type 0 for Login and type 1 for Logout. Type 3: use type 1 for Login and type 0 for logout

Enable this if the integrated software's source directory is protected

Username to authenticate for password protected directories. Only applicable if HTTP authentication is enabled.

Password to authenticate for password protected directories. Only applicable if HTTP authentication is enabled.

This full URL should point to the page where the login form is displayed

Normally the login routines will pickup existsig cookies when logging in. With the brute force option these cookies will not be presented to the integration when logging in.

ID or name of the login form. You can find this by displaying the page source of the login page. Use the action field as an ID when this is a name/id less form

Whether the loginform contains a relative path for the action parameter

The is either the username or the email address, used to identify the user.Only fill in this field when you have a login form with non standard id and name for the username field. The routines will try to find this username field by testing for common names for id or name of the username in the form.

See above, but now for the password field

Add hidden values during the POST of the form

Add button values during the POST of the form

There are three ways the curl routines can handle logout. Ur: The integration uses a logout link to logout. You may specify field/data pairs to post in this case. Form: The integration uses the modified login form to logout. Here you can set the action parameter being relative or not. Brute Force. Not really a logout. The routins mimic a user closing the browser and ending a session that way. After a set timeout the integration will internally close the session as well

This full URL should eitherpoint to the page where the logout form is displayed, or the URL for a logout link

Whether the loginform contains a relative path for the action parameter

String for variables to post when logging out with type URLlogout (field1=xx&field2=yyy&…)

JFusion menu Itemid to redirect to

Redirection Mod