Updating from 4.5.2 (in CivicSpace distro) to 4.6.7 Drupal

On  29.May.2006, at 11:21 PM, Laura Scott wrote:

> BTW, if this is CivicSpace (which I guess only from
your db name),  
> why are you doing a Drupal upgrade and not a CivicSpace
upgrade?

Thanks for the heads up. it occurred to me as I looked
through the  
instructions --which I will need to rewrite in a big and
ugly way--  
yeah, i will have to walk through each version of drupal
until the  
latest. it's insane if you ask me.

Why i am not upgrading using civicspace? To use CiviCRM I
had to set  
up a separate site --it slowed down and crashed
CultureKitchen  
constantly. I have only been able to run massmailer once, in
a  
textdrive development site i had with one of the earliest
versions of  
CivicSpace. Since then, nothing I do makes it work. So right
there,  
the two major reasons for me to run CivicSpace are
completely gone.

Last but not least, I have to pare down my sites. They suck
big  
chunks of bandwidth and I think the distro is part of the
problem.  
I'd rather set up the other CSL modules by hand and hope
for the best.

If you have a better idea as to how to go about this, please
shoot  
them my way.

Cheers,
liza

-- 
[ Drupal support list | http://lists.drupal.org/
]

Laura Scott wrote:
> Hi Liza,
>
> 4.5 to 4.6 was a tough upgrade, as I recall. From what
I remember, 
> what I had to do on a couple of sites is move back
through the update 
> versions. Your database update seems to have missed a
column insert in 
> a previous update. (A (mis)educated guess.)
>
> I believe a number of people were able to get the
update to work by 
> moving backwards through the db upgrade numbers. You
might even dig 
> through the update file looking for
"severity" and scroll up from 
> there to the update number it involves.
>
> In fact, I just dug through updates.inc (in the
database folder) and 
> found this:
>
> function update_115() {
>   $ret = array();
>   if ($GLOBALS['db_type'] == 'mysql') {
>     $ret[] = update_sql("ALTER TABLE 
ADD severity 
> tinyint(3) unsigned NOT NULL default '0'");
>   }
>   else if ($GLOBALS['db_type'] == 'pgsql') {
>     $ret[] = update_sql('ALTER TABLE  ADD
severity smallint');
>     $ret[] = update_sql('UPDATE  SET
severity = 0');
>     $ret[] = update_sql('ALTER TABLE  ALTER
COLUMN severity 
> SET NOT NULL');
>     $ret[] = update_sql('ALTER TABLE  ALTER
COLUMN severity 
> SET DEFAULT 0');
>   }
>   return $ret;
> }
>
> You might try rerunning update.php, and manually
selecting version 
> 115, and see how that goes.
>

Please never do this! Update.php assumes that all updates
are run just 
once, there are no checks for duplicate runs. You might
sseriously mess 
up your database. If you want to run a particular update,
copy the 
contents of the function to a .php file, include the
relevant files 
(bootstrap.inc, common.inc) at the top and execute that
instead.

> OR (safer) extract the MySQL from this update, convert
it into mysql 
> syntax and run the commands manually.

Or that, but this won't be possible for all updates.

Cheers,  
    Gerhard
-- 
[ Drupal support list | http://lists.drupal.org/
]