ps : ce billet n’est pas encore terminé.
Pourquoi changer de version Drupal ?
La dernière version de Drupal est la 7, actuellement la 7.18.
Votre site est en Drupal 6. Cette version est toujours supportée, càd que le core et les modules de Drupal 6 ont toujours des mises à jour de sécurité.
Drupal 8 est en développement. Il devrait sortir, si tout va bien, dans la 2ème moitié de 2013. Ce n’est pas le sujet de ce billet, mais il faut se souvenir que seulement 2 versions majeures de Drupal sont maintenues. Ça veut dire que, dés la sortie du futur Drupal 8, le core de Drupal 6, les modules et les thèmes ne seront plus supportés.
Si ce n’est pas trop grave pour la correction de bugs. Les modules que vous utilisez depuis des années sont probablement stables.
C’est bien plus gênant pour les éventuelles failles de sécurité ! Une faille importante découverte serait alors corrigée en Drupal 8 et 7, mais plus en version 6.x …
Vous avez donc 3 solutions pour votre site Drupal 6 :
- profiter de la sortie de Drupal 8 pour refaire un site tout neuf, tout beau en D8…
oui, bonne idée… sauf que cela peut prendre plusieurs longs mois pour que les modules intéressants (ne faisant pas parties du core de Drupal 8), soient mis à jour ou réécrit pour D8… Pendant tout ce temps, votre ancien site Drupal 6 peut être vulnérable !
- refaire un nouveau site en Drupal 7, avant la sortie de Drupal 8. De cette façon votre site ne sera pas vulnérable. Il aura toujours ses mises à jour de sécurité
- convertir votre site Drupal 6 en Drupal 7, sans devoir le refaire entièrement, en conservant évidemment son contenu
La 1ère solution n’est pas très réaliste : combien de temps faudra-t-il attendre pour que Drupal 8 et les modules les plus courants soient utilisables ?
La 2ème solution demande un investissement en temps et argent pour refaire un site en Drupal 7. De plus il faudra migrer manuellement le contenu… ou repartir entièrement à zéro avec un site vide… Coûteux et gênant !
La 3ème solution est la plus rapide. Pas besoin de recréer un site, et le contenu devrait être conservé.
C’est la solution que je vais appliquer pour le site de notre Linux Users Group http://culbutte.be/ actuellement en Drupal 6.
Update ou Upgrade ?
On confond souvent les 2 termes. En français, on dirait « mise à jour », mais je ne trouve pas d’expression française différenciant « update » et « upgrade » …
- Un update est une mise à jour « mineure », comme par exemple de Drupal 7.17 vers 7.18. Cela ne pose en général pas de problème si on le fait régulièrement, en suivant les procédures (update.php à la fin), manuellement ou avec Drush. Les modules devraient aussi être mis à jour, si nécessaire.
- Un upgrade est la mise à jour vers une version majeure de Drupal, par exemple de Drupal 6.x vers Drupal 7.x. En même temps que le core de Drupal, il faut également upgrader TOUS les modules et les thèmes.
Vous ne pouvez upgrader que d’une version de Drupal à la suivante. Si vous désirez upgrader un site en Drupal 5 vers D7, il faudra faire en 2 étapes : upgrader de D5 en D6, puis un 2ème upgrade de D6 en D7.
Problèmes courants lors des upgrades Drupal
L’upgrade d’un site Drupal peut se révéler très simple… ou très compliqué, voir impossible. Cela dépend de la complexité de votre site, des modules installés, et des développements que vous avez éventuellement fait.
Les éléments suivants peuvent vous poser problème :
- utilisation de modules qui n’existent pas (ou pas encore) en Drupal 7. Cela demanderait de remplacer le module manquant par un autre, mais la migration des données n’est alors pas automatique
- développements propres : si vous avez vous-même écrit un module, ou modifié le core de Drupal (c’est très très déconseillé) ou modifié un module, il est clair que l’upgrade ne se passera pas sans mal. Au mieux vous devrez réécrire votre module pour qu’il tourne en Drupal 7
- thème non compatible D7 : il faudra choisir un nouveau thème D7, ou adapter votre ancien thème
- utilisation de fonctionnalités n’existant plus, ou fortement modifiées dans Drupal 7. Je pense simplement au module image en Drupal 6. Image a été intégré dans le cœur de Drupal 7. Malgré tout, la migration de nodes de type « image » ne se passe pas toujours si automatiquement que voulu
Dans le cas qui m’intéresse, le site de notre Linux Users Group, c’est ce dernier cas qui va nous poser problème : de nombreux nodes de type « image ».
Backup
Comme pour toutes opérations importantes, TOUJOURS prendre un backup de votre site complet, càd la base de données ET tous vos fichiers (Drupal, modules, thèmes et tous vos fichiers dans /sites ….).
Je conseille même fortement de travailler sur une copie de votre site et de basculer la nouvelle version en opérationnel quand tout sera ok.
Évidemment, cela dépend de votre site. Il est très facile de travailler sur une copie d’un site assez statique (club info, site local) pendant quelques heures et de basculer ensuite.
Par contre, il n’est pas possible de laisser en ligne un site e-Commerce en Drupal 6 le temps de l’upgrade sur une copie, et de basculer ensuite. Cela reviendrait à perdre plusieurs heures de commande lors de la mise en ligne du nouveau site basé sur une copie vieille de plusieurs heures. Dans ce cas, il faut mettre le site en maintenance, de préférence en heures creuses. La nuit ou le WE par exemple.
Mais dans tous les cas, faites un BACKUP avant de commencer quoi que ce soit !
Upgrade « manuel »
La méthode la plus logique est de se lancer dans l’upgrade de votre site Drupal 6 manuellement, pas à pas.
En résumé, les étapes seraient :
- prendre un backup complet
- mettre le site en mode maintenance
- updater votre site à la dernière version stable de Drupal 6
- updater tous les modules « contributed » si nécessaire
- basculer sur le thème Drupal 6 par défaut (Garland)
- désinstaller et supprimer les modules inactifs qui ne sont plus nécessaire
- vérifier que votre site Drupal 6 fonctionne toujours correctement après ces étapes, AVANT l’upgrade en Drupal 7
- etc etc
Ce n’est pas cette méthode que je vais utiliser, mais vous pouvez trouver des infos plus détaillées sur Drupal.org, en particulier la page « Upgrade process« .
Upgrade avec Drush
Source
Je me base sur l’excellent article de Moshe Weitzman, d’Acquia : Use Drush to Upgrade from Drupal 6 to Drupal 7
Moshe explique la procédure d’upgrade de Drupal 6 vers 7 avec une seule commande « drush site-upgrade »
Drush
Drush est un utilitaire qui peut être exécuté en ligne de commande en Linux ou Windows. Ce n’est donc pas réellement un module Drupal.
Drush permet d’exécuter beaucoup de commandes directement depuis la ligne de commande sur votre serveur. C’est très utile pour automatiser des opérations sur vos sites, des mises à jour ou vos installations.
Drush est la contraction de « DRUpal » et « SHell« .
Si vous ne l’avez pas encore installé, vous le trouverez sur la page du projet Drush
sur drupal.org. Pour toute autre info sur l’installation de Drush ou son utilisation, voir les liens documentation en bas de cet article.
Extension de Drush
Avant de vous lancer dans l’upgrade de votre site Drupal, vérifier que vous avez la dernière version de Drush.
La version actuelle est indiquée 7.X-5.8.
Ne vous préoccupez pas de ce « 7.x ». C’est la version 5.8 de Drush, compatible avec les sites Drupal 7 et 6.
Drush contient déjà de base de nombreuses commandes très puissantes et pratiques, par exemple pour mettre à jour Drupal, installer et activer des modules, etc, mais rien pour l’upgrade d’un site Drupal.
Drush a été conçu pour pouvoir être étendu facilement. Certaines extensions de Drush lui apporte des commandes supplémentaires propres à un module, par exemple pour la gestion des langues et traductions.
Ici, nous allons installer l’extension « Drush Site Upgrade » .
Pas besoin de télécharger le fichier compressé, de le transférer, le décompresser… Non, Drush fait tout cela pour vous.
Il suffit de lui demander d’installer le « module » drush_sup.
# drush dl drush_sup
Project drush_sup (7.x-2.0-beta1) downloaded to /root/.drush/drush_sup. [success]
Project drush_sup contains 0 modules: .
Le « contains 0 modules » est normal car drush_sup n’est pas un module Drupal, mais une extension à Drush lui-même.
Drush propose maintenant des commandes pour l’upgrade de votre site web :
# drush
Other commands: (make,upgrade)
make Turns a makefile into a working Drupal codebase.
make-generate Generate a makefile from the current Drupal site.
(generate-makefile)
site-upgrade (sup) Run a major version upgrade for Drupal (e.g. Drupal 6 to Drupal 7). A copy of the site is made, and then upgraded;
the source site is not changed.
site-upgrade-progres Show information about the upgrade status of the target site.
s (upgrade-progress,
supp)
La commande « drush site-upgrade » a été ajoutée.
Upgradez une copie de votre site
Site-upgrade ne travaille jamais sur votre site Drupal 6. Il crée un nouveau site Drupal 7 au départ de votre site original D6.
Il est donc sans risque de lancer l’upgrade sur un site on-line. Le site D6 ne sera pas modifié et vous aurez en parallèle un nouveau site, migré en D7.
Drush alias
Pour copier votre site, vous aurez besoin d’une nouvelle data base MySQL et d’un nouveau dossier, mais même cela, drush site-upgrade peut le faire pour vous !
Il vous suffit de créer un alias avec les informations nécessaires.
J’avais installé Drush dans le dossier /root/drush. Dans le sous-dossier « examples » se trouve un fichier « example.aliases.drushrc.php« . Vous pouvez vous en servir comme base pour créer votre alias Drush.
Je vais exécuter le site-upgrade avec le userid Linux « root ».
S’il n’existe pas encore, créez un sous-dossier /root/.drush
# cd /root
# mkdir .drush
Dans ce dossier, créez un fichier « aliases.drushrc.php » et copiez y les informations pour votre nouveau site Drupal 7 :
# cd /root/.drush
# vi aliases.drushrc.php
Ma nouvelle DB Mysql sera dm_d7newculbutte. Le dossier sera /home/dug/www/d7new.culbutte.be.
L’URL, provisoirement définie dans le DNS, sera « d7new.culbutte.be ».
<?php
$aliases['d7new'] = array(
'root' => '/home/dug/www/d7new.culbutte.be',
'uri' => 'http://d7new.culbutte.be',
);
?>
L’information pour la nouvelle DB n’est pas dans l’alias. Le script « drush site-upgrade » me demandera le mot de passe root de MySQL pour créer lui-même une base de données.
Pourquoi « d7new… » et pas simplement « d7.culbutte.be » ?
Car c’est mon 2ème essais de migration du site. J’ai en effet eu quelques problèmes…
Problème de migration des nodes D6 de type image
En théorie, il ne reste plus qu’à lancer la commande « drush site-upgrade« , mais ne le faites pas encore !
Lors de mon 1er essais de migration, j’ai eu des problèmes dans le nouveau site Drupal 7 avec tous les nodes de type image.
Voici un node image en Drupal 6 :
Et voici le node après migration en Drupal 7 :
Il y a un problème. Le node affiche 2 messages d’erreur :
Notice : Undefined index: comment_node_image_form dans drupal_retrieve_form()
(ligne 763 dans /home/dug/www/d7.culbutte.be/includes/form.inc).
Warning : call_user_func_array() expects parameter 1 to be a valid callback,
function 'comment_node_image_form' not found or invalid function name dans
drupal_retrieve_form() (ligne 798 dans /home/dug/www/d7.culbutte.be/includes/form.inc).
On retrouve ces erreurs listées dans les entrées récentes du journal, dans les rapports.
L’image principale, celle qui sert à la création du node image, a disparue.
Les images suivantes ont été ajoutées avec l’éditeur Wysiwyg et elles sont correctement affichées.
En conséquence, toutes mes galeries photos ont disparu lors de la migration ! …
Bug de migration des nodes image.
Je fais une recherche Google sur « drupal Undefined index: comment_node_image_form dans drupal_retrieve_form()« .
Le 1er lien est Image module migration, qui me semble très intéressant.
C’est un très long fil de commentaires, commencé en novembre 2010, et terminé en août 2012. La solution à ce problème se trouve dans un des derniers commentaires.
Il faut faire tourner un patch sur tous les nodes de type « image » du site Drupal 6, AVANT la migration !
Ce patch a été écrit par Drew Gorton.
C’est du code PHP. Vous ne pouvez pas faire tourner simplement ce code dans un page Web, car alors aucune indication de la DB, du site Web ni des nodes à traiter ne sera présente.
Il faut inclure ce code PHP dans une page de votre site Drupal 6.
Pour cela, le plus simple est d’ajouter le module « devel ».
Module Devel
Pour installer le module Devel, vous pouvez bien évidemment utiliser Drush :
# cd /home/dug/www/d6.culbutte.be/sites/culbutte.be/
# drush dl devel
Project devel (6.x-1.27) downloaded to /home/dug/www/d6.culbutte.be/sites/all/modules/devel. [success]
Project devel contains 3 modules: devel, devel_node_access, devel_generate.
# drush en devel
The following extensions will be enabled: devel
Do you really want to continue? (y/n): y
devel was enabled successfully. [ok]
FirePHP has been exported via svn to [success]
/home/dug/www/d6.culbutte.be/sites/all/modules/devel/FirePHPCore.
Le module Devel donne la possibilité d’exécuter du code PHP dans vos nodes.
Je vais créer une page bidon pour y insérer le code PHP nécessaire pour préparer la migration des nodes images.
J’appelle, par exemple, cette page « patchd6 » . Un simple texte de quelques mots suffit.
La page est publiée, mais pas dans un menu.
L’exécution de code PHP avec Devel se fait en ajoutant un bloc dans la page.
Je vais donc dans les blocs du site Drupal 6.
Je trouve le bloc avec « Exécuter du code PHP », et je commence par le configurer.
J’autorise l’affichage de ce bloc PHP pour l’administrateur, et PAS pour les utilisateurs normaux, et j’indique le nom de ma page temporaire « content/pathd6 » .
Je sauve le bloc et je reviens à la page générale de tous les blocs.
et je positionne ce bloc PHP dans le contenu.
Exécution du patch PHP pour la migration des nodes image.
Je peux maintenant afficher ma page patchd6. Le bloc exécuter du code PHP doit se trouver en dessous du contenu.
Je reprend le code PHP de la correction proposée par Drew Gorton.
Voici ce code PHP :
<?php
$query = "SELECT * FROM {image} WHERE image_size = '_original'";
$result = db_query($query);
while ($row = db_fetch_array($result, MYSQL_ASSOC)) {
$fid = $row['fid'];
$nid = $row['nid'];
$file_query = "SELECT * FROM {files} WHERE fid = " . $fid;
$file_result = db_query($file_query);
$image_file = db_fetch_array($file_result);
if ( $image_file[2] != '_original') {
watchdog("Image Fix", "Fixing image node %nid for fid %fid", array('%nid' => $nid, '%fid' => $fid), WATCHDOG_NOTICE, l('view', 'node/'.$nid));
// Un-comment the next line to actually run the query!
// $fix = db_query("UPDATE {files} SET filename = '_original' WHERE fid = " . $fid);
}
}
?>
Copiez ce code, SANS la balise. Donc vous ne copiez pas les 1ère et dernière lignes.
Collez ce code dans le bloc « Exécuter du code PHP » de la page patchd6.
Cela doit donner ceci :
Vous remarquez qu’un des lignes est en commentaire.
Cela va nous permettre de vérifier que le code tourne correctement, sans erreur.
Cliquer sur « Exécuter« .
Vous devez voir dans les rapports, dans Écritures récentes du journal, la trace de tous les nodes image qui ont été parcourus :
Si tout est ok, que le script parcourt bien vos nodes images, il vous reste à décommenter la ligne pour les update DB.
// Un-comment the next line to actually run the query!
$fix = db_query("UPDATE {files} SET filename = '_original' WHERE fid = " . $fid);
et à cliquer sur « Exécuter« .
Vérifier dans les activités récentes du journal si cette exécution s’est bien passée.
Si tout est ok, on peut passer à la commande de migration elle-même.
Drush site-upgrade
Lançons la commande « drush site-upgrade ».
Vous devez être en root (ou dans un userid qui a les droits sur vos dossiers Web) et dans le dossier de votre ancien site Drupal 6. Utilisez l’alias que vous avez défini (ici, @d7new).
# cd /home/dug/www/d6.culbutte.be/sites/culbutte.be/
# drush site-upgrade @d7new
Si le dossier de destination existe, drush demande si il doit réutiliser ou supprimer ce site. Il est préférable de partir à 0. La procédure va créer elle-même le dossier de destination pour votre nouveau site D7.
Gathering information about core and contrib modules...
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 1
1. Check on the Drupal 7 status of your contributed and custom modules and themes. See
http://drupal.org/node/948216 for information on upgrading contributed modules and themes. See
http://drupal.org/node/895314 for a list of modules that have been moved into core for Drupal 7, and instructions
on how to update them. See http://drupal.org/update/modules for information on how to update your custom modules,
and http://drupal.org/update/theme for custom themes.
You may decide at this point that you cannot upgrade your site, because needed modules or themes are not ready
for Drupal 7.
Project Titre Installed Available Statut
advanced_help Advanced help 6.x-1.2 7.x-1.0 Recommended
backup_migrate Backup and Migrate 6.x-2.6 7.x-2.4 Recommended
comment_notify Comment Notify 6.x-1.6 7.x-1.1 Recommended
emfield Embedded Wave Field 6.x-1.26 7.x-1.0-alpha2 Recommended
getid3 getID3() 6.x-1.5 7.x-1.0 Recommended
globalredirect Global Redirect 6.x-1.5 - NO 7.x RELEASES; using
redirect
imce IMCE 6.x-2.4 7.x-1.6 Recommended
lightbox2 Lightbox2 6.x-1.11 7.x-1.0-beta1 Recommended
mollom Mollom 6.x-1.16 7.x-2.3 Recommended
pathauto Pathauto 6.x-2.0 7.x-1.2 Recommended
token Token actions 6.x-1.19 7.x-1.4 Recommended
transliteration Transliteration 6.x-3.1 7.x-3.1 Recommended
cck User Reference 6.x-2.9 7.x-2.x-dev Supported,Development
link Link 6.x-2.9 7.x-1.0 Recommended
location User Locations 6.x-3.2 7.x-5.x-dev Recommended
drupal Garland 6.27 7.18 Recommended
calendar Calendar Popup 6.x-2.4 7.x-3.4 Recommended
date Date Tools 6.x-2.9 7.x-2.6 Recommended
devel Devel 6.x-1.27 7.x-1.3 Recommended
image ImageMagick Advanced 6.x-1.2 7.x-1.x-dev Supported,Development
Options
imagecache_actions Imagecache Text Actions 6.x-1.9 7.x-1.1 Recommended
gmap GMap Taxonomy Markers 6.x-1.1 7.x-2.3-alpha2 Recommended
l10n_update Localization update 6.x-1.0-beta3 7.x-1.0-beta3 Recommended
google_analytics Google Analytics 6.x-3.5 7.x-2.x-dev Recommended
jquery_plugin jQuery plugins 6.x-1.10 7.x-1.0 Recommended
jquery_update jQuery Update 6.x-1.1 7.x-2.3-alpha1 Recommended
views Views UI 6.x-2.16 7.x-3.5 Recommended
xmlsitemap XML sitemap user 6.x-1.2 7.x-2.0-rc2 Recommended
redirect Redirect (globalredirect) 7.x-1.0-rc1 Recommended
bundle_copy Bundle copy (content_copy) 7.x-2.x-dev Recommended
field_permissions Field Permissions (content_permissions) 7.x-1.0-beta2 Recommended
field_group Field group (fieldgroup) 7.x-2.x-dev Recommended
ctools Chaos tool suite (ctools) (views_export) 7.x-1.2 Recommended
references References (nodereference,userrefere 7.x-2.0 Recommended
nce)
Special notes about some of the projects you are using:
cck : The module nodereference in this project has no D7 version available, but there are multiple alternative
projects that may be used instead. Drush picked references:node_reference, but entityreference also
available. Run again with --preferred to select a different preference.
cck : The module userreference in this project has no D7 version available, but there are multiple alternative
projects that may be used instead. Drush picked references:user_reference, but entityreference also
available. Run again with --preferred to select a different preference.
cck : This project requires data migration or other special processing. Please see http://drupal.org/project/cck
and http://drupal.org/node/895314 for more information on how to do this.
tok : This project requires data migration or other special processing. In Drupal 7, the contrib token module
en handles UI, as well as field and profile tokens; all other functionality has been migrated to core. You may
encounter problems when enabling the token module during a major upgrade; see
http://drupal.org/node/1477932.
dat : This project requires data migration or other special processing. The d6 version of the date_api module in
e the date project defines a table called date_formats, which is also defined by system/system.install schema
in d7. If this problem has not been fixed yet, then the updatedb function will fail, and it will not be
possible to upgrade to d7. If this happens, disable and uninstall the date_api module before running
site-upgrade (i.e. add '--uninstall=date_api' to site-upgrade call). See http://drupal.org/node/1013034.
glo : globalredirect: this project has been replaced by the project redirect. The new project will be downloaded
bal automatically.
red
ire
ct
Please review the upgread readiness report. You may want to uninstall modules that are not ready to upgrade yet.
[0] : Cancel
[1] : Begin upgrade
1
Il y a des warnings, des modules remplacés (par exemple, GlobalRedirect en D6 est remplacé par le module Redirect, qui sera téléchargé automatiquement), mais on peut continuer.
Rappellez-vous qu’on ne risque rien ! Le site original D6 n’est pas modifié. Au pire, on recommence après correction.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 2
2. Update to the latest available version of Drupal 6.x (if your current version is Drupal 5.x, you have to
upgrade to 6.x first). If you need to update, download Drupal 6.x and follow the instructions in its UPGRADE.txt.
This document only applies for upgrades from 6.x to 7.x.
You must also insure that all of your contrib modules are up to date!
Drupal core is up-to-date; version 6.27 installed.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 3
3. Log in as user ID 1 (the site maintenance user).
You will not need to log in if Drush is used to perform all upgrade steps for you.
Skipping optional step.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 4
4. Go to Administer > Site configuration > Site maintenance. Select "Off-line" and save the configuration.
When Drush does the steps of your site upgrade, it always modifies the working copy of your site; the original
site is left unchanged. You may wish to take your site off-line anyway.
Skipping optional step.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 5
5. Go to Administer > Site building > Themes. Enable "Garland" and select it as the default theme.
Drush will set the administrative theme to "Garland" in the target site without affecting the source site.
Skipping optional step.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 6
6. Go to Administer > Site building > Modules. Disable all modules that are not listed under "Core - required"
or "Core - optional". It is possible that some modules cannot be disabled, because others depend on them. Repeat
this step until all non-core modules are disabled.
If you know that you will not re-enable some modules for Drupal 7.x and you no longer need their data, then you
can uninstall them under the Uninstall tab after disabling them.
Drush will automatically disable all non-core modules in the target site without affecting the source site. You
may disable or uninstall contrib modules now if you wish; any that you do not do now will be disabled by Drush
after Step 12.
Skipping optional step.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 7
7. On the command line or in your FTP client, remove the file
sites/default/default.settings.php
Drush will remove default.settings.php from the target site later, after Step 12. You may remove it from the
source sit now if you wish, but doing so is unnecessary.
Skipping optional step.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 8
8. Remove all old core files and directories, except for the 'sites' directory and any custom files you added
elsewhere.
If you made modifications to files like .htaccess or robots.txt, you will need to re-apply them from your backup,
after the new files are in place.
Drush will create your upgraded site in a new location; it is not necessary to remove any core files from the
source site.
Skipping optional step.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 9
9. If you uninstalled any modules, remove them from the sites/all/modules and other sites/*/modules directories.
Leave other modules in place, even though they are incompatible with Drupal 7.x.
Drush will create your upgraded site in a new location; it is not necessary to remove any contrib module files
from the source site.
Skipping optional step.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 10
10. Download the latest Drupal 7.x release from http://drupal.org to a directory outside of your web root.
Extract the archive and copy the files into your Drupal directory.
On a typical Unix/Linux command line, use the following commands to download and extract:
wget http://drupal.org/files/projects/drupal-x.y.tar.gz tar -zxvf drupal-x.y.tar.gz
This creates a new directory drupal-x.y/ containing all Drupal files and directories. Copy the files into your
Drupal installation directory:
cp -R drupal-x.y/* drupal-x.y/.htaccess /path/to/your/installation
If you do not have command line access to your server, download the archive from http://drupal.org using your web
browser, extract it, and then use an FTP client to upload the files to your web root.
Drush will automatically do this step now.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 11
11. Re-apply any modifications to files such as .htaccess or robots.txt.
If you had no modifications to .htaccess or robots.txt, you don't need to do anything here.
Drush cannot do this step; you must perform it manually.
What would you like to do?
[0] : Cancel
[1] : I will do this step manually.
[2] : Skip this step.
Si j’ai modifié les fichiers .htaccess ou robots.txt, je devrais refaire ces modifications manuellement.
Ce n’est pas mon cas. Je continue (2 : skip this step).
2</pre>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 12
12. Make your settings.php file writeable, so that the update process can convert it to the format of Drupal
7.x. settings.php is usually located in
sites/default/settings.php
Note that Drush will instead *copy* your settings.php file to its new location. The copy is made writable, but
the original may remain write-protected.
Drush will automatically do this step now.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 12-a
12-a. Drush-specific step: Drush will now do steps 5 and 6 of UPGRADE.txt, and set the site theme to Garland and
disable all contrib modules. Before it does this, it makes a copy of your database, and does all modifications on
the *copy*, leaving your source site unchanged. Drush will also uninstall all modules specified via the
--uninstall option at this time.
Drush will automatically do this step now.
You will destroy data in d7newdb and replace with data from dm_d7culbutte.
You might want to make a backup first, using the sql-dump command.
Do you really want to continue? (y/n): y
Le script de mise à jour va maintenant désactiver tous les modules D6 « Contrib » .
Disabling advanced_help, backup_migrate, comment_notify, eminline, getid3, globalredirect, imce, lightbox2,[ok]
mollom, pathauto, token, token_actions, transliteration, content, content_copy, content_permissions,
emaudio, emimage, emfield, emthumb, emvideo, emwave, fieldgroup, filefield, filefield_meta, imagefield,
link, location_cck, nodereference, number, optionwidgets, text, userreference, aggregator, blog, color,
comment, contact, translation, dblog, forum, help, locale, menu, path, ping, profile, search, statistics,
syslog, taxonomy, tracker, update, upload, block, filter, node, system, user, calendar, calendar_ical,
jcalendar, date, date_api, date_locale, date_php4, date_popup, date_repeat, date_timezone, date_tools,
devel, image, image_attach, image_gallery, image_import, image_im_advanced, imageapi, imageapi_gd,
imageapi_imagemagick, imagecache, imagecache_canvasactions, imagecache_coloractions,
imagecache_customactions, imagecache_textactions, imagecache_ui, gmap, gmap_location, gmap_macro_builder,
gmap_taxonomy, location, location_addanother, location_fax, location_phone, location_search, location_node,
location_user, l10n_update, googleanalytics, jquery_plugin, jquery_ui, jquery_update, views, views_export,
views_ui, xmlsitemap, xmlsitemap_engines, xmlsitemap_node, xmlsitemap_taxonomy, xmlsitemap_user, garland
garland is the default theme and can't be disabled. [ok]
block is a required module and can't be disabled. [ok]
filter is a required module and can't be disabled. [ok]
node is a required module and can't be disabled. [ok]
system is a required module and can't be disabled. [ok]
user is a required module and can't be disabled. [ok]
The following extensions will be disabled: advanced_help, backup_migrate, comment_notify, eminline, getid3, globalredirect, imce, lightbox2, mollom, pathauto, token, token_actions, transliteration, content, content_copy, content_permissions, emaudio, emimage, emfield, emthumb, emvideo, emwave, fieldgroup, filefield, filefield_meta, imagefield, link, location_cck, nodereference, number, optionwidgets, text, userreference, aggregator, blog, color, comment, contact, translation, dblog, forum, help, locale, menu, path, ping, profile, search, statistics, syslog, taxonomy, tracker, update, upload, calendar, calendar_ical, jcalendar, date, date_api, date_locale, date_php4, date_popup, date_repeat, date_timezone, date_tools, devel, image, image_attach, image_gallery, image_import, image_im_advanced, imageapi, imageapi_gd, imageapi_imagemagick, imagecache, imagecache_canvasactions, imagecache_coloractions, imagecache_customactions, imagecache_textactions, imagecache_ui, gmap, gmap_location, gmap_macro_builder, gmap_taxonomy, location, location_addanother, location_fax, location_phone, location_search, location_node, location_user, l10n_update, googleanalytics, jquery_plugin, jquery_ui, jquery_update, views, views_export, views_ui, xmlsitemap, xmlsitemap_engines, xmlsitemap_node, xmlsitemap_taxonomy, xmlsitemap_user
Do you really want to continue? (y/n): y
aggregator was disabled successfully. [ok]
blog was disabled successfully. [ok]
color was disabled successfully. [ok]
comment was disabled successfully. [ok]
contact was disabled successfully. [ok]
dblog was disabled successfully. [ok]
forum was disabled successfully. [ok]
help was disabled successfully. [ok]
locale was disabled successfully. [ok]
menu was disabled successfully. [ok]
path was disabled successfully. [ok]
ping was disabled successfully. [ok]
profile was disabled successfully. [ok]
search was disabled successfully. [ok]
statistics was disabled successfully. [ok]
syslog was disabled successfully. [ok]
taxonomy was disabled successfully. [ok]
tracker was disabled successfully. [ok]
translation was disabled successfully. [ok]
update was disabled successfully. [ok]
upload was disabled successfully. [ok]
advanced_help was disabled successfully. [ok]
backup_migrate was disabled successfully. [ok]
calendar was disabled successfully. [ok]
calendar_ical was disabled successfully. [ok]
jcalendar was disabled successfully. [ok]
content was disabled successfully. [ok]
content_copy was disabled successfully. [ok]
content_permissions was disabled successfully. [ok]
fieldgroup was disabled successfully. [ok]
nodereference was disabled successfully. [ok]
number was disabled successfully. [ok]
optionwidgets was disabled successfully. [ok]
text was disabled successfully. [ok]
userreference was disabled successfully. [ok]
comment_notify was disabled successfully. [ok]
date was disabled successfully. [ok]
date_api was disabled successfully. [ok]
date_locale was disabled successfully. [ok]
date_php4 was disabled successfully. [ok]
date_popup was disabled successfully. [ok]
date_repeat was disabled successfully. [ok]
date_timezone was disabled successfully. [ok]
date_tools was disabled successfully. [ok]
devel was disabled successfully. [ok]
emaudio was disabled successfully. [ok]
emimage was disabled successfully. [ok]
eminline was disabled successfully. [ok]
emthumb was disabled successfully. [ok]
emvideo was disabled successfully. [ok]
emwave was disabled successfully. [ok]
emfield was disabled successfully. [ok]
filefield was disabled successfully. [ok]
filefield_meta was disabled successfully. [ok]
getid3 was disabled successfully. [ok]
globalredirect was disabled successfully. [ok]
gmap was disabled successfully. [ok]
gmap_location was disabled successfully. [ok]
gmap_macro_builder was disabled successfully. [ok]
gmap_taxonomy was disabled successfully. [ok]
googleanalytics was disabled successfully. [ok]
image_attach was disabled successfully. [ok]
image_gallery was disabled successfully. [ok]
image_import was disabled successfully. [ok]
image_im_advanced was disabled successfully. [ok]
image was disabled successfully. [ok]
imageapi was disabled successfully. [ok]
imageapi_gd was disabled successfully. [ok]
imageapi_imagemagick was disabled successfully. [ok]
imagecache was disabled successfully. [ok]
imagecache_ui was disabled successfully. [ok]
imagecache_canvasactions was disabled successfully. [ok]
imagecache_coloractions was disabled successfully. [ok]
imagecache_customactions was disabled successfully. [ok]
imagecache_textactions was disabled successfully. [ok]
imagefield was disabled successfully. [ok]
imce was disabled successfully. [ok]
jquery_plugin was disabled successfully. [ok]
jquery_ui was disabled successfully. [ok]
jquery_update was disabled successfully. [ok]
l10n_update was disabled successfully. [ok]
lightbox2 was disabled successfully. [ok]
link was disabled successfully. [ok]
location_addanother was disabled successfully. [ok]
location_cck was disabled successfully. [ok]
location_fax was disabled successfully. [ok]
location_phone was disabled successfully. [ok]
location_search was disabled successfully. [ok]
location was disabled successfully. [ok]
location_node was disabled successfully. [ok]
location_user was disabled successfully. [ok]
mollom was disabled successfully. [ok]
pathauto was disabled successfully. [ok]
token was disabled successfully. [ok]
token_actions was disabled successfully. [ok]
transliteration was disabled successfully. [ok]
views was disabled successfully. [ok]
views_export was disabled successfully. [ok]
views_ui was disabled successfully. [ok]
xmlsitemap was disabled successfully. [ok]
xmlsitemap_engines was disabled successfully. [ok]
xmlsitemap_node was disabled successfully. [ok]
xmlsitemap_taxonomy was disabled successfully. [ok]
xmlsitemap_user was disabled successfully. [ok]
Uninstalling [ok]
There were no modules that could be uninstalled. [ok]
Ensuite, toutes les mises à jour disponibles :
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 12-b
12-b. Drush-specific step: Drush will now do step 7 of UPGRADE.txt, and remove
sites/default/default.settings.php from the target site.
Drush will automatically do this step now.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 13
13. Run update.php by visiting http://www.example.com/update.php (replace www.example.com with your domain
name). This will update the core database tables.
If you are unable to access update.php do the following:
- Open settings.php with a text editor.
- Find the line that says: $update_free_access = FALSE;
- Change it into: $update_free_access = TRUE;
- Once the upgrade is done, $update_free_access must be reverted to FALSE.
Note that Drush will copy your database and run updatedb on the copy. The source database remains unchanged.
Drush will automatically do this step now.
The following updates are pending:
system module :
7000 - Rename blog and forum permissions to be consistent with other content types.
7001 - Generate a cron key and save it in the variables table.
7002 - Add a table to store blocked IP addresses.
7003 - Update {blocked_ips} with valid IP addresses from {access}.
7004 - Remove hardcoded numeric deltas from all blocks in core.
7005 - Remove throttle columns and variables.
7007 - Convert to new method of storing permissions.
7009 - Rename the variable for primary links.
7011 - Split the 'bypass node access' permission from 'administer nodes'.
7013 - Convert default time zone offset to default time zone name.
7015 - Change the user logout path.
7016 - Remove custom datatype _unsigned in PostgreSQL.
7017 - Change the theme setting 'toggle_node_info' into a per content type variable.
7018 - Shorten the {system}.type column and modify indexes.
7020 - Enable field and field_ui modules.
7021 - Change the PHP for settings permission.
7027 - Enable field type modules.
7029 - Add new 'view own unpublished content' permission for authenticated users. Preserves legacy behavior from Drupal 6.x.
7032 - Alter field hostname to identifier in the {flood} table.
7033 - Move CACHE_AGGRESSIVE to CACHE_NORMAL.
7034 - Migrate the file path settings and create the new {file_managed} table.
7036 - Split the 'access site in maintenance mode' permission from 'administer site configuration'.
7042 - Upgrade the {url_alias} table and create a cache bin for path aliases.
7044 - Drop the actions_aid table.
7045 - Add expiration field to the {flood} table.
7046 - Switch from the Minnelli theme if it is the default or admin theme.
7047 - Normalize the front page path variable.
7048 - Convert path languages from the empty string to LANGUAGE_NONE.
7049 - Rename 'Default' profile to 'Standard.'
7050 - Change {batch}.id column from serial to regular int.
7051 - make the IP field IPv6 compatible
7052 - Rename file to include_file in {menu_router} table.
7053 - Upgrade standard blocks and menus.
7054 - Remove {cache_}.headers columns.
7055 - Converts fields that store serialized variables from text to blob.
7057 - Increase the size of session-ids.
7058 - Remove cron semaphore variable.
7059 - Create the {file_usage} table.
7060 - Create fields in preparation for migrating upload.module to file.module.
7061 - Migrate upload.module data to the newly created file field.
7062 - Replace 'system_list' index with 'bootstrap' index on {system}.
7063 - Delete {menu_links} records for 'type' => MENU_CALLBACK which would not appear in a fresh install.
7064 - Remove block_callback field from {menu_router}.
7065 - Remove the default value for sid.
7066 - Migrate the 'file_directory_temp' variable.
7067 - Grant administrators permission to view the administration theme.
7068 - Update {url_alias}.language description.
7069 - Remove the obsolete 'site_offline' variable. @see update_fix_d7_requirements()
7070 - Remove the obsolete 'drupal_badge_color' and 'drupal_badge_size' variables.
7071 - Add index missed during upgrade, and fix field default.
7072 - Remove the obsolete 'site_offline_message' variable. @see update_fix_d7_requirements()
7073 - Add binary to {file_managed}, in case system_update_7034() was run without it.
7074 - This update has been removed and will not run.
7076 - Convert menu_links query strings into arrays.
7077 - Revert {file_managed}.filename changed to a binary column.
aggregator module :
7000 - Add hash column to aggregator_feed table.
7001 - Add aggregator teaser length to settings from old global default teaser length
7002 - Add queued timestamp.
7003 - Increase the length of {aggregator_feed}.url.
block module :
7000 - Set system.weight to a low value for block module. Block should go first so that other modules can alter its output during hook_page_alter(). Almost everything on the page is a block, so before block module runs, there will not be much to alter.
7002 - Rename {blocks} table to {block}, {blocks_roles} to {block_role} and {boxes} to {block_custom}.
7003 - Change the weight column to normal int.
7004 - Add new blocks to new regions, migrate custom variables to blocks.
7005 - Update the {block_custom}.format column.
7006 - Recreates cache_block table. Converts fields that hold serialized variables from text to blob. Removes 'headers' column.
7007 - Change {block_custom}.format into varchar.
7008 - Update database to match Drupal 7 schema.
color module :
7001 - Warn site administrator if unsafe CSS color codes are found in the database.
comment module :
7000 - Rename comment display setting variables.
7001 - Change comment status from published being 0 to being 1
7002 - Rename {comments} table to {comment} and upgrade it.
7003 - Split {comment}.timestamp into 'created' and 'changed', improve indexing on {comment}.
7004 - Upgrade the {node_comment_statistics} table.
7005 - Create the comment_body field.
7006 - Migrate data from the comment field to field storage.
7007 - Add an index to the created column.
7008 - Update database to match Drupal 7 schema.
7009 - Change the last_comment_timestamp column description.
contact module :
7000 - Rename the threshold limit variable.
7001 - Rename the administer contact forms permission.
7002 - Enable the 'access user contact forms' for registered users by default.
7003 - Change the weight column to normal int.
dblog module :
7001 - Update the {watchdog} table.
filter module :
7000 - Upgrade the {filter_formats} table and rename it to {filter_format}.
7001 - Break out "escape HTML filter" option to its own filter.
7003 - Upgrade the {filter} table for core filters.
7005 - Integrate text formats with the user permissions system. This function converts text format role assignments to use the new text format permissions introduced in Drupal 7, creates a fallback (plain text) format that is available to all users, and explicitly sets the text format in cases that used to rely on a single site-wide default.
7008 - Grant usage of all text formats to user roles having the 'administer filters' permission.
7009 - Converts fields that store serialized variables from text to blob.
7010 - Change {filter_format}.format and {filter}.format into varchar.
forum module :
7000 - Add new index to forum table.
7001 - Create new {forum_index} table.
7002 - Add new index to forum_index table.
7003 - Rename field to 'taxonomy_forums'.
7011 - Update {forum_index} so that only published nodes are indexed.
7012 - Add 'created' and 'last_comment_timestamp' indexes.
image module :
7000 - Install the schema for users upgrading from the contributed module.
7001 - Rename possibly misnamed {image_effect} table to {image_effects}.
7002 - Add width and height columns to image field schema and populate.
7003 - Remove the variables that set alt and title length since they were not used for database column size and could cause PDO exceptions.
7004 - Use a large setting (512 and 1024 characters) for the length of the image alt and title fields.
locale module :
7000 - Add context field index and allow longer location.
7001 - Upgrade language negotiation settings.
7002 - Updates URL language negotiation by adding the URL fallback detection method.
7003 - Update "language_count" variable.
7004 - Remove duplicates in {locales_source}.
7005 - Increase {locales_languages}.formula column's length.
menu module :
7000 - Migrate the "Default menu for content" setting to individual node types.
7001 - Rename "Primary Links" and "Secondary Links" to their Drupal 7 equivalents.
7002 - Rename the primarysecondary menu blocks to match previously renamed menus.
7003 - Add missing custom menus to active menus list.
node module :
7000 - Upgrade the node type table and fix node type 'module' attribute to avoid name-space conflicts.
7001 - Rename {node_revisions} table to {node_revision}.
7002 - Extend the node_promote_status index to include all fields required for the node page query.
7003 - Remove the node_counter if the statistics module is uninstalled.
7004 - Extend the existing default preview and teaser settings to all node types.
7005 - Add statuscommentpromote and sticky columns to the {node_revision} table.
7006 - Convert body and teaser from node properties to fields, and migrate statuscommentpromote and sticky columns to the {node_revision} table.
7007 - Remove column min_word_count.
7008 - Split the 'administer nodes' permission from 'access content overview'.
7009 - Convert node languages from the empty string to LANGUAGE_NONE.
7010 - Add the {block_node_type} table.
7011 - Update the database from Drupal 6 to match the schema.
7012 - Switches body fields to untranslatable while upgrading from D6 and makes them language neutral.
7013 - Change {node}.vid default value from 0 to NULL to avoid deadlock issues on MySQL.
profile module :
7001 - Rename {profile_fields} table to {profile_field} and {profile_values} to {profile_value}.
7002 - Change the weight column to normal int.
search module :
7000 - Replace unique keys in 'search_dataset' and 'search_index' by primary keys.
statistics module :
7000 - Update the {accesslog}.sid column to match the length of {sessions}.sid
taxonomy module :
7001 - Rename taxonomy tables.
7002 - Add {vocabulary}.machine_name column.
7003 - Remove the related terms setting from vocabularies. This setting has not been used since Drupal 6. The {taxonomy_relations} table itself is retained to allow for data to be upgraded.
7004 - Move taxonomy vocabulary associations for nodes to fields and field instances.
7005 - Migrate {taxonomy_term_node} table to field storage. @todo: This function can possibly be made much faster by wrapping a transaction around all the inserts.
7006 - Add {taxonomy_term_data}.format column.
7007 - Add index on {taxonomy_term_data}.name column to speed up taxonomy_get_term_by_name().
7008 - Change the weight columns to normal int.
7009 - Change {taxonomy_term_data}.format into varchar.
7010 - Change {taxonomy_index}.created to support signed int.
text module :
7000 - Change text field 'format' columns into varchar.
tracker module :
7000 - Create new tracker_node and tracker_user tables.
update module :
7000 - Create a queue to store tasks for requests to fetch available update data.
7001 - Recreates cache_update table. Converts fields that hold serialized variables from text to blob. Removes 'headers' column.
user module :
7000 - Increase the length of the password field to accommodate better hashes. Also re-hashes all current passwords to improve security. This may be a lengthy process, and is performed batch-wise.
7001 - Remove the 'threshold', 'mode' and 'sort' columns from the {users} table. These fields were previously used to store per-user comment settings.
7002 - Convert user time zones from time zone offsets to time zone names.
7003 - Update user settings for cancelling user accounts. Prior to 7.x, users were not able to cancel their accounts. When administrators deleted an account, all contents were assigned to uid 0, which is the same as the 'user_cancel_reassign' method now.
7005 - Changes the users table to allow longer e-mail addresses.
7006 - Add module data to {role_permission}.
7007 - Add a weight column to user roles.
7008 - If 'user_register' variable was unset in Drupal 6, set it to be the same as the Drupal 6 default setting.
7009 - Converts fields that store serialized variables from text to blob.
7010 - Update the {user}.signature_format column.
7011 - Placeholder function. As a fix for user_update_7011() not updating email templates to use the new tokens, user_update_7017() now targets email templates of Drupal 6 sites and already upgraded sites.
7012 - Add the user's pictures to the {file_managed} table and make them managed files.
7013 - Add user module file usage entries.
7014 - Rename the 'post comments without approval' permission. In Drupal 7, this permission has been renamed to 'skip comment approval'.
7015 - Change {users}.signature_format into varchar.
7016 - Update the database to match the schema.
7017 - Update email templates to use new tokens. This function upgrades customized email templates from the old !token format to the new core tokens format. Additionally, in Drupal 7 we no longer e-mail plain text passwords to users, and there is no token for a plain text password in the new token system. Therefore, it also modifies any saved templates using the old '!password' token such that the token is removed, and displays a warning to users that they may need to go and modify the wording of their templates.
7018 - Ensure there is an index on {users}.picture.
Do you wish to run all pending updates? (y/n): y
Performed update: user_update_7000 [ok]
Performed update: user_update_7000 [ok]
Performed update: user_update_7000 [ok]
Performed update: user_update_7001 [ok]
Performed update: user_update_7002 [ok]
Performed update: user_update_7002 [ok]
Some user time zones have been emptied and need to be set to the correct values. Use the new time zone [warning]
options to choose whether to remind users at login to set the correct time zone.
Performed update: user_update_7003 [ok]
Performed update: user_update_7005 [ok]
Performed update: taxonomy_update_7001 [ok]
Performed update: taxonomy_update_7002 [ok]
Performed update: taxonomy_update_7003 [ok]
Performed update: node_update_7000 [ok]
Performed update: node_update_7001 [ok]
Performed update: node_update_7002 [ok]
Performed update: node_update_7003 [ok]
Performed update: node_update_7004 [ok]
Performed update: node_update_7005 [ok]
Performed update: image_update_7000 [ok]
Performed update: image_update_7001 [ok]
Performed update: forum_update_7000 [ok]
Performed update: forum_update_7001 [ok]
Performed update: forum_update_7002 [ok]
Performed update: filter_update_7000 [ok]
Performed update: filter_update_7001 [ok]
Performed update: filter_update_7003 [ok]
Performed update: contact_update_7000 [ok]
Performed update: comment_update_7000 [ok]
Performed update: comment_update_7001 [ok]
Performed update: comment_update_7002 [ok]
Performed update: comment_update_7003 [ok]
Performed update: comment_update_7004 [ok]
Performed update: block_update_7000 [ok]
Performed update: block_update_7002 [ok]
Performed update: block_update_7003 [ok]
Performed update: block_update_7004 [ok]
The site mission was migrated to a custom block and set up to only show on the front page in the [status]
highlighted content region. The block was set to use the default text format, which might differ from the
HTML based format used before. Check the block and ensure that the output is right. If your theme does not
have a highlighted content region, you might need to relocate the block.
The footer message was migrated to a custom block and set up to appear in the footer. The block was set to [status]
use the default text format, which might differ from the HTML based format used before. Check the block and
ensure that the output is right. If your theme does not have a footer region, you might need to relocate
the block.
Performed update: block_update_7005 [ok]
Performed update: block_update_7006 [ok]
Performed update: block_update_7007 [ok]
Performed update: block_update_7008 [ok]
Performed update: system_update_7000 [ok]
Performed update: system_update_7001 [ok]
Performed update: system_update_7002 [ok]
Performed update: system_update_7003 [ok]
Performed update: system_update_7004 [ok]
Performed update: system_update_7005 [ok]
Performed update: system_update_7007 [ok]
Performed update: user_update_7006 [ok]
Performed update: user_update_7007 [ok]
Performed update: filter_update_7005 [ok]
A new Plain text format has been created which will be available to all users. You can configure this text [status]
format on the text format configuration page.
Performed update: filter_update_7008 [ok]
Performed update: filter_update_7009 [ok]
Performed update: filter_update_7010 [ok]
Performed update: user_update_7008 [ok]
Performed update: user_update_7009 [ok]
Performed update: user_update_7010 [ok]
Performed update: user_update_7011 [ok]
Performed update: contact_update_7001 [ok]
Performed update: contact_update_7002 [ok]
Performed update: contact_update_7003 [ok]
Performed update: system_update_7009 [ok]
Performed update: system_update_7011 [ok]
Performed update: system_update_7013 [ok]
The default time zone has been set to Europe/Brussels. Check the date and time configuration page to [warning]
configure it correctly.
Performed update: system_update_7015 [ok]
Performed update: system_update_7016 [ok]
Performed update: system_update_7017 [ok]
Performed update: system_update_7018 [ok]
Performed update: system_update_7020 [ok]
Performed update: image_update_7002 [ok]
Performed update: image_update_7003 [ok]
Performed update: image_update_7004 [ok]
Performed update: system_update_7021 [ok]
Performed update: system_update_7027 [ok]
Performed update: taxonomy_update_7004 [ok]
Performed update: taxonomy_update_7005 [ok]
Performed update: taxonomy_update_7005 [ok]
Performed update: taxonomy_update_7006 [ok]
Performed update: taxonomy_update_7007 [ok]
Performed update: taxonomy_update_7008 [ok]
Performed update: taxonomy_update_7009 [ok]
Performed update: taxonomy_update_7010 [ok]
Performed update: forum_update_7003 [ok]
Performed update: forum_update_7011 [ok]
Performed update: forum_update_7012 [ok]
Performed update: node_update_7006 [ok]
Performed update: node_update_7006 [ok]
Performed update: node_update_7006 [ok]
Performed update: node_update_7006 [ok]
Performed update: node_update_7006 [ok]
Performed update: node_update_7006 [ok]
Performed update: node_update_7007 [ok]
Performed update: node_update_7008 [ok]
Performed update: node_update_7009 [ok]
Performed update: node_update_7010 [ok]
Performed update: node_update_7011 [ok]
Performed update: node_update_7012 [ok]
Performed update: node_update_7013 [ok]
Performed update: comment_update_7005 [ok]
Performed update: comment_update_7006 [ok]
Performed update: comment_update_7006 [ok]
Performed update: comment_update_7006 [ok]
Performed update: comment_update_7006 [ok]
Performed update: comment_update_7006 [ok]
Performed update: comment_update_7006 [ok]
Performed update: comment_update_7006 [ok]
Performed update: comment_update_7006 [ok]
Performed update: comment_update_7007 [ok]
Performed update: comment_update_7008 [ok]
Performed update: comment_update_7009 [ok]
Performed update: system_update_7029 [ok]
Performed update: system_update_7032 [ok]
Performed update: system_update_7033 [ok]
Performed update: system_update_7034 [ok]
Performed update: user_update_7012 [ok]
Performed update: system_update_7036 [ok]
Performed update: system_update_7042 [ok]
Performed update: system_update_7044 [ok]
Performed update: system_update_7045 [ok]
Performed update: system_update_7046 [ok]
Performed update: system_update_7047 [ok]
Performed update: system_update_7048 [ok]
Performed update: system_update_7049 [ok]
Performed update: system_update_7050 [ok]
Performed update: system_update_7051 [ok]
Performed update: system_update_7052 [ok]
Performed update: system_update_7053 [ok]
Performed update: system_update_7054 [ok]
Performed update: system_update_7055 [ok]
Performed update: system_update_7057 [ok]
Performed update: system_update_7058 [ok]
Performed update: system_update_7059 [ok]
Performed update: user_update_7013 [ok]
Performed update: user_update_7014 [ok]
Performed update: user_update_7015 [ok]
Performed update: user_update_7016 [ok]
Performed update: user_update_7017 [ok]
Performed update: user_update_7018 [ok]
Performed update: system_update_7060 [ok]
The content type blog had uploads disabled but contained uploaded file data. Uploads have been re-enabled [status]
to migrate the existing data. You may delete the "File attachments" field in the blog type if this data is
not necessary.
Performed update: system_update_7061 [ok]
Performed update: system_update_7062 [ok]
Performed update: system_update_7063 [ok]
Performed update: system_update_7064 [ok]
Performed update: system_update_7065 [ok]
Performed update: system_update_7066 [ok]
Performed update: system_update_7067 [ok]
The new "View the administration theme" permission is required in order to view your site's administration [status]
theme. This permission has been automatically granted to the following roles: administrateur, rédacteur en
chef. You can grant this permission to other roles on the permissions page.
Performed update: system_update_7068 [ok]
Performed update: system_update_7069 [ok]
Performed update: system_update_7070 [ok]
Performed update: system_update_7071 [ok]
Performed update: locale_update_7000 [ok]
Performed update: system_update_7072 [ok]
Performed update: locale_update_7001 [ok]
Performed update: menu_update_7000 [ok]
Performed update: system_update_7073 [ok]
Performed update: locale_update_7002 [ok]
Performed update: aggregator_update_7000 [ok]
Performed update: system_update_7074 [ok]
Performed update: locale_update_7003 [ok]
Performed update: aggregator_update_7001 [ok]
Performed update: menu_update_7001 [ok]
Performed update: locale_update_7004 [ok]
Performed update: menu_update_7002 [ok]
Performed update: profile_update_7001 [ok]
Performed update: aggregator_update_7002 [ok]
Performed update: update_update_7000 [ok]
Performed update: system_update_7076 [ok]
Performed update: aggregator_update_7003 [ok]
Performed update: system_update_7077 [ok]
Performed update: color_update_7001 [ok]
Performed update: locale_update_7005 [ok]
Performed update: text_update_7000 [ok]
Performed update: profile_update_7002 [ok]
Performed update: search_update_7000 [ok]
Performed update: tracker_update_7000 [ok]
Performed update: update_update_7001 [ok]
Performed update: statistics_update_7000 [ok]
Performed update: menu_update_7003 [ok]
Performed update: dblog_update_7001 [ok]
Finished performing updates. [ok]
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 14
14. Backup your database after the core upgrade has run.
Drush will automatically do this step now.
Making backup: 'Upgraded Core' in /root/.drush/cache/@self-d6-to-d7new-d7/progress_backups/upgraded-core.tar
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 15
15. Replace and update your non-core modules and themes, following the procedures at
http://drupal.org/node/948216
Drush will walk through these instructions for each module. Note that all of the new modules will be downloaded
up-front now; they will be moved into place later.
No .info file could be found for eminline [warning]
No .info file could be found for token_actions [warning]
No .info file could be found for emaudio [warning]
No .info file could be found for emimage [warning]
No .info file could be found for emthumb [warning]
No .info file could be found for emvideo [warning]
No .info file could be found for emwave [warning]
No .info file could be found for calendar_ical [warning]
No .info file could be found for jcalendar [warning]
No .info file could be found for date_locale [warning]
No .info file could be found for date_php4 [warning]
No .info file could be found for image [warning]
No .info file could be found for imagecache_textactions [warning]
Note: in addition to the modules below, the following still need to be upgraded, but cannot be started until their dependencies below are upgraded: comment_notify (Deps: comment,token),pathauto (Deps: path,token),location_cck (Deps: location),calendar (Deps: views,date_api,date_views),date (Deps: date_api),date_popup (Deps: date_api),date_repeat (Deps: date_api),date_tools (Deps: date),gmap_location (Deps: gmap,location),gmap_macro_builder (Deps: gmap),gmap_taxonomy (Deps: taxonomy,gmap),location_addanother (Deps: location,location_node),location_fax (Deps: location),location_phone (Deps: location),location_search (Deps: search,location),location_node (Deps: location),location_user (Deps: location),views_ui (Deps: views),xmlsitemap_engines (Deps: xmlsitemap),xmlsitemap_node (Deps: xmlsitemap),xmlsitemap_taxonomy (Deps: xmlsitemap,taxonomy),xmlsitemap_user (Deps: xmlsitemap)
Le site-upgrade me propose alors la liste des modules que je veux upgrader :
Please select a module to upgrade, or some other action below:
[0] : Cancel
[1] : xmlsitemap
[2] : jquery_update
[3] : jquery_plugin
[4] : googleanalytics
[5] : location
[6] : gmap
[7] : image_im_advanced
[8] : devel
[9] : date_api
[10] : link
[11] : content_permissions (now renamed to field_permissions)
[12] : transliteration
[13] : token
[14] : mollom
[15] : lightbox2
[16] : imce
[17] : globalredirect (now renamed to redirect)
[18] : getid3
[19] : backup_migrate
[20] : advanced_help
[21] : content (now renamed to cck) (Deps: field_ui)
[22] : content_copy (now renamed to bundle_copy) (Deps: ctools)
[23] : emfield (Deps: media,media_internet)
[24] : fieldgroup (now renamed to field_group) (Deps: field,ctools)
[25] : nodereference (now renamed to node_reference) (Deps: field,references,options)
[26] : userreference (now renamed to user_reference) (Deps: field,references,options)
[27] : image_attach (Deps: image)
[28] : image_gallery (Deps: image,taxonomy)
[29] : image_import (Deps: image)
[30] : imagecache_canvasactions (Deps: imagecache_actions,image)
[31] : imagecache_coloractions (Deps: imagecache_actions,image)
[32] : imagecache_customactions (Deps: imagecache_actions,image)
[33] : l10n_update (Deps: locale)
[34] : views (Deps: ctools)
[35] : views_export (now renamed to bulk_export) (Deps: ctools)
[36] : Automatically enable and upgrade all modules remaining in list
[37] : Show upgrade progress so far
[38] : Finish upgrade, leaving remaining modules un-upgraded
Je ne vais pas faire les upgrades un module à la fois.
Je choisi [36] (Automatically enable and upgrade all modules remaining in list).
</pre>
36
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 1
Upgrading module: xmlsitemap
1. Check your notes, and the UPGRADE.txt files inside each module, to see if any special upgrade instructions
apply
There is no UPGRADE.txt file in xmlsitemap
Drush will now do the step 'Begin upgrade of module xmlsitemap'.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 2
Upgrading module: xmlsitemap
2. Fully remove the old module directory inside sites/all/modules/
Note that Drush builds the target site in a new directory; the modules directory therefore starts off empty, and
there is therefore no need to delete anything. If there is for some reason an old module directory in place,
Drush will automatically delete it when downloading the new module.
Skipping optional step.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 3
Upgrading module: xmlsitemap
3. Download, unpack and move the new module directory to sites/all/modules/
Drush has a cached version of xmlsitemap at
/root/.drush/cache/@self-d6-to-d7new-d7/project_cache/disabled/xmlsitemap. The destination directory is
/home/dug/www/d7new.culbutte.be/sites/all/modules/xmlsitemap
Drush will automatically do this step now.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 4
Upgrading module: xmlsitemap
4. Enable the module
Drush will automatically do this step now.
The following extensions will be enabled: xmlsitemap
Do you really want to continue? (y/n): y
xmlsitemap was enabled successfully. [ok]
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 5
Upgrading module: xmlsitemap
5. Run update.php again (you should have run it once already when upgrading core) and check for any message
output.
Drush will automatically do this step now.
The following updates are pending:
xmlsitemap_engines module :
6202 - Deprecate support for Ask.com, Moreover, and Yahoo! search engines.
xmlsitemap_node module :
6200 - Cleanup variables.
6201 - Empty update.
Do you wish to run all pending updates? (y/n): y
Performed update: xmlsitemap_node_update_6200 [ok]
Performed update: xmlsitemap_node_update_6201 [ok]
Performed update: xmlsitemap_engines_update_6202 [ok]
Finished performing updates. [ok]
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 6
Upgrading module: xmlsitemap
6. Back up your database and files again, between each module update, so that if there is a problem, you can
revert to the most recent update.
Drush will automatically do this step now.
Making backup: 'Upgraded Contrib Module xmlsitemap' in /root/.drush/cache/@self-d6-to-d7new-d7/progress_backups/upgraded-contrib.tar
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 15
15. Replace and update your non-core modules and themes, following the procedures at
http://drupal.org/node/948216
Drush will walk through these instructions for each module. Note that all of the new modules will be downloaded
up-front now; they will be moved into place later.
No .info file could be found for eminline [warning]
No .info file could be found for token_actions [warning]
No .info file could be found for emaudio [warning]
No .info file could be found for emimage [warning]
No .info file could be found for emthumb [warning]
No .info file could be found for emvideo [warning]
No .info file could be found for emwave [warning]
No .info file could be found for calendar_ical [warning]
No .info file could be found for jcalendar [warning]
No .info file could be found for date_locale [warning]
No .info file could be found for date_php4 [warning]
No .info file could be found for image [warning]
No .info file could be found for imagecache_textactions [warning]
Note: in addition to the modules below, the following still need to be upgraded, but cannot be started until their dependencies below are upgraded: comment_notify (Deps: comment,token),pathauto (Deps: path,token),location_cck (Deps: location),calendar (Deps: views,date_api,date_views),date (Deps: date_api),date_popup (Deps: date_api),date_repeat (Deps: date_api),date_tools (Deps: date),gmap_location (Deps: gmap,location),gmap_macro_builder (Deps: gmap),gmap_taxonomy (Deps: taxonomy,gmap),location_addanother (Deps: location,location_node),location_fax (Deps: location),location_phone (Deps: location),location_search (Deps: search,location),location_node (Deps: location),location_user (Deps: location),views_ui (Deps: views)
Drush will now do the step 'jquery_update'.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 1
Upgrading module: jquery_update
1. Check your notes, and the UPGRADE.txt files inside each module, to see if any special upgrade instructions
apply
There is no UPGRADE.txt file in jquery_update
Drush will now do the step 'Begin upgrade of module jquery_update'.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 2
Upgrading module: jquery_update
2. Fully remove the old module directory inside sites/all/modules/
Note that Drush builds the target site in a new directory; the modules directory therefore starts off empty, and
there is therefore no need to delete anything. If there is for some reason an old module directory in place,
Drush will automatically delete it when downloading the new module.
Skipping optional step.
... etc etc
La liste des upgrades des modules continues, énormes… et tout se passe automatiquement !
Cela se termine par :
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 15
15. Replace and update your non-core modules and themes, following the procedures at
http://drupal.org/node/948216
Drush will walk through these instructions for each module. Note that all of the new modules will be downloaded
up-front now; they will be moved into place later.
No .info file could be found for eminline [warning]
No .info file could be found for token_actions [warning]
No .info file could be found for emaudio [warning]
No .info file could be found for emimage [warning]
No .info file could be found for emthumb [warning]
No .info file could be found for emvideo [warning]
No .info file could be found for emwave [warning]
No .info file could be found for calendar_ical [warning]
No .info file could be found for jcalendar [warning]
No .info file could be found for date_locale [warning]
No .info file could be found for date_php4 [warning]
No .info file could be found for imagecache_textactions [warning]
Drush will now do the step 'xmlsitemap_user (Deps: xmlsitemap)'.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 1
Upgrading module: xmlsitemap_user
1. Check your notes, and the UPGRADE.txt files inside each module, to see if any special upgrade instructions
apply
There is no UPGRADE.txt file in xmlsitemap_user
Drush will now do the step 'Begin upgrade of module xmlsitemap_user'.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 2
Upgrading module: xmlsitemap_user
2. Fully remove the old module directory inside sites/all/modules/
Note that Drush builds the target site in a new directory; the modules directory therefore starts off empty, and
there is therefore no need to delete anything. If there is for some reason an old module directory in place,
Drush will automatically delete it when downloading the new module.
Skipping optional step.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 3
Upgrading module: xmlsitemap_user
3. Download, unpack and move the new module directory to sites/all/modules/
Drush has a cached version of xmlsitemap at
/root/.drush/cache/@self-d6-to-d7new-d7/project_cache/disabled/xmlsitemap. The destination directory is
/home/dug/www/d7new.culbutte.be/sites/all/modules/xmlsitemap
The correct module already exists at the destination directory.
Drush will automatically do this step now.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 4
Upgrading module: xmlsitemap_user
4. Enable the module
Drush will automatically do this step now.
The following extensions will be enabled: xmlsitemap_user
Do you really want to continue? (y/n): y
xmlsitemap_user was enabled successfully. [ok]
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 5
Upgrading module: xmlsitemap_user
5. Run update.php again (you should have run it once already when upgrading core) and check for any message
output.
Drush will automatically do this step now.
The following updates are pending:
Do you wish to run all pending updates? (y/n): y
Finished performing updates. [ok]
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Step 6
Upgrading module: xmlsitemap_user
6. Back up your database and files again, between each module update, so that if there is a problem, you can
revert to the most recent update.
Drush will automatically do this step now.
Making backup: 'Upgraded Contrib Module xmlsitemap_user' in /root/.drush/cache/@self-d6-to-d7new-d7/progress_backups/upgraded-contrib.tar
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPGRADE.txt Major Upgrade Step 15
15. Replace and update your non-core modules and themes, following the procedures at
http://drupal.org/node/948216
Drush will walk through these instructions for each module. Note that all of the new modules will be downloaded
up-front now; they will be moved into place later.
No .info file could be found for eminline [warning]
No .info file could be found for token_actions [warning]
No .info file could be found for emaudio [warning]
No .info file could be found for emimage [warning]
No .info file could be found for emthumb [warning]
No .info file could be found for emvideo [warning]
No .info file could be found for emwave [warning]
No .info file could be found for calendar_ical [warning]
No .info file could be found for jcalendar [warning]
No .info file could be found for date_locale [warning]
No .info file could be found for date_php4 [warning]
No .info file could be found for imagecache_textactions [warning]
Drush will now do the step 'All done; finish upgrade'.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Upgrading Contrib Modules from Drupal 6 to Drupal 7 Finish Up
If you have a Drupal 7 version of the theme you were using for Drupal 6, place it in sites/all/themes/ and
reenable it.
Drush cannot do this step; you must perform it manually.
What would you like to do?
[0] : Cancel
[1] : I will do this step manually.
1
Le site-upgrade me demande si j’ai une version 7 de mon thème.
Non, je n’en ai pas, et nous désirions de toute façon changer de thème, prendre un plus clair et « responsive » (càd qui va s’adapter à tous les types de terminaux).
Je répond donc [1].
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Post-upgrade Step A
A. Copy files directory from the source site to the upgrade site.
What would you like to do?
[0] : Cancel
[1] : Do it for me.
[2] : I will do this step manually.
1
Là encore, je laisse faire le script d’upgrade. Il va copier tout le dossier /sites avec tous les fichiers de mon site.
Post-upgrade Step B
B. Enable the core module content_migrate.
What would you like to do?
[0] : Cancel
[1] : Enable content migrate and show available migrations.
[2] : Do not enable the content migrate module.
1
The following extensions will be enabled: content_migrate
Do you really want to continue? (y/n): y
content_migrate was enabled successfully. [ok]
GMap is unable to save the marker bundle. Markers will not work! [error]
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Post-upgrade Step B.2
B.2. Migrate fields.
Statut Champ Type de champ Content type(s) Other information
Available field_date date Date
Available field_lien link_field Date
Available field_event_dates date Event
Available field_event_emplacement location Event Missing formatter: The 'map' formatter used in 1
view modes for the field_event_emplacement field
is not available, these displays will be reset
to the default formatter.
What would you like to do?
[0] : Cancel
[1] : Run all available migrations.
[2] : Do not migrate fields.
1
Bien logiquement, je laisse site-upgrade faite TOUTES les migrations.
The following fields will be migrated: field_date, field_lien, field_event_dates, field_event_emplacement [status]
Do you really want to continue? (y/n): y
Migrating structure for field_date [status]
Created field field_date [warning]
Created instance of field_date in bundle Date. [warning]
Migrating structure for field_lien [status]
Created field field_lien [warning]
Created instance of field_lien in bundle Date. [warning]
Migrating structure for field_event_dates [status]
Created field field_event_dates [warning]
Created instance of field_event_dates in bundle Event. [warning]
Migrating structure for field_event_emplacement [status]
Created field field_event_emplacement [warning]
Missing formatter: The 'map' formatter used in 1 view modes for the field_event_emplacement field is not [warning]
available, these displays will be reset to the default formatter.
Created instance of field_event_emplacement in bundle Event. [warning]
Migrating data for field_date [status]
Migrating data for field_lien [status]
Migrating data for field_event_dates [status]
Migrating data for field_event_emplacement [status]
Migration complete
Une dernière étape pour les permissions :
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Post-upgrade Step C
C. Fix up some file system permissions.
Note: Drush site upgrade does not know what file system permissions it should use; it just makes %files and %temp
world-writable for development.
What would you like to do?
[0] : Cancel
[1] : Do it for me.
[2] : I will do this step manually.
1
et un cron pour terminer !
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Post-upgrade Step D
D. Run cron, for good measure.
Drush will automatically do this step now.
WD cron: PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table [error]
'd7newdb.culbutte_xmlsitemap_sitemap' doesn't exist: SELECT smid FROM {xmlsitemap_sitemap}; Array
(
)
in xmlsitemap_regenerate_batch() (line 249 of
/home/dug/www/d7new.culbutte.be/sites/all/modules/xmlsitemap/xmlsitemap.generate.inc).
Cron run successful. [success]
GMap is unable to save the marker bundle. Markers will not work! [error]
root@ks380111 KS5:/home/dug/www/d6.culbutte.be/sites/culbutte.be#
Il y a eu une erreur avec GMap. Cela ne me semble pas important pour les cartes déjà publiées (en général le lieu de réunions, expo…). Mais ce sera à vérifier avant la création de nouveaux nodes contenant une carte.
Il est temps d’essayer la nouvelle version Drupal 7 de notre site.
Avec firefox, je vais sur son URL provisoire : la page d’accueil semble identique au site en Drupal 6.
Je fais logon avec mon user admin habituel… et ça se passe mal !
J’essaye en ligne de commande de nettoyer le cache.
Attention, vous devez aller dans le nouveau dossier de votre site en Drupal 7 !
# cd /home/dug/www/d7new.culbutte.be/sites/culbutte.be/
# drush cache-clear
Enter a number to choose which cache to clear.
[0] : Cancel
[1] : all
[2] : drush
[3] : theme-registry
[4] : menu
[5] : css-js
[6] : block
[7] : module-list
[8] : theme-list
[9] : registry
[10] : views
1
'all' cache was cleared in /home/dug/www/d7new.culbutte.be#culbutte.be [success]
GMap is unable to save the marker bundle. Markers will not work! [error]
Je remarque qu’il reste un message d’erreur concernant Gmap… à vérifier !
Avec firefox, je reviens sur ma page d’accueil. Je refais logon… ça ne fonctionne toujours pas.
Le module concerné semble être « xml sitemap« .
Je n’ai pas trop envie de chercher car ce module n’est pas fondamental.
Je peux le désactiver sans problème. Je le désinstallerai et je referai un install propre du module.
# drush dis xmlsitemap
The following extensions will be disabled: xmlsitemap, xmlsitemap_engines,
xmlsitemap_node, xmlsitemap_taxonomy, xmlsitemap_user
Do you really want to continue? (y/n): y
xmlsitemap was disabled successfully. [ok]
xmlsitemap_node was disabled successfully. [ok]
xmlsitemap_taxonomy was disabled successfully. [ok]
xmlsitemap_user was disabled successfully. [ok]
xmlsitemap_engines was disabled successfully. [ok]
GMap is unable to save the marker bundle. Markers will not work! [error]
Ok, cette fois je peux faire logon au site en D7.
Par contre, je n’ai pas pu désinstaller le module « xml sitemap », ni via l’interface Drupal, ni avec Drush. J’ai donc supprimé brutalement la table dans phpMyAdmin ! <— IMPOSSIBLE de désinstaller XML Sitemap !
Mais il reste des erreurs !
Si je vais sur le node « nos réunions » :
Le message est :
<em>Warning</em>: Missing argument 2 for theme_image_gallery(), called in /home/dug/www/d7new.culbutte.be/includes/theme.inc on line 1142 and defined in <em>theme_image_gallery()
</em>(line <em>83</em> of <em>/home/dug/www/d7new.culbutte.be/sites/all/modules/image/contrib/image_gallery/image_gallery.pages.inc</em>).
Une recherche rapide sur Google avec ce message ne donne rien…
Très gênant également, j’ai des pages blanches quand j’essaye d’accéder à mes galeries photos et, dans administration, et dans le Tableau de bord d’administration.
Heureusement, il y a moyen d’accéder aux sous-pages de l’administration en connaissance le path exact (voir sur un site qui fonctionne).
Je vais basculer sur le thème Drupal 7 par défaut pour bien faire la différence entre l’ancienne et la nouvelle version.
Mais lors de l’activation de Bartik, j’ai encore un message d’erreur :
Le message d’erreur est :
<em>Notice</em>: Use of undefined constant IMAGE_THUMBNAIL - assumed 'IMAGE_THUMBNAIL' in <em>image_attach_theme()
</em> (line <em>544</em> of <em>/home/dug/www/d7new.culbutte.be/sites/all/modules/image/contrib/image_attach/image_attach.module</em>).
Je remet l’ancien thème Garland, puis je rebascule sur Bartik : plus d’erreur ! ouf…
Ne soyons pas négatif… Il y a progrès pour certains nodes images !
Ma page avec les photos d’accès au local s’affiche maintenant correctement en D7, sans aucun message d’erreur.
Par contre, les autres images ne s’affichent toujours pas !
J’ai un début de page, avec le titre, mais rien en dessous. Idem quand j’essaye de les modifier : l’éditeur n’apparaît pas…
Autre message d’erreur quand je vais dans la page Modules :
<em>Notice</em>: Undefined index: distribution_name in <em>drupal_install_profile_distribution_name()</em>
(line <em>207</em> of <em>/home/dug/www/d7new.culbutte.be/includes/install.inc</em>).
Ce message revient à chaque fois.
Ok ! Là, je ne suis pas le seul ! Le bug est connu, et solutionné.
C’est une histoire de profile. Je vais activer le profile standard :
# drush pm-enable standard
The following extensions will be enabled: standard, rdf, overlay, toolbar, shortcut, dblog, menu, help, dashboard, contextual, color
Do you really want to continue? (y/n): y
WD php: PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Filtered HTML'[error]
for key 'name': INSERT INTO {filter_format} (format, name, cache, status, weight) VALUES
(:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3,
:db_insert_placeholder_4); Array
(
[:db_insert_placeholder_0] => filtered_html
[:db_insert_placeholder_1] => Filtered HTML
[:db_insert_placeholder_2] => 1
[:db_insert_placeholder_3] => 1
[:db_insert_placeholder_4] => 0
)
in filter_format_save() (line 210 of /home/dug/www/d7new.culbutte.be/modules/filter/filter.module).
Cannot modify header information - headers already sent by (output started at [warning]
/root/drush/includes/output.inc:37) bootstrap.inc:1212
PDOException : SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Filtered HTML' for key 'name': INSERT INTO {filter_format} (format, name, cache, status, weight) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4); Array
(
[:db_insert_placeholder_0] => filtered_html
[:db_insert_placeholder_1] => Filtered HTML
[:db_insert_placeholder_2] => 1
[:db_insert_placeholder_3] => 1
[:db_insert_placeholder_4] => 0
)
dans filter_format_save() (ligne 210 dans /home/dug/www/d7new.culbutte.be/modules/filter/filter.module).
Drush command terminated abnormally due to an unrecoverable error. [error]
Ça se termine par une erreur, liée visiblement à un profile Wysiwyg « filtered HTML ». Encore un truc à vérifier !
Mais ça a résolu mon problème de page Modules !
Je n’ai plus d’erreur. J’ai des modules supplémentaires activés (qui sont de toutes façons souvent nécessaire)… et j’ai le thème Garland en overlay pour l’admin… Ben ça ! …
Ok, dans Apparence, je mets « Seven » comme thème d’administration.
Une autre solution pour ce message « Undefined index: distribution_name » demandait de modifier une variable dans la base de donnée.
Comme cette solution est simple, je vais l’appliquer en phpMyAdmin.
Voici le code MySQL :
<code>UPDATE `my_database_name`.`system` SET `status` = '1',
`info` = '' WHERE `system`.`filename` = 'profiles/demo_profile/demo_profile.profile';</code>
Mais cela ne fonctionne pas ! La table « system » ne contient pas de record avec ce filename…
J’ai vérifié dans un site Drupal 7 : ce record n’existe pas dans la table system… Donc je ne suis pas cette méthode.
Revenons sur le message « GMap is unable to save the marker bundle. Markers will not work! »
Ce n’est pas un problème de définition du file system (fichiers temporaires), mais un problème de permission sur le dossier ../sites/default/js (dans mon cas sur ../sites/culbutte.be/js.
Pour le corriger, je dois donner la permission au serveur Apache2 sur le fichier ../js/gmap_markers.js :
# cd /home/dug/www/d7new.culbutte.be/sites/culbutte.be/files/js/
# chown www-data:www-data gmap_markers.js
Voilà, Gmap ne devrait plus donner de messages d’erreur. <— NON, toujours des erreurs !!!
Documentation :
]]>