For end-users, the most obvious new feature is our ability to now protect forms with CAPTCHAs only. Previously, all forms enabled for Mollom were protected by Mollom's text analysis algorithms, with CAPTCHA challenges used as backup. Though that is still the default option, you may set individual forms to use a "CAPTCHA only" form of protection. Data on forms protected with "CAPTCHA only" is not sent for analysis, and the forms always present a remotely-hosted CAPTCHA challenge. With these changes, the Mollom module for Drupal can now act as a replacement to the CAPTCHA module. For a screenshot of the configuration page, please see the Drupal module tutorial at http://mollom.com/tutorials/drupal.
The main challenge for this project was to build from scratch an online store that originally was running on OsCommerce. Our proposal to the client was to use Drupal for managing his online shop, which would mean a big quality improve, as we included some social functionalities to the project.
Year (2004) after year (2005), we have had a tradition on Drupal.org to look back at the last year and make predictions for the year ahead. Year (2006) after year (2007) we are amazed at how wrong we were trying to predict the future and how right we are making our own great future. Year after year, and 2008 was no exception. Take a look at the predictions for 2008 to see who was wrong and who was right, and post a comment in this thread to predict what will happen in the Drupal community for 2009.
As promised, we're organizing a series of sprints to help push the drupal.org redesign closer to completion. The drupal.org redesign is a massive project, and, when implemented, will be an important milestone for our community.
The Drupal.org website was originally launched in 2001 and last redesigned in 2005; over time we've simply outgrown it. The community has made it clear that new features were needed, and the Drupal Association has made the Drupal.org redesign one of its top priorities. By improving the navigation, the design and the organization of the site, we hope to further expand Drupal's reach and to provide us better tools to communicate and collaborate.
Most of you are likely familiar with the open redesign process that has occurred in the redesign group with the help from Mark Boulton, Leisa Reichelt and many other people in our community. Now it is time for us, the community, to take these designs and to implement them.
To that end, we're organizing a number of redesign-specific sprints over the next two months, each concentrating on a specific area of the process. Even though we won't be able to completely upgrade the entire site during these sprints, we will make valuable progress and form plans that will allow us to move forward to completion. Many Drupal contributors have already agreed to participate, and a number of companies and individuals have come forward to donate time, resources and money. I've included a Chip-in widget on this page, and I encourage you to contribute as well. Read on for the details.
All of you knows who is Dries Buytaert.
I'm reading his blog to know more about Drupal's future, sites of well-known companies and news.
But not all who is living in Russia and Ukraine knows english.
So I decided to start a blog where posted translated to russian language posts from Dries Buytaert's blog.
This blog is called "Dries Buytaert speaks russian about Drupal, Mollom, Acquia, fotos and future".
Happy to announce the provision of a new wizard in the existing NetBeans plugin to support development of Drupal based websites. The wizard assists developers to create a new Drupal Theme. On providing the new Theme name, the wizard auto-generates the mandatory '.info' file along with template code under 'sites/all/themes/
/' location. Now, the developer can continue with Theme development either by inheriting from an existing theme or creating an all-together new theme using a suitable theme engine.