If you are talking about ezcore extension then that contribution is in hidden projects section - see http://projects.ez.no/ezcore/ and http://projects.ez.no/ in general.
Be aware that it is not included in ez.no search, nor is it linked to, so you have to know it exists and the url to it to get the new and useful stuff.
Certified eZ developer looking for projects.
zurgutt at gg.ee
I don't think he is talking about ezcore, but how to setup multi site eZ Publish install.
One way of doing it:
1. Start by creating one in a normal way (using installer and all)
2. Modify it to your needs
3. Make sure there is no db or VarDir settings in settings/override (look over all settings here and move any site specific setting to the siteaccessed used by your site, including admin)
4. dump database, var/<site_name> folder and siteaccesses used (included admin)
5. adding new sites now involves the following:
* create a new db with the db dump
* insert var/<site_name> but with something else for the site name part
* insert the siteaccess copys with new names for the new site
* change the settings in these for the new site (db, VarDir, Sitename and so on) * change site.ini in settings/override to match the host/uri to the correct siteaccesses
I now use Drupal 6.x and adding a new web site to the core logic takes 30 seconds. I have 100+ web sites using a single Drupal install. They have unique web site names and never interfere with each other. I can have just 1 mySQL and each web site uses a unique prefix.
Not at the moment, there are a extension in the works that allows this. Currently it supports multi db setup (the reason its not out yet, is that the code is to customer specific at the moment), and it might also support single db setup* when done.
* Multi site single db setup in eZ Publish does not work by using db table prefix like drupal does. The sites actually share content, using the role system to separate who has access to what.
Yes, shared db multi setup is possible and works well but needs to be set up manually and small changes to half a dozen templates or so. Should not be attempted without good knowledge of ezp.
Certified eZ developer looking for projects.
zurgutt at gg.ee
I was able to create a new site access with a different host and still use the same admin tools to control two sites. I've created and assigned a new section name to my object (the one that will be a homepage of a new site). Then, using overrides, I could use different page_layout for the new site.
Why do you want to use one db. It would be just more trouble to separate the sites when the need for it eventually comes up.
If the sites are related, as in one company have several sites and they share content across sites (node location), media library, tight integrations like fetching calendar events from all the sites and administration of all sites in one place. But yes, if you suspect they will be broken up within a short amount of time, then this is not for you. (data_import would of course help you a lot, but it should be tweaked a bit more for ez export / ez import scenarios)
