Does VB4 support PHP5.5?
 

Does anyone here run their board on PHP5.5?

Yes, after you hide the warnings, everything works fine.
I'm running vb4 with php 5.5.11.

Hide the warnings?

It's just a matter of ignoring lines in the error log?

I am evaluating PHP 5.5 on vBulletin v4.2.2, on a local test board. At this point I have no reason to push the envelop. I like to sit back and watch others have the server problems. :) If you need it, I get it, but if you don't just run it on a test board. Only my opinion ... it's worth what you paid for it. :)

If you ask me, it would be hell easier if vb would make a topic or some guidelines about what it would need to be modified so that vb4 can be full php 5.5 compatible.
I tried to modify it but the source code is a mess, there's nothing sistemically organised.
But that is just my thinking.

The biggest issue is our use of /e in some regexes, and I think a few commands we use make use of e.

Hi

I am in the process of moving from a 32bit to a 64bit server but this runs PHP 5.5 now :( I also use vB 4.2.2 and the test I have done so far the new server seems to run quite well... I do have the stop all errors line in my vBulletin config file following an issue after an upgrade in the past..

Is there anything i should check to make sure it works before i take it live?

I did ask on vBulletin but got an outright no.... Lol

I do intend to upgrade in the next few weeks to at least 4.2.3 which I know they do say will work...

Stuart

The reason you'll have got an outright 'no', is because that's the correct answer. 4.2.2's code is simply not compatible with php 5.5.

Is there a reason why you can't just run the perfectly simple and minor upgrade to 4.2.3?

I know the upgrade is simple, done quite a few .. I use a custom skin which is not compatible at the moment but it is all part of the upgrade once the server is done..

Just did not want to do it just yet..

As I say two of us have checked and seen no errors as yet... I was just interested in what I could get..

Can't think of what there would be in a 4.2.2 style that would break in 4.2.3....