Just purchased JMS Multi site in hopes that it will provide me the functionality I am looking for.

I have a website that I want to use as a master that holds all data including users, groups, articles, pics. This site can be used by all users generically and the individual user can search for and use the data as needed.

My need is to create sub websites or portals for organizations to use as their website. Their site would pull data from the master as needed by the interests of its users. Each of these portals would need to be able to use different page layouts and modules in order to present the data in a customized way. So what Im looking for is one master site with all data and smaller websites using portions of the master's data as needed.

How do I go about setting this up? I was planning to use a master and then create a template site that organization leaders could use to create their own site but do I use one database and one joomla installation for all sites or do I use multiples

I would also like to do the same thing. I am setting up a number of city sites that will each have their own domain and logo. I want them to all use the same database. For example there will be a job and classified ad section that needs to share the same info for all cities.

I need to be able to change the modules for each city though. I have a banner ad script that needs to have a different module to target each city.

I have been looking through all of the tutorials and the pdf manual and still can not figure out how to set up everything. So it might be helpful to many people if you could explain how each field in both the template section and the manage site section should be set up.

I have tried many ways and can not seem to get anything set up.

Event if this is possible, we do not recommend to use the master website to store the data.
We recommend to consider the master website like a repository or a library where all the extensions are installed and used for the slave sites.
See tutorial technical document 0.b slide 21-24
www.jms2win.com/tutorial#jms12x-0b

Concerning the shared articles, see in the same video the concept described in the slide 41-43

So create in a specific website like "publisher" the articles that you want to store for the other websites. You could create sections and categories to organize them.
The other slave sites will come read them from this "publisher" website.


You can use a single DB or several DB.
With the "Article Sharing for JMS", there is no prooblem to read them from any location.
It is also compatible with older MySQL 4.0.x or higher.


So create a fresh slave site "publisher".
In the "publisher" website:
- create a section "national"
- create a category "sport"
- create articles that you store in the section "national" - categories "sport".

Create anothe slave site is "slave1"
In slave1:
- install the "Article Sharing for JMS"
- Create a menu item where you select the menu type "article sharing"
Select display articles as a "category blog"
Select the SITE = "publisher"
Select the section = "national"
Select the category = "sport"

That all.

Concerning modules for the header or thing like that you can use a customer HTML or other modules. As each website has its own content, they will have specific values.

OK Im installed. I decided to use one database for both master and slaves and it seems to be almost what I need. but I can not share all components. Only the more popular ones . I have some customized components that I need shared. The most important being a customized verison of Groupjive

I believe what I need is to configure slave using the third option in the manual 'Share an existing website' but there is only an explanation and no instruction on how to do this. I am assuming this type of configuration actually uses the same set of tables?

If you want to share an extension that is not present in current JMS tool definitiion, you have to send us this extension in attachement of an email.
We will review it.

You can not declare the sharing yourself.
This request to check all the DB access performed by the extension and discover the data model to ensure that it does not perform access to tables that would result by a sharing of the whole websites.