On Fri, 19 Jul 2002, Pascal Van Hecke wrote: > I suppose you're using Nadmin, only allowing you to attach images to > topics? And you are typing in the image locations manually in your > html?
Yes and yes. Actually, it took me a while to figure why the attachments didn't display when I tried to serve them from the article. Doh! =) I don't think it's so difficult to edit the path manually. Of course I don't use the msdhtml-tool either, as I'm 100% linux here. > Maybe it's a good thing then to separate the imagerequests-handling > code and the pagerequests-handling code by having just a separate > active page /files that analyses the URI "/files/xyxxy/img.png" Well, I thought about that but that requires that my users write a longer uri to refer to the images from their pages. It seemed like more work than having the users just type "file/img.png" ie a relative url. > If you, on the other hand, are building your own content admin > interface, why would you mimic a traditional file structure if it's > not necessary? Well first of, as a unix luser I really like to structure stuff in hierarchies. This way it is really easy to make a site with a large article structure featuring sublevels with option to limit access to just a few pages for certain users etc. Also I can pretty much just convert the web sites current structure to a topic/article structure without worrying about having to give people superuser capabilities only because the need to create a new first level page. > I'm allowing my users to upload attachments connected to articles > (so not to topics) and all requests for attachments are simple > requests on one active page with the attachment ID: (such as > /attachment/2168) I see many midgard examples using topic an article id:s directly in the uri. I much prefer to have a human-understandable uri so my entire structure is based on the name of topics and articles, not the id. It's easier to refer to /board/chairman than to /board/1356 especially if the site has many levels. It's interesting with discussions of site arcitecture and design choises in web system design like this one. And even though it feels like I've only scratched the surface of the capabilities of midgard I think It's a really neat system to build a greate system designs. -- Fredrik Jonson [EMAIL PROTECTED] - It's easy to delay a project a whole year. How? One day at a time. - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
