Big Change In The Database Model Of Mucms
Since 2008, Mucms went through major changes. In fact, before muCMS, my websites were made under Dreamweaver, and that totally sucks.
Then i met Smarty which introduced me to MVC programming, but i found Smarty added an unecessary step, so like Wordpress i programmed a custom framework for Mucms, that happened in the midddle of 2011, now it is freed from Smarty and i am very satisfied.
Really Smarty is a waste of time and i wish i had begun without it.
Now the database model is changing too
Although Wordpress is a great CMS, i find its data model simplistic and not flexible IMHO, but since i don't know WP API, i won't talk too much about it.
MuCMS data model was way simpler than WP's, and i encountered several limitations, like rigid categorization (no multi category), impossible to add new modules to the CMs like adding a directory script etc).
Now i have a central table that manage the urls, all urls are unique, so that's why it is important for them to be manage by one unique table.
the consequence is that i don't need url rewriting anymore, just find the right url, and display the content. the url can be a post url, a category url, a tag page url, a directory entry url, that's not a problem, and that's the beaty of the table. Now i can add as many types of url as i want provided they are not duplicate.
I also refined the hook system (like WP's) so that i can add or remove a hook to customize a webpage behavior or the entire website behavior very easily.
that central table also handle 301 redirect, imagine you chage a url of a page, the table will have the new url information so the cms can esaily redirect you to the new page.
Like wordpress, i am having a hook system here and there in the webpage.
the bcack office also needs a rewrite, because of the new way to handle urls, category.
Last big change, the htaccess file also needs to be rewritten. All these change must take place at once since they are all dependent.