Re: How to upgrade multisite installations to Drupal 5.0?

> Quoting dondi_2006 <dondi_2006libero.it>:
> 
> > Hello,
> > I have checked in the forums, and all I have found
is
> > other two users with the very same problem and no
answer at all in 
> > three weeks:
> >
> > http://drupal.org/node/
126461
> > http://drupal.org/node/
132425
> > http://drupal.org/node/
126438
> >
> > Is it really true that there is no way to upgrade
> > one multi-site drupal install from 4.7.6 to 5.0 or
5.1
> > working only on the command line????
> 
> You could use wget but the upgrade.php expects you to
pick a
> version to upgrade to.

I know that wget or curl can do this kind of things, thanks.
I haven't gone that way yet for two reasons:

1) I really, really couldn't believe that this case (one
drupal install
   for several sites, each one with its own database) had
been ignored
   or forgotten by the developers. I haven't even seen
anywhere any 
   official announcement that such a way to use Drupal would
have
   become deprecated with Drupal 5. Did I miss such an
announcement?
2) I am not going to play with several *live* websites,
risking to
   mess them up, to make an untested procedure work. Not
until there
   is the slightest possibility that a tested way to make
this upgrade
   comes up (I can't obtain more databases right now on that
server).

Is it at least possible to know for *sure*, before trying
it, if
running that procedure through ONE of the websites currently
managed by
Drupal 4.7.6 will upgrade all the others?

Thanks,
D.


------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind
http://click.libero.it/i
mode


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

Quoting dondi_2006 <dondi_2006libero.it>:

>
>
>> Quoting dondi_2006 <dondi_2006libero.it>:
>>
>> > Hello,
>> > I have checked in the forums, and all I have
found is
>> > other two users with the very same problem and
no answer at all in
>> > three weeks:
>> >
>> > http://drupal.org/node/
126461
>> > http://drupal.org/node/
132425
>> > http://drupal.org/node/
126438
>> >
>> > Is it really true that there is no way to
upgrade
>> > one multi-site drupal install from 4.7.6 to
5.0 or 5.1
>> > working only on the command line????
>>
>> You could use wget but the upgrade.php expects you
to pick a
>> version to upgrade to.
>
> I know that wget or curl can do this kind of things,
thanks. I 
> haven't gone that way yet for two reasons:
>
> 1) I really, really couldn't believe that this case
(one drupal install
>   for several sites, each one with its own database)
had been ignored
>   or forgotten by the developers. I haven't even seen
anywhere any
>   official announcement that such a way to use Drupal
would have
>   become deprecated with Drupal 5. Did I miss such an
announcement?

It isn't deprecated or removed.  Automation for updates were
improved 
in Drupal 5.  However, the multi site update detection must
be lacking 
for you to post this.  There is no reason why you can't
execute the 
update.php on each site manually by directing the URI to
update.php for 
each site.

> 2) I am not going to play with several *live* websites,
risking to
>   mess them up, to make an untested procedure work. Not
until there
>   is the slightest possibility that a tested way to
make this upgrade
>   comes up (I can't obtain more databases right now on
that server).
>

Only a fool would play with an update without first doing it
in a 
development environment first.  How will the update affect
your 
modules?  Are all of the modules you use up to date with the
current 
version?

> Is it at least possible to know for *sure*, before
trying it, if
> running that procedure through ONE of the websites
currently managed by
> Drupal 4.7.6 will upgrade all the others?
>

Look at update.php.  Test it in development.

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

I wouldn't object to having a script for command-line
multi-database
updates. But you can safely assume by now that nobody has
written such
a script yet.

This seems easier for upgrades between minor versions or for
core-only
upgrades (because the contributed modules and themes often
don't have
a matching major version).

Since the developer wouldn't know how people have messed
with their
sites, such a script would be mostly suitable for people who
can take
care of their module and theme versions, read error
messages, fix
their database, run test updates, or revert to an
interactive process
if necessary.


On 4/2/07, dondi_2006 <dondi_2006libero.it> wrote:
>
>
> > Quoting dondi_2006 <dondi_2006libero.it>:
> >
> > > Hello,
> > > I have checked in the forums, and all I have
found is
> > > other two users with the very same problem
and no answer at all in
> > > three weeks:
> > >
> > > http://drupal.org/node/
126461
> > > http://drupal.org/node/
132425
> > > http://drupal.org/node/
126438
> > >
> > > Is it really true that there is no way to
upgrade
> > > one multi-site drupal install from 4.7.6 to
5.0 or 5.1
> > > working only on the command line????
> >
> > You could use wget but the upgrade.php expects you
to pick a
> > version to upgrade to.
>
> I know that wget or curl can do this kind of things,
thanks. I haven't gone that way yet for two reasons:
>
> 1) I really, really couldn't believe that this case
(one drupal install
>    for several sites, each one with its own database)
had been ignored
>    or forgotten by the developers. I haven't even seen
anywhere any
>    official announcement that such a way to use Drupal
would have
>    become deprecated with Drupal 5. Did I miss such an
announcement?
> 2) I am not going to play with several *live* websites,
risking to
>    mess them up, to make an untested procedure work.
Not until there
>    is the slightest possibility that a tested way to
make this upgrade
>    comes up (I can't obtain more databases right now on
that server).
>
> Is it at least possible to know for *sure*, before
trying it, if
> running that procedure through ONE of the websites
currently managed by
> Drupal 4.7.6 will upgrade all the others?
>
> Thanks,
> D.
>
>
> ------------------------------------------------------
> Leggi GRATIS le tue mail con il telefonino i-mode™ di
Wind
> http://click.libero.it/i
mode
>
>
> --
> [ Drupal support list | http://lists.drupal.org/
]
>
-- 
[ Drupal support list | http://lists.drupal.org/
]

Quoting Chris Johnson <cxjohnsongmail.com>:

> Agreed.   Punting support for people who run multiple
sites from one install
> with Drupal 5 is pretty bad.  By the time we migrate to
D5 sometime this
> summer, I suspect we will have 40 to 80 sites, running
from 1 to 3 installs.
>

I would put D5 in a different directory and update sites
gradually.  
Add D5 to the DB table prefix and copy the existing data to
the D5 
table space before doing the upgrade.  You can point to D4
vs D5 using 
the httpd config files.  This gives you a backout path
should you need 
it.  Then when the upgrades are complete you can drop the
older tables 
and the D4 version.

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