Hello:

First of all i just want to say thanks, because this is a great component!

But i'm facing a challenge, and i need a little advice...

I need to create a small hierarchy for my sites, just 3 levels of sites, i need to access this information in another component i'm developing...

I'm using different databases for every slave site...

Where should i store this information?
and most importantly... HOW??

thanks in advance....

When you want to create a hierarchy between website this is done via the JMS templates.
In JMS templates you defined which is the "parent" website that is used for the replication and how to create the "children" website.

So if you want to have your "master" website as parent of 3 slave sites that themselve may have childrens, you can define a JMS template "replic_master" template to create your first sublevel of slave sites.
After that go in JMS manage site and create your first level of slave site based on this template "replic_master"

Once you have your slave in level 1 (ie. slave1, slave2, slave3) you can again create JMS template to define how you create a sublevel of slave1.
So create a JMS template "replic_slave1" and repeat the operation in JMS manage to create the sublevel 1.1 based on replic_slave1.

And so on.
See the tutorial video 13 that show how to create slave site from the front-end.
It used the JMS templates and create 1 level dependency.

Thanks for the quick reply!!

but, how can i retrieve the hierarchy "level" from another component?

Thanks again!!

Retreive the hirerarchy level is not easy.
The only information that you could get is the "JMS templates" ID that you have specified in site manager.
Based on that you should recompute yourself the hierarchy level.

JMS does not have this level information and when it display the tree in the JMS tools, it reads all the site information where it retreives for each site its "JMS templates" ID that it uses to build a temporary tree in memory.
We can not advise you to use our internal JMS tools routine that compute this tree because we can not guarantee the API and its functionality. It is possible that we change it for internal reason.
If you want to get inspired of our code, you have to look in the models/tools.php and its getSiteDependencies function.

Thanks!!

i'll havea look at that file...

Thanks!!

i'll have a look at that file...