Latest

The XOOPS Development Team is pleased to announce that a new stable version of the Top 5 Finalist of 2010 Packt Open Source CMS - XOOPS 2.5.0 Final is available for download.

The XOOPS 2.5.0 release is a major redesign of the System Module which has been AJAX-ed with jQuery. Some of the new features are truly amazing, like the visual placement of blocks, and we're sure that the System Admins will love them

Other major improvements/additions include:

• Help System for Admin and modules
• MySQL Dump in Maintenance
• New Redirect messaging
• Column sorting in tables
• Smarty plugin for icon pack
• Smarty plugin for breadcrumb navigation
• jQuery plugins for display popup or manage drag & drop
• File Manager (Plugin)
• Maintenance with Cache Clean-up, and Tables Maintenance
• Visual module ordering with drag & drop
• Visual block placement with drag & drop
• Refactor all PHP code for use XOOPS API
• Use template in the same way that front user, admin side for module can call a main template define in xoops_version.php
• Allow override of template in admin theme like frontend if we set template in ADMIN_THEME
• Manage editor for blocks, comments and for all module if module developper want to use it activate or deactivate system section
• Choose number of line for admin section
• Display or hide tips

For more info and download please click here

A couple weeks ago, one of Magnolia's press people gave me a sneak preview of a case study for how the Magnolia CMS was being used by one of their partners in redesigning the recruitment website of the United States Navy, Navy.com. I was given the opportunity to write a story about the redesign before the case study was published online. It was a great opportunity I was being offered but I just wasn't able to find the time in my schedule to write the story.

So it is only fitting, that I at least talk about this case study on the Navy's use of the Magnolia content management system on Veteran's Day. The recent Navy.com was redesigned to be more interactive, more responsive to user needs, and better integrated with social media communities nurtured by the U.S. Navy. Additionally, the site needed to support the Navy’s recently launched new brand, “America’s Navy. A Global Force For Good™”.

As mentioned in the case study, integrators spent six months researching and evaluating open source content management systems. Their evaluation was platform-agnostic; they considered Java, PHP and Python solutions in their research. Key evaluation criteria were:

• Easy to learn and easy to use for content authors
• Short learning curve for designers and developers
• Easy to integrate with custom business objects
• Compliant with Web standards and accessibility guidelines
• Scalable and robust

Magnolia CMS Enterprise Edition, together with the Magnolia STK and Blossom module, met all of these criteria. Navy.com is now running on Magnolia CMS Enterprise Edition with Magnolia STK and Blossom, Magnolia's instant Spring integration. The infrastructure supporting this site includes an Apache Web Server, Tomcat Application Server, MySQL Database, and Red Hat Enterprise Linux.

If you have ever worked for a large organization, you should easily relate to this Dilbert cartoon. As the IT guy trying to make everyone happy at work, I've spent the last year making sure everyone that needs two monitors gets two monitors. It's not an easy task in an era of tight budgets and cycle replacements but we're getting there...

The Tiki Community is proud to announce the release of Tiki 6. This version of Tiki Wiki CMS Groupware represents hundreds of hours of work by dozens of members of the Tiki Community. Nearly 50 developers contributed more than 1,500 code changes for this release.

In addition to countless tweaks and updates, Tiki 6 includes several new, key features:

• Extensive re-work and improvements to the Tiki blog, comments, spreadsheets and tracker features
• Batch functions (via cron jobs)
• Introduction of re-Captcha
• Expanded support of ccLite community currencies
• Integration with social networks such as Facebook
• Improved WYSIWYG support

Tiki 6 has been designated as the Long Term Support (LTS) version, replacing Tiki 3 LTS. Tiki 3 will reach end of life when Tiki 7.1 will be released (planned for April 2011). See the Project Roadmap for details.

To download Tiki, see https://tiki.org/download. Refer to the Tiki 6 release notes for additional information.

Earlier this week, the CMSMS Development team released another milestone version of CMS Made Simple. CMS Made Simple 1.9 is a feature version with focus on flexibility and maintaining ease of use.

Significant additions and improvements in CMSMS 1.9 include:

Slowly but surely, CMSReport.com has turned into a nice side business for me. The problem is that this site has grown to a point that it demands more of my time than I can currently offer it. The future of CMS Report is now sitting at crossroad. I plan to be spending the next few months deciding where this site should go from here.

Some of the options I am considering for this site include:

Like most website administrators, I have a long history of fighting spammers and protecting my sites from unwanted content. Over the years I've used a lot of tools and services to block spam from reaching the pages of my sites. In recent years, the service I've relied on most heavily is Mollom.  Mollom is a web service that helps you identify content quality and, more importantly, helps you stop spam on your blog, social network or community website

Overall I've been very happy with the spam filterering Mollom provides for my sites. However, occasionally Mollom can be too aggressive and remove legitimate story and comment submissions. And when I say "remove" I most definately intend to use the word in the literal way. You see, up to now, Mollom had an "all or none" approach to rejecting or accepting spam. When your stories or comments were rejected, the content submission was simply discarded without review by a human.

If you've ever submitted good clean content to CMSReport.com or another site only to only have it identified and discarded as spam, you have every right to be upset with spam filters. Over the past couple months, I've had a number of people upset that the spam filtering CMS Report has been using rejected their story submission. This may not be all the fault of Mollom either as I was also using the Bad Behavior module too. My apologies to everyone that has gone through this experience when they've submitted legitimate comments and stories to this site. Unfortunately, without spam filtering the content on this site would not be good to view. Spam filtering is a necessary part of maintaining a site open to the public.

Luckily, there has been some improvements in the Mollom for Drupal module that should keep your posts and comments from getting discarded while continuing to protect this site from spam. The module has now been improved to to retain spam comments as unpublished posts in a site's moderation queue. So we're giving the new module a try. I won't promise that your content will not be identified as spam, but I do promise you that every intent is being made to review your comments and stories for publication.

We are very pleased to present you X3, the new Xoops Engine for the next generation of XOOPS powered web application development.

This new Xoops Engine was long time in coming. During that time, we went through different phases of trials and errors, but we believe that we finally have the best combination of features and technologies to strategically position XOOPS as one of the top Web Application Platform solutions.

The new Xoops Engine has been re-designed from the ground up to take advantages of third-party frameworks like Zend Framework and Smarty 3.

Why did we rewrite XOOPS?

XOOPS is one of the most successful Open Source CMS and portal solutions, constantly placing in top places in various competitions, and receiving various awards. But it is showing signs of aging, that would require major rewrites of the Core.

In order to keep us focused on creating a flexible and extensible development engine for developers and a high performance application platform for end users, the development team has decided to use industry-standard frameworks. By doing so, we can focus our limited resources on aspects that make XOOPS unique and special, while leaving standard functionality to be addressed by off-the-shelf frameworks. This way we can take advantage of latest internet developments already included in those frameworks - it's like getting suddenly a whole new team of some of the best and brightest PHP and RIA programmers joining XOOPS!

After much research, we've selected a couple of frameworks at this stage:

PHP: Zend Framework
Template: Smarty 3
JavaScript: jQuery

Meanwhile the multi-engine mechanism of the Xoops Engine will ensure the possibility of adopting other excellent frameworks in the future, like Yii Framework, Dojo Toolkit, etc.