Upgrading eglug.org to Drupal 4.7

UPDATE (Tue Jan 30 22:56:03 EET 2007): eglug.org upgraded to Drupal 4.7.6.

---

UPDATE (Wed Nov 8 23:00:38 EET 2006): an upgrade test was performed, if you interested: http://eglug.org/node/2226

---

Drupal 4.7 was released few days ago. If you don't know already, eglug.org is powered by Drupal which means we should consider upgrading to the new version so we can enjoy the new features/possibilites, performance boosts and the better security.

We don't usually upgrade immediatly with a new release, it's always better to give it some time, if the release proves to be sound and safe, we upgrade. But until we decide to upgrade, let's make sure we will be ready for the upgrade when we want to.

What we should do now is to make sure that we have versions ready for Drupal 4.7 of the following components:

• The modules we use.
• Our php code snippets (which can be found in some nodes and blocks).
• Our theme(s).

Let's see what are we missing to achieve the goal above.

Modules (0 modules need to be resolved)

This is a list of all eglug.org contrib modules:

• Admin Block.
• Article.
• Bidi. (ported by MSameer)
• Code Filter.
• Comment RSS. (Works fine with me. MSameer).
• Event.
• Flexinode. (cvs version works) ported - We should consider moving to CCK ? MSameer
• Glossary.
• Hall of Fame.
• HTML Corrector. (filters don't need porting)
• Image.
• Image Filter.
• Mail.
• Private Messages.
• Subscriptions.
• Syndication.
• User Points.
• Workspace.
• Diff. HEAD is 5.x now, can't find a 4.7-compatible version of the module. MSameer contributed the port to 4.7. Thanks!.
• Lincount. (Working fine with 4.7. doesn't need porting)
• Members HEAD works after taking care of http://drupal.org/node/22218#tablesort_pager.
• Rankvote. (sucks anyways, should be replaced by something that integrates with decision module or a voting api based module, Advanced Vote is way better)
• Wiki. (filters don't need proting but useless config form must be removed, would be better if we integrate with liquid which involves patching liquid).

PHP Snippets

Nodes:

• BidiModule (these are only used to share the code, can be replaced by a link to some cvs repository)
• LinCountModule
• RankingVoteModule
• list of people who voted for italian food (these should be replaced by something in the module itself instead of this ugly hack)
• top 10 contributors (not needed anymore HOF can do that)
• list of people who voted in moderators elections
• List of people who voted in Administrators elections
• list of people who voted on the admin elections poll
• Welcome to my Blog (that must be mostafa abusing his admin privilege)
• DiffModule
• top 10 commented nodes
• List of people who voted in 2nd Administrators elections (2006)
• List of people who voted in Administrators elections (2006)
• List of people who voted in 2nd Moderators elections (2006)

Blocks:

• Icons Bar block (this block of icons on the left). (code should work fine) needed only to take care of links and base_path().

Themes

We have only one theme

• EGLUG theme. (porting the theme is not a big deal, we need to think of improvements though)

This upgrading procedure is one of the eglug.org administrators team tasks. But of course everyone is more than welcome to volunteer in many ways, like porting remaining modules, correcting/updating this page (as for example, some of modules above my be updated later with a 4.7 port by Drupal community).

The PHP Snippets may not need any effort at all, the above list is actually the result of a search in the database for all nodes with inline PHP code. Also, not everyone may be able to edit these nodes, but let's keep it here for now to make this document a complete list.

One more thing that's relevant to the upgrade procedure, with the new 4.7 (era) comes new (sometimes better) ways of doing things, like for example how Mail module is deprecated and can be replaced by other two modules, or Content Construction Kit is going to replace Flexinode. I think we need to consider these changes and how they are going to affect us. Needless to say, volunteering in this area is much appreciated.

Note

If you would volunteer in porting any code, it's recommended that you update this page to indicate this. That is to avoid having multiple volunteers working on the same thing without coordinating with each other.