Probleme bei Upgrade auf 2.0

Hallo zusammen,

habe gerade versucht eine Seite von 1.9.1 auf 2.0.3 upzugraden. Lokal
bei mir hat auch alles funktioniert.

Auf dem Server scheitere ich allerdings an der Aktualisierung der
Datenbank. Auch nachdem ich auf aktualisieren gegangen bin kommt immer
wieder die Meldung, dass ich die Datenbank anpassen muss.

Irgendjemand eine Idee?

Könnte es an der MYSQL-Version liegen? auf dem Server 4.0.24 (lokal 5.0.51)

Grüße

Torsten

Hallo Torsten,

auf Englisch hatte ich das schon einmal beantwortet, vielleicht hilft's:

I still forgot to mention that you should start your new SPIP installation or upgrade without plugins. You may later add them comfortably using the automatic intallation procedure for plugins.

klaus++

Ben. . schrieb:
> Also , just a little try when you have problems : try to remove all
> the content of the tmp directory ...
>
> On 12/13/08, klaus++ <klaus@spip.de> wrote:
>> Hello kamran Mir Hazar,
>>
>> it looks as if you are experiencing an conflict between your new SPIP
>> and remains of the former version. Therefore I think you should delete
>> parts of your former version to be sure to do a clean install.
>>
>> Hopefully you followed instructions and made a backup copy of your
>> database. Since this is a major upgrade you might also have made a
>> complete backup of all your files.
>>
>> Execute a rollback to your previous version and take the follwing steps:
>>
>> delete
>> ./dist
>> ./ecrire
>> ./local
>> ./tmp
>>
>> Either use the automatic installation or copy files and directories of
>> SPIP 2.0 in your installation path. Don't forget to adjust privileges.
>>
>> Start the installation by opening ./ecrire/
>>
>> If this fails, you may additionally delete ./config and try again.
>>
>> And as a last resort, if everything else fails, simply install SPIP 2,0
>> into an empty directory, upload your ./squelettes and ./IMG folders with
>> their files and subfolders and execute a restore of your 1.92e database
>> backup using the SPIP private sector. Just ignore the alert, this will
>> work fine.
>>
>> If you have a mes_fonctions.php and mes_options.php, if you are running
>> several instances of SPIP in the same database or if you are using PHP
>> in your templates, please let's discuss this before you continue..
>>
>> SPIP 2.0 is a major release so downward compatibility is not as complete
>> as usual but you will succeed to import your data and use your
>> templates. Maybe you will have to make some minor changes in your
>> templates if you used PHP or advanced SPIP functions which have been
>> partly revised.
>>
>> If your database is really huge (I am talking about tens of thousands of
>> articles, comments and other entries) you may have to install SPIP and
>> transfer your MySQL database using your server's command line. This is
>> due to limitations set by your webhosting company and you should
>> consider changing to a more powerful hosting package or a dedicated
>> server. This is not specific to SPIP but concerns every system based on
>> Apache/MySQL/PHP.
>>
>> good luck and have fun!
>> klaus++
>>

Torsten Willmann schrieb:

Hallo zusammen,

habe gerade versucht eine Seite von 1.9.1 auf 2.0.3 upzugraden. Lokal
bei mir hat auch alles funktioniert.

Auf dem Server scheitere ich allerdings an der Aktualisierung der
Datenbank. Auch nachdem ich auf aktualisieren gegangen bin kommt immer
wieder die Meldung, dass ich die Datenbank anpassen muss.

Irgendjemand eine Idee?

Könnte es an der MYSQL-Version liegen? auf dem Server 4.0.24 (lokal 5.0.51)

Grüße

Torsten
_______________________________________________
Spip-de@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-de