Problems with multiple site configuration

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
Sukhbir Khera	Wednesday 27 July 2005 5:11:03 am Hi all, First of all thanks to Mr./Mrs./Miss Lukasz Serwatka for the help. Somehow I designed three sites, but there are some problems with that. <b>1.</b> When I change the settings of one site in it's admin, it gets reflected in all the three sites. <b>2.</b> How to configure the database of two new sites I created manually. <b>what I</b> have done is just copied the folders of first site and renamed them, and the files containing its refrences to the new one. Please help . Thanks. Sukhbir
Frederik Holljen	Wednesday 27 July 2005 5:53:48 am Hi, The settings are reflected everywhere because you have chosen to store them as global override settings. Instead you should choose to store them in the specific override settings for each administration siteaccess. To be specific the global overrides live here: /settings/override/.ini and the siteaccess overrides here: /settings/siteaccess/[siteaccessname]/.ini
Sukhbir Khera	Thursday 28 July 2005 12:53:07 am Hi, Thanks for the reply, but can you please be specific what's needed to be changed in which files and in which directory. I have tried everything i can, but in vain. will be realy nice, if anybody can assist me. Once again, thanks. Sukhbir.
Luc Chase	Thursday 28 July 2005 5:38:45 am Sukhbir, Not sure how you got to this point.... did you re-run the wizard? Perhaps that would be an easy way for you to progress (set CheckValidity=true in site.ini.append.php). But remember to first ensure that there is a separate database available for each siteAccess. In over-simplified terms each siteAccess defines how the site looks and each database what it contains. Remember that content is stored in a database. Which database?? This is what you have to tell each siteAccess. The answer is placed in the site.ini[.append][.php] file of the particular siteAccess. The site.ini in the overrides directory is shared by all siteaccess and overrides any corresponding site.ini settings contained in /siteaccess/<siteAccessName>/site.ini... The ../settings/overrides directory is for .ini files to be shared by all siteaccess; they override all others. There it will find the name of the database, which server, login name, etc. So, (normally) you need a separate database for each site having separate content; and you need separate site.ini files to specify how to connect to the correct database. NB. The admin interface (which is just another siteAccess, but specially designed to manage the content) needs to always be the second siteAccess which has a login to the same database. e.g. [DatabaseSettings] Server=localhost User=root Password=xxxx Database=sitename The Web Application Service Provider
Sukhbir Khera	Friday 29 July 2005 1:25:39 am Hi all, Thanks to all and special thanks to Mr Luc Chase for the help. Now everything is, it seems, is working fine. One more thing, the original site is working fine, but the newly creted sites are asking for user name and password, any help on that. Thanks for the help. Sukhbir
Luc Chase	Friday 29 July 2005 6:46:38 am Sukhbir, go to /settings/siteaccess/<yourSiteAccess>/site.in[.append][.php] and look for 'RequireUserLogin=' and set it to RequireUserLogin=false The Web Application Service Provider
Leomar Soares de Almeida	Friday 29 July 2005 8:32:24 am <b>Gostaria de saber se alguem poderia me explicar a origem de ste erro no setup wizard.</b> Creating sites The setup wizard was not able to complete the creation of your selected sites. The following errors were detected: * EZSW-051Could not install addon package named contact_us * EZSW-040Failed to initialize site package corporate If you think you have fixed the errors you can try and click the "Retry" button.

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 19 2025 15:15:46
Script start
Timing:	Jan 19 2025 15:15:46
Module start 'layout'
Timing:	Jan 19 2025 15:15:46
Module start 'content'
Timing:	Jan 19 2025 15:15:46
Module end 'content'
Timing:	Jan 19 2025 15:15:46
Script end

Main resources:

Total runtime	0.0213 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0044	589.3906	152.6406
Module start 'layout'	0.0044	0.0025	742.0313	39.4766
Module start 'content'	0.0069	0.0124	781.5078	97.5234
Module end 'content'	0.0193	0.0020	879.0313	38.3047
Script end	0.0213		917.3359

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	11.0103	14	0.0002
Check MTime	0.0011	5.0358	14	0.0001
Mysql Total
Database connection	0.0005	2.3107	1	0.0005
Mysqli_queries	0.0026	12.1685	3	0.0009
Looping result	0.0000	0.0459	1	0.0000
Template Total	0.0016	7.5	1	0.0016
Template load	0.0009	4.1857	1	0.0009
Template processing	0.0007	3.3165	1	0.0007
Override
Cache load	0.0007	3.0679	1	0.0007
General
dbfile	0.0037	17.3701	8	0.0005
String conversion	0.0000	0.0336	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs