Drupal quickies, February 2005

Another round of Drupal quickies for those who don't have the time to keep on top of all the recent happenings in Drupal land.

PHP block examples

In this thread one can post working PHP code to be put in a block. You can copy the code in a new custom block on your Drupal site. Note that this code is "AS IS" and might not work on all versions/platvorms and isn't up to the quality of the Drupal core code itself.

Drupal.org: tracking projects and contributors

Over the past weeks I've been working on extending the project module and CVS module. The former is responsible for managing projects on drupal.org while the latter lets us track development. As of a few minutes ago, the improvements went live so read on for an overview of what changed.

Sites that have been under the slashdot effect

Just a thread to show what sites have been under extreme load from for example slashdot.

For example, on February 4th, 2005 Wikinerds Portal, a Drupal site running an article on GNU/HURD got hit rather hard.

If you know a Drupal site that has been /.-ed or better, if your Drupal site has been /.-ed and you want to share your experience, post it here.

Nautis project

After using XOOPS for the past year and using Mambo for another site, I discovered Drupal via the urlgreyhot.com site. I have a few sites, but I decided to pilot Drupal on my personal web site, Nautis Project. My day job is management consulting (IT Strategy and Knowledge Management) - so I work with information architects quite a bit. I'm impressed by Drupal's taxonomy core. This system seems to have been built correctly from the ground up. Some of the most sophisticated content management systems out there (Interwoven, Vignette, Documentum) have still not mastered this idea very well.

Code freeze in preparation of Drupal 4.6.0

In preparation of the Drupal 4.6.0 release, development of Drupal core will be frozen on February 1th. During the initial stage of the code freeze, documentation updates, usability improvements and performance improvements will be accepted. New functionality, on the other hand, will not be accepted unless deemed important. Thus, as of February 1th, the focus is to strengthen the code base's performance, usability and stability. As we progress, focus will shift towards stability and near the end of the code freeze, only bug fixes will be allowed, until no release critical bugs are left.

Pages

Subscribe with RSS Subscribe to Drupal.org RSS