[Zope-CMF] folder content (big post)

[Jens Vagelpohl]

stephan,

if i understand what you are saying correctly then you want, kind of in=20=

"normal" zope-fashion, have a site where somewhere down in the folder =
tree=20
the appearance changes. Using a normal dtml-based zope site you would=20
usually do something like drop in a different =
standard_html_header/footer.

the CMF just doesn't work that way. it is more about content and content=20=

management and "standard" zope entities (like dtml methods or standard=20=

folders) will misbehave if not used carefully. the normal CMF entities=20=

never try to (and are not made to) influence the site's look and feel =
and=20
change it. that's just not part of the CMF way of doing things.

so the reason you're not successful here is the basic CMF philosophy. =
look=20
and feel is not decided or influenced somewhere on the site, it is =
driven=20
by the stuff you have in the portal_skins tool, and all that stuff is=20
globally available. i don't see a way to "selectively" change look and=20=

feel at random points inside the CMF that is as easy as a new header and=20=

footer.

one workaround would be to develop a skin that gives you the desired new=20=

look and making sure it gets applied whenever people step into the part =
of=20
the site that is supposed to have it. that could be done by query string=20=

(append something like ?portal_skin=3Dmy_new_skin to the URLs) or by=20
manually twiddling the cookie that holds this value. that's hackish,=20
though. there is no really easy way.

jens





On Friday, November 30, 2001, at 03:56 , Stephan G=F6ldi wrote:

> In CMF, when I add a folder (not portal folder) via the ZMI, it is=20
> viewable
> in CMF. When I click on "folder content", it is not seen and not =
editable.
>
> When I add a portal folder (via the "folder content" functionality of =
CMF)
> ,
> it is seen by "folder content". But these folders behave different =
than
> standard folders:
>
> portal folders seem to include the functionality of =
standard_html_header=20
> and
> standard_html_footer. I do not have to include these two tags in an
> index_html. The standard zope folder needs these two tags. One level =
above
> resides an index_html, which includes these two tags. The index_html =
is
> needed, because the subfolders shall display some pre-formatted stuff.
>
> Now the standard Zope folders display everything correct, while the =
portal
> folders display the standard_html_headers twice. So the actions_box =
and=20
> the
> top of the CMF is displayed twice.
>
> So I need an answer on how I get these standard folders (not portal=20
> folders)
> seen, when I click on "folder content". I have to edit the folder =
itself
> (description etc.) AND the content (portal image etc.).
>
> Did I miss something essential?
>
> The other approach is, handling index_html on another way. Perhaps i=20=

> missed
> a basic cmf philosophy?
>
> When I change index_html in the 'custom' folder, it is clear, that the =
top
> level appearance of cmf is changed. But what, if I want to change the
> appearance of a subfolder? Is it correct, to create a dtml method in =
this
> subfolder as index_html? The problem is, that the above mentioned
> functionality of headers and footers doesn't work anymore, when i =
create
> such a method outside of cmf.
>
> --------------------------------------
> Goeldi.com - Internet Services
> --------------------------------------
> www.goeldi.com
> web@goeldi.com
> Tel   +41-61-7330555
> Fax  +41-61-7330556
> --------------------------------------
>
>
>
> _______________________________________________
> Zope-CMF maillist  -  Zope-CMF@zope.org
> http://lists.zope.org/mailman/listinfo/zope-cmf
>
> See http://www.zope.org/Products/PTK/Tracker for bug reports and =
feature=20
> requests