Multiple sites in one instance..

I know that Zope3 has a skin with some rough equivalence to much of the functionality of Zope2's ZMI, though I can't remember how to get to it now, either for default z3ext or grok setups.

I assume it is possible, but there is there some strategy or UI in the working to manage multiple z3ext sites in a single zope3 instance?

We've always done this with Plone, and esp with the functionality of so many Plone add-ons that we rely on provided default in z3ext, this should be even more natural!

Looking forward to answers, and happy to help any way that I can!

just add z3ext.site package to dependency list and you'll able create subsites in root portal intance

Oh, fantastic!

I know I will answer my question once I get around to adding this and some other extra packages you've mentioned to our z3ext buildout branch, but can you say if these are full sites or 'spaces' designed to allow people to publish within?

Both would be exciting options for me, but we definitely want to be able to create sites with no relation to one another, as a hosting offering.  I know you guys are doing this with Zojax.net, so, I'm sure it's very flexible, but I learned a great deal from reading others' forum discussions, so it seems better to ask and discuss than assume.

Best, and thanks again for so many quick responses today!

sites absolutly separate. each site have separate controlpanel, products, auth plugins, etc

Interesting..  This can mesh well with our LDAP plan, we've been thinking it would be handy to set our dn as Manager access for all client sites, and giving them their own LDAP trees.

Thanks again for the info!  We're testing z3ext.site now and very impressed, it seems in fact like a great solution for two major problems I've faced:

•  Tiered / chapter-based organizations that want to offer subsites and have control over subsites..
• Providers like us, offering a commerce-based site creation.
  

It does seem a concern, however, if say we create an addon for our main site which provides some service control, e.g. DNS, Apache/PHP stuff (Sugar), etc..  We might not want that inherited, but it makes sense why it works as you say, so we can probably design to this..

Best,

Justin

you can allow view/configure addon only in root.

We want to have different addons per site, but we may want to restrict - that is an interesting use case, however, as we currently have multiple installs of Plone for different levels of addons supported, it would be convenient to use the same buildout and simply leave some addons uninstalled.

I notice that the breadcrumbs don't seem to be site specific, so e.g. there is an item 'Portal' which points to the root, and another breadcrumb for the site itself.

Is this intended, or possibly a bug?

you should use ++vh++ and apache rewrite rule for subsite, in that case you'll have right breadcrums.

Of course!

Looking good..