Drupal

How to Upgrade from Drupal 5 to Drupal 6 - Steps 3 and 4: Actual Upgrade and Testing

latest drupal release graphicToday I finish up the series of articles about upgrading from Drupal 5 to Drupal 6. Earlier posts in the series included: Finally Time to Upgrade to Drupal 6, How to upgrade Drupal 5 to Drupal 6 - Step 1: Planning and Step 2: Getting Drupal 5 Upgrade Ready

The first few posts were all about getting you to the stage where you can actually go ahead and upgrade your Drupal installation. In 25 words or less, do rigorous planning and take several actions to prepare your Drupal 5 site for upgrade before upgrading to Drupal 6.

In this post I finally tackle the actual Drupal upgrade process and include some final thoughts on testing your success.

January 15th 2009 12PM
By: andre

 

How to Upgrade from Drupal 5 to Drupal 6 - Step 2: Getting Drupal 5 Upgrade Ready

Last week I started a series of posts about upgrading to Drupal 6. Starting with Finally Time to Upgrade to Drupal 6 followed by How to upgrade Drupal 5 to Drupal 6 - Step 1: Planning.

If you are planning an upgrade to Drupal 6, you might want to read those posts before reading this one. In the last post I suggested making an upgrade plan and doing some legwork before you jumped into the act of upgrading. Part of that plan is to prepare your Drupal 5 site for upgrade. In other words, do everything you have to do to your Drupal 5 site ready before you finally start moving it to Drupal 6. Depending on your site and how up to date you like to keep it, this may be at least as time consuming as the actual move from Drupal 5 to Drupal 6.

January 12th 2009 2AM
By: andre

 

How to Upgrade from Drupal 5 to Drupal 6 - Step 1: Planning

mindmap of drupal 5 upgrade Yesterday I posted an article about why you should upgrade to Drupal 6. Today I'm writing the first of a series of posts on how to upgrade, in an effort to make sure you have no excuses not to.

When you download Drupal it comes with an 79 line document called UPGRADE.txt. UPGRADE.txt is essential reading when going through an upgrade. So important in fact that you should go and read it now and come back.

Done? Very good. As you can see, the document only covers the mechanics of an upgrade. Important information indeed, but it doesn't include any of the dozens of things you may need to do even before you get started. You should not open the document and start executing the steps without planning ahead. If you jump right in you may get to step 9 (Re-install contributed modules) and find that there isn't an upgrade path for one of the contributed modules you use.

So as you may have guessed, the first thing you should do is start formulating your plan. The plan I created for the upgrade of this site had 4 basic phases:

  1. The "before you do anything" phase which includes:
    • module inventory
    • research module upgrades
    • documenting the plan
  2. The "getting Drupal 5 'upgrade ready'" phase. i.e. Actually doing things to your Drupal 5 site before you are ready to start the upgrade
  3. The "actually upgrading to Drupal 6" phase
  4. The "testing and deployment" phase

Today, I'm only covering the first phase.

January 9th 2009 12AM
By: andre

 

Finally Time to Upgrade to Drupal 6

Go Drupal 6It's a week into the new year, and many of us are nearly finished breaking the last of our resolutions. However, there is one resolution you should not break if you're still running a Drupal 5 site. You've put it off long enough and it is finally time to upgrade to Drupal 6. If you're not convinced I'm going to tell you why you should.

First, a bit of background and a brief look to the future. It used to be that the world could expect a new Drupal release every 12 months or so. Drupal 5.0 was released about a year after Drupal 4.7. Drupal 6.0 was released February 13, 2008, 13 months after Drupal 5. And, you may have noticed that it is now January 2009 so you might expect that there is a Drupal 7 release on the horizon.

I wouldn't blame you for thinking this, but a funny thing happened on the way to a Drupal 7 release.

January 8th 2009 12AM
By: andre

 

Drupal json_server.module to get some love

A while back I was looking to get someone a bit more involved in services module development to take a look at a patch I'd made for the json_server module. (Provide support for binary/file field handling in case you're interested and want to comment)

In doing so I got in touch with dmitrig01 on IRC and after a bit of chatting he said he'd love someone on board actively maintaining the json_server module. While I insisted that I am the poster boy for worst module maintainer hall of fame he added me as maintainer anyway after I helped out with some documentation. http://drupal.org/node/239796

That was in September. So in worst module maintainer fashion, I am now finally getting around to cleaning out the issue queue.

So in the near future you can expect:

  1. Support for services that expect file uploads
  2. Support for GET requests
  3. 5.x 1.1 and 6.x 1.0 Beta Releases
October 29th 2008 12AM
By: andre
File Under:

 

Drupal core getting slower?

Khalid over at 2bits.com has been doing some benchmarking recently.

The results seem to indicate that Drupal core is getting slower.

You would think by the comments on the 2bits site that Khalid had committed heresy by reporting his results. But, before we shoot the messenger lets clear a few things up.

  1. The purpose of a benchmark is to provide a baseline for the purposes of comparison. A methodology is chosen/stated, tests are done and results are collected and reported. Regardless of what those conclusions are, the 'benchmark' still stands unless there is a flaw in the methodology or method of reporting. A benchmark is usually considered more valid if it is independently reproducible. People can either accept this benchmark as is or attempt to reproduce them to validate or disprove.
  2. Benchmarks are not universal. They only report what was tested.
  3. The reader is left to draw their own conclusions.
October 28th 2008 2AM
By: andre
File Under:

 

Official Drupal Camp Logo?


Drupal Camp Toronto 2008 Logo

Is it official? Is this the new "official" Drupal Camp Logo. Well, no, nothing's official when it comes to druplicon, but it certainly seems to be catching on. Its now been spotted in Toronto, Montreal and L.A.

Of course it was in Toronto first and all thanks to the wonderful folks at Substance Communications who designed the logo and have been kind sponsors to Drupal Camp Toronto for two years running.

Back in 2007 I wrote:

Patricia and Crispin of Substance are looking into sharing the artwork with the Drupal community. I'm sure such a move would be a hit in Drupal land.

Looks like its become a hit. Let em know you love it.

p.s.

October 8th 2008 2AM
By: andre
File Under:

 

Services API Module - Future of Services for Drupal

Earlier this week Dries Buytaert wrote about CMIS a proposed standard to enable interoperability among content management systems. And in that article he said he wants to "push harder" for Atom as a default output format for Drupal so that Drupal be CMIS compatible in the future.

At Drupalcon Szeged Peter Wolanin (Dries colleague from Acquia) presented a talk "Page serving and rendering (XHTML/XML/JSON, etc.) - now and Drupal 7" in which he talked about the different ways Drupal may go about rendering output in formats other than (X)HTML.

September 23rd 2008 11PM
By: andre

 

Drupal Redesign is Much More than a Wordmark

Its been about 24 hours since Mark Boulton bravely posted some preliminary thoughts and sketches of a new Drupal wordmark. 60+ comments have been left on that post (and counting). Some of what has been said is useful to the discourse, others... perhaps not so much. I think the conversation can be boiled down to:

  • This is a work in progress
  • The initial concept is too 'Bauhausy' (i.e. people aren't crazy about the Bauhaus like word forms)
  • This will not be a design by committee process - the Designer will have the final word
  • Other options will be explored based on the feedback
  • Maybe it was too early to solicit feedback on the design

Luckily there is more to this redesign than just a wordmark

September 15th 2008 9PM
By: andre

 

A new wordmark for Drupal

Just the other day I wrote about the rebranding of Drupal. In that post I had guessed that there is a good chance that Drupal would be getting a new 'logo'. It turns out it will be a new 'wordmark'.

early sketch of new drupal wordmark
Over at markboultondesign.com, Mark has posted some sketches and thoughts on the process he's taking to come up with the new wordmark.

The post has only been up for a few hours, but there are already over a dozen comments. Everyone is going to have an opinion about the design, but Mark points out that ultimately the wordmark will have to be viewed in the context of the overall redesign of drupal.org. Perhaps people should reserve judgment until the entire rebranding is complete.

Bah - but even I can't resist commenting. I can’t help but feeling the sketch looks “dated”. That’s simply my initial gut reaction to the digital sketch - and I’m not sure why my gut is telling me that... but that's the first word that came to my mind.

September 15th 2008 2AM
By: andre
File Under:

 
Syndicate content