If locale module is active, you get tons of erros displayed on the screen, in particular because drupal starts to look for the locales_source and locales_target tables in the phpbb database and not in the drupal database (this is similar to the other bug reported earlier where the module complains about not finding the system table in the phpbb database when it should be looking for it on the drupal database).

Comments

naheemsays’s picture

naheemsays commented

Does this happen everywhere, or just in some places/steps?

(I think I need to go through the module with a fine comb to make sure all the db_set_active's are present and in the right places...)

Carlos Miranda Levy’s picture

Carlos Miranda Levy commented

The errors are shown (tons of them, of course, one per each string that can not be translated ... think every string in the page) before displaying the page.

I don't think it affects the conversion process though.

Once I finish the real migration (I'm migrating 7 huge forums from Snitz to phpbb and then to Drupal :p), I will re-test locally with the locale module enabled to replicate the error. For now, I am disabling it before proceeding with the migration.

On the other hand, it would be a good idea to suggest a list of modules to disableprior proceeding with the migration for large forums, such as locale and pathauto (a migration lasted over 2 days before timing out with pathauto enabled, but lasted only minutes without pathauto ... I will open another issue for that).

naheemsays’s picture

naheemsays commented
Status: Active » Closed (fixed)

Marking as closed - I think it is generally a good idea to do the data import with as few modules as possible running - only have the bare essentials that afect the data import.