On Wed, Sep 29, 2010 at 16:55, Hanno Schulz <[email protected]> wrote: > I am looking for a solution to restrict access between plone portals on the > same > zope server. > > The Problem: > Zope Root > / > |- Portal A > |- Portal B > > When you call server/Portal B/somefolder/Portal A/ you get the content from > Portal A instead an error page (for example 404). > I know it's the "normal" zope acquistion :( But is there a way to stop > traversing at the plone portal root?
There is not, short from not making Portal A public. In other words, any anonymous access in Portal B will be able to access any public information from Portal A through acquisition. This is by design. You can work around this by giving each Plone site it's own instance. If this is really not an option, consider giving instances names that are not likely to be accidentally accessed, such as a GUID. If you really want to be stubborn about this, and this is really a problem you feel needs solving (you may notice a skeptical tone in my email at this point :wink:), you could always create a custom folder type which has a default view that deliberately generates a 404 error. If you put each of your Plone sites in one of these custom folders, you can still traverse to the Plone site (using a VirtualHostMonster setup) but acquiring just that folder into Portal A will still generate a 404 error. I call YAGNI on this problem though. -- Martijn Pieters _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
