This forum is for questions about upgrading an existing Drupal site. Don't forget to read the UPGRADE.txt file that comes with every Drupal download.

Test site 4.6.5 -> 5.1 is corrupting main site

I'm trying to upgrade my 4.6.5 install into a 5.1 install. I'm not sure of the best path, so I decided to make a test site & see if I can upgrade the test site. The main site is http://www.mysite.com, and the test site is http://www.mysite.com/test. I've been able to get the test site & the main site to both function. I dutifully logged into my admin site as user 1, disabled all the extra modules, & reverted back to the basic theme. I renamed all the directories that would be overwritten with 5.1 to "testfolder-bak." I then uploaded the new 5.1 files onto the test folder. At this point, my main site still works & I'm logged into my main site as my normal log in. I then try to access http://www.mysite.com/test/update.php, and I get the "Access Denied" message followed by:

Length of upgrade script on 4.6 to 4.7 upgrade

(I'm actually in the process of upgrading a 4.5 site to 4.7 (and eventually 5.x), but my question is specific to the 4.6 to 4.7 step...)

I have done all the standard steps (d/l 4.7 code and appropriate modules that I want) and unzipped them on my server. Rather than doing the 'delete directory and re-create' mechanism I use a symlink to point to the active version (ie: In root directory I have a drupal-4.6 and drupal 4.7 directory and then a symlink called drupal that simply points to the appropriate 'active' version).

Anyway, I have triggered the upgrade.php script. The progress bar moved nicely along to ~55% and then has basically stopped for the past 20 minutes. If i look at 'top', I see apache and MySQL processes running at 65%+ and 35%+ of CPU the whole time.

Now, my test system isn't the most powerful in the world (Duron 700 / 256MB ram) and my database isn't small (5800 nodes, 20000 comments) but after sitting here for nearly 1/2 an hour I'm starting to worry that the upgrade will crap out at some point and leave me in nowhere land.

I guess I'm looking for some confirmation that "yes, it can take that long to perform the upgrade; don't worry about it" or a "Hmm, that is strange, you might have some problems".

All but the admin pages are blank

I just upgraded to 5.0 (as the suggested in-between to 5.1), but a peculiar problem arose. I seem to be able to access all administration pages, but none of the content. The main page is a blank screen and if I navigate to all content (?q=admin/content/node) I get a list of all forum posts, blogposts, articles and whatnot, but all lead to a blank page.

What could this be?

Register new user, e-mail has no uername and passwords

Hi all.

I have one drupal installation with a great problem when new users register an new account. When the notification e-mail ist sent to the new user, there is are just variables and no real username, password, paths .... Here ist the german e-mail text from a new user. Please help with a hint.

Mibur

--------------------------------------------------------
%username,

Ein Administrator hat ein Konto auf der Website %site für Sie erstellt. Sie können sich nun unter %login_uri mit folgendem Benutzernamen und Passwort anmelden:

Returns from homepage to the installation page

Hello there.

I tried migrating from WordPress to Drupal by using the wp2drupal module for 4.7 and then upgrading to 5.1 (current version).

The migration to 4.7 went alright, but now, after upgrading, when going to the homepage, it keeps bouncing me to the /install.php page.

What do I do?

Thanks.

module_exist() not found

I'm upgrading a 4.6 site to 5.0 in preparation for going to 5.1

I seem to have a whole load of warnings in the upgrade which I think is related to me trying to use old 4.6 modules and themes in 5.0

However my current sites are showing this error

Fatal error: Call to undefined function module_exist() in /home/owal/html/drupal-5.0/includes/common.inc(1343) : eval()'d code on line 3

Now I've read up on this site which says that module_exist became module_exists sometime around 4.7 BUT I've recursive grep'ed the whole codebase and can't find it.

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal