Some modules not available.
Bucephalus - May 22, 2008 - 22:07
| Project: | phpBB2Drupal |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I'm trying to migrate from phpbb2 to Drupal 6.2, but I'm having problems.
Under 'encoding settings' I'm getting a message that says, " * Module comment_upload is disabled. The comment_upload.module is not enabled." and this seems to be preventing me from progressing. This message appears whether I have "Change encoding of text strings during the import" checked or not. The problem is that comment_upload,module is not available for Drupal 6.2
Another problem - phpBB2Privatemsg requires the module Privatemsg, but this is not available for Drupal 6.2 either.
Any ideas?
Thanks!
#1
comment_upload is only needed if you also import attachments. There is some work on it here: http://drupal.org/node/197015. IF this functionality is not needed, just intick the option to import attachments.
for privatemsg, you can either use a mostly working patch, or wait til a final version is released.
#2
Thanks for your help - I think I was getting confused because the error message for comment_upload wasn't appearing in the 'import attachments' section but the one below, so I thought the problem was maybe with the encoding settings.
Anyway, it seems to have worked mostly now - although no follow-up posts were showing. It seems as if it did import them as comments, but set their node id's to zero, so they didn't appear under any forums posts. I wrote a small and unreliable program to fix this, but has anyone else had this issue?
#3
I imported from phpbb2.22 to Drupal 6.1 and never had that problem.
What database connection are you using? (postgres?mysql?mysqli?)
Reason for the question is I have run into other problems (there is a code needs work issue here for album import) where it did not pick up things correctly when using mysql database, but it did work for mysqli... no idea what the real issue there is, but it may be linked. (or not - I took over maintaining this module to scratch my own itch. I am not a real developer, but with a little effort I was able to fix bugs, hack things into place.)
Anyway, good to know it was fixable.
#4
this problem should now no longer be the case.