Critical problems with CMS Made Simple
Unless it is a security patch, do not upgrade CMSMS for "features" for several months after a new version release. There are always issues with bugfixes which need to be released, and the majority of modules which are not yet compatible with every new CMSMS version release.
Some out-of-the-box module installations are blatant security and / or privacy flaws. As two examples, News module reveals admin username while CGFeedback publicly shows email of anyone who posts comments on your website.
It is critical to backup database before every uninstallation (deletes tables) or upgrade (may break) of a CMSMS module.
The CMSMS way of making sure that modules do not break is the Firefox way: disable the modules with each upgrade, delete after 6 months of no updates.
CMSMS developers push ahead with PHP-massaging releases, but do not address usability or functionality feature requests which are reported by the public and actual users.
˅˅˅ Additional valuable information is available at one of the links below: ˅˅˅
Did you like the article? Let Google Search know by clicking this button:
Page last modified 20-Aug-12 22:56:26 EDT
Previous page: How to upgrade from 1.9 to 1.10
Next page: PHP errors in version 1.10
. 