Hi all,

I found this converter trying to find a solution to convert from my existing phpNuke to drupal.
Well, i know that this one is not for phpNuke but the forum inside is the same :)

I changed the name of the user table to match the settings of this module. So checking the setup everythings looks great.

Here some stats on my current board:
3574 users
about 16.000 topics with roughly 240'000 posts
I would consider this as rather big ;)

So I have problems converting this forum. It already starts at the users section. In the apache error log I see the message that the scripts runs out of memory. Initially I had the max mem to 64 M. I had to increase the limits to 512 M in order to the get users migrated.

Would it be possible to change the script to not do all in one request? I made (long time ago) a converter from TBB to phpBB. Here I made one http-request per topic in order to have no issues with memory or timeouts. May be this would be an option here as well.

Migrating the categories I do get these to messages (more than once each):
user warning: Table 'dd_eh6_nuke.drupal_locales_source' doesn't exist query: SELECT s.lid, t.translation, s.version FROM drupal_locales_source s LEFT JOIN drupal_locales_target t ON s.lid = t.lid AND t.language = 'de' WHERE s.source = 'Found %cat_count categories: Beginning Import' AND s.textgroup = 'default' in /var/www/ddraes/eh6_drupal/drupal-6.14/modules/locale/locale.module on line 365.

warning: cannot yet handle MBCS in html_entity_decode()! in /var/www/ddraes/eh6_drupal/drupal-6.14/modules/phpbb2drupal/phpbb2drupal.module on line 1340.

Is this critical? The categories are there and look good.

The migrating topics it ran quite long until it ran out of memory again. It migrated about 4500 topics/nodes until the crash. Any hints on what I should change?

Also the watchdog table grew to almost 1 GB of data. Can this be avoided?

Best regards,
Daniel

Comments

naheemsays’s picture

naheemsays commented

the watchdog queries etc and those error messages can be ignored (and have been fixed for the 2.x version that imports from phpbb3.x). you can manually modify the module to get rid of those issues(and that may also allow you to use less memory) by modifying lines such as

drupal_set_message(t('Found %topic_count topics: Beginning Import', array('%topic_count' => $topic_count)));

to to remove the "t()" translate function (or move the line to somewhere else, in an area where the default database is the drupal one).

If an import runs out of memory, rerunning that segment should start where it left off, so there should be no problems.

(as for the MBCS decode, I am not sure what that is).

Fogg’s picture

Fogg commented
Status: Active » Fixed

Hi nbz,

thanks for the quick answer.

Most important part:

If an import runs out of memory, rerunning that segment should start where it left off, so there should be no problems.

I tried and it seems that it really starts of where it broke. So it is currently running again....

As for the watchdog - I watch the db via phpmyadmin and truncate the table every now and than. It is mainly the MBCS that comes thounsands of times.

Best regards,
Fogg

Fogg’s picture

Fogg commented

just a comment on the MBCS thing. This is due to the fact that I am still using php4 where this is a known bug.

I added not error_reporting(0); ... error_reporting(1); around the html_entity_decode() statement. This way the error is ignored. Probably not the best solution, but this way the converter seems to complete it's task.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.