Stephen Simmons wrote:
My thoughts were to use an html_header that tracks how deeply
components are
nested so that inner components turn off the page wrapper. This
achieves 1
and 2. This also achieves 3 if sections raise an exception if their page
wrapper is not turned off.
You only
Stephen Simmons wrote:
3. Sections are only used as building blocks for other documents so it must
not be possible to retrieve a section via a URL.
That is not currently possible in Zope and is one of my pet peaves :-S
See the 'Protocol Accessibility' proposal on dev.zope.org for a possible
Stephen Simmons wrote:
Any suggestions? Something involving permissions/roles? Hacking
before_bobo_traverse()? Something simpler?
You could use SiteAccess for this; get it to match the allowed paths and
patterns to those documents you want available directly through the web,
and return a
mber 21, 2000 9:56 AM
Subject: Re: [Zope] Restricting URL access to objects that are not complete
web pages
Stephen Simmons wrote:
3. Sections are only used as building blocks for other documents so it
must
not be possible to retrieve a section via a URL.
That is not currently possible
2000 3:21 PM
Subject: Re: [Zope] Restricting URL access to objects that are not complete
web pages
Stephen Simmons wrote:
My thoughts were to use an html_header that tracks how deeply components
are
nested so that inner components turn off the page wrapper. This achieves
1
and 2.
Stephen Simmons wrote:
Steve,
Ideally the publishability of an object would be an internal property of
that object, not something that is set externally via rules in SiteAccess.
It's been a little while since I last looked at SiteAccess, but wouldn't
using SiteAccess force you to store
After reading the Zope lists for a couple of months to struggle up the Zope
learning curve, it's time for my first question.
I want to serve web pages build up from a database of document components.
Zope's object-based subsystems should be completely hidden so that the only
objects accessible
