1.0 "Hawaii" Released!

Ted · **Posted:** Sun Sep 10, 2006 9:35 pm

Sent to the announcements list moments ago.

\$1:

1.0 is ready for mass consumption.

You can get the new release from here:

http://dev.cmsmadesimple.org/frs/downlo ... 1.0.tar.gz
http://dev.cmsmadesimple.org/frs/downlo ... le-1.0.zip

The MD5 sums for these files are:

5f029c32ac84a4ef57b4f1872945e638 cmsmadesimple-1.0.tar.gz
07d3eac27a96d959ef555a61c2850090 cmsmadesimple-1.0.zip

This is a major release. Updating from 0.13 is optional. There are database changes and backups are HIGHLY recommended. Also, not all modules are up to date with the 1.0 changes, so please tread lightly and backup often.

The ChangeLog follows below.

Bugs can be submitted to the bug tracker for the CMSMS core at:
http://dev.cmsmadesimple.org/tracker/?a ... unc=browse

Thanks,
The CMS Made Simple team

--------------------8-<-------cut-here---------8-<-----------------------

Version 1.0 "Hawaii" -- Sep 10 2006
-----------------

* Events

A workflow system. Events are generated either by the core, or by a module
and can be handled either by other modules, or by User Defined Tags. The
administrator can add, remove, or re-order any of the event handlers
for a particular event. This functionality allows site administrators to
add custom behavior and workflow to their system that have not been
coded directly into the core or into other third party modules.

For example, with a simple user defined Tag, it is now possible for
a news article to automatically be added whenever a file is uploaded
in the Uploads module.

* Search

A brand new search module has been written that allows indexing of content,
excluding certain words, and unlimited customization. It is possible for
third party module developers to write some code into their modules to
allow searching of module content.

* Module Manager

The module manager allows querying, and installing of modules hosted
on a remote server. The Module Manager allows an administrator to
see the help, and about information, the dependencies, and other
details of a module before downloading it.

* Module List Improvements

The Module list as been optimized and some new functionality added:
- Core modules can no longer be exported to XML
- Only installed third party modules can be exported to XML
- There is an option to completely remove all of the module files
after a module has been uninstalled (if sufficient permissions exist).
- A check is done for permissions to indicate that there may be a
problem removing the files.

* Improved Installer

The installer has been given some tweaks, and some additional checks
to hopefully ward off some of the more common installation issues, and
to ensure that most of the functionality of CMS will work properly
after installation.

* Simplified Default Stylesheets

The default stylesheets have been simplified and documented, so that
it is (hopefully) easier for somebody to start modifying their site
given the standard stylesheets

* Improved default templates and content

The default templates and content have been improved in appearance and
in content, and thoroughly documented.

* Improved content list

Content list has been given an overhaul:
- Active, Default, Collapse and Move buttons now work via AJAX calls
for faster response.
- A drag and drop reodering system
- Reordering boxes for the css/javascript impaired

* AJAX Content Preview

The preview has been moved to a tab and will update as soon as you click
on it.

* Admin interface improvements

The appearance of the admin interface has been improved significantly.
There are now help links in each module and in other core locations that
will link back to the wiki.

* New default layouts

tested with all major browsers (including Internet Explorer 7 beta 3)
Styles and templates now have comments so editing is easier
sample stylesheets for handheld devices and print

* Improved plugins

The image, cms_selflink, anchor, breadcrumbs, and other plugins have all
been improved, and other plugins added, such as "recently_updated"

* New System Modules

nuSOAP and CMSMailer are now included in the default install, since so
many modules rely on them for basic functionality.

* Upgraded smarty to 2.6.14

* Upgrade ADODB Lite to 1.20

CMSMS doesn't require that adodb or adodb lite be modified anymore. If you need a different
version, just download from their site and you're good to go.

*** IMPORTANT NOTE ***

Modules that use timestamps, or that use the RowCount() method in CMS 0.13 or
earlier, will need to be upgraded. This accounts for a large majority of modules and
hopefully new versions of most modules will be out by the final release.

* Some of the bigger bugs that were fixed

- Fixed a bug in the metadata tag where showbase would default to false, even when
it should be true
- Fixed a bug with displaying a few admin images
- Fixed most of the -- Add Me -- messages when using other languages besides the default
one for that module
- Fixed bug with IIS support
- Fixed bug with stylesheet display in postgres
- Fixed bug where content type changes wouldn't stick

Thanks to everyone! This is a momentous day for the dev team, that's for sure. Hopefully we've made software that everyone can use and enjoy using!

Note: Also, I can't stress it enough. Backup before upgrading! Not all modules are ready for 1.0 yet and you could be stuck having to downgrade back to 0.13 and ride out the module development changes. Please, please, please don't yell at us because an upgrade turned bad and you have no backup to go to. The dev team probably can't help you without charging a fee for the time spent fixing it.

Cheers! Onward and upward to 1.1!

Ted

Signex · **Posted:** Sun Sep 10, 2006 9:37 pm

great to hear !

stopsatgreen · **Posted:** Sun Sep 10, 2006 11:53 pm

Congratulations to all on their hard work!

However... a personal gripe:

I wish you had worked harder on improving the News module rather than, say, implementing Events; for me, and I suspect a number of other users, News is one of the key components of the CMS - yet there is no pagination, no decent archiving.

Yet something like Events has obviously received a lot of attention. For me, a workflow system this goes away from the Simple part of the CMS Made Simple title. I want a CMS that will let me manage my content before I want something that will manage a workflow.

Sorry if this sounds unduly negative; I genuinely like this software and, up until 0.13, was really happy with it. But the 1.0 betas suddenly introduced a whole bunch of complexity that I would have thought was a long way down the pipeline, at the expense of a simpler way to manage content.

MichaelK · **Posted:** Mon Sep 11, 2006 12:03 am

Great great work

Little thing I'll agry with stopsatgreen about the News module. But maybe version 1.1? Also with multilanguage?

:P

Keep up the good working man!!

calguy1000 · **Posted:** Mon Sep 11, 2006 12:24 am

Stopsatgreen:

Unfortunately with any product, you cannot make everybody happy all of the time... You can, however, make some of the people happy some of the time. This is, I think, what we've accomplished. Every user we talk to has different requirements, different dreams, and different "wishes" for CMS. We try to aim for the middle of all of those. However, no matter what we do, some people will undoubtedly express disappointment. There is no way to prevent it.

Even items such as "Pagination", and "Archiving" are functionalities that at the outset seem "easy", and "obvious". But I'm sure if we were to have implemented each of these functionalities in CMS 1.0, some people would be overjoyed and it would work perfect for them, and others would complain that we did it "completely wrong", and that it is "no good". It never fails.

1.0 has incorporated a massive restructuring and optimization for performance and memory usage. As well, numerous improvements to the admin interface (Module Manager, an improved module interface, and numerous new "core" modules to make things easer are just some of the improvements). as well, and improved installer, and Events. Also, on the frontend is a dramatically new default set of pages and templates, and a builtin search interface. Some changes have been done to News, and numerous other modules. I am not mentioning the hundreds of other improvements that have been made that you probably haven't noticed yet.

We have attempted to look at the most striking feature requests, and address what we saw as the most important bug fixes. We compromised those with the roadmap, and what time was available to implement them, along with the priorities of each of the development team members. We've spent hours in online meetings, and discussions, and even more hours in development, re-development, and testing.

Hundreds, if not thousands of hours of free time by dozens of people has gone into the 1.0 release. It has been a collaberative effort, and we've attempted to incorporate as many of the ideas and concerns of people as we can. Again, pleasing everybody isn't possible.

"Events" was spearheaded by me as a way to build flexibility into the system and to try to remove a barrier that was preventing us from adding even more flexibility into other modules. Many of the development team members, and other module developers have understood the concept and think about it enthusiastically. As well, it was seen as a foundation to many interesting things that could be done in the future. The new, standard Search module uses events to allow indexing of the content of other modules. The Uploads and News module currently takes advantage of this, and I am sure that more will follow.

The core package now sends events that can be handled by other addon modules to do various things. As well, numerous other modules send events that allow other developers to add functionality to their modules, or to bridge CMS into other applications. I don't view this endeavor as a wasted effort. An example of this is the NewsToCalendar module which bridges the News and Calendar modules respectively. I guess you just have no need for this type of stuff at the moment.

I think that the 1.0 change list, though it may not appear so at first glance, is considerable. 1.0 provides features for the end user, for the site developer, and for the php programmer/addon developer. It improves security and performance, and reduces memory requiremeents. 1.0 is in my oppinion, a good, well balanced achievement.

I think you'll warm up to it. Even if you didn't get everything on your "whish list".

stopsatgreen · **Posted:** Mon Sep 11, 2006 12:37 am

I didn't want to sound as if I was ungrateful; I do appreciate the work that has gone into improving memory usage and restructuring.

It's just that a key feature of a CMS is the way it handles news stories, and I think this is sorely lacking in CMSMS. I have a couple of sites using CMSMS already, and I appreciate the simplicity with which I set them up and can manage them; but with sites which have at least one news story per day, I find it frustrating that I can't easily navigate through the stories, and I'm pretty sure other users have the same experience.

While I'm sure Events is powerful, flexible and forward-looking, Simple it isn't.

Ted · **Posted:** Mon Sep 11, 2006 12:40 am

Keep in mind these 2 little bits as well...

- We now have a way that we can slipstream module releases through the module manager. I can release a new version of News tomorrow, and you'll easily have it in a minute or so. No need to update your site, etc.
- To be honest... where are the FR's in the News module project for those features? Unfortunately, I don't read every post on this forum anymore. I just don't have the time these days, so if it's mentioned in the forums, chances are that I didn't see it.

Enjoy!

calguy1000 · **Posted:** Mon Sep 11, 2006 2:22 am

stopsatgreen \stopsatgreen:

I didn't want to sound as if I was ungrateful; I do appreciate the work that has gone into improving memory usage and restructuring.

It's just that a key feature of a CMS is the way it handles news stories, and I think this is sorely lacking in CMSMS. I have a couple of sites using CMSMS already, and I appreciate the simplicity with which I set them up and can manage them; but with sites which have at least one news story per day, I find it frustrating that I can't easily navigate through the stories, and I'm pretty sure other users have the same experience.
[/quote[
Don't you mean that "A key feature of a CMS (to me) is the way it handles news stories". People developing a blog site, or an albums site, or a corporate site, or an intranet site may not have the same primary issues.... See the problem here.

\$1:

While I'm sure Events is powerful, flexible and forward-looking, Simple it isn't.

The events stuff, as a general rule doesn't have to be messed with by module admins that much. Especially at this point and time when there isn't many co-dependencies on things, and you don't have to worry about the order that events get handled in. Essentially, at this point in time, most site administrators probably won't have to do anything in the event admin, other than maybe look around and see what events (if any) are being handled. Though this may change later as more modules that send and/or handle events come onstream.

Dr.CSS · **Posted:** Mon Sep 11, 2006 2:36 am

I believe Archiving and pagination can be done to the News as is, it just depends on how you set up your pages.

I have a site with News/Blogs going back to April 2004 that you can access thru a drop down or thru the calendar which uses Events thru the News To Calendar module.

Pagination can be achieved by making pages that have the news tag...

{news category='news' number='10' start='1'}

{news category='news' number='10' start='11'}

{news category='news' number='10' start='22'}

{news category='news' number='10' start='33'}
.
put each one of those on a diff. page then use the self_link to point to the next news page, these pages can be set to not show in the menu but still be active.

Now the only other real complaint has been the url system for News as it gives all kinds of &=cntntid#returnlink&=#15 crazy 'looking' links in the address bar, but it seems most of that comes from the worry of how the search spiders find the content.

I've googled for stuff on my site and it found a news article that mentioned the keyword in my search when I clicked on it I was shown my page with the news article from the right side open in the middle, as if some one came to my site and clicked on the more link to read the details.

Summary: when a spider crawls your site it opens all links be they in the menu or in the page if they have content it's read and cataloged and ranked according to how many times the 'word(s)' shows up in your site.

I don't believe the keywords in the make all that much diff., I've seen pages with 80 or more and they didn't show up on a google search, it was a site that sold t shirts and every page had t shirt on it and all the keywords in the had something to do with t shirts, after 25 pages into google I stopped looking for his site.

just my 0.02$usd

newclear · **Posted:** Mon Sep 11, 2006 11:54 am

WOW Great news here.

The events rocks the way of developing sites. They can be really usefull for a developer to make a complex site to have well integrated modules into the core.

Thanks to the team.

cyberman · **Posted:** Mon Sep 11, 2006 12:01 pm

Thanks a lot for your work but can't found this feature from roadmap ::)

\$1:

Dropdown for internal link when using Link as Content Type

Piratos · **Posted:** Mon Sep 11, 2006 1:43 pm

You can change this 2 x in install.php, 1 x upgrade.php, 1 x class.global.inc.php

... = ADONewConnection($_POST['dbms'], 'pear:date:extend:transaction');

to this

... = ADONewConnection($_POST['dbms'], 'pear:date:extend');

This gives you 10 - 12 kb more memory so the author of adodb litet describe it in his handbook. Transactions are never in use with cmsms.
-----------------------------------------------------------------------------------------------------

The time shown as http://f.byethost33.com/viewtopic.php?p=267#267

and put it in the folder plugins.

lemkepf · **Posted:** Mon Sep 11, 2006 2:51 pm

Is it me, or does the preview not show multiple content areas? it seems that the preview is only showing the main content area. Displaying the rendered page is fine, it's just the preview not working.

I'm setting in the template the second block like this:

\$1:

{content block='left_block'}

Ted · **Posted:** Mon Sep 11, 2006 2:53 pm

Doh! We'll get it in a future release... to be honest, I completely forgot about that one.

cyberman \cyberman:

Thanks a lot for your work but can't found this feature from roadmap ::)

\$1:

Dropdown for internal link when using Link as Content Type

Ted · **Posted:** Mon Sep 11, 2006 2:55 pm

Piratos \Piratos:

You can change this 2 x in install.php, 1 x upgrade.php, 1 x class.global.inc.php

... = ADONewConnection($_POST['dbms'], 'pear:date:extend:transaction');

to this

... = ADONewConnection($_POST['dbms'], 'pear:date:extend');

This gives you 10 - 12 kb more memory so the author of adodb litet describe it in his handbook. Transactions are never in use with cmsms.
-----------------------------------------------------------------------------------------------------

The time shown as http://f.byethost33.com/viewtopic.php?p=267#267

and put it in the folder plugins.

The stylesheet change is a good idea, however, it was a bit controversial to put in at the last minute, since it changes a lot of how the system works. In theory, stylesheet's should be cached by the browser and it shouldn't have to actually generate that stuff for EVERY page. Of course, that's all theory.

As for the transaction change, I just didn't get a chance to totally test it. There was a reason that I turned that on to begin with, though it escapes me now. If it's working fine, then I can turn it off in the next release. Just trying not to break anything before such a major release...

1.0 "Hawaii" Released!

Share On:

Share On:

Share On:

Share On:

Share On:

Share On:

Share On:

Share On:

Share On:

Share On:

Share On:

Share On:

Share On:

Share On:

Share On:

Who is online