21
Agree 100% with you Mithrandir.
Presently, my own blog, I run with my favourite, XOOPS.
It beats all the nuke types hands down.
The postnuke permissions systems needs a Ph.D to understand!
And to move the blocks up and down using arrows is like living in the iron ages.
My other site with has a lot of content is based on Mambo.
This is because it is geared towards the student Community and I needed to ask a few questions right during sign up. Mambo has this Mambot which can help me create unique, dynamic and customisable user fields.
When an editor or publisher logs in into Mambo, he/she sees this 'edit' icon next to all the content he/she can edit. This saves the hassle of logging in seperately into the backend, navigating the menus and editing a piece of content. ( you only would have wanted to correct a typo or spelling mistake).
What I don't like in Mambo is its total INFLEXIBILITY to create Groups and Permissions. (yep Mithrandir)- You have a few hard coded groups - The writer, Editor, Publisher, Admin, Super Admin, all with pre-configured permissions.
In this regard, XOOPS rules the whole OS CMS scene (apart from Typo3 which can be classified as a professional CMS)
In mambo, I can't tailor content for different groups. I can't assign certain blocks to be seen by some and some not to be seen by others.
The Template system of Mambo is quite easy that I figured it out the very first day. With use of Dreamweaver extensions, one can make a template in 10 minutes flat.
Xoops looks fantastic, but its the work of great artists. The smarty templating systems turns off rookie php newbies like myself into everlasting dependence on Template Creators.
Xoops has a rich feature set.
In my opinion, the very first thing XOOPS needs is the user fields, secondly, explore still more possibilities to simplify the template creation task. Thirdly and most importantly, implement a Content Management module in the core for inclusion of Long Articles (without having to use the News module or custom Blocks)
Thanks for reading!
Presently, my own blog, I run with my favourite, XOOPS.
It beats all the nuke types hands down.
The postnuke permissions systems needs a Ph.D to understand!
And to move the blocks up and down using arrows is like living in the iron ages.
My other site with has a lot of content is based on Mambo.
This is because it is geared towards the student Community and I needed to ask a few questions right during sign up. Mambo has this Mambot which can help me create unique, dynamic and customisable user fields.
When an editor or publisher logs in into Mambo, he/she sees this 'edit' icon next to all the content he/she can edit. This saves the hassle of logging in seperately into the backend, navigating the menus and editing a piece of content. ( you only would have wanted to correct a typo or spelling mistake).
What I don't like in Mambo is its total INFLEXIBILITY to create Groups and Permissions. (yep Mithrandir)- You have a few hard coded groups - The writer, Editor, Publisher, Admin, Super Admin, all with pre-configured permissions.
In this regard, XOOPS rules the whole OS CMS scene (apart from Typo3 which can be classified as a professional CMS)
In mambo, I can't tailor content for different groups. I can't assign certain blocks to be seen by some and some not to be seen by others.
The Template system of Mambo is quite easy that I figured it out the very first day. With use of Dreamweaver extensions, one can make a template in 10 minutes flat.
Xoops looks fantastic, but its the work of great artists. The smarty templating systems turns off rookie php newbies like myself into everlasting dependence on Template Creators.
Xoops has a rich feature set.
In my opinion, the very first thing XOOPS needs is the user fields, secondly, explore still more possibilities to simplify the template creation task. Thirdly and most importantly, implement a Content Management module in the core for inclusion of Long Articles (without having to use the News module or custom Blocks)
Thanks for reading!
