First, normally JMS Multisites should not be installed in a slave site.
So this is normal that you have a patch error return on the "configuration.php" files of a slave site that does not contain the stuf present for a master.

Concerning JCE, it has its own configuration for the image path.
So see the JCE configuration for the path.

Concerning the error on "multisites" symbolic link, it seems that you try to deploy a slave site in the "master" root directory.

As you could read in this forum, most of extension hardcode the directory "/images" and does not read the Global Configuraion "media setting" to get the real path where the images are located.
This is the reason, why we have suggested to deploy the slave site into their own directory.

Which is the value present in the "domain".
Did you used the {site_url}/multisites/{site_id} or something else ?
If this is the {site_url}/multisites/{site_id}, check if you have a .htaccess with rewritebase present.
If you don't have a .htaccess, perhaps you should add one with the rewritebase.

Thanks Edwin, and Merry Christmas!

Multisites is installed on the master, so it gets copied to the slave sites when I deploy them. I haven't reinstalled in the slave sites. So it sound like that's not something I need to worry about - I'll ignore it.

My slave sites are being deployed in /multisites/slave1/, not into the site root. Is this not correct?

Which field are you referring to as the Domain? The domain names are set as:


I enter the site ID of each slave as the URL: slave1.com. So each site is an independent domain name that should be rewritten to the multisites directory of the master site.

I played with the .htaccess and did some research on the forum. I've written it as RewriteBase / and placed a copy in both the master root and slave root, but it's still not working. Can you clue me in on the correct settings and location for this file? Would it need to contain the full path to the site directory? (RewriteBase /multisites/slave1.com/)

Just an update...

The .htaccess in each slave site directory is not being recognized. I've set the site template to copy the .htaccess from the master and rewrite the RewriteBase value for the slave site. It's not changing anything on the way the site works. As a test, I deleted the contents of the file and added a simple redirect to Google. In the slave sites, this doesn't work. In the master site it works correctly.

Entering the URL of the slave site's deploy directory (http: //master.com/multisites/slave1) causes the .htaccess redirect to forward me to this URL: http: //google.commultisites/slave1.com. The code in the .htaccess is: Redirect 302 / http: //google.com

So obviously it's picking up that multisites/slave1.com path somewhere and appending it to the Google URL, but the .htaccess files aren't being used when accessing the site from it's own domain (slave1.com).

Is there any possibility that I could give you admin and server credentials to take a look at this? I've spent a couple of weeks now trying to sort out this problem with a paid version of the component and I'm not feeling that I'm any closer than when I started.

When using a domain like www.{site_id} this means that you have to setup your http server with the correct "document root" directory.
You should not have to setup or create a specific htaccess when you setup correctly your domain in your http server (cPanel, Plesk, ...)

If you are using cPanel, use the "AddOn Domain" menu to setup the "document root" directory associated to your www.{site_id}.

You could get inspired of tutorial video 0.b slide 21-24 that present a proposal directory structure.

For example:
Domain = slave1.com
Document root = domains/slave1.com/public_html

In JMS Multisites manage site
Domain = www.slave1.com, slave1.com
Deploy directory = [Home path]/domains/slave1.com/public_html

That is all.

Okay, I'm confused. I'm using Plesk. In the manual it says (pg 20) that you recommend setting up domain aliases for each new domain and keeping all of the slave websites in the /multisites directory of the master, which is what I've done. I'm not opposed to setting up full domains for each new site, I was just doing it the other way since that was what the directions recommended.

The problem I'm having now is anytime I enter any path in the "Deployed Directory" field (right now I'm using /var/www/vhosts/{site_id}/httpdocs/) it returns this error:

But it does exist - I've set up the new domain in Plesk and I can see the directory in the terminal and FTP browser. Incidentally, I get this same error even when I'm trying to deploy into the multisites directory inside the master. If I leave the "Deployed Directory" field empty it works fine (deploying into /multisites/slave1/) but anytime I enter a value it returns that error. This also occurs if I check the "Create Deploy Directory" option.

Plesk does not allows you to configure a domain with another directory than the one created by Plesk. In addition, plesk add security between different domain in a maner that a domain can not access the directory of another domain (event when using the same account).

You need to apply the procedure described in Plesk - help - appendix II to create a vhost.conf file with the appropriate permission and allow different domains to see the directory of the master.
You also have to create a vhost.conf for the master be able to see the slave site directory.

This is part of the Plesk administration.

See the openbase_dir that add protection on the directories that can be accessed by each domain.