Monday 04 October 2010 12:01:58 am
Hi Chris, You are certainly correct in as far as running multiple "sites" off a single install isn't trivial. I spent months figuring it out and have got it nailed. What's worse is the number of different ways there are of doing it and no authoritative documentation explaining the procedure. One point where you are perhaps not 100% with is with separate logging. If you employ the extension-siteaccess method, where each extension is a new "site", you simply edit the site.ini for each one and ensure you edit the LogDir settings for each, so you have a nice logging dir hierarchy under var/log/<your_site>/error.log (for example) see here: http://doc.ez.no/eZ-Publish/Technical-manual/4.x/Reference/Configuration-files/site.ini/FileSettings There are of course decisions to be made about multiple databases. I went for a single DB and multiple extensions which is working well. I used a single DB because the sites were related and shared the use of the same custom-tags. So changing the value of a setting that a custom-tag in another site relies on, means it is updated everywhere it is used, regardless of which site it's in. I'm not sure what you mean about having to alter a class for an extension. If you're talking simple design extensions, then there is no need for separate classes. If you want to have some specific OO functionality called from each extension, think of the problem differently: Why not create a separate extension soley for this class and in the classes logic, differentiate between siteaccesses on that level instead - if that makes sense?
Cheers Russ
Russell Michell, Wellington, New Zealand.
We're building! http://www.theruss.com/blog/
I'm on Twitter: http://twitter.com/therussdotcom
Believe nothing, consider everything.
|