By trantt on

After successfully converted my database to version 4.7, do I need to reinstall all previous modules manually? I received the white page when replacing the new module folder with the previous module folder (bust select 'NO' to replace).

Thanks

trantt

⋅ Categories: Drupal 4.7.x

Comments

dlr’s picture

dlr commented

The form API has changed a lot between drupal 4.6 and 4.7 so you have to go to the project page and download the module you need for 4.7 and install them (take care, the install process has changed a bit, many modules can install themself automatically)
Hope it helps

trantt’s picture

trantt commented

This is my first upgrade and I didn't know we have to reload all previous modules manually. Anyway, thank you very much for your help and I will give it a try.

trantt’s picture

trantt commented

dlr,

As I mentioned above, I was successfully upgraded my databases to v4.7 but still couldn't able to figure out what I need to do with all the previous installed modules. Let's pick i18n.module for example, since this module wasn't available on 4.7, I went ahead and reused the previous version instead. Once I dropped it in the new modules folder, my entire screen went blank when tried to access to the i18 block. This is my first upgrade and it is really confused the hell out of me.... please help

Thanks

dlr’s picture

dlr commented

As i told you, modules for 4.6 or earlier can't work with 4.7. So don't try to use them. If a module is not available for 4.7 and you really need it,try to take the cvs version.

So try to clean you're installation a bit by removing all 4.6 modules.

Hope it helps

trantt’s picture

trantt commented

dlr,

do you know much about the Internationalization module? All of my previous international blocks were removed after successfully upgraded to version 4.7. I noticed that i18nblocks.module and i18nmenu.module were missing from the cvs version. What do I need to do dlr?

Thanks

dlr’s picture

dlr commented

the internationalization module.
I think that the best solution would be to ask the maintener of the module.
http://drupal.org/project/i18n
Hope it helps