Description: This is a random name that you can assign to the plugin. It basically helps you to recognize the plugin. This setting is especially helpful in situations where you maybe using more than one instance of a plugin.
-
Full Path to Software: This refers to the path of the Magento installation on your server. It shall look something like this '/home/my_account_name/my_domain_name/magento' (Without the ' ')
Store views code of languages: you need to provide a list of store views code of Magento if you have a multi language shop and you want that Joomla change the language from a module of joomla. The list to provide should be like this one: en-
GB=store_view_english_code;fr-FR=store_view_french_code and so on. The en-
GB or fr-FR are the two
ISO letters code from Joomla used. See in Joomla Admin Extensions > Language manager to see the list integrated in your installation.
Note: In almost al cases the wizard will fill in these parameters for you.
Database Type (ie mysql): The type of database. mysql, mysqli etc. are among the various options.
Database Host: 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'. Choose accordingly.
Database Name: The name of your Database used to install and run Magento.
Database Username: The username required to access the database.
Database Password: The password used to access the database for the above mentioned username.
Table Prefix: The table prefix for Magento tables in the Database.
Database charset: by default it’s utf-8. So let it in utf-8.
Cookie Domain: First try leaving this value empty. In the majority of the installations this will work. If the login checker shows no errors and you are not logged in then it is time to set this cookie domain field. If you do so, it is very essential to set this value also correctly in your Magento administration (System > Configuration > Web > Session Cookie Management). The value should be set in both locations to '.yourdomain.com' (Without the ' '). This governs the cookie domain the generated cookies possess and is essential for dual login to work perfectly.
Cookie Path: Again, first try leaving this value empty. If you, after setting the cookie domain, still have problems logging in then it is time to set the cookie path. Start with '/'. This must be set in your Magento administration (System > Configuration > Web > Session Cookie Management) as well.
Cookie expiry time (minutes): This setting defines the Cookie duration for the Cookie generated by JFusion. You must set the same value as the one in the Magento administration (System > Configuration > Web > Session Cookie Management).
HTTP Auth: Allow authentification with cUrl through
HTTP authentification (not displayed in the screenshot)
HTTP Auth username: Username of the
HTTP authentification (not displayed in the screenshot)
HTTP Auth password: Password to provide for
HTTP authentification (not displayed in the screenshot)
Cookie secure: Determine if you need to secure the cookie with https.
Cookie HTTP only Determine if the cookie will use only http.
Form override: You can overwrite any data in the form.
Cookie Leave alone: Cookies that you don't wish to remove when logout.
Integration type: 0 = use same session for each request at login, 1 = it will not.
Relative Path: Determine if we should modify the url in the form or not.
Hidden: Add hidden values during the POST of the form.
Button: Add buttons data during the POST of the form.
API User: Username of the access to the
API provided to and by your Magento installation to allow some functionalities with the plugins like delete a user from Joomla.
API Key: Key of the access to the
API provided to and by your Magento installation to allow some functionalities with the plugins like delete a user from Joomla.
Login URL: Url where the form to log exist.
Login Form ID: Id or name of the form.
Input username ID: 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.
Input password ID: See above, but now for the password field.
Logout URL: Url where you logout.
Usergroup Mode: Mode in which way to handle user groups. 1) Simple: usergroups are only set for newly created users, after that usergroups are completely independent from other softwares. 2) Advanced: For JFusion slave plugins, you have the options to link usergroups to the JFusion master plugin. If the usergroup is changed in the JFusion master, the user will automatically be updated to its associated slave usergroup. Warning: When using advanced mode and JFusion as slave you can easily loose access to Joomla because the Joomla admin user will be moved out of Joomla's admin group. To prevent this you must create a special super admin group (and, if needed, an admin group) in Magento. Make Joomla master and Magento slave and set advanced user usergroup mode to on. Map the Joomla super admin group to this newly created super admin group in Magento. Map the admingroup also when you use it. Now perform a usersync from Jfusion (master) to Magento (slave). You now can safely set Magento as Master and Joomla as slave as long as you map the admin groups in both softwares correctly.
Default Usergroup: Select default user group of groups available in Magento, that new users will be assigned to.
Auto Update Activation: Update Activation status.
Allow user deletion: Allow to delete users include in this software. The
API user and key must be configured previously to work.
Did you disable registration: When you set Magento to be a slave, user registration must be disabled because the master will be handled this. Because Magento has no simple way of doing this you have to modify or delete the login/registration form. You can suppress Jfusion registration problem warning by setting the parameter below to 'yes'. See
How to disable user registration? to get a How to …?