When i try to run update.php i get a 500 server error.
If i set my memory limit to 12m then the page displays a drupal notice about raising the limit however when raised the 500 error returns.
In my error log i have....
Tue Feb 24 19:06:53 2009] [error] [client x] PHP Warning: Unknown column 'serialized' in 'field list'\nquery: SELECT data, created, headers, expire, serialized FROM 1_cache WHERE cid = 'variables' in /var/www/vhosts/x/httpdocs/drupal_new/includes/database.mysql.inc on line 128, referer: http://www.iceskating.org.uk/drupal_new/update.php
[Tue Feb 24 19:06:53 2009] [error] [client 90.199.168.79] PHP Warning: Unknown column 'serialized' in 'field list'\nquery: UPDATE 1_cache SET data = 'a:294:{s:13:\\"theme_default\\";s:4:\\"nisa\\";s:13:\\"filter_html_1\\";s:1:\\"1\\";s:18:\\"node_options_forum\\";a:1:{i:0;s:6:\\"status\\";}s:17:\\"menu_primary_menu\\";s:1:\\in /var/www/vhosts/x/httpdocs/drupal_new/includes/database.mysql.inc on line 128, referer: http://x/drupal_new/update.php
We are attempting to upgrade from D5.x to D6.x but cannot because multibyte string in php.ini is set to on. I must have this ON for another application on the same server. How can I do this?
This is the first time for me to upgrade. My website is http://www.anxietyfreeexam.com
I want to upgrade it from 6.2 to 6.9
Please give me complete information and steps to do it.
Thanks in advance.
Okay, So I was able to successfully get upgraded from Drupal Core 6.4 to 6.9 and I was able to install some of my modules like CCK and Views. But there are a few modules I'm having trouble with.
Advanced Help (latest Version)
FCKEditor (Lastest Version)
PNGFix (latest version - not so important)
Everytime I try to install these, this is my course of action:
1. Upload tarball
2. extract files to the modules directory
3. go to the Adminster modules page and see if they appear
4. enable modules
I tried to simulate upgrading my 5.15 site to Drupal 6.9 today. As described in http://drupal.org/upgrade/ , I created a test site by copying all files into a subdirectory of my shared hosting "root" and creating a second database. I could verify that the test site worked as expected, logging in and doing administrative tasks worked indepentenly from the main site.