Ok, first the configuration:

List of domain names (*):
http://{site_url}/sites/u{user_id}s{site_id}
barhemmungslos.de
clubhemmungslos.de
www.barhemmungslos.de
www.clubhemmungslos.de

Template Deployed directory: {root}/sites/u{user_id}s{site_id}
Template create deploy: on
Template Media folder: {root}/images
Template Images folder: {root}/images/stories
Template Themes folder: {deploy_dir}/templates

Template Folder and Files: Copied

The problem is, http://{site_url}/sites/u{user_id}s{site_id} works fine and the template will be shown within the right way, but if you call barhemmungslos.de or any of the other domains, the template will not be shown, because the folders (template folders) for the .css, script etc are not found.

I figured out then:
is not working: www.barhemmungslos.de/templates/ja_quartz/css/template.css
is working: ig-lifestyle.com/sites/u62sHemmungslos/t...rtz/css/template.css
is working: www.barhemmungslos.de/templates/system/css/system.css
is working: ig-lifestyle.com/sites/u62sHemmungslos/t...ystem/css/system.css
Ok, then I copied the template also to Master Site Template folder, and see what will happen. Well, it was working in this way that if you call www.barhemmungslos.de it will first look into the Master Site Template folder to get the template, but just after this it also looks into the Slave Site Template folder and graps the definitions again, so that you will get several php errors because of redeclaring class.

I think somewhere within the definitions I have made an error, please could you help me with this?

Ok, i think I have found a work around for this problem.

If you open the configuration.php and set the

var $live_site = '';

to the first url or full Master URL with the full path to the slave site

var $live_site = 'ig-lifestyle.com/sites/u62sHemmungslos/';

it works.

So, that means that there are some definitions within the .htaccess are missing, which can redirect the domain request to the real path of the site.

You can NOT for the "live_site" to a specific value.
When you do that, you force the website to always using this URL whatever the domain that is used.


In you template definition, there are several errors.
The images and media folders are RELATIVE path and NOT full path as you have provide them.
If you just want to replicate the "images" directoy, you can also let this field empty as you have deployed the slave site into a specific directory. In this case, you just have to click on the "file and folder" images action = "copy" instead of "special copy".

If you the domain or subdomain is not displayed correctly, you have to check the "hosting configuration" and in particular the document root or similary that you have defined.
It must be EQUAL to the deploy directory.

So you mean the definition of the template should look like this

Template Deployed directory: {root}/sites/u{user_id}s{site_id}
Template create deploy: on
Template Media folder: images (using special copy)
Template Images folder: images/stories (using special copy)
Template Themes folder: templates (using copy - means this slave site will get it own template directory?)

And now my question: if I use shared DB for Sobi, Jomsocial, Kuena and Events - as I do - what happen to the pictures, videos etc. which are upload by the users?
Are they delived to the main Master Site Directory? As I have also other slave sites which are also sharing the DB's and therefor they should also share the folders.

It must be EQUAL to the deploy directory.

Yes, all sites are within the same root path like:
Master: /var/www/hosts/MasterDomain/htdocs/
Slaves: /var/www/hosts/MasterDomain/htdocs/sites/

or will it be better to use the Mastersites folder? Then I guess i have to declare nothing and the Template Deployed Directory should look like this:
Template Deployed directory: u{user_id}s{site_id}
right?

Ok, I tried it again and set up the site again, but without any chance to get it running

Template Deployed directory: {multisites}/u{user_id}s{site_id}
Template Media folder: images
Template Images folder: images/stories
Template Themes folder: {deploy_dir}/templates


Is working: ig-lifestyle.com/multisites/u62sHemmungslos/
is not working: barhemmungslos.de/
is working: barhemmungslos.de/multisites/u62sHemmungslos/

The Server it self is fine, as it's working for another site, sharing the same DB, without any problems

Ok, it seems I have fixed the problem. The problem was taht within the template_tools of the template which I have used, they have re-written the full path to the template folder.

As Multisite just maps the urls, the full path will be different than. A solution to prevent these kind of problems within the future could be, - even this could work on linux system with links allowed only - that Multisite will write a rewrite_rule for the urls within the .htaccess. Maybe it's something to think about as it will make life much easier