Announcing CMS Made Simple 1.6
June 22nd, 2009 by Robert CampbellSo here it is… after building alot of anticipation, and only a week behind schedule, CMS Made Simple 1.6 is now ready for public consumption.
- Changes/Features/Bug Fixes
There have been a great deal of changes,.. so I’ll just brush on them here… please read the changelog notes attached with the release at:
http://dev.cmsmadesimple.org/project/changelog/1897
* Content Type Changes
Major effort has been undertaken to make the system faster, better and easier to extend. We’ve reworked the content types and various
classes so that the number of queries is better optimized, and so that there is more options for configuration of what is to be displayed to
your users on the edit content page.
* Permissions Changes
We’ve completely re-worked the content permissions to allow more flexibility, and allow greater control over what your users are allowed
to do with respect to content. Briefly, the permssions model has changed to:
– Additional Editors or Owners of a content page
can edit that content page
– The “Add Pages” permission states that the user can create pages as children of pages that he is already an owner/additional editor of.
– The “Remove Pages” permission states that the user can only remove pages that he is an additional editor/owner of
– The ‘Manage All Content’ permission allows you to do anything with all content.
* New Themes and Content
– Two new frontend themes have been developed, and the default content for new installations changed considerably.
* Forgot Password functionality in admin
– The admin console now has the ability to handle forgotten passwords, if an email address has been associated with the admin account.
* 404 error handling changes
– A new content type ‘Error Handler’ has been created to handle 404 errors. This page is just a regular content page with some extra
functionality. This will allow you to do things like embed module calls, etc. into the 404 page.
* Site Preferences rewrite
– The site preferences page has been completely re-written.
* Sitedown IP address exclusion
– When sitedown mode is enabled, it is now possible to exclude certain IP addresses from that restriction. In this way the site can be
down for everybody but the developer working on it.
* Page Preview fixes
– Page preview now works with page templates that have multiple content blocks.
* UTF-8 changes for new installs
– On new installs, the installer now tries to change the default encoding for newly created tables, etc. This allows better utf-8 flow
for most sites.
– A new ’set_names’ config entry has been created to allow doing a ’set names utf-8′ at the beginning of any request. This is on
by default for new installs, and off for upgrades.
* config.php cleanup
– We’ve removede a bunch of the redundant stuff out of the config.php, and optimized the pretty url stuff so it should be a bit easier to
understand.
* MenuManager improvements
– The admin panelo for menumanager has been completely re-worked to be more obvious, and easier to use… there is now the ability
to specify a ‘default’ menu template.
* ModuleManager improvements
– Module Manager now has the ability to check dependencies before installing a module.
– Module Manager can now check to see if there are newer released versions of any of the modules that you are currently using on
your site.
* TinyMCE improvements
* Search improvements
* Printing improvements
* Many, Many bug fixes.
- Compatiblity
- For sites with multiple admin users who have different levels of permission for editing content, you will need to re-visit the permissions,
and to make sure that everything is setup the way it needs to be.
- Users using Cataloger, PageBlocks, and other modules that create content types will experience problems with compatibility. Please
contact the authors of these modules and ask them to release a version compatible with CMS 1.6 as soon as possible.
- Diff Packages
Due to the extent of the changes, there will be no diff releases for 1.6. You will need to download the full package, and transfer the whole thing up to your new website… please download the appropriate checksum package and validate your upload with that.
Thanks
I would like to take this time to give my thanks to the development team, and the beta testers who contributed hundreds of hours in testing, fixing, enhancing, and debugging this release. If I forgot your name, please remind me and I’ll add it ASAP.
- Dev Team Members
Ronny Krijt
Rene Helminsen
Alberto Benati
Nuno Costa
Mark Reed
Morten Poulsen
Ted Kulp
Tyler Boespflug
- Beta Testers
SimonSchaufi
duclet
Sonya
bess
Nullg
JeremyBASS
ZiggyWigged
Maarten
That’s it… I’m sure you’ll find this release the best ever…. It can be downloaded from the usual locations… Enjoy.
June 22nd, 2009 at 12:15 pm
Since there are substantial changes, do you recommend older sites to upgrade to 1.54 first?
Cheers,
Alex
June 22nd, 2009 at 2:01 pm
Awesome – thanks very much to everyone for their excellent efforts.
June 22nd, 2009 at 9:03 pm
[...] There are a lot of changes, some large, some small, to learn about them all, you should get them from the horses mouth. Some of the ones worth mentioning are: better, faster, easier, more advanced permissions, new [...]
June 23rd, 2009 at 12:05 am
Hi,
How can i upgrade a latest version of cms, like version 1.54 to 1.6 etc.
Thanx,
Deepak
June 23rd, 2009 at 12:33 am
[...] original post here: CMS Made Simple – Blog This entry is filed under CMS, Management. You can follow any responses to this entry through [...]
June 23rd, 2009 at 3:45 am
Congrats to all involved in getting v1.6 out.
I recently uploaded an admin theme, based on Nuno Costas ‘NCleanGrey’, called ‘OxygenFire’.
Are there a lot of changes between the original ‘NCleanGrey’ and the new ‘NCleanBlue’ that goes with CMSMS v1.6?
Will older admin themes need to be upgraded to work with CMSMS v1.6?
Thanks again for 1.6, I’ll be using it very soon.
Simon66
June 23rd, 2009 at 5:52 am
Congrats on the upgrade. But I seem to have found a problem.
The menu seems to be broken. The {$node->image} and {$node->extra1} tags are not working. On the page HTML it is simply blank. Have these tags changed or is this a bug?
June 23rd, 2009 at 6:17 am
Ahh found the issue.
loadprops=”1″ must be in the menu smarty tag in order to load the advanced properties.
June 23rd, 2009 at 6:26 am
very cumbersome to upgrade, shame as the CMSms is so easy to use. I followed instruction in the doc folder for upgrade, the install script thinks that it’s a new install instead of an upgrade. Plus, it does not recognize the new version and still thinks I am installing v1.54. I aborted the upgrade and rolled back the old version, waiting for more time to install v 1.6 from scratch and import the database from v 1.54. Or would that screw up the script?
June 23rd, 2009 at 5:16 pm
Why aint it possible to export all content to a file? – Right now I want to upgrade, but to create a new installation and transfer each site, takes too long time.
Please incoporate an function so it’s a lot easyer… With all the other big php projects, it’s is easy to upgrade. Why isn’t it here?
June 24th, 2009 at 1:58 am
Open Source CMS “CMS made simple” Version 1.6 veröffentlicht…
Das Open-Source CMS “CMS made simple” ist in der Version 1.6 (New Caledonia) veröffentlicht worden. Hauptaugenmerk dieser Version war die Überarbeitung des Berechtigungssystems, aufgrund derer die Berechtigungen der verschiedenen Benutzergruppen z…
June 24th, 2009 at 2:55 am
Yeah, upgrading is a real pain. I have numerous websites running CMSMS and with every new release it takes a long time to upgrade them. An automated process (like WordPress has) would be very handy.
June 24th, 2009 at 3:44 am
thank you guys (and girls, if any)
June 24th, 2009 at 4:15 am
Learn from history, you who complain.
When there’s a new version of CMSMS, there’s generally a patch one week after.
Plus: CMSMS site does not yet use the latest version (which I think should be a mandatory step before publishing any new version).
As long as I see this, I will always wait at least 1 month before getting a new release (at least for something critical).
June 24th, 2009 at 9:47 am
Looking forward to the upgrade. Faster Better Stronger… Very nice.
June 24th, 2009 at 10:09 am
[...] Arbeit mit CMS made simple 1.6 soll flotter vonstatten gehen als mit den Vorgängerversionen, denn die Entwickler haben einige [...]
June 25th, 2009 at 3:43 am
Have started using 1.6 – it looks very good. Thanks
One problem when editing or crating new pages I cannot select the template I require as the template option is missing. Any ideas?
Thanks
Barry
June 25th, 2009 at 3:58 am
[...] Ebenfalls überarbeitet wurden die mitgelieferten Module, die jetzt noch leistungsstärker sein sollen. Auch die im CMS enthaltenen Templates wurden einer Überarbeitung unterzogen und sollen jetzt modernen Ansprüchen entsprechen. Insgesamt macht die neue Version einen frischeren und schnelleren Eindruck. Alle Änderungen der Version 1.6 kann man im Changelog im CMSms-Blog nachlesen. [...]
June 25th, 2009 at 4:20 am
[...] Änderungen können im Changelog nachgelesen [...]
June 25th, 2009 at 9:18 am
“One problem when editing or crating new pages I cannot select the template I require as the template option is missing. Any ideas?”
Yea, its’ the first item within the Options Tab when editing or creating a new page.
June 25th, 2009 at 4:59 pm
Personally I will leave all existing sites at 1.5.4 and install 1.6 for all new sites.
1.5.4 was very stable and secure and, in my opinion, was the best it could be. Sites based on 1.5.4 should last a couple of years without any problems. After that, the need for a site re-do should allow for the time to upgrade to whatever version is available then.
Simon66
June 26th, 2009 at 2:52 am
does the cms support arabic notations!
June 26th, 2009 at 5:43 pm
Hi there,
I have upgraded my site already a couple of times to a newer version ofCMSMS, this is the third one, now to 1.6. Up to now upgrades have been easy and painless this time, when editing pages, it does not show the WYSIWYG menu in any of the pages where it was before!
Aside of this all well.
June 26th, 2009 at 8:04 pm
I just noticed that 1.6 is called New Caledonia. Great choice of name!!
That has to be a good omen as it’s my main ambition to learn french and get a place on New Caledonia to spend long summers lazily drinking great wine, eating great food and exploring the island, that’s what I’m working towards.
I already moved from England to Sydney Australia, so I’m nearly there!
Simon66
June 27th, 2009 at 10:41 am
CMSMS team, thank you so much for all your effort on this wonderfull CMS. I’m not a developer, but a frontend man, and you enabled me (and many others) to work with a very user-friendly product – for me as ‘developer/designer’ and for the end user.
I greatly appreciate your work and hope you’ll be releasing upgrades of CMSMS in the future!
Ruud.
June 29th, 2009 at 3:58 pm
I upgraded a couple of my installs but stopped when I realized that the WYSIWYG editor doesn’t work anymore. I checked the Modules to see if TinyMCE needed to be upgraded and it doesn’t. Please tell me there is a fix coming for this because I don’t want to have to roll all the sites back to 1.5.4
June 29th, 2009 at 5:28 pm
so here is what I did, install 1.6 and imported the 1.5.4 database, it’s working fine but for tinyMCE which I had to re-install. I still was not happy with it so I installed FCEeditorX and that worked great,even better.
Thank you for designing such a great software!
June 30th, 2009 at 12:20 am
Great work on the latest release loving the new themes.
I’m finding as usual … upgrading breaks tinyMCE so I’ve got to go in and reset it via Extensions -> TinyMCE WYSIWYG … and reset the various tabs back to default
(at least the last few upgrades I’ve made it disappears when I go to edit pages so I need to reset the options on it)
July 2nd, 2009 at 12:58 am
Thanks for the new release! Upgrade 99% fine, just had to follow the instructions from http://forum.cmsmadesimple.org/index.php/topic,35034.0.html as well to have the editor back, but otherwise everything is great, merci!
July 2nd, 2009 at 3:22 am
PS: If you are upgrading, make sure to read *all* the release notes (not like me), especially the part “7) TinyMCE: TinyMCE has had some serious enhancements as well. However, those enhancements make it so that on an upgrade you may not see the TinyMCE editor in your content pages, or various frontend forms. To resolve this problem, you may need to uninstall the TinyMCE module (in Extensions >> Modules) and re-install it, then reset the settings.”
July 2nd, 2009 at 9:42 am
Nice job, dev team! I appreciate the improved attention to detail, on everything, including the default install page.
July 2nd, 2009 at 11:01 pm
It i usually a good idea to disable and uninstall modules before upgrading. May also apply to core modules. Mind though that you’ll lose all content when disabling albums and news.
July 3rd, 2009 at 8:32 am
For all this peoples crying about upgrade, i can’t follow you?
Easy upgrade is one reason why i choose CMSMS! It’s really much easier then upgrade a Wordpress Site.
@denis Says:
the install script thinks that it’s a new install instead of an upgrade. Plus, it does not recognize the new version and still thinks I am installing v1.54.
Are you sure you did overwrite ALL files?
@Benjamin Says:
Why aint it possible to export all content to a file? – Right now I want to upgrade, but to create a new installation and transfer each site, takes too long time.
Please incoporate an function so it’s a lot easyer… With all the other big php projects, it’s is easy to upgrade. Why isn’t it here?
It is actually easy! Just learn how to make a SQL Dump and you can import/export the content to one file! I am sure there is phpmyadmin preinstalled on your Hosting. Of course, you still have to copy the files (not content) with FTP but that isnt easier with any other CMS.
July 3rd, 2009 at 8:40 am
Thanks, I really appreciate all the work you guys put into this project.
July 3rd, 2009 at 2:00 pm
[...] Så er CMS Made Simple 1.6 klar til download. Jeg gennemgår her nogle af de væsentligste ændringer forbundet med opdateringen. Indlægget er delvist oversat fra CMSMS.org [...]
July 4th, 2009 at 11:48 pm
So is the dev server down. I want to use this but any time I go to the dev subdomain, I get an error that the network is timing out…
July 5th, 2009 at 5:00 pm
I may have had problems because I originally installed CMSms in the root folder. Anyway, I re-installed and imported the database and everything is fine…. except tinyMCE, but I resolved that as well, by getting rid of it. One hing I was not able to work with is captcha for the tellafriend plugin. That’s still not showing. The documentation for implementing captcha is not clear.
Yes, I know I am bitching but all in all, I find CMSms the easiest cms I have tried. I actually got to make it work for my website, I could not do that with joomla or drupal and I did not try wordpress.
So thank you for the CMSms team.
Denis
July 6th, 2009 at 9:35 pm
Thanks CMSMS team! I have used CMSMS for almost 4 years now and while I look most forward to version 2.0 I am quite imrpessed with this CMS system. I look forward to installing 1.6 on a test site to learn all the changes prior to applying to any of my clients’ sites. Thank you all for your dedication to this open source project.
Rich
July 10th, 2009 at 2:40 am
Except fort he bug with the links and characters I think it is a great update!
I updated
15 sites from 1.41
5 from 1.1
1 from 1.08
All went great!
July 19th, 2009 at 1:25 pm
Hello, the update to CMSMS looks awesome – thank you so much for this amazing project you are all legends! Just one question – i have a bug with 1.6 – where do i report it?
Thanks,
Karl
July 21st, 2009 at 3:34 am
Loving CMS 1.6 – One small suggestion … on the module manager, where you list the modules to be upgraded, can you make it so its clickable or add an upgrade button, cause at the moment, you still have to go into the module list to find the module to upgrade it.
July 28th, 2009 at 8:54 am
I think the TinyMCE issue is related to the CPANEL mod_security which switches the server API to CGI. What’s happening is that the new tinyconfig.php file is being requested with get variables attached: templateid and languageid. It looks like the Suexec setting is sniffing that as an attack and responding with a 404. DENIED.
Now before you say, “post that in bug tracker”. Our website admin is going to have to fix up the problems with the signin form. No real point having bug tracker if you can’t sign in to use it guys…
The fix? Run a 1.6 locally and copy out of Firebug the tinyconfig.php response and insert into the admin/webpage template.
Hope we see the removal of get variables in file requests real soon. That’s not a smart solution to language versioning in, well, anyone’s language.
August 5th, 2009 at 10:14 am
Yes, we need an automatic upgrade button like WordPress.
September 28th, 2009 at 7:07 am
For people editing pages and wondering why the “Template” droplist isn’t there:
If, like me, you didn’t liked the moving of the “Template” droplist from the main Page editing tab to the Advanced options, here’s how to fix it: go to Site Admin, click Advanced Setup and check Template in the Basic Properties list. Your template will now appear back into the main tab when you edit the page.
This took me some time to figure it out by digging into the source code :-]