#2 Bug when forums are switched off in UBB

[David Green]

Bug 1: When a forum is switched off in UBB, ubb2phpbb
fails due a null value in the SQL statement for the
cat_id field.

Opening forums index...Open
Connecting to phpBB...Connected
Converting forum #7, Forum 7...Error: Unable to insert
new forum into the phpBB database. mySQL error: You
have an error in your SQL syntax near ' 0, 000007)' at
line 2

The following SQL statement causes the above error:
INSERT INTO forums (forum_id, forum_name, forum_desc,
forum_access, forum_moderator, cat_id, forum_type,
forum_order) VALUES ('7', 'Forum 7', 'Forum 7
Description', 1, 0, , 0, 000007)

The forum on or off setting in UBB needs to be
checked, as it is likely (as in my case) that a forum
set to off will not have a category assigned.

In short, ubb2phpbb fails if any UBB forum does not
have a category assigned.

I do not know how phpBB stores a forum that does not
have a category. If it sets forums.cat_id to 0, then
perhaps the same should be done here to trap the null
values.

Bug 2: ubb2phpBB fails when forum#.threads is not
found in a forum. It should simply ignore this and
continue converting message from the next forum.

Bug 3: ubb2phpBB thinks there are more forums than
there are and fails.

The following error message occurs:
The conversion process has halted, due to a fatal
error.
Fatal Error!
Unable to open the forum index for forum #10
Index File: ubb/ForumInvalid Forum/forum_Invalid
Forum.threads

General Comments:

I think most of the errors occur on a nearly empty UBB
forum like mine.

Wow, its worked in the end! After doing various
workarounds to fix the error messages as I went along,
i've just gone into phpBB and it converted all of my
user, forums titles and messages, even though the
script didn't reach the end and failed at Bug 3 that I
found above.

I think the error messages should be less severe
(perhaps use something else instead of die all the
time), so the script becomes more robust and continues
especially for bug 2.

Thanks

Dave Green

[Nukenet]

Logged In: YES
user_id=341351

Bug 1: Simply create one category in UBB, such
as 'General', and add all forums to that category.

--------------------

Bug 2: If running UBB > 6.05, you MUST downgrade to 6.05 -
else the converter won't work. Here is how to do this:

First, upload all the ubb 6.0x files right over the top of
your current ubb 6.1.0.x files. Check permissions, and
head to the next step.

Second, find your ubb_lib.cgi file in your cgi directory
and do the following.... (this is because UBB 6.1 added
two extra fields in to the member registration, therefore,
if you try to login to your 6.0x CP w/o doing this, you
will have been logged in as a "hack attempt" so do this
first)

Find:

my $maxmemfields = 29; #total fields permitted in member
file

Replace with:

my $maxmemfields = 31; #total fields permitted in member
file

Or if you have hacked your UBB, it will have to be even
larger (I tried 56 and it worked fine)

Third, rebuild your member stat & forum stat files.

Last, before you begin the conversion process MAKE SURE to
click & enter each forum, and click on one topic in EVERY
forum, to make a forum_x.threads file for each "Forum"
directory in your non-cgi folder. I believe UBB 6.1.0.x
does not use this, and therefore is one of the reasons
that the current ubb6 import script does not work with
6.1, as the import script looks for this file to make the
threads.

One note of a problem I ran into. I ran into what I
believe were corrupted PM messages that halted the
conversion process. If at all possible, contact your forum
members to delete all their stored PM's. Unfortunately you
can't really continue the process when it stops except for
deleting the messages for the user (I just logged into
their accounts and cleared out the PM's). Fortunately it
was only about 5 members out of 300 that had corrupted
PM's. So the best solution is to keep your CP open for the
UBB as well to delete the corrupted files. Since going
back like this can cause duplicate files, I would go back
through the whole install process again and dump the
database and start from scratch. Now you will not run into
the PM problems because you have dumped the problematic
messages already If you're lucky, you won't run into
this..

------------------

Bug 3: If you have reached this, the conversion process
completed successfully. Don't worry about it.