So I'm currently working on converting a vBulletin board to SMF. So far I'm getting the forum prepared for the conversion, so I'm getting the Membergroups, Permissions, Settings, etc all configured.

I'm running into an issue in the Package Manager where if I try to browse the third party server, I will get a white screen on some catagories. First, it was on catagories with more than 25 entries. I went through the sticky here and did some adjustment on the memory allocation in the SMF files. I had already set my PHP environment to allow 128MB of Memory, so I don't know why SMF wouldn't pick up on that.

After upping the memory, I could then see those catagories, up until I started to try to look at the larger catagories with over 100 entries. On those, I still get the white screen.

This is the error that shows up in my Error Log.


Apply Filter: Only show the error messages of this URL
/forum/index.php?action=admin;area=packages;get;sa=browse;server=1;relative=posting
Apply Filter: Only show the errors with the same message
8: Undefined offset: 1
Apply Filter: Only show the errors from this file
File: .../forum/Sources/Subs-Package.php
Line: 1489

A little bit on my setup.

It's a VPS running Ubuntu 12.04.3
4GB RAM
Apache2/PHP 5.3/MariaDB 5.5

There are 3 vBulletin installs on this server, all of them work just fine. One of them is the one I'm moving to SMF.

If you can help me out, it'd be greatly appreciated.

Thanks folks.

If you are not running php5.5, I suggest converting to smf 2.0.6 instead...

So, PHP5.5 is becoming required for current versions of SMF then? I'd rather have it stay current, so I think I'll check vbulletin compatability with 5.5 and then upgrade via PPA.

You think it's really a PHP version problem though?

No, it isn't.

2.0.7 introduced compatibility with PHP 5.5 and that caused some memory issues in some setups (strange enough, it seems more relevant with PHP 5.3)

What Kindred says is that, if you don't run PHP 5.5, you can keep SMF in version 2.0.6, thus not having those white screens.

Anyway, don't use that function. The list isn't really updated, server-side...

I'm glad I asked. Also, it looks like I'm stuck on 5.3 for now. One large vB forum is on 3.8.7 and that doesn't work on 5.4+.

As for SMF 2.0.7, I've been through every part of the forum and it seems like the large package browser lists are the only areas where I get a white screen. I can install packages manually just fine, so I can probably just ignore it and stay on 2.0.7? Then again, I've yet to migrate the data in, so maybe those memory problems might become an issue again once the forum is populated with content?

Really appreciate the help! You guys are great so far!

You can keep 5.3 although, IIRC, that version is already EOL.

And you can keep 2.0.7, yes. Having more data will not cause new WSOD causes.

Do note, there were no security updates between 2.0.6 and 2.0.7

The main reason for the 2.0,7 release was php5.5 compatibility,  because php5.5 breaks older versions.