Forums / Install & configuration / New site access problems with copied templates

New site access problems with copied templates

Author Message

Mark Emms

Friday 29 June 2007 8:01:18 am

I have set up a large and fairly complex site (lots of templates and overrides etc).

Now I find that having separate site accesses for sections of the site should solve a number of my problems.

To start with I have tried to create some dulpicate site accesses with new names but identical designs etc.

I have done the following:

1. Copy the settings directory and put identical copies in the sttings directory with a new name each.
2. Copy the design directory for the original site access and put identical copies in the design directory with a new name each (to match the names in 1).
2. Edit the site.ini.append.php in each new settings folder for the site access file to give it new default node, index node, site name, and site design directory
3. Edit the site.ini.append.php in the overrides folder to list the new site accesses by adding lines like

AvailableSiteAccessList[]=newaccessname

4. Change the anonoymous user so that it has read permissions for the new site accesses.

Now I can use the new site accesses but none of the templates seem to be working in the new site accesses - how do I ge all of the templates to work in the quickest possible way?

Mark Emms

Monday 02 July 2007 5:38:20 am

All of the css links are to the original site access - I've obviously done something radically wrong!?

Mark Emms

Monday 02 July 2007 6:02:27 am

OK I've sorted the css problem.

Do I need to go through and manually create a whole bunch of over rides that are the same as the existing ones in the original site access?

Help greatly appreciated!!!!

Mark Emms

Monday 02 July 2007 6:54:57 am

Job done:

All I did was copy across the .ini files from the origianl site access settings to the new one (making sure not to over write the site.ini.append.php file. The override.ini.append.php file is the one responsible for the templates working.

It is all in the documentation - I just didn't look carefully enough!