vbulletin 3.8.11 on php 7.2 ?

[amine13420]

Thank's, i have installed under Mysql, i don't beleive a lot in MariaDB.

thank's for your time

[RCK]

Hello guys,

As you know, vB 3.8.11 is limited to PHP 7.0

Today I find two paid custom version 3.8.12 who support PHP 7.2 / 7.3 :
* Removed By Moderator *

Did someone already test one of them ?

Cheers !

[Dave]

Originally Posted by RCK

Hello guys,

As you know, vB 3.8.11 is limited to PHP 7.0

Today I find two paid custom version 3.8.12 who support PHP 7.2 / 7.3 :
* Removed By Moderator *

Did someone already test one of them ?

Cheers !

Please do not share such links. Those sites share nulled versions of vBulletin which often contain backdoors and goes against vBulletin's terms and conditions.

[RCK]

Originally Posted by Dave

Please do not share such links. Those sites share nulled versions of vBulletin which often contain backdoors and goes against vBulletin's terms and conditions.

Hello Dave,
Thanks for link removal, I was not aware of backdoor sorry.
Are "nulled" versions are pirate php files without license ?

I also find some thread with modifications todo listing.
Are those kind of listing are also forbidden to be shared ?

[ShikiSuen]

Originally Posted by RCK

Hello Dave,
Thanks for link removal, I was not aware of backdoor sorry.
Are "nulled" versions are pirate php files without license ?

I also find some thread with modifications todo listing.
Are those kind of listing are also forbidden to be shared ?

This reply only talks about vBulletin 3.x releases.

1. Whether they have back doors or not challenges your expertises in computer programming. Only you (or any expert you can trust in helping you doing this) can tell whether there are backdoors made deliberately.

2. vBulletin 3.8.x NULLED versions are pirated php files. They were made based on official files. Official php files are zend-encrypted. Null teams decrypt them and rip out the customer system (and possible watermarks) throughout these files. Making such distros is doing software piracy and is under legal risk. **Some** null teams do deply backdoor codes among their distros.

3. On consumer side, official encrypted builds of vBulletin 3.x are definitely not compatible with PHP 7.2 and later. They also have lack of MySQL 8.x syntax support (and later), requiring users to use MariaDB or continue using MySQL 5.x builds.

4. I am not familiar with PHP programming related to MySQL. One can go through error messages generated by PHP 7.4 (probably the final major release of PHP 7 series) to troubleshoot the compatibility issues throughout PHP files, theme templates, language xmls, etc. These must be performed on an decrypted version, which means that the removal of customer system is not necessary. Also, if you are doing this, turn off gzip compressions in both your forum settings and your web hosting software (apache, nginx, etc.)... Otherwise, a forum page can be unloadable due to being scrambled by syntax warning messages injected by PHP itself.

5. You should be fine as long as you have a valid license in your vBulletin official customer account and it is only designated to the sole forum site you are using (whether this site is using Nulled version of vBulletin or not). I suggest you to confirm by emailing (not by posting on their official forums) vBulletin pre-sale teams to confirm possible legal risks. Posting such questions on vBulletin official forums can cause lifetime ban of your forum account within 24hrs.

6. To my knowledge, if a site is running unlicensed vBulletin, the domain provider and / or the host provider may under DMCA pressure from vBulletin officials and they are likely to have to stop providing you their domain / host service.

// I don't make decryptions or Null piracy. I am just recently having curiocities in vBulletin 3.8.x compatibility with PHP 7.4 and modern system environments.

[RCK]

Hello ShikiSuen,

Thanks for the detailled explanation

Yes I have a valid vB licence for my domain since vb2 release.
I don't want to move to vB4 or 5, and lack of php 7.2 support is starting to be problematic.
I'm not aware of encrypted php version of vb, as far as I know, all the php files I download from member area are tagged with my customer number, but unencrypted.
Finally, since I have access to my PHP files and vb templates, I'm simply looking for one guideline of modifications to be applied to make my own vb 3.8.11 compatible with php 7.2

Paul_M, your support of old vB are missing us !

[ShikiSuen]

Originally Posted by RCK

Hello ShikiSuen,

Thanks for the detailled explanation

Yes I have a valid vB licence for my domain since vb2 release.
I don't want to move to vB4 or 5, and lack of php 7.2 support is starting to be problematic.
I'm not aware of encrypted php version of vb, as far as I know, all the php files I download from member area are tagged with my customer number, but unencrypted.
Finally, since I have access to my PHP files and vb templates, I'm simply looking for one guideline of modifications to be applied to make my own vb 3.8.11 compatible with php 7.2

Paul_M, your support of old vB are missing us !

(I decided not to download any build of vBulletin from customer area despite that I have the license, this is to make sure I am clean with my license.)

Supposing that your downloaded source code of vBulletin 3.8.11 from vBulletin official is not zend encrypted: You can find an online PHP grammar checker (e.g. https://phpcodechecker.com) and check through PHP files and fix them one by one. After that, check both the language xml and the template xml: find all condition expressions and make sure that all constants used in these expressions are not like [constant] but like ['constant']. If not, gzip-compressed pages of vBulletin may return to either a blank page or crashed webpage to your web browser. If these are enough, then I guess you can use it with MariaDB (at least 10.4.x).

(Please stay away from MySQL 8 due to its SQL syntax changes, unless you update vBulletin source code to use new syntax and the new stronger password encryption system.)