PHP7 Compatability

[Paul M]

If you're going to do 7.2 you might consider making sure it's compatible with 7.3, as it offers performance improvements and will have a security update life cycle at least a year longer than 7.2.

Yes, I was looking at the php site other day and noticed they had started on the release schedule for 7.3

Atm, I have not looked at whats changed, or obtained a copy to see what happens.

They deprecated a whole bunch of stuff in 7.2, if thats removed in 7.3 then 4.2.5/3.8.12 will not run on it.
(even with errors reporting suppressed, as all those warnings will become fatal errors).

 

[Paul M]

They deprecated a whole bunch of stuff in 7.2, if thats removed in 7.3 then 4.2.5/3.8.12 will not run on it.

A quick look over the documentation does not seem to suggest any of the previously deprecated stuff has been removed.

Also, I didnt see any changes that would have any adverse effect on vB.
From what I read, I think 4.2.5/3.8.12 would continue to run on PHP 7.3, as long as you had all error reporting disabled.

I have not physically tested it, but I dont see any obvious (new) issues.

 

[djbaxter]

The problem will still be plugins. I didn't take it very far but I tried going to PHP7.2 for one 4.2.5 forum and it broke the forum. I didn't explore why - I just reverted to PHP 7.1 - but if I recall correctly it was giving me a blank page.

 

[Paul M]

Yes, plugins may well fail, but thats a whole different issue.

 

[djbaxter]

Yes. Just reminding people that even if you upgrade vBulletin we'll still have to go through the fun process of figuring out which plugins have broken and why.

 

[Banxix]

Yes. Just reminding people that even if you upgrade vBulletin we'll still have to go through the fun process of figuring out which plugins have broken and why.

The safest way is to make a copy of your forum in your localhost, it will give you free time to explore the cause.

 

[Paul M]

A few people have asked if I'm still working on making vB3 & vbB4 compatible with PHP 7.2, and how this would work.

The answer is yes, in my spare time (which I dont have much of !).
I'm not in a rush as 4.2.5 & 3.8.11 work with 7.1, so PHP 7 is covered for a while.

When I'm ready, I will have Alpha Versions (most likely as 4.2.9 & 3.8.15).
These will of course be completely unofficial, but would work as upgrades from the current versions.
(Leaving a gap of 3 versions between them and 4.2.5/3.8.11, just covers things in case IB ever release an update).

I would likely make these available as a private update service, which would work as follows.

1. You pay me (!).
2. You download 4.2.5 (or 3.8.11) from your members area, and send me the zip file.
3. I will extract your files, run them through an update process, and then zip them back up.
4. I will return the zipped 4.2.9/3.8.15 files back to you.
5. You use them to upgrade your site in the normal manner.
6. You report any bugs to me, and in time I will look at them.
7. I would periodically make bug fixes available (as zipped updates).

The reason for doing it this way is because I can only edit your licensed files, not supply my own.

A few points - I would not update any version other than 4.2.5 or 3.8.11, for two reasons ;

1. Its just much harder to update older version files
2. It proves you are licensed for the latest version (this is really only an issue for vB3).

The cost would likely be around the $40 to $49 mark (once only).
Support (and bug fixes) would be limited, and only for issues directly related to PHP 7.2

I would stress at this point, I'm still only considering this.
Whether I actually do it depends on my time (and of course, any interest shown).

The "Pay Me" first would not be negotiable.
I dont have time to be chasing people for payment.
If you dont trust me, thats fine, you simply would not use the service.

I hope this answers all the questions people have been asking me in the last few months.

Just an update on this, as another four months have passed.

In short, I'm not going ahead with any vB3/vB4 upgrade service.

1. I dont have the time.
2. I simply dont have the interest or desire anymore.
3. I dont use vB4 at all, and were I ever to update, I would then no longer be using vB3 !
4. The fact is that it works fine on php 7.1 - and with error reporting turned off, will limp along well enough on php 7.2
5. PHP just keep updating, I could not keep up - people are already asking about php 7.3, and I havent even finished working on php 7.2

Basically, 4.2.5 & 3.8.11 are good for another 1.5 years on supported php 7.1 versions.
After that you can continue on PHP 7.1 of course, it will just be unsupported by PHP themselves.
Equally, you could likely limp along on 7.2 (maybe even 7.3) with error reporting turned off for another 2+ years.

If any of these options is an issue for you then you should consider a move to something else by then, if not before.

 

[Pete]

people are already asking about php 7.3

WTH... it's not even out yet.

 

[R0binHood]

Beta is now out http://be2.php.net/archive/2018.php#id2018-08-02-1

 

[eva2000]

Beta is now out http://be2.php.net/archive/2018.php#id2018-08-02-1

Looking good so far on Centmin Mod LEMP stack

php -v
PHP 7.3.0beta1 (cli) (built: Aug  3 2018 04:35:10) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.0-dev, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.3.0beta1, Copyright (c) 1999-2018, by Zend Technologies

php --ri sodium

sodium

sodium support => enabled
libsodium headers version => 1.0.16
libsodium library version => 1.0.16

php -r 'print_r(get_defined_constants());' | grep -i argon
    [PASSWORD_ARGON2I] => 2
    [PASSWORD_ARGON2ID] => 3
    [PASSWORD_ARGON2_DEFAULT_MEMORY_COST] => 1024
    [PASSWORD_ARGON2_DEFAULT_TIME_COST] => 2
    [PASSWORD_ARGON2_DEFAULT_THREADS] => 2
    [SODIUM_CRYPTO_PWHASH_ALG_ARGON2I13] => 1
    [SODIUM_CRYPTO_PWHASH_ALG_ARGON2ID13] => 2
    [SODIUM_CRYPTO_PWHASH_STRPREFIX] => $argon2id$

Paul M appreciate all you have done, otherwise vB3/4 would of died alot sooner without PHP updated support !

 

[steris56]

i put in 4.2.5 suite but for some reason i get a blank page for forum only my server folks upped me to 7.1php

 

[Paul M]

Probably an incompatible plugin.

 

[CyberJoe]

I am still stuck on running VB4.2.5. I have already bought the Invision licenses, but the sheer amount of time it takes to convert is keeping me from going ahead, it looks like my site will be almost unusable for about a week while the converter is doing its thing.

So I decided to get VB installed on PHP 7.2 (my host is doing a forced migration in November, either migrate to 7.2 or move, I do not want to move).

The install worked 100%, the site is running 100% so far.

My next step will now be to find and install the very few plugins I use one at a time, if we find errors the devs at the office will try and resolve the code changes to facilitate the upgrade to 7.2, so there is light at the end of the tunnel.

Also I do not use any plugin that I absolutely have to have, so if we cannot fix the plugins I will just remove it.

Then between I need to get access to a super duper fast server to check the conversion, I might prep a small linode box, then once I have my site running on it bump it up to the fastest server they offer and see how long it will take there.

 

[CyberJoe]

I use very few plugins, and just reinstalled them all on my 7.2 installation, and only two are failing so I will get those checked and updated by own our team this week.

 

[pierce]

how many posts? (i usually find the posts table was the nightmare)

 

[Qoueo]

My host ends support for PHP7.1 so I tried PHP 7.3 and it seems to work fine for me. Thanks!

 

[HallofFamer]

PHP 7.4 introduces a lot of interesting and useful new features, may be worth giving it a try and hope VB 3.8 will run on it.

 

[CyberJoe]

To pick up on an old thread, we have now already fixed a few plugins, some fixed were as simple as one line of code for example.

 

[craigForo]

So to verify vB4.2.5 will not run on php 7.2? Or is it just anything above 7.2?

 

[zappaDPJ]

So to verify vB4.2.5 will not run on php 7.2? Or is it just anything above 7.2?

vBulletin 4.2.5 is not compatible with PHP 7.2.