[SMF Converter] YaBB SE 1.5.4

[JayBachatero]

Software: YaBB SE
Version: 1.5.4

This is the official support topic for YaBB SE 1.5.4 converter.  Use this topic to ask for support for this converter.

Changelog

convert.php
Use this convert.php with the .sql file attached in this topic.

[Cyberclone]

My Problem:

Code Select Expand

Converting posts (this may take some time)... Successful.
Converting polls... Successful.
Converting poll options... Successful.
Converting poll votes... Successful.
Converting personal messages (step 1)... Successful.
Converting personal messages (step 2)... Successful.
Converting topic notifications... Unsuccessful!
This query:

    SELECT m.ID_MEMBER, lt.ID_TOPIC, lt.notificationSent AS sent
    FROM (`spocrati_ht4uforum`.yabbse_log_topics AS lt, `spocrati_ht4uforum`.yabbse_members AS m)
    WHERE notificationSent != 0
    AND lt.memberName = m.memberName
    LIMIT 0, 500;

Caused the error:

    Unknown column 'lt.memberName' in 'where clause'

I have no any idea what I can do... My solution was create a new field memberName in yabbse_log_topics. After them, the script works but for ever on the same step

[JayBachatero]

Try the one attached in the first post.

[Cyberclone]

Thanks for your help 
With your new file, I have no error messages, but the script works for ever:

Code Select Expand


Converting...
Converting topic notifications... Incomplete.

Not quite done yet!
This conversion has paused to avoid overloading your server, and hence not working properly.
Don't worry though, nothing's wrong - simply click the continue button below to start the converter from where it left off.

in the last 24 hour it works on the same step. Have you an another soloution?

[JayBachatero]

Try this file.

[Cyberclone]

  Now it works wonderfull, thanks for your support 

Conversion Complete
Congratulations, the conversion has completed successfully. If you have or had any problems with this converter, or need help using SMF, please feel free to look to us for support.

[Chuck]

Hi,  I have been trying to convert my yabbse forum to SMF using the files in this thread.  It works fine until after it converts the post and then it gets an Internal Sever Error.

Any ideas?

Thanks.

[Chris Cromer]

I don't know why but after using this converter random members have an ID_GROUP setting of 11... even though that group does not exist. This caused me alot of headaches since the members with that group id could not see anything. It was funny that when they logged in the boards where gone, but when they logged back out they came back.

I already fixed it in my conversion since it was just a matter of running an update query, but thought I would report it for you to look into.

[JayBachatero]

Hi,  I have been trying to convert my yabbse forum to SMF using the files in this thread.  It works fine until after it converts the post and then it gets an Internal Sever Error.

Any ideas?

Thanks.

Does the post conversion make any process at all or once it gets there it gets the error?

I don't know why but after using this converter random members have an ID_GROUP setting of 11... even though that group does not exist. This caused me alot of headaches since the members with that group id could not see anything. It was funny that when they logged in the boards where gone, but when they logged back out they came back.

I already fixed it in my conversion since it was just a matter of running an update query, but thought I would report it for you to look into.

Chris that is weird.  Was it a primary or secondary group?  If you look at this part it shows you that it gets the correct group.

Code Select Expand


CASE
WHEN mem.memberGroup = 'Administrator' THEN 1
WHEN mem.memberGroup = 'Global Moderator' THEN 2
WHEN mg.ID_GROUP = 8 THEN 2
WHEN mg.ID_GROUP = 1 THEN 1
WHEN mg.ID_GROUP > 8 THEN mg.ID_GROUP
ELSE 0
END AS ID_GROUP


[Chuck]

Yes, all the post are converted successfully.. When it says converting priveat messages, or after that, I get the internal sever error.  When I look in the datatbase it appears that the pm's have been converted-at least there is the same amount in the new table.  

[Chuck]

The last message that I get before the internal sever error is

Converting private messages step 2 incomplete..

[Chuck]

I got this from the server error log, it seems to have somethng to do with it

Allowed memory size of 8388608 bytes exhausted (tried to allocate 10240 bytes)
[Thu Feb 15 19:48:44 2007] [error] [client 65.24.102.63] Premature end of script headers:..........

[Chris Cromer]

That's just it, there is no group 11 in either the YaBBSE forum or in the SMF forum. Infact the groups in the YaBBSE are unaltered, there are no new groups.

Oh and just to let you know, attachments where an issue as well for me. The directory is missing alot of attachment files and I had to do some pruning on the attachments from the admin center to get it to convert. If I didn't do it the script would die and all you see is a white screen. My error log shows it trying to access files that don't exist and having trouble and failing.

[JayBachatero]

Umm I'll have to look more into this.  I still don't understand how the ID_GROUP was set to 11.

[tinfoilhat]

The last message that I get before the internal sever error is

Converting private messages step 2 incomplete..

I had the same error.  The way I solved it was by using the yabbse_to_smf.sql file in the 4th post rather than the file in the 1st post.  After that it worked well for me.

[Chuck]

Hey, thanks for the reply.  That is the file that I use and I  still get the error.

[JayBachatero]

Post your phpinfo.php file.
What is phpinfo.php?

[Chris Cromer]

I don't know if this is because the forum I converted was converted from YaBB to YaBBSE to SMF. But I noticed in the database in the members table, old members that didn't set their birthday are set to 0000-00-00, where as members who signed up after the conversion to SMF have 0001-01-01.

I doubt it affects anything, but I thought I would report it since I didn't know if it's something specific to the forum I converted or a bug that happens for all conversions.

[JayBachatero]

I'll look into it.  If I'm correct the correct format is 0001-01-01 cause of MySQL running in strict mode.

[Chris Cromer]

Yeah, I updated all the rows to the 0001 setting. I just wanted to report it incase it might be a issue with the converter.