Is it possible to create a new slave site that is a fresh installation, but is completely independent of the original master? If I do Manage Sites > New > Fresh Slave Site it still creates symbolic links to the media folders, etc. I can't have that. I need a baseline template to work off of that is completely independent. It doesn't necessarily have to be a copy of the master either. It could just be a blank template.

Thanks!

I realized after posting I should make this more clear. Here is what I need to do:

I have created a Master website. This company has subsidiaries that will live under subdomains of the master website. I need a baseline slave site (a watered down version of the master) to use a cookie cutter to create slave sites, so that I have a good baseline starting point when rolling out the slaves sites.

It would be great if the slave sites could:
1. Have the template copied and ready to use
2. Have all the same modules available to it that the master does, but with their own individual settings
3. Unique users for each slave site
4. Unique images and media folders at a bare minimum

THANK YOU!

Okay, so that gave this a try myself and here's what I did and what happened...

I created a new Template called BASELINE. And here are my settings:

ID: BASELINE
Domains: http://{site_url}/services/{site_id}
Template Site: - Template Site -
Deployment Folder: /home/mydomain/public_html/services/{site_id}
Create folder: Yes

Folders and Files:

SL: administrator
mkdir: cache
copy: cgi-bin
SL: components
mkdir: documents (this is a folder I use for storing PDFs and such)
mkdir: ePublications (this is a folder I use for storing eBrochures)
copy: images
SL: includes
dirlinks: installation
SL: language
SL: libraries
mkdir: logs
copy: media
SL: modules
SL: plugins
ignore: services
copy: templates
mkdir: tmp
copy: xmlrpc
copy: .htaccess
ignore: robots.txt
redirect: Special redirection index.php
redirect: Special redirection index2.php

When I do this everything is created properly. If I go to the new site, it looks like a copy of the master (for the most part). However, the problems start when I log into the Admin panel.

If I login to the Admin Panel (Slave) and go to Global Config > Site > Site Name and change the name, it changes the name ON THE MASTER and then resets all the DB settings and everything on the MASTER site to that of the slave site. The slave site is not changed at all (even though the DB settings are correct).

Each site is using it's own separate DB. We are on a dedicated server.

I tried changed a module name to see if that worked and it worked fine. The slave site changed but not the master. It seems that the configuration.php file is being symbolically linked or something.

Please help!

Somethng that you have to check is that you have all the JMS patches installed (in particular the one "administrator/components/com_config/controllers/application.php"

Second thing that you can check is to you login in to the correct administrator website.
Sometime, users think login into a slave and in fact is logged into the master because they forget to put the definition of the slave site with and without WWW

edwin2win wrote:
Somethng that you have to check is that you have all the JMS patches installed (in particular the one "administrator/components/com_config/controllers/application.php"

I clicked on the Check Patches tab and it looks like everything is installed correctly:

Joomla Multi Sites version: 1.2.17 (Latest available: 1.2.17)
Patches definition version: 1.2.23 (Latest available: 1.2.23)

Files Status
administrator/components/com_multisites/install.xml OK
administrator/index.php OK
administrator/includes/defines.php OK
includes/defines.php OK
includes/defines_multisites.php OK
includes/multisites.php OK
installation OK
installation/includes/defines.php OK
installation/installer/helper.php OK
installation/installer/jajax.php OK
xmlrpc/includes/defines.php OK
configuration.php OK
administrator/components/com_config/controllers/application.php OK
administrator/components/com_installer/models/templates.php OK
administrator/components/com_modules/models/module.php OK
administrator/components/com_templates/admin.templates.html.php OK
administrator/components/com_templates/controller.php OK
libraries/joomla/application/application.php OK
libraries/joomla/document/html/html.php OK
libraries/joomla/filesystem/folder.php OK
libraries/joomla/session/session.php OK
components/com_content/helpers/route.php OK
plugins/system/remember.php OK
administrator/components/com_jce/installer/installer.php OK


Second thing that you can check is to you login in to the correct administrator website. Sometime, users think login into a slave and in fact is logged into the master because they orget to put the definition of the slave site with and without WWW

I am positive that I was logging into the correct site. As I stated previously, I changed a module title on the slave site and the master site was unaffected so that proves that I was logged into the correct interface.

I don't know if you are using the FTP layer.
If YES, perhaps you have provided a wrong "root path" to the FTP Layer that use the "master" root directory instead of the "slave" root directory