Your requirement are now more clear.

Concerning the users that you want to share between the master and the branches, you need to follow the procedure described in the tutorial video 16.
The difference is that you need to use the master instead of the "slave1" as website to replicated.

So create a JMS Template rule that consist in the sharing of the <master DB> and in which you enable the "sharing" for VirtueMart, Community Builder.

DocMan is NOT an extension that can be shared.
So all the definitions must be defined in each slave site.
Only the "dmdocument" directory can be shared.

Concerning the articles, you can use the "Article Sharing for JMS" that is able to read the articles coming from any website.
This will allow you display the articles coming from the master (event when present in the branch).
See for example the tutorial video 0.d that present how to setup the "Article Sharing for JMS"

To have the possibility change the template, you can follow the procedure described in the tutorial video CP-05.

If you want to share the menu, we have the "Multisites Menu Item" that allow create a bridge between website. Perhaps this will help you.

In very brief, the JMS Templates configuration could be inspired from the following (not tested)

Template ID = shareMaster
Domain = {site_url}/multisites/{site_id}
Select the template site = <master DB>
New table prefix = {site_id}_
Deploy directory = {site_dir}
Template folder = {deploy_dir}/templates

Select in "folder and file" tabs
Images => action = "Special copy"
Templates => action = "Special copy"
installation => action = "Ignore"
Ensure that the other directories are SL symbolic link

Select in the Share tabs
- VirtueMart - enabled
- Community Builder - enabled

Once you have create the "shareMaster" template
Create a slave using
Site ID = slave1
Select the template = shareMaster
Title = Test slave1 to share the master

Thats all

You can NOT create a fresh slave site as this will NOT share the users.
You need to repliacte a website in which you decide to share the users.

Hi Edwin

I see that you say ""In very brief, the JMS Templates configuration could be inspired from the following (not tested)"".....has this configuration not been done before?
Would you suggest another way?
I am going to try and let you know.

Rgds carmen

Hi edwin,

I did a brand new master website and then did exactly what you have said and it is not working from a "login user" point of view. The users cannot login from the front. It says "You must log in first".
Do you know what this could be?

I have attached the config of the template.
Rgds Carmen

When I say "not tested", this is because I have not installed an environment with exactly the same setup as you have described and I have given to you the setup that I would did in the same case.


In this post you mentioned "You must log in first".
Nowhere in the scenario that I provided you it is mentioned something from the front-end.
The scenarion that I given to you is for a creation of a slave site from the back-end. Not from the front-end.

It seems that you try creating a slave site from the front-end.
Does my assumption is correct ?
If you want to create a slave site from the front-end, the procedure is different.
In this case you can get inspired from the tutorial video 13 and you effectivelly need to login first.
In this case, you have to modify the JMS Template rule to use {site_prefix} and compute a {site_id}.

If you want that we setup the environment for you, this is possible with our billable support that you can order at
www.jms2win.com/download?page=shop.produ...35&category_id=1

Hi Edwin,

The login in that I am referring to is registered users logging from the front to access documents etc.

Now that I have setup Master and Slave 1, do I create the next websites from the master template or create another template copying slave 1?

Thanks for your assitance.
Carmen

Thsi is you that decide which webiste you want to replicate.
With JMS Multisites you can replicate any website.
In general, when you consider the master website as a repository or a library where the extensions are installed without any data then it is better to replicate a website in which you pre-configure the content.