I’ve started working on my cms again lately and many improvements have been made to the platform. The basic structure has now been set. One of the improvements made was the addition of an integrated error system which handles every PHP error that occurs inside the system (even non-PHP errors in e.g. DB class) and passes it onto an error handler which writes it safely to an error log just in case the Database has dropped out. Still might need to add a rollback feature to that and then it works like a charm. Also the modules work correctly now which is quiet a unique aspect. It works as follow: Modules are divided into two main groups, Passive and Active ones. The passive modules run in the background and won’t be displayed to the average user.
Passive modules are also again divided into critical and unnecessary ones. Passive modules that are critical for the system will terminate the program when they aren’t executed properly or when they just simply don’t exist but are listed. When the other type of passive module isn’t found the program will just simply continue because it forms no risk. However in both cases an administrator will be alerted.
The active modules are modules that do have displays, they often manage news, forums, users, etc. When these modules aren’t found the user will simply be redirected to the default one. There can only be one active module at a time but several passive. They can be turned on and off in the admin area. I don’t know if there is any system like this out there yet or if this is the best way to do it. But this is just how I do it. And I prefer beeing unique and creative than just simply copying off other people their code. Anyhow, now the coding of the modules can begin and this also means the actual content of the system!
