Adam Blomberg wrote: > I'm in the process of deploying Midgard at a moderately sized but > very dynamic site, and I've been quite concerned with one issue: > Can one map topics to pages (or pages to topics) in a automatic, and > transparent, manner? You could, by having the root page active. > My problem is this: The major parts of the site will be administrated > by a group of administrators, but then several departments will > administrate their own pages (or subsites). For them (and for us), > the content management part would be great, if you conveniently could > map topics to pages, so that you can browse the topic structure > without having to make an active page which handles all > requests. (Btw, in the current stable version, this doesn't seem > to be possible.) That would be how we usually handle it. It's possible with the current stable version although you'd have to write the 'by name' access functions in PHP. These have been added as native midgard functions in the 1.4 releases. You can attach data to pages in the 1.4 releases (attachments, parameters) although these will still need help from active pages to get served out. In what way does the active page approach not service your needs? > I would like it to work something like this: When you create a new > topic (named "support" for example), a "virtual" page is also set up, > based on a template (or parent) page of the current topic tree. All > articles added to this topic would then be accesible by very > simple means; as we know which topic we are in right know, one can > simply fetch all articles which have the current topic as parent. But you'd need to have a standardized approach to formatting these articles. I can't concieve of having a fixed formatting engine in midgard. > Another approach could be that each page created in the "page > admin" results in a topic, that can then be filled with articles (and > possibly other topics as well, depending on the user privileges). > The page would then "know" which topic id that corresponds to the > current page, so that you won't have to hard-code topics to pages > (this is what I'm doing right know, slightly annoying :) I understand this problem. Access-by-name plus an active page has been the approach I've taken so far. > Are there any functions that would support this proposed behavior in > the upcoming versions, and if not, is there a better way to solve the > problem of connecting content "folders" to actual pages? If there are, I'm interested. The main problem would be how to do the transformation from raw content to HTML sent to the browser. Emile -- This is The Midgard Project's mailing list. For more information, please visit the project's web site at http://www.midgard-project.org To unsubscribe the list, send an empty email message to address [EMAIL PROTECTED]
