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.

Upgrading from 6.x to 6.8 returns fatal error on update.php

I'm upgrading from I think 6.x (don't remember the exact version) to 6.8 and when I run update.php after I upload all my files I get the following error:

Fatal error: Call to undefined function filter_xss_admin() in /home/site/public_html/includes/theme.maintenance.inc on line 246

I downloaded the update and untar'ed it on the server. I ftp'ed the sites folder and my custom theme.

Anybody know where I should start looking?

Thanks in advance.

Drupal Fine Now -- But What Happened? Any Ideas?

Hi -

Drupal Newbie here.

I am working with drupal on local development site (Windows XP standalone, with Apache Triad loaded at C:

I needed to upgrade my 6x Drupal to 6.8. My steps: (1) I backed up MySql database locally using PhPAdmin; (2) I next copied to local backup directory the Drupal folders: themes, sites, scripts, profiles, modules, misc and includes; (3) I finally copied htaccess to local backup directory.

I did not put my local site into maintenance mode. I had no reason to disable custom/contrib modules.

Now here's the interesting part.

After doing this backup work, I looked at the admin page in Drupal (http://localhost/drupal/admin). Oddly enough, the list of tasks under EVERY major heading (Content Management, Site Building, etc) were truncated, significantly. Under Site Building, for example, only Blocks was displayed. Note that I was logged in as user 1/admin.

I got tired of trying to figure out how to solve the problem. At this point, I had not installed 6.8!

Customization of drupal and upgrade it later

Hi
i want to use drupal as framework for a web appplcation but i have a doubt regarding how to organize the code.

I know for example that one way is to write my own modules and "override" all core and contributed functions so that when i need to upgrade drupal or modules, i won't need to restart to code. But for this solution, i am afraid of the useless code ...

The second idea is to modify "wisely" the core code and contributed modules and update "wisely" later.

thanks for giving me some ideas.

Moving systems

I am attempting to move my production environment from one physical system to another. What are the steps involved in making this move? The steps I am aware of are:

  • Backup/copy the MySQL database
  • Copy custom code (Themes, Modules)
  • ...

Oh, one other thing I also need to change the "domain" name for the site

Any assistance would be appreciated.

Regards,
Harold

Strict Standards: Declaration of DatabaseStatement::execute()

I'm trying to create a (clean) D7 test site and get this:

Strict Standards: Declaration of DatabaseStatement::execute() should be compatible with that of PDOStatement::execute() in C:\www\webapps\drupal-7\includes\database\database.inc on line 1118

upgrade from 6.2 to 6.8 killed site

hi,

i decided to upgrade my site from 6.2 to 6.8.
partly because it said it was a security upgrade, and partly because my cck date view filter wasn't working, so thought i'd make sure everything was current before fixing it.

took a backup of site plus database.

installed the backup on my localhost. practised running the upgrade on my local copy. appeared to work. so got ready to do it in production.

took site offline.
turned off modules.
uploaded code.
ran update.php

blank screen.

ran update.php
blank screen, with address http://www.mysite.com.au/update.php?op=info

just in case it really had worked, tried www.mysite.com.au.
got fatal error with Call to undefined function db_set_active() in bootstrap

in case code hadn't ftp'd in correctly, reuploaded stuff.
tried the update.php again.
still got blank screen with same url.
using the home url this time gets Call to undefined function db_query() in /mysite.com.au/includes/session.inc on line 32

hm. site screwed.

uploaded code from the upgraded localhost backup.
tried uploading backup database.

packet size too big on the cache table.

couldn't use heidi to export the sql from my test database - kept hanging.

ended up using xampp/phpmyadmin to export the sql from the test database. edited the file to remove the cache table contents.

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal