hi there,

when trying to access the respective config files of slave sites via browser I get 3 different results:

- one config file returns the 403 error msg
- one returns a blank page
- 2 return the message 'Direct Access to <filename> is not allowed' with the path being displayed in the browser tab

any chance it would be possible to make them all return the 403 message?

have you tried to apply the 'hello world" procedure and put the hello.txt and hello.php in your directory to check the hosting server configuration and see if you can execute PHP in this directory.

When you have checked that your hosting server is correctly configured, you can check also that you have the autorisation to follow the symbolic links (if you have deployed the slave site in a specific directory).

well I did on the master where symbolic links are ok

however since the slaves are in the same folder as the master (subfolder multisites in J! folder of master) and they share the same db with different prefixes I didn't test the slave

my dummy slave has the domain name
http://{site_url}/multisites/{site_id}
and is deployed to
{site_dir}

settings of JMS in the MAster says:
Unix Symbolic Links: Allowed
MySQL Version: 5.0.67-log Sharing supported

- the slave is set up
- several extensions have been installed using tools in master, found that the config/ settings of these components are the same as with the master
- have tested submitting a blog entry from front end (from the slave site) which is working;
- have also installed JMS menu items and added links to the master's main menu.
all of these appear to be working alright

what am I overlooking?

When you say that the slave site is in the same folder than the master, this is wrong because you give after that the multisites directory.
If this is a subfolder, this mean that this is not the same directory than the master (the root directory).

You say that you have deployed the slave in {site_dir} that seems OK and correspond to the video CP-04 (so OK)

Symbolic Link is OK - so the test with tutorial step 4 to 7 is OK (good).

I see effectivelly that you follow the procedure described in the tutorial and I congratulate for that.
I know this is not always easy and depends on each specific environment.

So now, you can experiment more in depth all the possibiilties of JMS.

okay

only the above problem (post #2205 ) occurs under the described setup in post #2210

thus I'm still facing the problem that the config files do not return a 403 error on the slave site

This is not clear.

You say Okay.

After you say still facing problem
and after you say "do NOT return a 403 error".

Then this is solved ?


If not solved, give the real URL to see the result of the "hello.php" application.
Does it works ?