I upgraded from 4.7.2 to 4.7.3 HEAD a few days ago and it has given me a lot of problems. Most of them seem to revolve around 3rd-party modules calling on discontinued APIs. Image.module is giving me tons of trouble, it appears to be breaking all over the place:
I have a user with the username Åsmund (A with a small dot on top).
While running Drupal 4.6 the database was set to latin1 and when I looked at it using phpMyAdmin his username showed up as "Ã…smund" (A with a squiggle on top followed by three dots).
I didn't think much of it while running running 4.6, since it worked anyway. But after upgrading to 4.7, which changed the table to utf-8, his username is "Ã…smund" both in phpMyAdmin and in Drupal. So he can't login.
Is it still best to upgrade from 4.5 to 4.7 by way of 4.6 ?
To flesh things out, I am upgrading a Fedora Legacy 7.3 box to Fedora Core 5 (will Drupal 4.6 and 4.5 even run on that ?), which also means upgrading MySQL and PHP versions (as well as everything else).
My current plan is to use the update option in the FC5 installer, and hope that migrates PHP, MySQL and Apache without too much mess. Which just leaves me with Drupal to (re?)install and get it to update the DB (will it do this) ?
After the recent upgrade from 4.6.2 to 4.7.3, every admin page I visit is reported in logs as "Access denied to admin/[...]", although I do visit them normally. These logs are attributed to Anonymous user, but the visits are done by the admin (myself).
Although this is not generating any noticeable problem, I wonder if this is a symptom of something more serious going on. Should I worry about these erratic logs?
Embedded Gallery2 worked OK for me with Drupal 4.6, but now I upgraded to 4.7 and have a problem. There is quite a number of posts on URL rewrite problems related to Gallery2 integration; it is said that there should be a separate .htaccess file for the Drupal-embedded gallery module (different from the Gallery2 one).