FAQ/Change History

Get a new download ID for the latest version

To receive a new download ID corresponding to the product you have ordered, you have a special "get latest version" menu that is available when you are logged into JMS.
http://www.jms2win.com/get-latest-version

Select (check box) the product for which you want to receive a new download ID and click on "get latest version" button in the top right.

This will resend youan email with the new download ID corresponding to the selected producted.

Here we show in a video how to get the latest version.

How to update Joomla Multi Sites

Normally, you can install JMS over a current one.
Nevertheless, It is advised to "uninstall" the JMS patches with current version of JMS before installing the new JMS version.
When the new JMS version is installed, you can re-install the JMS patches.

Uninstall the JMS patches is also recommanded when you want to update Joomla itself.
This reduce a risk of inconsistency between the patches that are present and the patches that are missing due to the Joomla update (new files installed by Joomla).

YES, with JMS 1.2.x, it is now possible to share the users between several website.
With this new feature, you can share the standard Joomla users but also a limited number of extension such as:

• VirtueMart users;
• Full VritueMart including the catalog, prices, ...
• Full Community Builder
• Full JomSocial
• Full SOBI2

This is not an exhaustive list.

Joomla multisite version 1.2.x also share the sessions (Single Sign-in). That means for example that you don't have to login again when you go from one website to another website.

In previous version JMS 1.0.x or JMS 1.1.x, it was NOT possible to share the users.

YES, with JMS 1.2.x, it is now possible to share the users between several website.
With this new feature, you can share the standard Joomla users but also a limited number of extension such as:

• VirtueMart users;
• Full VritueMart including the catalog, prices, ...
• Full Community Builder
• Full JomSocial
• Full SOBI2

This is not an exhaustive list.

In JMS 1.0.x or JMS 1.1.x, it was NOT possible share the user.

Joobi JSetup is an extension encrypted with IonCube.

The installation of this extension into a slave site is not easy due to the way this extension is working and due to its encryption.

We have identified a method to re-install it into a slave site.

JMS does allow to re-install the extension into a slave site because JSetup delete its temporary component that is used for the installation.
Therefore JMS refuse to re-isntall it into a slave site because it does not find it in the master website.

The procedure consist in a partial installation of JSetup in the master website to let the JSetup temporary installation component "Joobi Installer" remaining on the master website.
So you install JSetup in the master website and stop when it ask you accept the license and click on "next" button to complete the installation.

Once you have the "Joobi Installer" present in the master website, you can now re-install JSetup in a slave site.

If will ask you again to accept the license and click on the next button.

Once you have installed JSetup in the slave site, the result will be that JSetup will delete on the disk the "joobi installer" that will cause your master website not able to use it anymore. At this moment, you can Uninstall "joobi installer" in the master website and re-install it for another slave site.

When you will try re-isntall again the JSetup in a second slave site, JSetup will detect that some files are already present on the disk and will propose you to un-install them for your current slave site (ie slave no 2). You can un-install them and re-install just after.

When done, you will have a second slave site installed with JSetup.

You have to repeat the master "joobi installer" uninstallation and partial re-installation to allow re-install JSetup in each slave site.

Yes and No.

NO

because JMS only share the files and folders present on the disk. It shares the Joomla Installation.

The each websites used its own content or at least different table prefix when it shares the same database.

This means that articles, news, forum, users or whatever that is stored in the database is totally independent.

YES

because we have developped a special component “Articles Sharing for Joomla Multi Sites” that allow to display the articles, categories, sections from any websites defined with Joomla Multi Sites.
With this extensin, you don't need anymore to replicate or use special extension to synchronise the websites.

This “Articles Sharing” consists in a new menu type “Multi Sites articles sharing” that works like the standard Joomla menu type “Articles” except it adds the possibility to select the websites where the articles, categories, or sections are located.
“Articles Sharing for Joomla Multi Sites” only display the articles.
The menu type implemented are:
-    Multi Sites articles layout;
-    Multi Sites Category Blog Layout;
-    Multi Sites Category List Layout;
-    Multi Sites Front Page Blog Layout;
-    Multi Sites Section Blog Layout;
-    Multi Sites Sections Layout;
It does not allow to edit or submit articles.
“Archives” is not implemented.

The "articles sharing" required with JMS 1.1.5 or higher.

YES, we have redo the test with Joomla 1.5.8 and it is working.
We already have customers that have updated with success their Joomla and now working with the version 1.5.8.

Joomla FTP Layer is a feature introduced in Joomla 1.5 to resolve some permission problem experienced by many Linux/Unix host Users.

Some Hosting provider or Shared hosting servers or simply server may have a high security level that does not autorize to write files or create directories.

With Joomla 1.5 and FTP Layer, it is now possible to use FTP to create directories or simply write files.
To use the FTP Layer, some parameters must be specified such as the URL or IP address, the user name and the password.

The FTP Layer can be setup during the installation or changed in the Global Configuratoin (if you can write it).
If you have already installed Joomla and the FTP Layer is not enable and you can not modify it using the Global configuration, the only solution consists in updating the "configuration.php" file manually. (Probably using an FTP connection or telnet).

Keep 'jos_' table prefix for the websites is possible when only one site uses this database.
When one or more slave sites share the same database, the 'jos_' table prefix CAN NOT be used because all the users present in the jos_users are deleted during the installation of a slave site. (Whatever the table prefix chosen during the installation procedure).

Some person wants to install Joomla Multi Sites on an existing websites that is already installed using the 'jos_' table as prefix.
This is possible if ALL the slave sites are installed using one or multiple databases other than the master site database.

In that case, the slave sites will use diffrerent table prefix and never use the 'jos_' table prefix.
As any 'jos_' table is present in the slave database, there is no risk to delete the jos_users present in the slave database.
If you want to keep 'jos_' table prefix for the slave sites, you will have to create as many slave database than there are slave sites.

In conclusion, each time you want to use 'jos_' as table prefix for a website, this website must be alone to use this database.
When you share a same database for multiple website, you can NEVER use 'jos_' table prefix to prevent the jos_users record deletion during the installation of a slave site.

YES, it is possible to see JMS working in a demo environment.
You have a description of this demonstration environment in the document "demo installation".
We invite you to read this document that show you all the steps of a typical installation and will give the URL of the master and slave sites.

In addition, we have live installation.
This www.jms2win.com is already a slave site of our company website.
www.faq2win.com is another slave site that share the same database than www.jms2win.com

NO, a trial version of JMS is not available.
It is not possible to create a special JMS that will not provide all the functionalities or give the full functionalities for a limited period of time.
As this is a component developped in PHP, it is difficult to protect this code. Event with obfuscation.

To help you have a better idea on how JMS is working, you have different video present in the tutorial that illustrate some cases:

• Tutorial Step 0 present the concept of joomla multisite
• Tutorial step 9 present how to create a slave site into a sub-directory of the master website.
• Tutorial step 13 present how to create a slave site from the front-end.
  It uses the "website template" to define the replicate rules that must be applied to create the new slave sites.

For people that want to test this component, we have a "demo" website that can be used on case by case basis to test the installation of specific extensions.
We give the administrator password to the potential customer that have doubt concerning the installation of some extensions.
As there is only one demo environment and we have to reset it each time a new customer want to test his specific extension, this explain why we deliver the login and password for a limited period of time and on case by case basis.

YES, each web sites can select its own default template.
As each sites use its own database or at least diffrent table prefix, the customisation each sites is independant.
The only exception concern the extension that save their configuration information on disk rather than in database.
Sometime we have to provide a patch for such extensions to let them use separate configuration.

YES, all websites share the same Joomla Installation.
In fact, a new 'multisites' directory is created and store all the 'configuration.php' parameters associeted to each website.
In such maner that we a domain is called, Joomla Multi Site select the appropriate 'conifiguration.php' file to connect the database and proceed with the request.

Joomla Multi Sites (Version 1.0.x and also Version 1.1.x when Symbolic Links is not available) requires that ALL the domains and sub-domains SHARE the same directory (The Joomla Installation - Files and Folders).

The procedure below describes how to check if the Domain Hosting is correctly configured for each of the domains that you want that Joomla Multi Sites manage.

This procedure does NOT require Joomla Multi Sites and can be tested totally independently without anything else than the "hello world" files that you can be download here.

The objective is to install a "hello word" file into the directory of your master domain and check if you can see also this files from the domain that will be used as slave domain.

The hello.zip file contain:

• hello.txt : This file contain "Hello world";
• hello.php : This file is a php script that:
  • display the text "Hello world script";
  • display the current path where it is installed
  • test if the Symbolic Links are available on your environment
    This last point is important when your different domains are located and defined into separated directories.
    In this case, the Symbolic Links could be (conditional) used to create a bridge between the master directory and the slave directory. Perhaps you will encounter permission problem to create the bridge between the master and slave directory.
  • When the slave sites is located into another directory than the master website AND the Symbolic Links is present then this script also allow you to test the creation of the bridge between the Slave Site and the Master Website.
    This allows you to verify if the Joomla Multi Site Symbolic Link feature present in the version 1.1.x can be used.

If you want to see a sample of results of those scripts and therefore the expected results here are some links that you can use.
Master website URL:

• http://master.demo.jms2win.com/hello.txt
• http://master.demo.jms2win.com/hello.php

• http://slave1.demo.jms2win.com/hello.txt
• http://slave1.demo.jms2win.com/hello.php

Notice the both Master and Slave websites display exactly the same "The current path is".
This is because the Domain hosting share the SAME path (share the same joomla installation - share the same files and folders)

"Hello world" Installation and test procedure

• Unzip the hello.zip file into the root of domain you will consider as it will be your master websites.
• Enter the URL http://www.master_domain.com/hello.txt
  You should see the "Hello world" text displayed.
  • If you see the "Hello world" text, you can repeat the operation with the script "hello.php"
    http://www.master_domain.com/hello.php
    This script will display "Hello world script" and additinoal information such as the path where it is installed and if the Symbolic Links are available
• Now that you know the the"hello" files are correctly installed on the master website, you can check the slave site domain hosting configuration
• If the "hello.php" display that "Symbolic Links IS NOT OK", this means that is mandatory to map all the slave sites into the same path than the master website. The path is the one displayed by "hello.php" script.
• If the "hello.php" display that "Symbolic Links is PRESENT", this means that it should be possible to have the slave sites deployed into an external directory. Perhaps you will encounter later problem with permission.

Test that slave sites are mapped in the same directory than the master website

The objectif is to check that you can see the "hello.txt" file from the other slave domain.
To help you, the "hello.php" script display the path that must be used when you setup the slave domain into your Domain Hosting tools.

You can have different scenario:

Case of another domain than the master domain

He this is the case of "www.slave-domain.com" and "www.master-domain.com".
In this case, it is necessary to ensure that both domain (slave and master) use the same full path.

GoDaddy - Domain and Sub-domain setting with the same folder path

This is a summary of the steps to configure GoDaddy:

• Login to the "Hosting Management" -> "My Hosting Account"
• Manage the Hosting: Select "My Products" menu, option "Hosting"and in "Control Panel" click on the link "Manage Account"
• Go in the "Domain Management".
  - Open the "Setting" panel;
  - Click on icon "Domain Management" to display the list of domain that are currently attached to your account.
• Clik on button "Add Domain" (top right)
• Enter your "domain name" and specify its "folder".
  For Joomla Mulii Sites, put here the same folder than the one used by your master domain.

 See also Godaddy Configuration here.

CPanel  - Same path using AddOn Domain

When using CPanel, this can be achieved with AddOn domain where you can specify the path that must be used by the domain. Becarefull if you are using different CPanel account. In this case, it is probable that path will be different as they will be relative to each account. You probably will have to consider using Symbolic Links to create a link between the different accounts.
In summary:

• Go in CPanel and select AddOn domain
• Once in the AddOn Domains, then you will see an interface similar to this:
  Create an AddOn domain
  • New domain: the “slave site” name
  • Document Root: This is the root where the Master Site with the installed component is installed.
    This is also the path that is displayed by JMS after it has created the slave site (see the message in blue in the top)

See also CPanel Configuration here. For screen shot provided by one of our customer: click here

When you have configured your CPanel, you can test the "hello.txt" file and "hello.php" scripts.

Plesk - Create an alias domain on the master domain
When using Plesk tool to configure the Hosting Domains, this can be achieved in defining domain alias on the master domain.
When you define an alias, this automatically use the same path than your master domain as it is defined as a synonym (an alias).
The procedure conisists in:

• Login into Plesk
• Click on Domain
• Click on the master domain to manage it
• Click on "alias domain" to create alias on the master domain
• Create entries for the slaves domain.

To have a more detailled description of this procedure and screen shot, see How to configure Plesk alias domain.

Case of sub-domains using the same domain than the master domain

He this is the case of "slave1.master-domain.com".
In this case, you can generally defined the sub-domain (slave1) as a Hosting Domain alias of your (master-domain.com).
When you define an alias, this automatically use the same path than your master domain as it is defined as a synonym (an alias).

The present GoDaddy domain configuration is based on the configuration of a customer.

Thsi procedure shows you how to configure several domain to share the same directory path than the master domain.

The steps described below are:

• Login to the "Hosting Management" -> "My Hosting Account"
• Manage the Hosting: Select "My Products" menu, option "Hosting"and in "Control Panel" click on the link "Manage Account"
• Go in the "Domain Management".
  - Open the "Setting" panel;
  - Click on icon "Domain Management" to display the list of domain that are currently attached to your account.
• Clik on button "Add Domain" (top right)
• Enter your "domain name" and specify its "folder".
  For Joomla Mulii Sites, put here the same folder than the one used by your master domain.

Login

Manage account

Domain Management

 Add Domain

 Domain name and folder definition

Joomla Multi Sites requires that all the websites (master websites and all the slave sites) share the same Joomla Installation folder.

This mean that you have to setup each domain to be mapped on the same folder.

In the procedure below, we summarize the different steps to folllow.
We also provide you a link to a document provided by one of our customer that explain with screen shot, the different steps he followed to configure CPanel.

In summary:

• Go in CPanel and select AddOn domain
• Once in the AddOn Domains, then you will see an interface similar to this:
  Create an AddOn domain
  • New domain: the “slave site” name
  • Document Root: This is the root where the Master Site with the installed component is installed.
    This is also the path that is displayed by JMS after it has created the slave site (see the message in blue in the top)

Some customers use Plesk for the administration of their domains.

Most Plesk users know how to create a domain but not necessary how to provide a specific folder for this domain.
In general the users create a domain that has its own folder.

When working on Unix platform, Joomla Multi Sites Version 1.1.x or higher offers you the possibility to deploy a website in a different directory than the master but only if the Symbolic Links is supported by your hosting provider and if you have the permission to create such links between the directories.
In this case, you can specify the directory that is created by Plesk from within Jommla Multi Sites.

If you want to use the same directory as the master website (as we recommend), the procedure below is provided by one of our customers.
We are providing it to help Plesk users in the configuration of their system.
We cannot guarantee the accuracy.

In summary:

• Login into Plesk
• Click on Domain
• Click on the Master domain on which you want to add alias
• Click on "domain alias" 
• Add the different slave sites as an alias domain of your master.
  As the slave sites are defined as an alias (synomym) of the master website, they automatically also use the same path of the master websites. This means that they share the same files and folder of the Joomla Installation.

 Login into plesk

Click on the domain

Click on the "master-domaincom" to enter in the DNS definition of this domain

Click on Add Domain Alias to declare the slave sites as a synonym (alias) of the master website

When using Joomla Multi Sites on a Windows Platform, it is required that all the domain and sub-domain share the same directory path.

When you define the domain or sub-domain, you must be checked the permission of the directory that you have create allow to be accessible via Internet. For that, the security permission must include the user "Internet Guest Account".

The second element is to share the same directory path than the master website.

For that, in IIS, when you have a look in the property of the domain or sub-domain that you have defined, you have to check the "home directory".
The local path must have a value identical to the one of your master website.
This is the path that JMS display you when you create a new slave site.

You may also have to check the permission of the domain or sub-domain to ensure that you allow to execute PHP script.
Otherwise, only HTML files can be displayed by your domain or sub-domain.

Here below, we present how to configure a domain or a sub-domain on DreamHost web hosting.
The ScreenShots have been provided by a customers that use Joomla Multi Sites.

In summary, the operation consists in:

• Go in "Manage Domain" and click on "Add New Domain / Sub-Domain)
• When you arrive in the "Manage Domains"
  • "Host to domain": Enter the domain or sub-domain you want to host
  • "Specify your web directory": Change the default value by the directory path of your master website.
    For example
    if you have a "domain.com" with directory "/home/username/domain.com".
    When you define a "subdomain.domain.com" must change the path to "/home/username/domain.com".

Here are the screenshots that illustrate this case

Manage Domain

Specify Website Directory

The following procedure is a summary of the full procedure described by one of our customer and present in the PDF "How to configure JMS with IX Web Hosting". This ful document contain screenshot that can be helpfull.

In summary the operation consist to setup a domain as usual in IX WebHosting and retreive the "HTML Directory Name" that must be used by JMS in the deploy diirectory field. This assume that Symbolic Links is allowed in JMS.

• Login in IX Web Hosting
• Select Hosting Products menu / Manage 
• Click on "Domains" present in the section "Main"
• Click on "Add a new domain" button in bottom right
• Enter the domain name
• When done, edit the domain that you have just created to retreive the "HTML Directory Name" that must be used in JMS deploy directory
• Return in "main" section and select "Web Options" to setup your domain to recognize index.php by default
• Enable MultiViews
• Go now in "Tools" section and start "File Manager"
• Remove or rename the index.html

Based on the information provided by one of our customers, here it is the procedure he has communicated to us concerning the configuration of lighthttpd.conf.
The information provided below was not checked and is provided AS IS in hope this will help other customers

 1.- Enabled mod_simple_vhost en your /etc/lighttpd/lighttpd.conf

server.modules  = (
                                "mod_alias",
                                "mod_access",
                                "mod_fastcgi",
                                "mod_simple_vhost",
                                "mod_accesslog" )
2.- Configure a Virtual Host for your Parent Site
     $HTTP["host"]=~ "joomla.puebla.gob.mx"{
                                 server.document-root = "/var/www/lighttpd/puebla"
      }

3.- Configure your Slave Sites using vhost sintaxys for the same Document root
     $HTTP["host"]=~ "joomla.sep.puebla.gob.mx"{
        simple-vhost.server-root = "/var/www/lighttpd"
        simple-vhost.document-root = "puebla"
      }
4.- Restart lighttpd "/etd/init.d/lighttpd restart"

This message may appears when try to access a slave site that you have created into JMS and when you have deployed your website into a specific directory.

In this case, JMS creates several Symbolic Links into the deployed directory and in particular a Symbolic Link on the installation directory.

The problem may comes on the fact that apaches is not configured to follow the symbolic link and therefore that the installation PHP files can not be founded.

When you are using the ".htaccess" provided by Joomla it normally contain a statement like
Options +FollowSymLinks

This statement inform apache to follow the symbolic links.

If you don't use the  ".htaccess", you may have to directly enable the FollowSymLinks into the apache configuration file.

Some customers have reported a problem during the standard Joomla installation.

If you received an error like:

Undefined index: DBtype in /home/heinoset/muut_html/joomla/installation/installer/models/model.php on line 764

This is due to a problem when installing the sample data or trying to migrate some data from an older joomla database.
To solve this problem, it is recommended to install joomla without the sample data.

This problem is reported with Joomla Multi Sites 1.0.8 and affect also all previous versions.

This issue is solved in Patch Definition versoin 1.0.7 or higher.

Sometime when sharing a large number of websites, it is welcome to have specific folders for Media or Images.
In Joomla global configuration, it is possible to change the default Media and Images folder present in the system panel.

If you want to change those default value for a slave site, it is suggested to point on a directory that contains a duplication of the original Media / Images folder in aim to provide a default set of images. 

Those setting are saved in the database and are specific to a website.

Joomla multisites is sensitive to permission as it needs to update some core Joomla files.
When working in Windows environement, the FTP Layer can not be used to solve the permission problem.
An alternative solution consist in giving ALL rights to IIS during the installation of JMS.

The  procedure below describe how to change the permission in Internet Information Service (IIS).
This procedure consists in:

• Add the user everyone to main directory of the website
• Give to the user everyone the permission "WRITE"
• Install Joomla Multi Sites
• Remove the user everyone to restore the IIS normal rights.

Start Administrative tool - Internet Information Service (IIS) manager

Select the permission menu

First select the directory where you want to change the permission. In our case, we have selected the root directory of our website.
Click the right button to see the contextual menu.

Add the "everyone" user

Here the objective is to add the user "everyone" with the "write" permission

First click ADD to add a new user

Enter the "everyone" and check it exists and is correctly spelled.

Set write permission to the "everyone" user

Here the objective is to add the user "everyone" with the "write" permission

NOW YOU CAN INSTALL Joomla Multi Sites.

Don't forget to DELETE the user "EveryOne" when the installation is done.

When an error message “Unable to write entry” appears, this means that joomla try to extract files from an archive (tar.gz) file and that the destination is write protected.
This can happen when some files of the list of patches have the "Read only" attribute or when the owner is different than the current one.

The action consist to check the permission and owner of each files present in the patches list.
Starting with Joomla Multi Sites version 1.0.4, additional checks are now performed to report the user on potential permission problem.

Some customers have reported some difficulties when using Joomla Fantastico that protect files and give different owner between joomla standard files and the extensions.

Sometimes, you install a slave site and you forget to install the "sample data" or you change your mind after the installation.

The procedure below give you different alternatives to recreate a database with the sample data

Solution 1: Delete the sites and recreate it.

This probably the faster method and that can be done using JMS interface.

Solution 2: Create a second site that use the same DB name and table prefix

This solution consists in creating another slave site in using the same db name and table prefix than the previous one. When it is installed, you can delete the second site.
This solution is slower because it requires to declare the new domain or sub-domain.

Solution 3: Delete the configuration present in the specific site directory.

This solution consists in a manual deletion of the file configuration.php present in the directory multisites/xxx where xxx is the site id.
When you connect again into the slave site, it will request a new installation.
This solution is very fast but require a direct access to the file. (You need an FTP tool, telnet, or a direct access to the file)

Standard Joomla has the possibility to specify a table prefix for all the tables created for a website.
By default, the table prefix is jos_ but can be modified when multiple websites share the same database.

Joomla Multi Sites uses also this feature that consists in using different table prefix when multiple websites wants to share the same database.

The configuration of the table prefix can be specified at the installation as show below or after the installation in using the adminitration global configuration panel.