Version SPIP3est already widely used [6] reliably, and you may want to spend: this is perfectly rea

A peculiarity of SPIP is its ability to multi-base management, both in the sense of simultaneous use several sets of tables in question, using the XML interoperability, that also multiple DBMS (MySQL historically, PostgreSQL, SQLite rather, not to mention the almost complete portages including Oracle ..).
Successive versions of SPIP ensure backward compatibility of data (and most of the skeletons), but charging an export base on another version of SPIP, exposes problems in general [1].
Move or convert an SPIP data sets games two aspects: - the engine fcc change database (or server) - the change in structure of SPIP tables between two versions. and should not omit field management or specific additional tables related plugins or custom fcc enhancements SPIP. Formats of the database
SPIP base data is stored in a server database (MySQL, SQLite ..) in a set of standardized, possibly with a separate $ prefix prefix spip_ standard tables. The native format is not always easily transportable without difficulties (encodings, internal engine ..) between servers of the same type, not to mention an engine change DBMS.
In addition to their internal format, all SQL engines generally fcc can do a "dump" in a specific format, and a "SQL export" fcc only with the SQL standard [2] instructions, but unfortunately these "SQL dump" are not all compatible them.
On the other hand, take a SQL size often requires access to a particular tool (the mysqld engine or PhpMyAdmin made integrated spip a plugin), much less friendly fcc than SPIP and not always accessible (even by the webmaster) according fcc to the system constraints and security posed by the host.
SPIP had so long been integrated into its private interface tool for managing backup and restore a native format-text-inspired XML. It is now left in the SPIP3 new version until a plugin fcc equivalent [3] to be finalized, but it raises the issue of import and export between bases during transition SPIP2 in SPIP3.
Note that a similar problem is often treated, namely transfer a remote site to a local server for up-to-develop new skeletons, or otherwise Transfer a local site to a remote site, these approaches highlight the all files and steps to follow, but are implicitly the same basic version of SPIP or an upgrade (see # migration).
Some plugins Backups fcc (Automatic Backup and Mes_Fichiers ..) provide additional fcc facilities to enable sending an email backup or recovery fcc also documents [4] without making any response to the change in format, see contrary related to phpMyAdmin regression.
In addition, another plugin "migration" fcc can "carry" [5] a SPIP database to another server (base and attachments and skeletons, fcc so the same content already recovered by Mes_Fichiers: read the documentation for this prodigious tool unfortunately only referenced and documented in Nursit! The special case of passing SPIP 3
Version SPIP3est already widely used [6] reliably, and you may want to spend: this is perfectly reasonable, after having understood the implications, because fcc the rollback is almost impossible!
- You should know that significant changes in the structure of database are automatically performed during the update, especially on the management of related keywords [7] an extension of SPIP still considered standard tables: backsliding you require a more complex manipulations, because you would have to completely restore an old basic structure, so with phpMyAdmin or MySQL.
- The system of plugins has also undergone changes related to the integration of Bonuxes and modification of traditional descriptive plugin.xml paquet.xml to become the new version of the plugins are not immediately recognized: check the compatibility of new version with a tested SPIP3 site!
The approach seems advisable taking into account fcc these two main points are as follows: full backup of the site (including IMG - database [8] - skeletons and directory p