Hi Edwin,

Thanks for finalising the new Create Site module.

Just a quick question; does the create site module need to be run from the frontend of the master site or can it be run from a parent site or even a slave site?

Just to be clear:

Master Site
- Parent Site 1
- - Slave Site 1
- - Slave Site 2

Thanks and regards.

Like for the component, the module can be used in any website where you have JMS installed to process the website creation from the front-end.

The module submit the request to the component.

Hi Edwin,

Thanks for your response.

Question 1: Is there an issue if I have JMS installed on multiple 'Parent Slave' sites and I run the installer from these Parent Slave sites?

So for example my Master will have 2 Parent Slaves with JMS installed and these parents will have their own slave sites:

Master (JMS Installed)
- Parent 1 (JMS Installed)
-- Slave 1
-- Slave 2
- Parent 2 (JMS Installed
-- Slave 3
-- Slave 4

Question 2: When I update or upgrade extensions do I first do this in the Master and then in the Parent Slave or does it all flow through from the Master (I understand in some cases I need to install directly into the slave if the tables are not present in JMS)?

Question 3: Are the symbolic links linked from the Master to the Parent Slave to the Slave or from the Master to the Slave directly? (regardless of where I run the JMS extension from)

Question 4: When I look at the JMS component on my Parent site under the Check Patches there is a warning for the configuration.php file: Not OK - The routing wrapper is not present in this MASTER configuration file. Actions: Add 16 lines containing the routing wrapper to the slave site.

Is it safe to run the JMS Patch on the Parent Slave site?

Thanks and regards.

If your question is how to install the "Multisites Create Site Module" in a slave site, you can just define it with the JMS tool menu as it does not contain any table.

Q3) See the result of the website created.
Normally, the link is always to the master.

Q4) Normal that a slave site report a warning message because this is not a master website. Normally JMS should never be administrated from a slave site.
We have disabled the "install" button to avoid trying install patches in a slave site.
So you can NOT install the patches in a slave site.

Hi Edwin,

I'm now in the final stages of setting up the front-end new site creation module.

JMS has been installed in the master website and I have created a slave site for the front-end public viewing.

The new site creation module will appear on the public front-end website and will be utilised by anonymous public users (i.e. the user has not logged in).

To get the module to work with an anonymous user you have suggested that I create a hidden menu item pointing to the JMS component and then set the item ID in the new site creation module to this menu item. This has worked without any issues because I have been testing everything in the master website.

Can you please confirm how I should setup the module in the slave website? Should I create a JMS Shared Menu Item and use this item ID in the module? Will the module work when I uninstall JMS from the slave site?

I've tried a few configuration options however I'm getting some strange behaviour so your advice is greatly appreciated.

Thanks and regards.

If you provide the "Creation Site Module" in the slave site, the "Set Item ID" make reference to the slave site menu item id.

In this case, the JMS Multi Sites component must be installed in the slave site to allow using the component to create the slave site from another slave site.