Posts tagged "release"

Drupal 7.0 Alpha 4 - What is to be expected of the upcoming release

This release includes many critical bug fixes and other improvements, including:

  • Color module now usable by themes other than Garland.
  • Usability improvements including re-weightable roles and saner Forum module defaults.
  • A variety of optimizations made to data import-related functions to make migrations faster.
  • Lots of previously missing documentation for hooks has now been documented. Hooray!
  • Increased test coverage, particularly core Tokens.
  • Lots of smaller bug fixes, security patches, and improvements.
  • critical bug: enforce e-mail verification with OpenID auto-registration.
  • Upgrade jQuery BBQ library to 1.2.1.
  • Added support to color.module for flexible color schemes and gradients, and removed hard-coded assumptions about Garland.

Drupal 7.0 Alpha 4 is a popular system for publishing news or called. CMS (Content Management Systems) systems. With its help you can easily publish and manage news, blogs, pictures, articles and more. It has also built a forum and opportunity to create a catalog for download.

Drupal 7.0 is open source platform and management system for content that serves to build dynamic web sites offering a wide range of features and services such as administering users, publishing, opportunity for discussion, news gathering, metadata functionality, using controlled vocabularies and XML publishing targets sharing agreement.

It  is equipped with a powerful set of features and settings. Drupal 7.0 Alpha 4 can support a wide range of web projects, from the personal to the wider community sites.

The standard release of Drupal, known as Drupal core, contains basic features common to most CMSs. These include the ability to register and maintain individual user accounts within a flexible and rich permission / privilege system, create and manage menus, RSS-feeds, customize page layout, perform logging, and administer the system. As installed, Drupal provides options to create a classic brochureware website, a single- or multi-user blog, an Internet forum, or a community website providing for user-generated content.

 

History

Originally written by Dries Buytaert as a message board, Drupal became an open source project in 2001. Drupal is an English rendering of the Dutch word “druppel”, which means “drop” (as in “a water droplet”). The name was taken from the now-defunct Drop.org website, whose code slowly evolved into Drupal. Buytaert wanted to call the site “dorp” (Dutch for “village”) for its community aspects, but made a typo when checking the domain name and thought it sounded better.

A large community now helps develop Drupal, and Drupal's popularity is growing rapidly. From May 2007 to April 2008, Drupal was downloaded from the Drupal.org website more than 1.4 million times, an increase of approximately 125% from the previous year.

As of April 2009, over 70 well-known brand names and not-for-profit organizations use Drupal. Drupal has also won several Packt Open Source CMS Awards and three times (in a row) won the Webware 100.

Drupal 6.16, released in March 2010, is the latest release. On March 5, 2009, Dries Buytaert announced a code freeze for Drupal 7 for September 1, 2009. The latest test version, DRUPAL-7-0-ALPHA-2, was released on February 23, 2010. There is no date announced yet for the final release of Drupal

Joomla Upgrade 1.5.17 (formerly known as 1.5.16)

23 April 2010 joomla.org released the new version 1.5.16 - almost 5 months after the release of 1.5.15 - although the .15 version had no major security issues, there are some moderate security concerns:

  • If a user entered a URL with a negative query limit or offset, a PHP notice would display revealing information about the system.
  • The migration script in the Joomla! installer does not check the file type being uploaded. If the installation application is present, an attacker could use it to upload malicious files to a server. (It is NEVER recommended to leave the installer script on a live server)
  • Session id doesn't get modified when user logs in.  A remote site may be able to forward a visitor to the Joomla! site and set a specific cookie.  If the user then logs in, the remote site can use that cookie to authenticate as that user.
  • When a user requests a password reset, the reset tokens were stored in plain text in the database. While this is not a vulnerability in itself, it allows user accounts to be compromised if there is an extension on the site with an SQL injection vulnerability.

There are also some minor fixes in the core components of joomla, mainly:

  • contact
  • newsfeeds
  • media


Unfortunately there were at least three new bugs introduced with this new version, so 4 days later there was a new release 1.5.17 with these fixes:

  • Fixed problem logging in when Session Handler is set to None
  • Fixed error message when running Joomla! in a PHP version prior to version 5.2
  • Reverted change to JFolder::makesafe method that introduced a bug


There are a few issues you have to have to take in account when updating to 1.5.17 :

  • If you used an early version of the upgrade files for 1.5.16 (not the full release) you may have incorrect file permissions of 775 instead of 664 for your files. This was do to an error in the automatic packaging of those files.


How to upgrade Joomla ?

  1. Download the needed patch file (according to the version you want to upgrade)
  2. Backup your site (use Akeeba Backup or Backup from Hosting Cpanel)
  3. Unpack the patch file
  4. Overwrite all files on your FTP
  5. Check that your website is working correctly



Keep in mind not to overwrite the configuration.php file (it is never supplied in the package, the sample configuration is named configuration.php-dist)

Our recommendation: Upgrade sometimes in the near future, but don't rush into it. If your website is stable and you're running 1.5.15 - you should be fine for a while. Test an upgrade first on a less important website you have, see how it plays out.

Drupal 7.0 Alpha 2 has been released

Our first Drupal 7 alpha version was released just over a month ago. Today, we're proud to announce the release of the second alpha version of Drupal 7.x for your further testing and feedback. The first alpha announcement provided a comprehensive list of improvements made since Drupal 6.x, so in this announcement we'll concentrate on how you can help ensure that Drupal 7 is released as soon as possible and is as rock solid as the previous Drupal releases that you've grown to love!

The most notable change for developers is moving $form['#field'] to $form_state. This makes field forms more resilient to form_alters and debugging became a lot less tedious. Comment body became a field and new fields can be added to comments through the field UI module. And congratulations to the docs team and associated helpers for their outstanding work in enhancing and correcting lots of API documentation this release.

We've also fixed a number of issues since the previous alpha, most importantly one that caused all files to be deleted after six hours.

You can download from the announcement or Drupal.org