YaBB ==> VBB

[beheader]

Originally posted by FlyingThunder
Beheader, thanks for your work, but we can't use it. You ran the CGI version YaBB 1 Gold, we run the YaBB SE php version so it doesn't work, I tried the converter but it does not work, though thanks for your work for the YaBB 1 Gold people!

You are welcome....

But if phpbb comes out with a YaBB SE converter... well, then you are in the running again....

Personally, I believe they will. Once that happens.... just plug my instructions in ...

I hope...

[FlyingThunder]

You're right I searched their forums, but currently noone is developing one, so I guess no Vbulletin for me Why don't Vbulletin develops one ? I saw many request so what is in the way ? Oh well I think then I'l be doomed to YaBB for a while :'(.
I love Vbulletin...

[beheader]

Originally posted by FlyingThunder
You're right I searched their forums, but currently noone is developing one, so I guess no Vbulletin for me Why don't Vbulletin develops one ? I saw many request so what is in the way ? Oh well I think then I'l be doomed to YaBB for a while :'(.
I love Vbulletin...

Well as I understand it there are a relatively small numbers of YaBB boards out there to convert relative to some of the other bb systems available.

Also, judging from the conversion process I went through, the YaBB data might be a little more thorny than other systems.

I agree a converter would be nice. Hope they do it... I drank WAY too much coffee working on this conversion...

[memobug]

Greetings folks,

I'm trying to make some sense out of the bbimport_phpbb2.php importer that I downloaded tonight from the vbulletin download.net.

After translating my database from YaBB to phpBB2, I ran the importer and wound up with a bunch of wacko italic, bold & image tags. They had all been adulterated from

[img ]whatever[ /img] and [ b]whatever[/ b]
^sorry I had to add the spaces to get it to display

to fun stuff like this

[imgBCB1231233]whatever[/imgBCB1231233]

and interestingly, there was a section of code commented out of of the convertor in the function bbcode($text, $uid=0)
just, following the comment "BB CODE IS TOUGH":

/*$text = eregi_replace("[/b:[a-zA-Z0-9]]", "[/b]", $text);
$text = eregi_replace("[i:[a-zA-Z0-9]]", "[/i]", $text);
$text = eregi_replace("[/i:[a-zA-Z0-9]]", "[/i]", $text);
$text = eregi_replace("[u:[a-zA-Z0-9]]", "", $text);
$text = eregi_replace("[/u:[a-zA-Z0-9]]", "", $text);
*/

Which would, apparently to my novice PHP eyes, possibly have fixed that wacko bit.

Two questions, please

1) Does anyone know where that stuff is coming from, because it doesn't show in the phpBB code. It looks clean in phpBB and displays properly.

2) Does anyone know why that section of the code (that apparently would clean it up) has been commented OUT?

Regards,

Matt

[beheader]

Originally posted by memobug
Greetings folks,

I'm trying to make some sense out of the bbimport_phpbb2.php importer that I downloaded tonight from the vbulletin download.net.

After translating my database from YaBB to phpBB2, I ran the importer and wound up with a bunch of wacko italic, bold & image tags. They had all been adulterated from

[img ]whatever[ /img] and [ b]whatever[/ b]
^sorry I had to add the spaces to get it to display

to fun stuff like this

[imgBCB1231233]whatever[/imgBCB1231233]

and interestingly, there was a section of code commented out of of the convertor in the function bbcode($text, $uid=0)
just, following the comment "BB CODE IS TOUGH":


Which would, apparently to my novice PHP eyes, possibly have fixed that wacko bit.

Two questions, please

1) Does anyone know where that stuff is coming from, because it doesn't show in the phpBB code. It looks clean in phpBB and displays properly.

2) Does anyone know why that section of the code (that apparently would clean it up) has been commented OUT?

Regards,

Matt

Matt,

If you actually go in to edit a post under phpbb you will see all that legacy garbage....

When you save after your edit, phpbb stops translating the garbage correctly (dunno- but it's true)...

The only solution I found was to make the manual changes to the database...