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.

upgrade failed, unable to restore database, need a little help

Hello All

I am having problems restoring a backed up drupal database through phpmyadmin hosted with 1 &1.

A couple days ago I dumped the database for my drupal site before running the drupal 4.7 update script. It didn’t work out for some reason I have yet to discern (I realize that I should have made a test site). When I went to upload the sql dump file back into phpmyadmin it wouldn’t load.

However, it did work when I tried loading it into phpmyadmin on my local development server at home. It looks like an issue with not having the permissions with 1&1 to have phpmyadmin create databases (I can only create them through a control panel). So my brain tells me that I need to somehow modify the first part of the file that has the CREATE DATABASE line. And instead, somehow, get it to use an already existing database.

Here is the first part of the sql dump that I am referring to. If anyone can help me it would help me out big time. I’m running up against deadlines, and this trial and error stuff isn’t cutting it.

-- phpMyAdmin SQL Dump
-- version 2.6.4-pl3
-- http://www.phpmyadmin.net
--
-- Host: dbxxx.perfora.net
-- Generation Time: Sep 07, 2006 at 05:40 PM
-- Server version: 4.0.27
-- PHP Version: 4.3.10-2
--
-- Database: `dbxxxxxxxxx`
--
CREATE DATABASE `dbxxxxxxxxx`;
USE dbxxxxxxxxx;

-- --------------------------------------------------------

--
-- Table structure for table `access`

cron Unable to select database

I just recently finished my upgrade to 4.7 (from 4.6) and my site seems to be running fine except for one little detail. My cron results are "Unable to select database". Why would my cron say that when the rest of my site is running fine?

4.5 -> 4.6 upgrade "best practices" for image.module?

Hi,

I'm about to upgrade two sites from 4.5.2 to something more recent (at least 4.6, and maybe 4.7).

Both sites make heavy use of the image.module.

I've been reading many horror stories about the upgrade here in the forum, but I couldn't find anything definitive about the right wat to go about it.

I was wondering if there was a canonical discussion about how to do the upgrade properly?

Cheers,

Geoff S.

Update hangs

I trie upgrading from 4.6.3 to 4.7.3. When I run updates.php it hangs on the "Starting updates: Please wait while your site is being updated" screen. When I go to my website I get the following error

Page not found
user warning: Unknown column 'theme' in 'where clause' query: SELECT * FROM blocks WHERE theme = 'bluemarine' AND status = 1 ORDER BY region, weight, module in /home/peakcli/public_html/dive/includes/database.mysql.inc on line 120.

Upgrading confusion

I fixed the security vulnerability in a 4.7.2 site by patching (given as one of the options on this page) rather than doing another tedious upgrade.

I expected the changelog.txt to show 4.7.3, but it's still at 4.7.2. Or am I mixing up the two? The patch applied cleanly.

Correct way to upgrade to new versions of contrib modules ?

The immediate context is my need to upgrade pathauto which was diagnosed as having an XSS vulnerability.

Now, should I just overwrite the old module in my 4.7 install with the new one? Should I then run update.php and choose pathauto from the list of modules and do something? It's the latter part that is not clear from the handbook pages on upgrading.

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal