SPIP now separates properly the development version from the stable
branch, which is maintained separately (that's wasn't the case in the
1.9.x versions).
Your version is really old (older than 08/2006 !) and wasn't a stable
version (that's what means the 'SVN' suffix).
So I strongly advise you to upgrade in two steps :
- first upgrade to the latest version of the 1.9 family : SPIP1.9.2g,
available here : http://files.spip.org/spip/dev/SPIP-branche-1.9.2.zip
- Then upgrade to the version 2.0.
If you use plugins, you will certainly have to upgrade them two.
And some of them are not compatible yet with SPIP 2.0 : that's another
good reason to first upgrade to spip1.9.2g !
Of course, don't forget, for each step, to backup the complete
installation before any modification (files and database -- exported
with phpMyAdmin or another MySQL admin tool -- but not the export
functionality of SPIP)
.Gilles
--
On Thu, Mar 26, 2009 at 1:42 PM, Tereza Loparic <telopa@gmail.com> wrote:
Hi, all
I would like to upgrade the spip version of my site. Once I've been
told that it would be better not to skip steps.
My version is 1.9 beta 3 SVN. Does "beta" mean that is not already 1.9?
Which one is the next version, 1.9.0, 1.9.1 rev 7385 or 1.9.1 rev7502 ?
So I strongly advise you to upgrade in two steps :
- first upgrade to the latest version of the 1.9 family : SPIP1.9.2g,
available here : http://files.spip.org/spip/dev/SPIP-branche-1.9.2.zip
- Then upgrade to the version 2.0.
I strongly disagree wth this point, as the upgrade code in version 2.0
contains the upgrade code in version 1.9.2, and hence everything
you'll get by doing it this way is just... more work.
The rest of Gilles' message is perfectly correct : backup with SQL tools
On Fri, Mar 27, 2009 at 9:05 PM, Fil <fil@rezo.net> wrote:
So I strongly advise you to upgrade in two steps :
- first upgrade to the latest version of the 1.9 family : SPIP1.9.2g,
available here : http://files.spip.org/spip/dev/SPIP-branche-1.9.2.zip
- Then upgrade to the version 2.0.
I strongly disagree wth this point, as the upgrade code in version 2.0
contains the upgrade code in version 1.9.2, and hence everything
you'll get by doing it this way is just... more work.
I agree with you if there isn't any plugin installed.
But if it's the case, some of them can make the site crash : spip2.0
won't always work on plugin that where installed for a beta version of
spip 1.9.0
The "A.9 to 2.0" step is mainly for the plugins.
.Gilles
---
The rest of Gilles' message is perfectly correct : backup with SQL tools
I agree with you if there isn’t any plugin installed.
But if it’s the case, some of them can make the site crash : spip2.0
won’t always work on plugin that where installed for a beta version of
spip 1.9.0
The « A.9 to 2.0 » step is mainly for the plugins.
Anyway, regarding plugins, it’s also highly recommanded to rename the plugins directory during the SPIP upgrade process, to avoid those possible crashes.
Then, when SPIP upgrade is Ok, you can upgrade existing plugins with v2.0 complient ones when existing (which is still not the case for every plugin), and then again, when plugin upgrade is complete, you can put the directory back in place and test all the site.
All is a question of method after all
Etienne.
.Gilles
The rest of Gilles’ message is perfectly correct : backup with SQL tools
Anyway, regarding plugins, it's also highly recommanded to rename the
plugins directory during the SPIP upgrade process, to avoid those possible
crashes.
Then, when SPIP upgrade is Ok, you can upgrade existing plugins with v2.0
complient ones when existing (which is still not the case for every plugin),
and then again, when plugin upgrade is complete, you can put the directory
back in place and test all the site.
Yes, your process seems to be the best one
But it's not in the official documentation :
Maybe we should update this page too
.G
All is a question of method after all
Etienne.
.Gilles
---
> The rest of Gilles' message is perfectly correct : backup with SQL tools
>
>
> -- Fil
>
_______________________________________________
spip-en@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-en