Updating Modules to Drupal 4.7 from Drupal 4.66
Having upgraded into a fresh 4.7 installation, save for the modules that you would have had to add to be able to complete the installation (front_page in this case), the code_base/modules folder should only contain the files that come bundled with a fresh installation of Drupal 4.7. The database on the other hand is an upgraded duplicate of the 4.66 installation that you previously had along with all the tables previously created (in your regular updates to 4.66) to support modules, most/all of which are not in the new installation since we have so far only added the modules that are important for the upgrade to start-up.
You MUST NOT attempt to use the 4.66 module code and database tables as they are because that would muddy your installation and prepare you for a life of error messages and unexplained failures whenever Drupal 4.7 will run into a module that was intended for 4.66 and is not compatible. The right way to do this is to use only 4.7 approved modules and only use out-of-version modules if you know what you need to modify to make them work (I would strongly suggest again that you either roll-up a new version of your modules for 4.7, or wait for the module owner to update it)
At this point of the upgrade, you should carefully find the tables in the now updated database that are affiliated with the now-unnecessary 4.66 modules and DROP them. My favourite approach for this is to open the MYSQL definition for all the modules in the former installation (which should still be the live version of your website until you finish upgrading and testing the copy into 4.7), and identify the modules that are specifically for 4.66 and were not upgraded by the code upgrade process (All added modules). Since we do not have any module sub-folders in the 4.7 modules folder (the core modules come as individual files) match the modules folders for the two versions and open all the MYSQL definition files for all the modules that are not part of the Drupal Core (If you have a module that has critical data for which you may want to maintain continuity e.g click thru), you can leave the Dababase table intact and make a note for yourself to revisit it and compare the 4.66 table structure with that of the 4.7 version and see how you can modify the 4.66 table to work with the Drupal 4.7 module code to maintain the existing content.
Access your favourite DBA tool such as phpmyadmin and DROP the tables that are not necessary.
Drupal 4.7 Module installation
Having cleared the old 4.6x modules (both MYSQL tables and Module code) from your upgraded installation, you can now proceed to installing new modules as you would in a fresh installation of Drupal 4.7.
NB: With some modules were previously used in Drupal 4.6 missing from your upgraded installation, calling a feature on the new site that previously depended on a removed module will give youÃ? blank page, aÃ? blank page with numeral 2 on it, or an ugly PHP error message across the screen especially if you have not set your errors to be hidden from the screen and only shown in the watchDog
You MUST NOT attempt to use the 4.66 module code and database tables as they are because that would muddy your installation and prepare you for a life of error messages and unexplained failures whenever Drupal 4.7 will run into a module that was intended for 4.66 and is not compatible. The right way to do this is to use only 4.7 approved modules and only use out-of-version modules if you know what you need to modify to make them work (I would strongly suggest again that you either roll-up a new version of your modules for 4.7, or wait for the module owner to update it)
At this point of the upgrade, you should carefully find the tables in the now updated database that are affiliated with the now-unnecessary 4.66 modules and DROP them. My favourite approach for this is to open the MYSQL definition for all the modules in the former installation (which should still be the live version of your website until you finish upgrading and testing the copy into 4.7), and identify the modules that are specifically for 4.66 and were not upgraded by the code upgrade process (All added modules). Since we do not have any module sub-folders in the 4.7 modules folder (the core modules come as individual files) match the modules folders for the two versions and open all the MYSQL definition files for all the modules that are not part of the Drupal Core (If you have a module that has critical data for which you may want to maintain continuity e.g click thru), you can leave the Dababase table intact and make a note for yourself to revisit it and compare the 4.66 table structure with that of the 4.7 version and see how you can modify the 4.66 table to work with the Drupal 4.7 module code to maintain the existing content.
Access your favourite DBA tool such as phpmyadmin and DROP the tables that are not necessary.
Drupal 4.7 Module installation
Having cleared the old 4.6x modules (both MYSQL tables and Module code) from your upgraded installation, you can now proceed to installing new modules as you would in a fresh installation of Drupal 4.7.
NB: With some modules were previously used in Drupal 4.6 missing from your upgraded installation, calling a feature on the new site that previously depended on a removed module will give youÃ? blank page, aÃ? blank page with numeral 2 on it, or an ugly PHP error message across the screen especially if you have not set your errors to be hidden from the screen and only shown in the watchDog
