Another Noelinho CMS Update
I've been continuing to use whatever time I can to work on my little CMS project which I have mentioned before. Just over a month has passed since then, and I have managed to progress a little further, especially in the last week. Given that a few people have asked about it recently, I thought I'd post a little update.
I'm still only working on the back-end of the system at the moment - the front-end can be sorted out afterwards. The basic structure of thre back-end has remained the same, but I've decided to split many of the pages in the different sections into two or three pages. The idea of this is to make the whole thing easier for people to understand, and to make each page a master of its domain, so to speak, rather than to make it a lengthy complexion of 'if' statements for five different tasks. It makes working out bugs much easier too!
One significant change is in the way 'categories' are stored on the system. They were stored in a set' field on the 'posts' table, but I've now created a 'categories' table, and each category is a row on that table. It enables categories to have parent categories, but also means I can have one table for both link and post categories. There are problems with creating arrays from this at the moment, so I've decided I'll come back to it another time. I have kept my previous 'set' system just in case it doesn't work in the end, but I was more disappointed that I no longer had a use for my wonderful explode() code, which I did rather enjoy...
I have managed to adapt TinyMCE to fit better in the back-end now, but also to use a more complicated theme that didn't previously work. It still needs a little tweaking, but it would probably work fine just as it is at the moment.
Many of the other things I mentioned in my previous post have not yet been worked on, but there are other things which have progressed. Submitting new links now works well, as does submitting new categories for links, and distinguishing between post and link categories. Parent categories do not yet work, since that option hasn't yet been fully added to the database. The forms have all been nicely styled now too, making them both easier on the eye and clearer to use, as you can see from the image.
I haven't written any documentation yet (I expect this will be done last), but I have transferred my nice 'to-do' task list to the database. I originally developed this so that I could keep track of what I needed to be doing, but then realised it would actually be very useful for other people to keep track of all the things they wanted to do if they were using it too. Thus, the 'to-do' tab probably shows the most complete part of the software at the moment. It is split into three sections: 'implemented', 'in progress' and 'not yet started', with a form at the bottom for submitting tasks. In time, functionality will be added to alter task status and to delete tasks - but only completed ones. To delete uncompleted tasks, one will have to change their status to 'implemented', then delete them, so they can't delete them by mistake.
There is currently 1 comment on this article.
BigAlhttp://www.jedimoose.org
Call it Thor! THHHHHOOORRRR!!!!!!!
2008-02-26 01:51:43