Since my last post about the Nexus CMS on July 17th there have been made soo many changes to the system that I thought it would be better to move on 0.3 more versions 
. First of all. The Main System, RSS system, Ajax Handler and Admin backend are fully operating!
Changelog:
- Added backend admin system
- Added authorization (better roles etc.)
- Added admin core modules (+ override feature)
- Fixxed error handler with buffers activated (all systems: rss, ajax, main and backend)
- Added several core modules ( dashboard, settings, …)
- Base Paths for includes, requires, templates etc. (much more stable when moving the application)
- Created seperation in templates ( private => backend, public => frontend)
- Mod Rewrite feature implented
The admin core modules come standard in the Nexus CMS. But they can be overriden by user modules. They are pretty much the same as site modules but they do not have XML files, rss or ajax request handler which is pretty obvious why =). Also they live in a restricted area, unauthorized users have no access to anything related to the core. When the override feature is activated for a certain module the system will skip scanning for an admin core module but will instantly check if the site module has a control.php file to manage the administration from the site modules. The admin HTML documents are located between the frontend HTML. This override will allow a programmer to keep pretty much every operation of his site in the frontend modules. But if they like they can also create a seperate core module.
You can activate apache’s mod_rewrite from the admin backend (in a core module). The mod rewrite isn’t actually deactivated so you can still manually type the URL’s more decently when it is turned off. The rewritten URL’s look like this: ?com=News => /main/News/ or ?com=Portfolio&offset=3 => /main/Portfolio/offset/3/ . The last rewrite with the variables still has to be implented, but the basic one is already working. You on’t have to define this when you write it in your template, I thought it would be a lot easier not to use some kind of syntax like {LINK=”?com=News” , “/main/News/”} . This syntax was never implented, instead I just created a function in the Template class that runs at the very end before we display. It rewrites all the ?com= links to the correct rewritten links if mod rewrite is turned on.
To do list:
- Implement caching system
- Change language constants and use an internationalisation function instead.
=> These language strings will be stored in the database. The default is hardcoded and in English.
- Add more backend modules
So thats pretty much my latest changes at the Nexus CMS so far . It has been smoothened up a lot, and runs a lot more stable.
So far it’s looking very good and I might release an Alpha version soon.
