VB 3.8.7 and PHP 5.4
 

Well I heard that VB3.8 aint compatible with PHP 5.4, one of the big issues is the deprecated call-time refernece ampersand & symbols. VB support staff told me there were other things incompatible with PHP 5.4, I wonder what they are.

Can anyone of you please give me a list of such incompatibilities between VB 3.8 and PHP 5.4? It does not need to be a detailed description of every line I need to modify, a general picture is perfectly fine with me. A good example is, well, 'this syntax used in VB3.8 is no longer valid in PHP 5.4'. I do not need to know all locations this syntax is used, I just need to know which syntax it is.

Check this out http://php.net/manual/en/migration54.php

Are you kidding me? Just tell people to learn from php.net or w3school.com? If so, what does this subforum have to exist in the first place? lol

I am here asking for what is inside VBulletin 3.8 that I need to modify, although not really for detailed list of every little thing like the location of each line. A general picture will be good, like what kind of script in VB aint compatible with PHP 5.4.

That migration manual actually shows you whats changed, simply do a text search through vb files for the things that have changed and change them - am i kidding? errrr no! :)

Alright, guess I should say thank you for the unhelpful answer?

Your wrong, it was helpful, i think you have the attitude like that because i couldn't provide you a definitive list of thing in vb that need changing, but with the help of a text program for find and replace you can go through that manual page and change the things needed.

I may want to re-think your attitude, its unlikely anyone will want to help you with posts like that.
No one is here just to just blindly do all the work for you. The information provided is helpful and can be used to work out what might need to be changed.

@Simon Lloyd:
Oh yeah, you seriously believe I didnt know there exists a page on PHP called 'Migrating from PHP 5.x.x to PHP 5.x+1.x' before I came here? I was asking for something specifically related to Vbulletin 3.8, not what has become deprecated in PHP 5.4.

@Paul M:
Was I asking for someone to code for me? Doing ALL the work for me? lol. I just intended to ask what were the things in VB3.8 that became deprecated in PHP 5.4, and in fact I plan to fix these myself just after I got a list of things to fix. All I got instead was an answer 'You should go to PHP.NET!'. Its just like a newbie asking how to learn PHP and you say 'read PHP's manual ' or 'Go to w3school.com'. If thats the way you answer questions, there's no need for this subforum to exist at all. Its better this thread left unanswered or dead rather than insult me with crap like this.

Sigh!

Oh yeah, you finally got it. Anyway, if this is the way you guys answer questions here, it may be a good idea to just close down this forum and leave a note:

"Got a problem? Go to PHP.net and w3schools.com".

Just like the magic quote "Google is your friend", it works doesnt it?

I understand what you mean, you're hoping to find someone who already knows the kinds of things that have to be changed, so that you don't have to go through all the code looking for things (which is a big task even if you know what needs to change). But I think in post #3 you could have explained that without starting with "Are you kidding me". That kind of puts people on the defensive.

Anyway, the only one I know is that you can change " &= new " to " = new ", but that's the same one they've told you about. It would be great if someone could take a fresh copy of vb3.8.7 and fix it for php 5.4, then post a diff.

Oh thanks for your comment, and yeah I was looking for something at least more helpful than 'please read on PHP's manual'. Indeed, if someone actually has fixed it for PHP 5.4 and post a solution, that would be the best. I am not hoping for that, but at least some hints.

I am aware of the ampersand issues, I surely can fix them all myself by searching through the files. The reason why I posted this thread here is that I saw a thread on VB's official forum that the incompatibility is more than just the ampersand. I asked what the others might be but received no answer, instead I was directed here. This makes me really curious, if there are more compatibility issues than merely ampersand, what are they?

Clearly you'll share with us all, the specific v3 solutions once you find them. Leading by example, as it were?

If I do find the answer myself I will share. At least, I wont be telling people to read PHP.net manual for reference.
:)

Oh yeah, it pretty much works after I remove the deprecated ampersands, but there are minor issues. I fixed one of them in includes/functions_online.php, simply add this one at line 452(assuming you are using VB 3.8.7 patch level 3:

Anyway my forum is working out nicely so far after I upgrade to PHP 5.4.10, but there are still a few things I havent tested so I aint quite sure if everything is fine now. Once I figure this out, I will be posting a PHP 5.4 guide for VB3.8.7 users. It may be a bit messy, but at least I wont be telling people to go to PHP.NET and read that manual.
:)

Hall of Famer, do you have any updates on your progress in patching in PHP 5.4 support?

VB 3.8.8 is being worked on by Paul M which will address the PHP issues :)

New version of 3.8?

I like your method of giving advice much better than those who like to sit and point.

Anyway, if you have anything you can write in terms of a guide, that would help me soooo much in my migration to php 5.4.

I am having so much trouble and my forum won't even show up at all on my wamp test server. Can't even get admincp to load up.

Why not just wait for 3.8.8, which has PHP 5.4 support and is in beta right now?

I've got a server upgrade occurring in less than a week and I'm trying to get all my scripts PHP 5.4 compatible before the upgrade, so that I don't have to install PHP 5.3 or 5.2 instead.

Due to when my license support expired, I also won't have access to download the vB 3.8.8 update and I don't have the amount of cash needed to pay for a full blown upgrade. I'll need to have an idea of what parts of the legacy code I can modify myself. I have no problem with that and am willing to assume the risk.

Any insights relevant to the areas of code in 3.8.7 to target for PHP 5.4 compatibility would be greatly appreciated.

Probably because people with vb3.7 and below wont be able to download it.

Bump. I'd be interested in a survey of php edits required, or syntax changes specific to VBulletin 3.8.x. and php 5.4 as well.

If anyone has tackled this successfully, or unsuccessfully, and can share the experience that would be very helpful.

You could use 3.8.8.

Like Simon mentioned a while back, not all can download and use that and some may not want to pay for a vB5 Connect license in order to download an update to their existing 3.x software as they have no plans to upgrade to 4.x or 5.x.

This is one reason I believe 3.x license owners should have an option to pay < $50 to download an updated 3.8.x most current version as I believe many more would pay for that then they would the $209 to upgrade, granted it is -40 off a full license but to me they should only be paying that $40 difference only.

Edit: Although to be fair... everyone must realize that you cannot and most hosts will not keep you on php5.2/5.3 forever, in fact sometimes they update your php to a newer version because of security risks in older outdated versions so while you might be able to retain your same php and vBulletin version for quite a while, it will most certainly not be forever. So with all that said, eventually your php will need to be updated and in-turn your forum patched (3.x series) or upgraded to a newer version such as vBulletin 4.x or 5.x.

I like my version 3.8.5 very much, what does 3.8.5 not do when the hosting company upgrades from PHP version 5.3 to 5.4.

It's just going to kick a bunch of depreciation warnings, most all of them have to do with the use of ampersands in php files.

Next time an old lady asks me to help her cross the road im going to tell her to look left and right and do it herself.

I like your thinking on this matter.
I ask a while ago if there would be a cost for 3.8.8 or if it would be given to all license holders that did not want to upgrade to vb 4 or vb54, I was told "Not sure at this time".


That's funny.

Well that is just how I think* it should be done, I do not own vBulletin nor guarantee that they will do this as its their business to shape and mold into whatever they wish.

I do know that the licenses are intangible therefor its literally no skin off their back to do this and imo like I said above more would pay for a new version of 3.8.x that's up to date with php5.4 then they will a 5.x license just to download and upgrade from for example 3.8.6 to 3.8.8 (again imo) as paying for something you will not use even if you get a "bonus" still does not sit well with many.

What do you like about it? 3.8.8 is literately bug fixes and security updates.

Make sure you're running the latest version you can download from the members area, and that you've applied the security patch from vBulletin.com.

I'm looking for an experienced vBulletin programmer. 3.8.7 to do a migration.
I would like to find someone in the New York City / long island area to work a long side us in our office,
Please contact: me
thanks!