[Zope-CMF] CMF-in-CMF searches

[Gary Poster]

I tackled part of the CMF-in-CMF problem with my CMFVirtualHost.  It did
what I needed and I had to move on to other tasks, but, depending on your
project's requirements, it might be worth checking out, perhaps as a
starting point.

It is designed to work in only one CMF site, as Tres suggests, but with
different skins etc. for each sub-portal.  If each sub-portal is another
domain (or subdomain), you can use my solution.

I use it with CMF 1.2 and have not tested it with 1.3 or CVS.

My search solution was very rough-and-tumble-low-tech, by the way: for each
subsite's search, include a hidden path field as below.

<form action="search" method="GET"><input type="hidden" name="path"
value="/myCMFsite/myCMFsubsite" />
<input type="text" name="SearchableText" size="16" />
    <input border="0" type="image" name="go" value="go" src="go.gif"
align="middle" width="20" height="20"></form>

This matched with my desire to have the parent site searches include the sub
sites.  You can then set up redirects in the VirtualHostFolder so that links
to the subsite (from the parent CMF site) redirect to the correct sub-site
domain.

I only have one copy of each of the CMF tools--no nesting of tools.  The
search trick above combined with the skinning abilities added in the
CMFVirtualHost made that unnecessary for me.

See
http://www.zope.org/Members/poster/CMFVirtualHostTool
which is an extension of (and requires) my
http://www.zope.org/Members/poster/VHF
which itself requires iuveno's
http://demo.iuveno-net.de/iuveno/Products/OrderedFolder
which then in turn is a bit buggy visually unless you include their
http://demo.iuveno-net.de/iuveno/Products/ZBabel

If all that doesn't scare you off from my solution, I don't know what will.
;-)

Gary



-----Original Message-----
From: zope-cmf-admin@zope.org [mailto:zope-cmf-admin@zope.org]On Behalf
Of Heeten
Sent: Friday, July 19, 2002 11:36 PM
To: zope-cmf@zope.org; tseaver@zope.com
Subject: Re: [Zope-CMF] CMF-in-CMF searches


On Fri, 2002-07-19 at 15:26, Tres Seaver wrote:
> "Nested portals" aren't directly supported, but can be emulated using
> two complementary strategies:

Just curious, why doesn't nesting cmf sites work, and is this something
that could be fixed?

>   - Create only one CMF site, and force its tools to allow replacement
>     (e.g, change their '__replaceable__' from OFS.ObjectManager.UNIQUE
>     to REPLACEABLE.  Then add these tools to the PortalFolders
>     representing the "sub-sites".
>
>   - Create a top-level folder and instantiate the "shared" tools there;
>     create a CMFSite in that folder per "sub-site", and delete the tools
>     which you want to share from the acquired folder.

It looks like I'm going to have to use the top method, cause I'll have
to nest cmf sites in each other at least 3 levels deep.  (ie.
cmf_site1/cmf_site2/cmf_site3)

Thanks for the help.

Heeten




_______________________________________________
Zope-CMF maillist  -  Zope-CMF@zope.org
http://lists.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests