Hi Edwin,

We've made a dozen or so slave sites and have realized that each one doesn't need to have its own template folder. The design is the same for all of them, and at the moment, each time we make even a small CSS change, we need to update the CSS files in the master and all of the slave template directories. It would be great if we could simply maintain the master template files instead.

I know how to change the template so future slaves will have symbolic links, but is there a way to change the existing slaves so their template folders will have symbolic links pointing back to the master?

Thank you,
Chris

Hmm, just tried updating the template to use a symbolic link for the "templates" folder but I don't see the option. There's only special copy, copy etc. Is there no way for the slaves and master to all share a common template?

As a workaround, for now I updated each slave site's template index.php file with the hard-coded path to the master site's CSS file. That seems to work fine, though I'm still curious as to why the "symbolic link" option isn't available for the /templates folder.

On linux platform and when the sypmbolic links is allowed the action "special copy" correspond to a symbolic link.

If you have already created a "/templates" directory that you want to replace by a symbolic link, you need to delete the "/templates" directory manually (or rename it for security) and Open/Resave the slave site definition once you have changed the JMS template action with "special copy".

JMS does not modify a directory that is already created.
So if you have created a physical directory that you want to change in symbolic link, you need to remove it manually before that JMS rebuild it.
This is also true in the other side. If you have a directory that is a symbolic link that you want to convert in physical directory, you need to delete the symbolic link before rebuilding the /templates directory with the "action = copy".

The "Symbolic Link" action is not directly available because on Windows platform, this is a copy and not a link that is created. So this is a "special copy" because the action depends on the environment and if the symbolic link is allowed.

Same reason for the "/images" directory.

Thanks Edwin!

Chris