Announcing CMS Made Simple 1.9 – Bora Bora

[compufairy]

Once again the CMSMS™ Dev team has joined forces over hundreds or thousands of hours of effort to release yet another milestone version of CMS Made Simple™. This release is a feature version where we expanded the flexibility of your favorite package while maintaining its famous ease of use. We are confident that you find this version of your favorite content management system to be the best one yet.

Complete Freedom in URLs now customizable in any way preferred:
We have addressed some long standing concerns and wish list items with respect to URLs in this issue. There is a new URL field for each and every content page, allowing you to specify the exact URL (relative to the start of your site) for each content page. i.e: if you want the URL to be 'blah' you can do that. if you want it to be 'a/really/complex/path' you can do that too. You can have two pages that end in the same string, like: ´toronto/restaurants' and ´calgary/restaurants'. The site developer has complete control over the URLs for each page. Developers have the option of leaving the URL field blank, and thereby using the old page-alias method of doing things, or URLs can automatically be filled in from the page alias. To make it easier to track your URLs or see them at a glance, the listcontent page has been enhanced to show the page alias, and the page URLs. This is a huge feature and we are sure will further cement your relationship with CMSMS™.

News Module allows customizing the URLs
The News module has also been modified to allow customizing the URLs to the detail view on news articles. i.e: You can choose exactly what the URL will be to each news article. There is a preference as to which content page to use to display the detail view, and it will use the 'default' detail template. I am sure that this functionality will also appear in other third party modules like blog and e-commerce modules soon.

MenuManager module improved
The MenuManager module has been greatly improved with an eye on performance. Since building the navigation(s) is often the most memory and time consuming portion of every page request, but page structure doesn't change that often, we've added the ability for MenuManager's output to be cached. If the page that is being generated is cacheable, and the MenuManager template that is being used is cachable, and thirdly if the 'nocache' parameter (new in CMSMS 1.9) is NOT specified, then MenuManager's output can be cached. If a cache file does not exist then one will be generated to optimize the next request. In our tests this resulted in a significant performance increase. This is another huge feature for 1.9.

'use_hierarchy=false' issue solved
The URL modifications we have made have finally allowed us to permanently resolve the 'use_hierarchy=false' issue that we have wanted to get rid of for a long time, but caused a bit of a stir in the 1.8 series. On upgrade, if you were using 'use_hierarchy=false' in the config.php all of your page aliases will be copied to the 'URL' field, thereby preserving your link structure. New preferences in site admin can control how URLs are defined for new content items.

Features, Features and more Features
We also went through our feature request list, and picked off quite a few of the items that people have asked for. Included in this are: You can now add a description to Global Content Blocks, Additionally, developers can disable the WYSIWYG editor on each individual GCB to remove the risk that it may mess up some formatting. There is also a new option to 'run' a User Defined Tag from within the admin. This allows site developers to create a UDT that maybe does some database cleanups or queries, and to run it from within the admin console rather than having to create a dummy hidden page on the sites frontend. Additionally, a new preference allows displaying either the menu text, or the page title in the content list. The sitedown functionality has been improved. now you can display a 'Site Down' message to site visitors while logged in administrators can still see the site. And due to popular request we have improved the behavior of the {content_image} and the thumbnail and image properties of each page.  These are just a few examples of the enhancements you will find in CMSMS 1.9 Bora Bora.

jQuery Replaces script.aculo.us
We've finally gotten rid of script.aculo.us and prototype (hooray) from CMS Made Simple™, and replaced it with jQuery. This will make things a lot easier for module developers to do nice fancy ajaxy and javascripty things in their modules. Once we did this we were able to completely re-write the page re-ordering function. You can now order pages as you would expect, and change the parents of pages, etc. It's a fantastic benefit to using jQuery.

New Admin Theme
We are also concerned about presentation, and therefore the NCleanGrey admin theme has gotten an overhaul. We really like the new look of this theme, and we think you will to. Many thanks to Nuno Costa for his contributions in this area.

Optimization
We also spent a great deal of time focusing on optimization. Though we are still not overly worried about a dozen lines of code here or there, we looked at the bigger picture like removing redundancies, optimizing things so that where possible data wasn't loaded from the database multiple times, etc. Particularly in the area of loading content. To that end we have new classes for managing loaded content objects, and loading them. This should result in slightly better memory utilization, and certainly better scalability.

E_STRICT and E_DEPRECATED
Though we still don't officially support the E_STRICT and E_DEPRECATED error reporting levels in php we have made a lot of effort to clean up whatever errors we have found. We will endeavor to do a review of each function to try to remove E_STRICT and E_DEPRECATED errors in the future.

For security reasons, and because it is not good practice for modules, UDTs or plugins to modify internal CMSMS™ variables we have made some core API changes. The {$gCms} smarty variable has been removed, and it is no longer possible for third party modules to use $gCms->variables to store config data. Additionally, the configuration data is now stored in an object once loaded, and setting data at runtime into the config structure is deprecated, and that ability will be removed at a later date.

In addition to the items listed above there are dozens of other changes that have been made to the core, including removing some deprecated plugins from the release, handling the timezone setting for PHP 5.3, rework of the cms_selflink tag and more. Please read the doc/CHANGELOG.TXT for a more complete list (though it is quite technical) of what has changed.

IMPORTANT NOTE for users that have created their own admin theme and developers of 3rd party modules:
Removing script.aculo.us and using jQuery may cause difficulties for our users that have created their own admin themes. As well, there may be a few third party modules that relied on script.aculo.us, or did some non-standard things to include jQuery. Some module developers may need to release new versions of their modules because of the jQuery changes. Additionally, the changes to the core API functions and the removal of the {$gCms} smarty variable may cause problems on existing sites, and break the behavior of some modules. As always, it is highly recommended that users make backups of sites before they upgrade, and to test this upgrade of CMSMS™ on a development server before upgrading your production sites.

Beta Team
This release had the best beta testing cycle of all of the releases. The beta testers spent many many hours installing the release, testing upgrades, spotting issues and verifying that they were fixed, and generally being a great assistance to the CMSMS™ community. Although we did not close every single issue that was reported by the beta team, we did analyze each one for severity, and fixed what was important (especially in the days leading up to the release). Here we would like to give thanks to: alby, bertoost85, binarydesign, Dabnis, dc2, DIGI3, duketown, gdur, hexdj, janvi, jce76350, jd447, jos, lowell, milehigh, mww, NaN, Nullig, Peciura, pedes, seensite, Sonya, Stikki, uniqu3 and vilkis.

The CMSMS Dev team has once again come together in a unified effort, and contributed hundreds of improvements to CMS Made Simple.  We have focused on ensuring stability, consistency, security, performance and presentation. Please give special thanks to your Dev Team:

   * Ted Kulp - CMSMS Project Founder
   * Robert Campbell (calguy1000) - Project Manager / Development
   * Samuel Goldstein (SjG) - Development
   * Morten Poulsen (Silmarillion) - Development
   * Ronny Krijt (RonnyK) - QA Team Lead
   * Jeremy Bass - QA Team
   * Rolf - QA Team
   * Reneh Helminsen (reneh) - Translation Team Lead
   * Mark Reed (Dr.CSS) - Support Team Lead
   * Jeff Bosch (ajprog) - Support Team
   * Anne-Mieke Bovelett (Compufairy) - Marketing Team Lead
   * Keith Lauchlan (Utter) - Marketing Team Member
   * Bruce Marable - Marketing Team Member

NOTE: if you upgrade and have any problems please use this thread, thanks...

http://forum.cmsmadesimple.org/index.ph ... 822.0.html

[nervino]

Wonderfull!
Thanks a lot!!

[totophe]

I'm so glad to see that there is color in the admin at the end !

Congrats !!!

[nicmare]

Awesome Update and very nice admin theme! Thanks for that!

I think i found a bug but in bugtracker is no option for choosing current release (1.8.2 is the latest) and therefore i post it here:
Screenshot
If you want to create a simple Sectionheader, then i get this error message. current walkaround:
use "Content" as "Content Type". Fill in your values (the title) and then (before submitting) choose "Section Header". Now you can submit and it works-> wtf?? 

[panthus]

Yay, finally! I really like the new admin theme and the custom url feature is awesome! Gonna love playing around with all the other upgraded stuff. Lots of thanks to the DevTeam and the BetaTeam for all the hard work!
CMS Made Simple gets better and better. Love it. 

Code: Select all

string(128) "Smarty error: [in temporary template line 1]: syntax error: unrecognized tag 'JQueryTools' (Smarty_Compiler.class.php, line 590)" string(128) "Smarty error: [in temporary template line 2]: syntax error: unrecognized tag 'JQueryTools' (Smarty_Compiler.class.php, line 590

I get the same error with CGBlog, it seems like a problem with the integration of JQueryTools and the CG Modules. No idea what it is, yet.

[Dr.CSS]

Please direct all problems/bugs etc. to this thread, and I will tell you why you get that error...

http://forum.cmsmadesimple.org/index.ph ... 822.0.html

In case you didn't notice this on the board title...

Announcements
Project Announcements. This is read-only.

[jmcgin51]

In case you didn't notice this on the board title...

Announcements
Project Announcements. This is read-only.

Hmmmm, it's obviously NOT read-only, or you wouldn't have had to respond to any posts 

Perhaps it should read "Project Announcements.  This ought to be read-only."

[Rolf]

@ panthus

New release JQueryTools already available in the Forge:
http://dev.cmsmadesimple.org/projects/jquerytools


Other 1.9 related issues and solutions here:
http://forum.cmsmadesimple.org/index.ph ... 822.0.html

[kendo451]

Do the .htaccess rules need to be changed to work with the new Pretty-URL system?

The original is here & here:
http://wiki.cmsmadesimple.org/index.php/User_Handbook/Tips_And_Tricks
http://wiki.cmsmadesimple.org/index.php/User_Handbook/Installation/Optional_Settings

[calguy1000]

Nope, the .htaccess stuff has not changed.

[kendo451]

I am always impressed when the dev team delivers increased functionality, without making it more complicated to set up.  This new prettyURL system is great!

[nicmare]

yea. but do not wonder. when you cache the menu and then active mod_rewrite, the menu still outputs the old code. its cached. just clear cache and you are ready

[calguy1000]

Hello all.

Well, as usual, there were some issues that neither the development team or the beta team caught prior to release.

Because there were more than a handful of issues (this is understandable due to the amount of changes in the 1.9 release)  we decided to wait and gather the issues, and then release a new version once the majority of the items had come in.

Over the past week the dev team has been working hard to get these issues confirmed, fixed, and confirmed fixed.. There are quite a few of them actually.  And we even managed to find a few that weren't reported in the 1.9 beta cycle, or since the release.  Some of them old issues, some of them new.  In particular, MenuManager has received a lot of attention.

So we're just waiting now on some final testing, and to update the changelog and a few other documents, and then we'll be releasing 1.9.1

Stay tuned, and thank you for your time.

[katea]

Fantastic update, shame about the bugs ....

As for the theme ..... Well, sorry, but I'll be going back to the last one .... This one is shockingly drab ... It's like a negative, void of all color ;o) ...

Love the last one .... Though Minimalist Theme I really like ... May use that when updated to work with 1.9 ;o)

[kendo451]

Calguy & other dev team members, we all thank you, for your time!