Upgrading Drupal

I'm having the following problem with the image module :

It used to work fine in the past, but now when you post an image you get an error like this :

warning: Invalid argument supplied for foreach() in /home/user/dreamgate/www/modules/image/image.module on line 329.
warning: Cannot modify header information - headers already sent by (output started at /home/user/dreamgate/www/includes/common.inc:384) in /home/user/dreamgate/www/includes/common.inc on line 192.

Also, the logs give this error twice :

Hello!

After upgrading my Drupal 4.6.3 to 4.7 it only generates white pages. The upgrade finished without any errors.

Do you've any idea what the problem could be?

Thx
Florian

I just upgraded to 4.7 and I am very happy with it.
everything works fine exept one thing.
I used image_import a lot and it worked good with 4.6
After the upgrade i could not go to settings/image_import so i downloaded the latest image_import.module from CVS and it looked OK. But when I finally come to settings/image_import and open the page everything I see ist "Array".
This is the hook_settings function from image_import:

function image_import_settings() {
// First, check the status of the directory path and report any problems
_image_import_check_settings(FALSE, 'image_import_default_import_path');

$form = array();
$form['file_path'] = array(
'#type' => 'fieldset',
'#title' => t('File path settings'),
'#description' => t('These settings control the path on the server from which image and caption files will be imported. You can put the string <code>%u</code> or <code>%U</code> in the path fields, and these strings will be replaced by the username of the person doing the import. %U and %u are the same except that %U automatically removes space, %, <, >, *, /, \, and ? from the username.'),
'#tree' => FALSE,
'#collapsible' => TRUE,
'#collapsed' => FALSE,
);
$form['file_path']['image_import_default_import_path'] = array(
'#type' => 'textfield',
'#title' => t('Default import path'),

I've been trying to upgrade my 4.6.5 site to 4.7beta5 and I'm not sure the DB update is actually working.

When I perform the update.php script, the pre-selected system module is 129. The actualy update is very fast - maybe only a second or two.

Immediately after the update, I see this:

http://www.michaelanello.com/drupal/1.gif

Should there be anything in the "the following queries were executed" area? Also - what about the severity error? Is this related to the pre-selected system module?

When 4.7 is released as stable, will upgrading cause modules written for 4.6 to break, if they've been written 'correctly' - maybe what I'm trying to say is, are there any big changes to the existing hooks_ system that Drupal modules make use of?

Cheers,
K

I must say that the 4.6 to 4.7 series move has been the biggest, in terms of time spent anticipating when to upgrade and dealwith all the accompanying problems, that I have seen here since I have been a member. I have been fiddling with 4.7.0 from the beginning of it's first beta all the way to now. What a ride. I lost track of the changes and bugfixes. It's awesome software. However, one particular thing that is irking me now are relative paths. Earlier I knew where I stood. You plug in your base url into the settings page and boom...everything worked. Even with legacy data. Not so in 4.7, at least with egacy data.

As can be seen here: http://drupal.org/node/51382, here: http://drupal.org/node/13148#comment-77673, and here: http://drupal.org/node/51612 this is an ugly little problem.

Two immediate issues I have. First, all internal links created by users pointing to other internal pages are broken. Nasty.Second, when the source code of each page is viewed in a browser, you get Login instead of Login, which I natrally do not want. In other words, the folder where things live is being shown.

I have read all about this in the changelogs, particularly for themes. Can someone PLEASE tell me how to just get things working(just the links and paths).

Bèr Kessels has been kind enough to offer this patch "phptemplate_engine_add_base_url_0.patch" here http://drupal.org/node/51612. Only problem is, I do not know what is meant by putting the "base tag" on the "page.tpl.php" page. So I can't even test it. What exact tag and where exactly on this page? Any help would be appreciated. My prediction is people with reams of legacy links who upgrade to 4.7 will be very unpleasantly surprised, unless of course, an easy to implement solution is there. From all the posts I've read, and I've spent many, many hours(yes, I'm embarassed!) on this, there is not yet one available. Any