Zaapt CMS Working under Preassure
There are two types of pressure: technical and environmental. Let's talk about technical pressure to start off with.
On the technical side, I had a bit of a personal challenge last night, but I managed to fix it up in what I thought was a nice way.
As a bit of background information. Each content type contained in Zaapt comes with a Perl Module for (database) abstraction and a load of Mason pages to render that content to the web page. So far, I have been dealing with the administration side of things (the edit pages) and the public side of things (the view pages). Most of the content types fall into this category: the news, blogs, content pages, FAQs, etc
Last night I realised there was a third category. For the Forums, I had written the view and the edit pages. So far this has worked since the view pages were only seen by people once they had logged in, but we (KiwiWriters) also wanted the forums to be publically viewable too.
Therefore, I had to think about what I could name the type of pages which can be read but not changed. This kinda threw me for a while but then realised that it was simply these pages which should be called the view pages.
I set about renaming the current forum view pages to the new category I have called user pages. After a fair bit of renaming I then added the proper view pages. And guess what, it worked a treat :-)
The best thing about it is that there is now a more formal idea about what types of pages there are. This will also come in handy in the future for things like Wikis and being able to post comments or trackbacks on blogs. It is these pages which blur the line between site content and user generated content as demonstrated yesterday with forums.
This post originated on http://chilts.org/.
Email me on andychilton -at- gmail -dot- com.