Coming Soon - CMS Made Simple 1.10
Posted: Mon May 02, 2011 3:50 pm
Hello Everybody.
It's been two or three months since the latest stable release of CMSMS (v1.9.4.1) and all seems to be going relatively well on that front. So I thought I'd tell you about the efforts that are ongoing and our plans for the next great version of CMS Made Simple.
The CMSMS Dev team has been working on a version 1.10 hopefully for release in the late summer / early fall. Already a few things are done in the new release, and there is a long list of things on the list. Here are but a few of them.
- Memory Optimizations
- Clean up the module class (Get rid of the last of the long deprecated callback functions, and replace the smarty, db, and cms members with accessor methods)
- Introduce module lazy loading on the frontend. This will be an 'opt in' process for modules, and will not work initially for modules that handle routes, or a few other conditions, but for some modules this could be implemented providing for a significant reduction in memory requirements on many pages.
- General 'Under the Hood' Improvements
- Add more events to allow for a proper multi-language addon module
- Rewrite the config.php stuff to provide a sparse config.php file at the start, with just the minimum amount of stuff necessary to get started. Other variables, if not specified in the config.php file will be calculated dynamically. This should minimize config problems.
- Provide a seperate SSL admin path
- Cleanup of the Content Object (private/protected members/methods etc).
- Cleanup the $gCms class to do better take advantage of the autoloader and have less members....
- Cleanup the $gCms->modules public array. We'll probably make this an object of sorts as it needs to be really cleaned up for the possibility that a module may be installed in the database, but not exist in memory.
- Module Manager Optimizations
- Get rid of nuSOAP in the distribution and replace it with a generic rest interface.
- Memory optimizations for Module Manager when downloading or expanding packages.
- Better handling of dependencies when upgrading
- {cms_stylesheet} changes
- Change it to combine stylesheets into a single css file by default. unless there are stylesheets with mixed media types attached to the template.
- Improve support for SSL
- Admin Interface Changes
- We're hoping to provide an admin side search capability to search inside pages, GCB's, templates, stylesheets, etc. This will be handy for solving the 'where is this called' problems.
- We're planning on adding a new page to handle various admin tasks like clearing the cache, repairing database tables, doing table optimization, cleaning up content, etc.
- A preference for the default content type when adding new content
- A new (again) permission called 'Reorder Content' that will allow for people to have limited ability to re-order their own pages.
- We're planning on writing and slowly introducing a replacement to listcontent to get past our scalability and memory issues. We'll see how much time we have though.
- Salted MD5 Passwords (for the uber paranoid).
- Re-work of the Admin log to provide filtering, sorting, and better pagination, and automatic cleanup.
- General smarty Items
- A drop in replacement for the {html_date} plugin that will use jquery to provide a popup calendar.
- A review of all plugins to ensure that the assign parameter is available where it needs to be.
- A new plugin to automatically generate the tags to use the JQuery provided with CMSMS inside your templates.
The 1.10 version will need to go through a beta cycle when it is ready and we will be asking for testers around that time. Development is sporadic right now, (everybody seems soo busy) so our schedule may have to change a bit, and/or we'll drop features.
As usual, we HIGHLY DISCOURAGE and WILL NOT SUPPORT people using the svn stream directly, unless they are part of the development team. This is because the software is in a state of flux, and cannot be considered ready for production. And we just don't have the time to support people that just want to kick the tires.
We will keep you posted.
It's been two or three months since the latest stable release of CMSMS (v1.9.4.1) and all seems to be going relatively well on that front. So I thought I'd tell you about the efforts that are ongoing and our plans for the next great version of CMS Made Simple.
The CMSMS Dev team has been working on a version 1.10 hopefully for release in the late summer / early fall. Already a few things are done in the new release, and there is a long list of things on the list. Here are but a few of them.
- Memory Optimizations
- Clean up the module class (Get rid of the last of the long deprecated callback functions, and replace the smarty, db, and cms members with accessor methods)
- Introduce module lazy loading on the frontend. This will be an 'opt in' process for modules, and will not work initially for modules that handle routes, or a few other conditions, but for some modules this could be implemented providing for a significant reduction in memory requirements on many pages.
- General 'Under the Hood' Improvements
- Add more events to allow for a proper multi-language addon module
- Rewrite the config.php stuff to provide a sparse config.php file at the start, with just the minimum amount of stuff necessary to get started. Other variables, if not specified in the config.php file will be calculated dynamically. This should minimize config problems.
- Provide a seperate SSL admin path
- Cleanup of the Content Object (private/protected members/methods etc).
- Cleanup the $gCms class to do better take advantage of the autoloader and have less members....
- Cleanup the $gCms->modules public array. We'll probably make this an object of sorts as it needs to be really cleaned up for the possibility that a module may be installed in the database, but not exist in memory.
- Module Manager Optimizations
- Get rid of nuSOAP in the distribution and replace it with a generic rest interface.
- Memory optimizations for Module Manager when downloading or expanding packages.
- Better handling of dependencies when upgrading
- {cms_stylesheet} changes
- Change it to combine stylesheets into a single css file by default. unless there are stylesheets with mixed media types attached to the template.
- Improve support for SSL
- Admin Interface Changes
- We're hoping to provide an admin side search capability to search inside pages, GCB's, templates, stylesheets, etc. This will be handy for solving the 'where is this called' problems.
- We're planning on adding a new page to handle various admin tasks like clearing the cache, repairing database tables, doing table optimization, cleaning up content, etc.
- A preference for the default content type when adding new content
- A new (again) permission called 'Reorder Content' that will allow for people to have limited ability to re-order their own pages.
- We're planning on writing and slowly introducing a replacement to listcontent to get past our scalability and memory issues. We'll see how much time we have though.
- Salted MD5 Passwords (for the uber paranoid).
- Re-work of the Admin log to provide filtering, sorting, and better pagination, and automatic cleanup.
- General smarty Items
- A drop in replacement for the {html_date} plugin that will use jquery to provide a popup calendar.
- A review of all plugins to ensure that the assign parameter is available where it needs to be.
- A new plugin to automatically generate the tags to use the JQuery provided with CMSMS inside your templates.
The 1.10 version will need to go through a beta cycle when it is ready and we will be asking for testers around that time. Development is sporadic right now, (everybody seems soo busy) so our schedule may have to change a bit, and/or we'll drop features.
As usual, we HIGHLY DISCOURAGE and WILL NOT SUPPORT people using the svn stream directly, unless they are part of the development team. This is because the software is in a state of flux, and cannot be considered ready for production. And we just don't have the time to support people that just want to kick the tires.
We will keep you posted.