Latest

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.

gpEasy 1.7 is now available. The latest release of gpEasy represents months of development and testing from the growing community of gpEasy users. Find out why gpEasy is right for you, download now: http://www.gpeasy.com/Download

New Features Since 1.6

• Missing link management
• Link auto-completion in CKEditor
• Improved multi-site managment
• More flexibly drag 'n drop layout control
• Revamped user permissions
• Better SEO and permalinks
• Integrated Updating
• And More...

About gpEasy

A few days ago, I read Mary Jo Foley's article titled Microsoft: Our strategy with Silverlight has shifted. According to an interview with the President of the Server and Tools Division at Microsoft, the company will be shifting support for Silverlight away from the PC and Mac desktop and toward the phone market.

So what’s a developer to make of Microsoft’s messaging (or lack thereof) about Silverlight at its premiere developer conference?

I asked Bob Muglia, the Microsoft President in charge of the company’s server and tools business, that very question and got what I consider to be the clearest answer yet about how Microsoft is evolving its Silverlight strategy.

“Silverlight is our development platform for Windows Phone,” he said. Silverlight also has some “sweet spots” in media and line-of-business applications, he said.

But when it comes to touting Silverlight as Microsoft’s vehicle for delivering a cross-platform runtime, “our strategy has shifted,” Muglia told me.

Microsoft plans to be using HTML 5 to replace the functions currently being provided by Silverlight 5.

It is not the point of this post to debate the merits of HTML 5, Silverlight and even Flash. What is my point though, is that Microsoft appears to me to be desperate. Desperate to come up with a strategic plan that will carry them beyond the day of Windows PCs. Microsoft is desperate to become innovative for the sake of innovation that they're really confusing a lot of their developers. If only after a few years of support, Microsoft is shifting focus of it's Silverlight platform...what potential developer in his or her right mind would support another future Microsoft endeavor? Just take a look at the comments to Bob Muglia's blog post discussing this topic and I think you'll see my point.

Why Web Content Management Systems are the way of the future, making traditional web development a thing of the past

The Web is an exciting place. With excitement come innate complexity and an overwhelming abundance of choices when defining how to take your website into the future.  Ask web evangelists of today versus evangelists of say 5 years ago, and they will highlight the importance of device support, marketing tools, analytics and focusing on creating great content that will stand the test of time.

Recently, companies like Google and Apple have prompted questions to the public, such as, “Why are we still building things like we did 30 years ago?” These types of provocative questions are spawning answers in the form of new tools, such as the iPhone 4 and the upcoming wave of Google WebOS notebooks. Ask yourself these questions:

• Would you still create artwork using MS Paint?
• Would you still write articles using Notepad?
• Would you still use Netscape as an Internet Browser?

Then why are you still developing websites in the traditional approach?

Let me start by defining what I mean by “traditional”. Traditional Web Development refers to the act of taking a Web Framework such as HTML, ASP.net, PHP and building a website from the ground, up. This includes everything from setting up Database connections, setting up Database Tables, creating separate files for your Contact Us and Products page, the list goes on. Most web agencies that I consult with have control libraries that make this process less tedious and time consuming but this is not addressing the fundamental issue, being, this is a traditional methodology for building web sites. Weddings should be traditional; your grandmother’s brownie recipe should be traditional. Your web presence should be innovative.