This is a security release of your favorite flexible, powerful, and proactive content management system. The CMSMS Dev team considers security issues to be a top priority, and tries to fix security vulnerabilities as soon as possible. Therefore, we are releasing CMSMS 1.11.7. All users should upgrade as soon as possible. Please see the upgrade instructions at http://docs.cmsmadesimple.org/upgrading. As always, the latest release can be found at: http://www.cmsmadesimple.org/downloads/

We would like to thank the people at leakfree.nl who found these issues and worked with us to ensure that they were resolved.

In addition, we have added a feature that will allow you to have your CMSMS install on any server in any timezone and allow you to enter and display times and dates in a timezone of your choosing. The new config.php entry 'set_db_timezone' (which defaults to OFF) will send another query to the MySQL server so that it does date comparisons while considering your desired timezone. This should solve the problem of having to enter news, blog, and calendar entries in times that are in the server's timezone.

As we have not changed the database schema at all, there are diff releases available from CMSMS 1.11.5 and 1.11.6. As of this release the currently supported versions of CMSMS are 1.11.6 and 1.11.7.

Thank you for your time, and enjoy using CMSMS.

The following issues were addressed in this release:

1. XSS Vulnerabilities in the core, and in the installer.


2. Fixes problem with page template parsing wrt the and
   HTML tags.


3. Fixes a problem with some modules not listening to the {cms_set_language} stuff... order of execution problem.


4. Fixes some problems with the Simplex demo theme and touch screen interfaces.
   

   ** Note, the Simplex theme is not intended to have full functonality on lower resolution devices like phones. It is intended for tablets etc.

   
   

EDIT: For your information the sample .htaccess file shipped with CMSMS has been modified to include fixes for other potential points of attack. It may be useful to look at this file and merge the changes into your .htaccess.

Because of the nature of the vulnerabilities, we request people to upgrade their websites as soon as possible.

As of this release the only supported versions of CMSMS are 1.11.5 and 1.11.6.

Among the fixes in this version is a change to the behavior of Global Content Blocks. From 1.11.5 onward, the name of GCBs can only contain alphanumeric characters and the underscore. This is because Smarty treats some special characters (particularly the ":") differently in its parsing mechanism. For the same reason, ThemeManager has been changed to use "//" as a delimiter between the theme name and the template or stylesheet name when importing an XML theme.

Additionally, some of the noticeable issues fixed in 1.11.5 are:

1. An issue with regards to aliases and section header pages


2. A pesky, hard to nail down issue with module upgrades when upgrading from CMSMS 1.10.x


3. Problems with error reporting when processing Smarty templates.


4. The previously released MenuManager fix for cached menu templates


5. Fixes to the News and Search modules.

For a more precise list, refer to the doc/CHANGELOG.txt file in the distribution.

This release does not address every bug report entered into our bug reporting software, however, we feel it fixes most of the issues that were introduced in the 1.11.x series and all of the issues that will effect a large portion of the user community.

We encourage you to upgrade your websites to CMSMS 1.11.5 as soon as possible (always ensure you have a backup first). As of this date, the only supported versions of CMSMS are 1.11.4 and 1.11.5

Many thanks to the members of the Dev team who found and reported issues, tested the release, updated translations, and approved its release.

1. What do you do in the Dev Team?

TeamLead Quality Assurance and TeamLead BugSquad

2. What is it that made you want to get involved with the Dev team for CMS Made Simple?

After looking for a CMS in 2006 and testing multiple, I went for CMS Made Simple.... As I had some issues starting, I used the forum and IRC to get some answers. When things became clear (reasonably quick because of the short learning curve), I remained there, supporting in the forum and IRC. After some time there, I was asked to do the same, but then from within the Dev-team.

3. How long have you been involved?

On the forum registered since Oct. 2006.

4. What do you find to be the most fulfilling part of your role as a CMSMS Dev Team Member?

Discussing/testing new features and solutions.

5. What has been the biggest challenge you have faced as a Dev Team member?

Maintaining momentum. As we dont 'meet' regularly, there have been people in the dev team over the years that did promise, but didn't deliver (for many different reasons). So every time we had to postpone certain feature which were intended to go in a next release.

6. What keeps you motivated as a Dev Team member?

The nice people in the group and the perfect tool all are working on.

7. If you could be ‘dictator for a day’ for CMS Made Simple and implement one ‘fantasy function’ immediately into the Core, what would it be?

Version control. (A way to put versions of pages in, for approval and have logging on changed pages).

8. Have there been any commercial or personal successes that have been because of being in the Dev Team?

Multiple times, requests come in to do stuff. Most of the time of people unknown, just asking me, as being part of the dev-team

9. What do you do when you are not wearing your ‘Dev Team hat’?

I am a Business Analyst at FrieslandCampina, a big dairy company with 19.500 employees. Currently working on a big project, which spans 5 years, when I am TeamLead of the ProcessIntegration team and IT-lead of the Production team within that project

10. What is your favourite thing about CMS Made Simple as it works right now?

The flexibility of core, making it possible to use core-only with only limited add-on modules to create a working site.

Do you have what it takes to join the Dev Team?

If you want to find out more about the roles we are recruiting for then take a look at http://www.cmsmadesimple.org/about-link/join-the-dev-team. There you can read about the roles and also send us a message if you think you are the right sort of person to join our extended family.

1. What do you do in the Dev Team?

Currently less than I had hoped I could find time for. But, historically, I have maintained the TinyMCE/MicroTiny module, I also started off the printing module and FileManager although the later developments has been taken over by someone else. The 1.11 system maintenance page was also partly done by me.

2. What is it that made you want to get involved with the Dev team for CMS Made Simple?

"The same old story", guy wants nice CMS, tries to do one himself, realized that either you spend way too much time on it or you start looking for an existing one which speaks to you. Finds CMSMS, never looks back. But, wanting to help and improve it in ways I think important I volunteered as developer.

3. How long have you been involved?

Uhm, hard to say, but 6-7 years I guess. I hosted the first Geekmoot in Copenhagen, so at least that long :)

4. What do you find to be the most fulfilling part of your role as a CMSMS Dev Team Member?

When time allows to work on the core system and/or important modules, it is great to have a feeling that you actually get to participate in steering this ship in some direction... (continued in 5.)

5. What has been the biggest challenge you have faced as a Dev Team member?

... but as the amount of time you can put into this grows thinner, you also feel your influence thinning. That is how it should be, I am perfectly aware! The people who does the work also decides the direction. But when decisions are made which I do not agree upon it is sometimes hard. But I'm not talking things that would steer me away from CMSMS, here, mind you ;-)

6. What keeps you motivated as a Dev Team member?

That progress is being made, that being part of the Dev Team keeps me sharp and up to date with regards to developing custom modules for customers, which I do quite a lot. And that the other team member are generally quite nice guys :)

7. If you could be ‘dictator for a day’ for CMS Made Simple and implement one ‘fantasy function’ immediately into the Core, what would it be?

A full features, core integrated, image resizing, pretty and customizable wysiwyg-system. I believe that the single most important feature of any CMS is a well-integrated, advanced wysiwyg. I do what I can by maintaining the "full" TinyMCE-module but only have time for so much.

8. Have there been any commercial or personal successes that have been because of being in the Dev Team?

As I said in 6, I earn a bit of money developing custom modules for other companies, some are opened up in Forge others not, but I believe I would not be as good a developer if I did not also have hands-on experience in the inner workings of the core.

9. What do you do when you are not wearing your ‘Dev Team hat’?

Don't get me started... I teach music in gymnasium (high school), I'm a full time organist in the church of Denmark, I compose, I have a music publishing firm... oh, and I own a bar :P

10. What is your favourite thing about CMS Made Simple as it works right now?

The ability to quickly convert existing static designs and easily maintaining them from a browser, together with the API-framwork (with my Neo-extensions, of course (; ) must be the absolute highlight that makes my day!

1. What do you do in the Dev Team?

Documentation/QA team member, and team lead for documentation. I'm also fairly active with providing user support in the IRC forum.

2. What is it that made you want to get involved with the Dev team for CMS Made Simple?

I've been quite active in the IRC channel for the past 3 years, and Robert approached me to see if I would like to be involved with the development (he originally had other ideas where I would fit in, but I've naturally progressed into documentation and user support)

3. How long have you been involved?

Approximately 3 years.

4. What do you find to be the most fulfilling part of your role as a CMSMS Dev Team Member?

I really enjoy sounding out new ideas with the rest of the team, even if they prove to be impractical or unpopular. The range of skills and personalities is very diverse, and it makes for some interesting discussions and debates.

5. What has been the biggest challenge you have faced as a dev team member?

As discussed above, the range of personalities is quite diverse. Couple this with language and cultural barriers, and it took some time to realize that despite often tense debating, everyone has CMSMS's best interest at heart

6. What keeps you motivated as a dev team member?

Daily chatting in the dev channel

7. If you could be ‘dictator for a day’ for CMS Made Simple and implement one ‘fantasy function’ immediately into the Core, what would it be?

Versioning, with edit locking. Nothing too complex, but the ability to make draft changes to content, and remove the ability of two people to edit a page simultaneously.

8. Have there been any commercial or personal successes that have been because of being in the DEV Team?

Not yet, but it certainly has helped me be more confident bidding on larger web development projects, knowing I have the dev team's ear.

9. What do you do when you are not wearing your ‘dev team hat’?

I manage the prepress department of a commercial print shop, have a hobby farm, wife, and little daughter. If there's any free time left, I'm passionate about ultralight backpacking.

10. What is your favourite thing about CMS Made Simple as it works right now?

The usability for the end-user. I've never had to provide more than 10 minutes of training for even the most entry level editor.

Do you have what it takes to join the Dev Team?

If you want to find out more about the roles we are recruiting for then take a look at http://www.cmsmadesimple.org/about-link/join-the-dev-team. There you can read about the roles and also send us a message if you think you are the right sort of person to join our extended family.

1. What do you do in the Dev Team?

I am mainly active in the fields of marketing, partners and sales.

2.What is it that made you want to get involved with the Dev team for CMS Made Simple?

What makes me want to be involved are actually two things: a fantastic content management system that my customers love to use, and the great team of dedicated people who make this content management system happen and improve it all the time.

3. How long have you been involved?

I signed up on the forum in September 2008, and I joined the development team in the spring of 2010.

4. What do you find to be the most fulfilling part of your role as a CMSMS Dev Team Member?

I can seriously say that working with the people in the development team has enriched my life, not only on a professional basis but also on a personal one. I have seen and learned so much, and that has given me an understanding of what open source actually means. We are scattered all over the planet, but we try to meet in person at least once a year, during the Geekmoot. It's never awkward. Somehow finally meeting someone in person that you have worked with for so long is the icing on the cake! Last year in the UK one of our latest members at that time, Tapio, suddenly said to us: "I had no idea there is so much love between you". To see the system being improved all the time, and to see the presentation improve over time, that is what gives me fulfillment. CMSMS has been downloaded over 1.6 million times, and I am very proud of that!

5. What has been the biggest challenge you have faced as a dev team member?

Finding the right balance between dedicating time to the work for CMSMS and time for my own business. Especially in the beginning. Nowadays the marketing team is larger and better organized. And learning ‘geekspeak!’ *wink*

6. What keeps you motivated as a dev team member?

Progress. New beautiful websites in the showoff section in the forum. Teaching and helping each other out in our daily work. Those are just a few examples of things that keep me motivated.

7. If you could be ‘dictator for a day’ for CMS Made Simple and implement one ‘fantasy function’ immediately into the Core, what would it be?

Interesting question. I tend to agree with our core developers. The core should be kept light weight. So there's no fantasy function that I think that should be added to it. But… I dream of the development of a great module that makes it very easy to make a CMSMS site multilingual. Hard work is being done currently to create hooks to make this possible, so I know my dream may come true real soon. Because now people can actually create this module. And if they need us marketing peoples to start a crowd funding project for, just let us know at marketing@cmsmadesimple.org!

8. Have there been any commercial or personal successes that have been because of being in the DEV Team?

Yes, several! A lot of times when I'm approached for a nice project, people tell me they found me on the pages about CMSMS. So even though I do not get paid for the hours that I invest in the work that I do for CMSMS, it pays off in interesting well paid projects that I get or coordinate.

9. What do you do when you are not wearing your ‘dev team hat’?

I do guerrilla marketing projects, design websites, write functional designs for larger projects, and I haul in and manage several projects for the developers I work with. Besides that I paint, make music (also on a commercial basis) and I write blog articles.

10. What is your favourite thing about CMS Made Simple as it works right now?

Basically the same things as what made me fall in love with CMSMS a couple of years ago. I don't know any other system where you can actually port your static HTML files with such ease and speed. And neither do I know any other system (and don't you believe for one second that I do not ever try other systems, I do) which has such ease-of-use for my end customers. Even the most computer illiterate ones are able to manage and maintain their website with CMSMS.

Do you have what it takes to join the Dev Team?

If you want to find out more about the roles we are recruiting for then take a look at http://www.cmsmadesimple.org/about-link/join-the-dev-team. There you can read about the roles and also send us a message if you think you are the right sort of person to join our extended family.

1. What do you do in the Dev Team?

I am project manager, head of the programming team for CMS Made Simple and head systems guy.

In my role as project manager, I try to keep the team together and moving forward towards our goals without deviating too much.  This is done by largely working with the other dev team members to make sure things get done in a timely manner.  I also usually organize and chair our monthly meetings and other housekeeping duties like adding and removing access to various things, as needs arise.  Also, if a decision needs to be made that either doesn't need a vote by the membership or cannot wait for a vote, the decision usually fall on me.

The programming team manages everything related to the CMSMS core.  This includes implementing new features, fixing bugs, cutting releases and managing beta programs.  As head of this team, I am influential in deciding what new features or bug fixes will be included in a version and when that version will be released.   I also work with the other programming team member(s) and dev team members to manage those lists of features, new content, new ideas, etc.

As the head systems guy, I am largely in charge of managing the servers, managing users on those servers, managing email, upgrading server software, dealing with attacks, dealing with system difficulties and whatever else comes up that is system related.  I am one of the only users with access to the servers. Since that root access is tightly controlled, and I have years of linux/unix administration experience. If there is something that needs to be done as root.. it usually falls to me (unless somebody manages to get ahold of Ted first).

2. What is it that made you want to get involved with the Dev team for CMS Made Simple?

I was a programmer and a project manager for numerous years before I found CMSMS.  I found CMSMS because I wanted a simple PHP based package for my personal website that I could easily build on.  CMSMS fit the bill perfectly and I have been with it ever since.

3. How long have you been involved?

I found CMSMS in 2004, just shortly after its initial releases.   Something like version 0.079 or something like that.

4. What do you find to be the most fulfilling part of your role as a CMSMS Dev Team Member?

The best part of being a part of the dev team is when you see all of the great reviews that our professional users give CMSMS and some of the great things they do with our work.

5. What has been the biggest challenge you have faced as a dev team member?

The biggest challenge I face for CMSMS is in making sure that people know who we design CMSMS for.  The dev team learned long ago that CMSMS would never be a replacement for Microsoft Frontpage, or a drag and drop site builder for novices.  It's a tool built for professional web builders.  However, it's hard to educate the public to that fact and it comes up every day.

6. What keeps you motivated as a dev team member?

I still have a lot of great ideas (and get more regularly) as to what CMSMS could do, or what we could add on.  I want to see many of those ideas through.  Additionally, we have haven't finished getting CMSMS into the market that we want, or adding features.  I want to see that through too.

7. If you could be a "dictator for a day" for CMS Made Simple and implement one "fantasy function" immediately into the Core, what would it be?

Heh, some people will tell you that I AM the dictator :)  but that is far from the truth.  Most features and even bug fixes are discussed at length, and go through a "sales process" where we convince the other dev team members that the features are good ideas.  

However, that aside:  The one thing that is on (or near) the top of my list of things to do for CMSMS is to completely change the admin login stuff to make that more flexible, and to implement modules for a flavor of multi-site control.  This would allow one CMSMS install to be the 'master' and others to be 'slaves'.  It would allow central user management, module management and be flexible enough to grow as time goes by.  This would probably involve some kind of RESTFUL interface for the admin console.

8. Have there been any commercial or personal successes that have been because of being in the DEV Team?

I have been a part of many commercial CMSMS successes.  I have written modules, added features to those modules, or solved problems for many (hundreds) of websites that use CMSMS or successful commercial ventures.

9. What do you do when you are not wearing your "dev team hat"

Well, I read a lot (gotta keep up with technology you know), and I'm a big fan of watching new movies.  And when I am not doing that.. in the winter time I'm blowing snow :).  However, in the summer time it's time to work on my truck or go camping.

10.   What is your favourite thing about CMS Made Simple as it works right now?

The best thing about CMSMS is how flexible it is.   The various templates, modules and plugins are extremely powerful.  There are millions of websites that can be built without having to do any work in php, or have any programming knowledge.   However, you still need to know stuff about design, html, css, systems stuff (like Linux permissions, and finding error messages), and basic debugging skills.

Do you have what it takes to join the Dev Team?

If you want to find out more about the roles we are recruiting for then take a look at http://www.cmsmadesimple.org/about-link/join-the-dev-team. There you can read about the roles and also send us a message if you think you are the right sort of person to join our extended family.

We are looking for coders, designers, marketers, writers, movie makers, support gurus and more. Would you be interested in joining the dev team? It's a great way to give something back to CMS Made Simple and of course it raises your profile internationally. Over the next couple of weeks we will be releasing interviews with some of the existing dev team so you can find out more about what they do and what being in the dev team has done for them.

If you want to find out more about the roles we are recruiting for then take a look at http://www.cmsmadesimple.org/about-link/join-the-dev-team. There you can read about the roles and also send us a message if you think you are the right sort of person to join our extended family.

Since the release of CMSMS 1.11, whilst simultaneously supporting the 1.11.x series and fixing issues, we have also been quietly working on the next new feature version of CMS Made Simple. Though we do not have an arrival date yet, the version is progressing nicely and we felt it was time to give you a preview of what you can look forward to.
The new feature release is not a complete rewrite; however it will contain many new rationalizations and features. We feel that they are significant enough to have decided that we are tentatively naming the new release ‘CMS Made Simple 2.0’.

So, we are delighted to unveil some of the new features.

Confirmed New Features

1. Design Manager

The new Design Manager is our solution rationalizing all template, css, and design capabilities into one module, plus providing a new set of classes.

With the new template ‘inheritance’,A ‘include’ and ‘function’ capabilities of Smarty3 we decided that it was time to rationalize the whole template functionality, making it easier to re-use templates, provide one common interface for editing both templates and stylesheets, and work with designs. The Design Manager, and it’s associated classes have the following features:

• A new concept; a “Design” object is created that contains associations to stylesheets and templates. A Design can be associated multiple stylesheets, templates. Though this is just a loose relationship.


• The Design Manager module provides the editors for Stylesheets, and Templates


• Designs can be read from, and written to XML (including old theme files). The exported design xml file will contain all images, stylesheets and templates associated with the design.


• Templates, Module Templates and GCBs now all fall into the new ‘templates’ section, with no real distinction between them other than a unique name.


• Templates are only loosely associated with their type (e.g. You could use a Menu Manager template within Products if you really wanted to).


• Templates can belong to zero or more designs.


• Templates can belong to zero or more categories.


• Stylesheets can belong to zero or more designs.


• Templates, Designs and Stylesheets must all be uniquely named.


• Content pages must now be associated with both a ‘Design’ and a ‘Template’ (the design association is used to find stylesheets to render).


• All objects (Designs, Templates, Stylesheets) now have a description field.


• Templates can have additional editors, and an owner for more granular control of design.


• All Core modules (such as Menu Manager, News and Search) no longer have template editing functionality. This is now handled entirely by the Design Manager.

2. New smarty plugins for module form and page creation.

We have added numerous smarty plugins (and will probably add a few more) to make creation of forms in a module template simpler. This marks a change in the way forms are created in modules and moves most of the layout functionality into Smarty, whilst keeping the business logic in PHP. To that end, many of the module API methods that create input elements will now be deprecated.

3. Enhancements to Add/Edit Content

The Add/Edit content forms have been rationalized into a single form and moved into smarty as much as possible, thus to allow for customization and enhancements. Additionally, we’re working on the ability for better management of the various content properties.

4. Rewrite of the UDT interface.

We have rewritten the User Defined Tag code to be more aesthetically pleasing and to go with our new admin interface style.

5. AdminSearch

This will be a big feature for site developers; an admin side search that will search through templates, stylesheets, designs, page content, and (with hooks) the content of other modules to find specified text. This is extremely useful to help you find elements in admin that previously would have required manually looking through templates, pages and GCBs, etc. This will dramatically improve site development in CMSMS.

6. A better end user experience.

We are going through all admin forms and adding interactive help and making sure that the forms are reasonably accessible for persons with disabilities.

Planned New features

7. ‘Navigator’ Module

One of the biggest issues developers face with CMSMS is creating unique navigation. The primary reason for this is that, when it comes to styling and editing templates, the flat lists of nodes currently generated by MenuManager do not fit very well with a hierarchical data structure.
The new Navigator module will work in much the same way as MenuManager does, however, instead of generating a flat list of nodes, it will generate a hierarchical data structure. With that, and some simple smarty logic it will become a trivial task to generate custom dynamic navigation within CMSMS.

7. New Installer

A big problem with installing and upgrading CMSMS is the requirement to upload and expand the entire package on your website before you can find out that there’s compatibility or other issue. To that end we’re working on a single file installer to improve the process. The concept of this is as follows.
By uploading the single installation file and browsing to it you will begin the process. The new installer will detect if CMSMS is already there and create an install or upgrade situation depending on what it finds. The installer will then guide you through the various compatibility tests to ensure that you won’t have a problem with the core package and modules. Thirdly the installer will allow you to select which packages you want to use (base vs. full package, diff packages, language packs etc), download and expand those selected into your installation and finally will execute the appropriate routines to seamlessly install or upgrade your core. Whilst this new installer won’t solve problems with 3rd party module compatibilities, it will go a long way towards making the installation process smoother.

8. PHP 5.3.x or greater

As previously announced, CMSMS 2.0 (tentative) will require PHP 5.3 or greater.

Notes on Compatibility and Support

As the saying goes, you can’t make an omelette without breaking a few eggs, but we think you will find this to be a very tasty omelette. Thus, with these major changes we are predicting that there will be inevitable upgrade and compatibility issues with some third party modules (at this time WYSIWYG modules, and modules that create content types are known to be effected). However, we will not be breaking the module template API or the module form API so many modules should continue to operate with zero, or minor modifications.

Additionally, there will probably be some layout issues as we try to manipulate the data structures containing templates, GCB’s and stylesheets into the new design structure. We will however attempt to minimize, and/or document any upgrade issues.

Due to the compatibility issues that we know we will have, the Dev team has decided that the 1.11.x series will be supported (for bug fixes and security issues) for one year from the release of the first 2.0 package. This will give site developers the opportunity to work with module developers to ensure a smooth upgrade process.

So, that is the state of play right now. We will look forward to telling you more information as it becomes appropriate. Thanks for reading.

The Dev team

The CMS Made Simple Dev team is happy to announce another maintenance release in the 1.11.x series. CMSMS 1.11.4 is now available for download. Our focus has been on stability and removing problems. Particularly of note are issues we have fixed with respect to the new parsing mechanism we have instituted with respect to content page templates.

Numerous users encountered problems when editing content pages or page templates with some syntax. i.e: syntax that addressed the {ldelim}$content_obj{rdelim} variable, or other objects or arrays of Smarty objects, etc. The Smarty parser should now handle most of that syntax properly. We also fixed problems with the {ldelim}cms_stylesheet{rdelim} and other plugins with respect to Smarty caching.

User defined tags are once again enabled in the admin interface. This solve problems our users encountered when using user defined tags in stylesheets, and in some admin templates. For performance reasons however we wish that this was not required.

We fixed a significant issue with the static route creation mechanism that may have effected the installation of CMSMS and definitely effected installation of modules that used static routes to allow for lazy loading.

Additionally, there were numerous fixes to file manager and image manager with respect to remembering directories, advanced mode, and deleting images. We also made changes to the behavior of CMSMS when using secure pages. This should significantly reduce, or eliminate, problems related to content being blocked due to requesting insecure content in a secure page—whether that be a content page, or an admin page.

Some people also reported a particular slowness when installing CMSMS in Windows environments due to some tables being created in the InnoDB format rather than the MyISAM format. Though technically not a CMSMS issue, we have now made modifications so that, by default, all tables are created in MyISAM format for new installations.

We also performed some cleanup of minor issues, including handling of email fields when adding or editing an admin user, cleaning up an internal page variable, removing all references to the Wiki URL config entry (this is no longer valid since we removed the Wiki).

For a more precise list of the changes please read the doc/CHANGELOG.txt file that is included with the release.

Once again, it is our intent that this be the last release of the 1.11.x series so that we can focus on new development. We remind everybody that the 1.11.x series of CMS Made Simple will be the last release that supports PHP 5.2.x. We recommend everybody contact their hosts to at least enable PHP 5.3 as soon as possible.

The members of the development team and the community at large have donated hundreds of hours towards reproducing, fixing, and testing this release with the intent that it fix as many of the known issues as possible. Please give them your thanks.

As of this release, and due to our limited support resources, the only officially supported versions of CMSMS become 1.11.3 and 1.11.4 respectively. We encourage everybody to upgrade their websites as soon as possible.

Have fun with CMSMS

These are just the major points. For more detail as to what was accomplished in CMSMS 1.11.3 please read the doc/CHANGELOG.txt file available in the download package.

Because of the large amounts of changes in this release that will in some way effect most users, we recommend that all sites be upgrade to CMSMS 1.11.3 as soon as possible. Also, as per our support guidelines, the only supported versions of CMSMS at this time become 1.11.2.1 and 1.11.3.

Thank you all, and have fun with CMSMS.

You can vote now at http://www.cmscritic.com/critics-choice-cms-awards/

The voting stage has now opened and will be running from now until November the 11th.  It's early days yet but we are currently at second place.  You can help us get to first!  All you need to do is go to the CMS Critic website following the link below and look at the section for 'Best Open Source CMS'.  Click the little thumbs up icon to the right of CMS Made Simple.  The first time, it may need to log you in via Facebook or one of the other available Social Networking sites IDs available, so check to make sure that it registers your vote.

The link to the voting page is http://www.cmscritic.com/critics-choice-cms-awards