Hi - I am trying to achieve a Full Shared template directory. I've read enough posts and tutorials, to understand the differences between Special Copy and Copy, and am doing the following:

In JMS Templates
- In file/folder, put the "templates" directory action = "special copy".
- In Common, put the template folder = "empty field", I originally had {deploy_dir}/templates

The result, I can create slave sites that point back to master, and a symbolic link is created for the Templates Folder and it's content, which is what I want, but when I launch the slave site, no template is displayed - only text.

Is this because my slave site is pointing to a copy of the master? What am I missing? I would appreciate any advice?

Check that the Symbolic Link is created correctly and that you have the expected CSS present at the place that is defined in the front-end.

See the HTML source produced and verify the CSS link.

Check also that you can access the directory with a "hello.txt" file and that the server correctly follow the symbolic links

Thanks Edwin....

I uploaded the Hello.zip and extracted to both my master and slave sites, which are in different directories.

master = /public_html/ms
slave= /public_html/ms2

Hello Results in:
- the hello.txt shows correctly on both master and slave when browsing,
- the hello.php comes back with "Symbolic Link is PRESENT" on both master and slave

Viewed source shows:
- master: /templates/yoo_studio/css/template.css
- slave: /home/mst/public_html/ms/templates/yoo_studio/css/template.css
...the slave path is pointing to the master/template dir, but should it be the full path?

Also, I did not encounter any errors or permission issues when I created the slave site...still not sure why the slave site opens up in "text only", no css/template

I did try creating the slave site with:
1: Common Templates = {deploy_dir}/templates, and File/Folders to "copy", this scenario worked perfectly, and the slave site displayed its template
2: Common Templates = "empty", and File/Folders to "special", this scenario fails to load the template.

I hope the above detail helps....

Thanks again for the help.

Btw - I also read earlier in this post, you recommended setting:

Common Templates = "{deploy_dir}/templates" and File/Folders to "special"...this does not work for me either. The slave site loads text, no template.

I'm currently running:
Joomla Multi Sites version: 1.2.43 (Latest available: 1.2.43)
Patches definition version: 1.2.49 (Latest available: 1.2.49)

Perhaps I should level-set here, since I've been swimming in this for several hours....please check my logic:

I believe, I want my slave sites to have a templates directory of their own, and want to have symlinks to the templates of the master site. So that users can select new templates for their slave sites from the master as I make them available.

So, shouldn't I be using either Full Shared or Partial Sharing settings to achieve this? Am I running into a bug or some other config issue and not seeing it?

Cheers,

Viewed source shows:
- master: /templates/yoo_studio/css/template.css
- slave: /home/mst/public_html/ms/templates/yoo_studio/css/template.css
...the slave path is pointing to the master/template dir, but should it be the full path?


The URL that you mentioned in the CSS is not correct.
A URL is NOT a path on the disk.
YOu should NOT have the url /home/mst/public_html/ms/templates/yoo_studio/css/template.css

This is probably the "yoo_studio" themes that compute the CSS path incorrectly.
I see that they provide "/" in the begining of the path.
If your slave site is also a domain or a subdomain, you should have exactly the same in both cases.
The expected result should be
- master: /templates/yoo_studio/css/template.css
- slave: /templates/yoo_studio/css/template.css

Cocnerning your other question concerning the JMS Template configuration, this just declare how to create the directory "/templates" on your disk.
This is explained in the tutorial video 0.b slide 34
Don't make confusion between a directory on the disk and URL in a HTML page.
This is 2 differents things. A URL is converted in a location on the disk and they must be matched but are not identical as based on a "Document Root" directory that give the entry point of the domain or subdomain.

Thanks Edwin, I appreciate your feedback.

You bring up a valid point, one that I was not clear on; the slave should NOT be pointing to the actual path of the template, instead it should be the URL.

Not sure how to go about testing/modifying the template to play nice with Jms2Win, or if I even need too.

Understanding the difference between a directory on the disk and the templates URL....But, what is the difference in procedure when I had Jms2Win create the slave site with:

1: Common Templates = {deploy_dir}/templates, and File/Folders to "copy", this scenario worked perfectly, and the slave site displayed its template

2: Common Templates = "empty", and File/Folders to "special", this scenario fails to load the template.