Weaknesses: There are a lot of info but big wiki in one place would be better.
Lots of reading has to be done before going for advance stuff (i guess it is always true).
php knowledge is rather a must than an advantage (smarty templates, UDTs and module mods).
some separate solutions to build multilingual site (should be more consistent way some time in 2012 )
At the moment there is no place to exchange and rate module mods, templates, UDTs and other stuff .

Weaknesses: Most of the extensions are a little rough and need help to work or don’t work as expected. The blog feature isn’t very intuitive or easy to use. This cms is best for simple brochure style sites rather than feature rich sites.

Weaknesses: Maturity

Weaknesses: Some modules need adjustments to work

Weaknesses:

The module manager is very nice to use, as it lets you see all the modules that are available to you without having to visit another website; it’s all accessed through the admin panel.

Documentation as always could use a little work but it’s not that bad for basic CMSMS understanding. There is very little documentation if you which to go ahead and develop or customise your own modules. The community is generally active and most of the time very helpful, though because of the target market there are few highly skilled developers available for guidance.

Weaknesses: As a module developer one of the biggest problems I have found with CMSMS is the api and functions exposed to module developers. For some reason the highly repetitive aspects of module development has not been made easier by the api design – much of module development has to be done manually which could really be done automatically. ie: each time you develop a module you have to re-template the admin area for it.

The way pages and actions work is also rather clunky and very difficult to understand, even after using it for more than two years.

Many of the modules which are available have not been written very well, and can exhibit some rather annoying bugs. This also makes it more difficult to modify various modules.

The admin page layout and design, despite a recent refresh, is still pretty terrible and relies on a lot of inline javascript and inaccessible design practices. Again this makes it far more difficult than it should be to modify the backend design.

Overall though the think I dislike the most is the smarty templating engine. It’s structure and control patterns are so unlike html or php that it makes it difficult to incorporate it into the template. Just figuring out which variables and data sets are available to you at any one time can be very frustrating.

On this topic, I am still at a loss as to why CMS developers do not consider XSLT as the templating language of choice. It’s similarities to html make it easy for those with no prior programming knowledge to pick up. It offers far more control than smarty and is far more unified. Also, as it is a recognised standard, experience and practices gained using one cms can be instantly transported to another. Considering the widespread use of XSLT this is a formidable skill to have.

Overall CMS Made Simple is ok for very simple sites, but because of the pain experienced extending it, it would be far better to jump ship to a more flexible cms, such as Symphony.