Upgrading Drupal

Okay, I had to install my personal server to new hardware this weekend. The system is running under Mandriva 2009 (kernel 2.6.27.14), Apache 2.2.9, PHP 5.2.6, and MySQL 5.0.67. This is just a single site installation.

It went pretty well and it seems everything restored smoothly, but I noticed that the Gallery2 module wouldn't initialize when I restored drupal 6.9. I updated everything that needed updating, put the site into maintenance mode and updated to 6.10. The update went fine, but I still have no images anywhere and the Gallery menu item won't appear because the gallery2 module will not initialize. The log yielded four instances of "Error in function '_gallery_init()' ...".

Expanding those gives me "Error in function '_gallery_init()' (gallery_base.inc:127):" and suggests that I configure my embedded gallery. I've been fussing with that config since late last night. At this point it has been reset and looks like this:

Location of Gallery2: file ./gallery2/embed.php does not exist [Error]

(I've fussed around and this error has come and gone. At this point, I'm not even sure what I did to make it go away. It does exist, BTW.
-rw-rw-r-- 1 madams madams 1520 2009-02-05 01:46 /var/www/drupal/modules/gallery2/embed.php)

Could this be related to ownership or permissions?

Gallery2 URL or URI: /gallery2/

So to be listed under bonehead things to NOT do - my uninstall method for modules up to this point has been to disable them on the Modules page and then to delete them from my directory. (I missed the large UNINSTALL button at the top of the page) I now know this method to be incorrect. Most modules have not given me trouble however Date module which Date API extends into many Drupal modules did throw up significant errors, bright hellfire and brimstone errors, which let me know what I did was very dumb. Sorry Drupal, my bad.

Hello all, I have been tasked with updating an older Drupal site running 6.2. Is it a good idea to run an update from 6.2 straight to the latest version (6.10) or should I perform incremental upgrades (to 6.3, 6.4, 6.5, 6.6, etc)?

Thanks

Just figured out that I am doing it wrong.

To update, I open winSCP, wget the tar'd file, untar it, and then duplicate or move the relevant files to my drupal root.

Good idea, right? Should overwrite the existing files, right?

Nope. Modules directory gets installed as a subdirectory of modules and so forth

As if that weren't bad enough, a visit to the database shows that the systems table is now looking at these sub-sub directories

This is crazy.

I can fix the stupid database by hand, i guess, but how to do this right?

Hi All,

I am quite new to drupal.

I have only ever worked on an old site version 4.6.3

However, I have recently installed version 6.10 on a number of new sites with no problems.

Now, my difficulty is that I have tried to upgrade the 4.6.3 site to the latest version. I have literally spent 40 hours or so, trying to get from 4.6.3 to 6.10 with no success.

Actually, I have managed to get from 4.6.3 to 4.6.11 ok.

Anything further than this and I get all sorts of update erros, or blank screens or whatever. Too many different problems to list.

Just did my first D5->D6 upgrade following http://drupal.org/node/340073. Things went pretty well for the most part, when I followed the most important piece of advice that the article doesn't mention: follow the steps slowly, carefully and precisely. Not how I usually work, but it definitely serves in this case. But this post is more about the surprises I ran into, just to get things somewhere where they might show up better in future searches, to wit:

Views need to be converted to Views2. Fortunately, there's a Convert option under the Tools tab on the Views admin page. Unfortunately, the converted views require a lot of tweaking. In the case of a site like RATCF that has a lot of different but very similar views, like the Ragin' and Cubicles types, it's a lot quicker to get one converted and then clone that to create the others rather than convert them all one-by-one.

Menus disappear? Probably because the views behind them haven't been converted yet. Mine started showing up again when I got my views fixed.

Custom CCK fields are inactivated after upgrade. This is a known CCK issue (http://drupal.org/node/335597), one that affects even D6 users simply upgrading CCK, so it's not specifically caused by the D5->D6 migration.