Although CMS offer their users the advantage of web based editing interfaces, it turns out they also have drawbacks. The average open-source CMS has multiple editors and contributors, each intent on developing their own section of the code. While this results in robust development and testing, it also results in a constant state of churn as new features are added, old bugs eliminated, and the core code changes.

If the user has their Word Press, or Joomla, Drupal or Blogger hosted in their own site, they had better hope that the ISP offers Fantastico, or some other ISP wide way to update the CMS. Otherwise, they will need to keep their code updated by downloading new versions as they are posted, and migrating the old posts.

For some minor version updates, updates aren’t usually a problem, but when the new version of the code rearranges entire modules, changes the location of various functions, renames folders, and eliminates other sections, it can cause both loss of content, and css problems.

If you are looking for ease of administration, be aware that CMS either require an environment that eases the burden of code updates, or requires that the site owner have the ability to recognize and deal with the version changes.