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.

update.php vs. multisite shared tables

I run Drupal in a multisite environment. The default site is the "main" site and the other sites are for various subsets of the organization.
http://main.example.com
http://site1.example.com
http://site2.example.com
...
http://siteN.example.com

Each site has its own MySQL database
main
site1
site2
...
siteN

Certain tables are shared by all sites and live in the default database. Default db tables are not prefixed, other site db tables are. sites/site1/settings.php includes:

'prefix' => array (
        'default' => 'site1_',
        'role' => 'main.',
        'users' => 'main.',
  ),

When doing a major or minor core upgrade or module upgrades, it is necessary to run update.php on each site so that the db updates will be applied to each site's database. I run
http://main.example.com/update.php first, followed by
http://site1.example.com/update.php
http://site2.example.com/update.php
...
http://siteN.example.com/update.php

Can't Login After Updating to 7.19 Core

After I updated to the latest core I am unable to login to my site.

I had to remark out the following lines in my .htaccess file for the site to work with my provider:

Options -Indexes
Options +FollowSymLinks

This is the error that I get when I try to login:

Fatal error: require_once() [function.require]: Failed opening required '/home/www/waltonbusad.com/password.php' (include_path='.:/usr/local/php/pear/') in /home/www/waltonbusad.com/modules/user/user.module on line 2204

Upgrade to 7.19 works but not recognized

I've wiped clean my public_html and uploaded the 7.19 core with my sites folder to this directory. For some reason when I view the status report it says that the Drupal version is 7.19, but a few lines below there is a message telling me that updates are available, and when I go to the available updates page, it appears to think that my Drupal core is still 7.15. I've cleared all tables in myPHPadmin that start with cache, and I've run update.php, and it still shows this.

Backwards compatibility - the fight plan

It's 2013 out there. And hopefully, in about 8 months or so, we'll see another major Drupal release: Drupal 8. <woot> !

That also means (</woot> ) the end of the life cycle for the first massively popular Drupal series - Drupal 6.

Upgrade 6.27 to 6.28 error

Unable to update drupal from 6.27 to 6.28

Message array_pop() expects parameter 1 to be array, boolean given in /var/www/springfirm/update.php on line 316.

warning: reset() expects parameter 1 to be array, null given in /var/www/springfirm/update.php on line 316.
warning: array_pop() expects parameter 1 to be array, null given in /var/www/springfirm/update.php on line 316.
The update process was aborted prematurely while running update # in .module. All errors have been logged. You may need to check the watchdog database table manually.

ds module

ds module
Update #7201

Failed: DatabaseSchemaObjectDoesNotExistException: Cannot add field ds_fields.ui_limit: table doesn't exist. in DatabaseSchema_mysql->addField() (line 325 of /home/content/v/p/e/vpesebook/html/includes/database/mysql/schema.inc).

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal