vbulletin is finally dead: vb3/4 EOL and not compatible with php7.2 and up.

[Alfa1]

https://www.vbulletin.com/forum/foru...-x-end-of-life
https://www.vbulletin.com/forum/foru...te-end-of-life

Warnings displayed at vbulletin.com:
Please note that vBulletin 3.8.11 is not compatible with PHP 7.2.
Please note that vBulletin 4.2.5 is not compatible with PHP 7.2.

[pegasus]

Yeah I assume they had to do it because the security vulnerabilities I reported required too much development to fix. It took almost 2 months for us to do it in VaultWiki. The vulnerabilities were crippling for avatars and attachments: https://www.vaultwiki.org/articles/2...ecurity-Issues

Additionally, I don't think there was a way (without lots of work) to make them compatible with PHP 7.2 without raising the minimum requirement to PHP 5.3 (unless they did that already). The only issue I'm aware of is the use of create_function(), which should only issue E_DEPRECATED errors, which vBulletin suppresses already.

[Mccreary]

Yeah I assume these are the best fat burners for women and had to do it because the security vulnerabilities I reported required too much development to fix. It took almost 2 months for us to do it in VaultWiki. The vulnerabilities were crippling for avatars and attachments: https://www.vaultwiki.org/articles/2...ecurity-Issues

Additionally, I don't think there was a way (without lots of work) to make them compatible with PHP 7.2 without raising the minimum requirement to PHP 5.3 (unless they did that already). The only issue I'm aware of is the use of create_function(), which should only issue E_DEPRECATED errors, which vBulletin suppresses already.

Well, that's a shame. What can you do. I still think they should have done more to extend the life of those versions a bit longer, but it was ultimately inevitable.

[Delfi R]

If you are interested there exists a vW version 4.2x that runs on PHP 7.2.