Thursday, January 6, 2011

Drupal 7 vs Drupal 6

Drupal 7 Alpha 1 has just been released. Although it's not the definite version, Alpha means that it is stable enough to be tested by the public. And since I'm the public, I downloaded, installed and looked at Drupal 7. These are my first impressions, together with a couple of screenshots.

The download and the installation of the files is very similar as with Drupal 6. The same directories (sites, modules, themes,...) appear, you upload them with an ftp-client, you have to make a settings.php-file and a database. But a quick look into the directories themes and modules reveals some changes in the core already: 7 more modules, and the themes Stark and Seven.

Although I'm a big fan of Drupal, I regret that the basic installation (and upgrade), although logic, still requires (too much) knowledge about file-transfers, mysql, apache-servers, 7-Zip etc. But there is some good news about this release here: once Drupal is running, it's very easy to install new themes and modules (see further).

Installation of Drupal 7
When you start the installation of Drupal itself, you see the look of the new administration-theme: gray, black, white and a touch of blue - simple. The installation is very similar to Drupal 6, the differences are in the installation-profile (standard or minimal) and the choice in database-type (mySQL or SQLite).
The welcome-screen

Ah... Garland! The good-old Drupal-theme. With the big difference that Garland became a lot more flexible than before, and that Seven became the default administration-theme. The original Drupal 6-text has been moved to the help-section where it belongs, and people get the simple message that No front page content has been created yet. A good thing, 20% of the searches pointing to my website involves how to get rid of the welcome-page. People know now. By putting Add new content so prominently it shows what it is (mostly), a Content Management System. But I should replace Change the default front page with help with Drupal, since no content has been created.

The big changes are the 2 menu-bars at the top. The black one is quite similar to the one produced by the Administration-menu module and the gray menu-bar is for shortcuts, a place to put links to the tasks you perform the most.

The administration-bar


Gone are the confusing Content management, Site building, User management and Site configuration. Instead a much more logical structure. It didn't take me more than one hour to adapt and for the record, I used half of that time to find content-types; it's not under Content, as I expected, but under Structure, just like Blocks and Taxonomy. But in the end, I liked what I saw.

Completely new is Dashboard, a place where you can drag and drop the different blocks, and see them without the necessity to put them on the site itself. It's a great place to test them out. You don't need to assign a user-role and to put them in a region. Just drag them into Dashboard.

Content: still the (artificial) difference between a Page and a Story. Instead it's called Article and Basic page now. I'm sure that I'll get searches like what is the difference between Article and Basic page. I understand the idea behind it, but it's not really necessary for me. What I also miss is an integrated text-editor, but ok, an extra module will do the trick... Great is that you can add and manage different kind of fields to the content, like you did with CCK. Fields can be added to users & taxonomy too.

Structure is about Blocks, Menus, Content-types and Taxonomy, Appearance is the new word for Themes. Several new functions extend the theme 'Garland': it's possible to apply different colors, for example, and to choose between a fixed or flexible lay-out.

Users became People (nice). Really great is the creation of another role, the Administrator. Clever! The 1st-user (the god-role) is not necessarily the administrator of a site (the site can be created by the 1st-user for somebody else).

Something else. Think about what you have to do to add new modules in D6.

1. Find, Download them from drupal.org and Unzip
2. Upload the unzipped file to your site.
3. Administer>>Site building>>Modules, and enable
4. Administer>>User management>>Permissions and set the permissions
5. Administer>>Site configuration>>by Module and configure the module. and sometimes
6. Help

That's all over now, in D7 everything is located under Modules. Above the list a new link: Install new module. That brings you to this screen


Beautiful!!! Download, Unzip and upload in one go! No fiddling with files anymore, and it's the same system to upload new themes. I don't know if it works for FCKeditor, a more complex module (I couldn't try because it's not available for D7 yet), but it is a great solution for most other modules.

After the upload (and running the update.script) you go to the Modules-list to do the rest. Here a picture of a detail of the modules-list.



Conclusion

Some features I didn't examine yet, like the new way of dealing with private files, the implementation of pictures and Test stalled when I tried to run it. But I saw already enough changes to be impressed with the improved functionallity of Drupal 7. Nevertheless, I (personally) hope that in later stage we'll see an easier installation and the implementation of a text-editor.

Things I liked the most:

* the User-interface, which is state of the art. Only after working with D7, I realise how 'messy' D6 actually is. In D7, logic prevails.
* The default implementation of CCK
* The way how one can install modules and themes with D7 is a giant leap forward.

If you want to download Drupal 7 Alpha 1 or read more about this release, go to Drupal.org.

Upgrading from Drupal 6 to 7

Upgrading your Drupal installation
Upgrade vs. Update
Before you continue reading we need to define the difference beween upgrading and updating:
* Upgrading refers to moving from one major release to another. E.g. you are moving from
Drupal 6 to Drupal 7.
* Updating typically refers to bringing your site up to the latest minor version of Drupal
e.g. like updating from Drupal 6.12 to Drupal 6.14.
For information on updating your Drupal site see: http://drupal.org/node/390448

Upgrading your Drupal installation
The process of upgrading to the latest version of Drupal can vary in difficulty depending on the complexity of your current installation. This guide aims to help you plan for and complete a successful upgrade regardless of the size or complexity of your current site.

Any Drupal upgrade has four general steps: Planning; Preparing your current site for upgrade; Upgrading and Testing.

Before you begin reading this guide please make note of the following.

Upgrading Between Versions
You can only upgrade from one version to the next version. For example you are trying to move from Drupal 5 to Drupal 7 you first need to upgrade to Drupal 6 before you upgrade to Drupal 7.

Back Up Your Existing Site
Regularly backing up your site is considered a best practice. A full backup of your site database, core Drupal files, non-core files (e.g. contributed modules, and file upload folders) is strongly recommended before starting any site upgrade.

You may also wish to familiarize yourself with restoring your site from a backup prior to starting your upgrade. If something should go wrong during your upgrade and you need to restore your site from backup, it is best to be prepared so you can restore your site quickly. See [link] for more information on how to back up and restore your site.

Drupal 7 new features

Easier installation
The installation process has been simplified. Drupal supports most web servers (Apache is recommended), PHP 5.2.4+, and most databases (MySQL 5.0.15+ is recommended).

Improved administration panels
The administrative interface has been overhauled to make it slicker and simpler. A new configurable shortcut bar provides quick access to the most important tasks:

More flexible

Drupal 7 allows you to define your own content structure and add custom fields to pages, users, comments and other types of content. More than 800 modules are known to be compatible with the new version.

Speed and scalability
Drupal is fast and can handle huge amounts of traffic with better caching and improved JavaScript and CSS optimization.

Accessibility

Accessibility is better and Drupal now offers semantic web support with RDFa.

It’s still open source
Drupal remains a capable CMS which can be downloaded, adapted and used by anyone for free.