The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
Is VB4.2.2 safe to run under PHP5.4?
VB insists on not providing a straight answer to this question in their requirements section.
Has anyone run 4.2.2 under PHP5.4 or higher? Is this a supported install? |
#2
|
||||
|
||||
Yes, that is what 4.2.2 was released for, php 5.4.x
|
#3
|
|||
|
|||
The release notes don't make that clear.
I am still unsure about it. Will have to test it. |
#4
|
||||
|
||||
Sure it does.
vBulletin 4.2.2 is a maintenance release primarily focused on php 5.4 compatibility issues, as well as a few other important fixes for Facebook, PayPal & MAPI updates for Mobile 1.5 vBulletin 4.2.2 FULL has been released. Yesterday, 3:40pm vBulletin 4.2.2 is NOW AVAILABLE for download. The feedback thread for the 4.2.2 release is HERE for our licensed customers. vBulletin 4.2.2 is a maintenance release primarily focused on php 5.4 compatibility issues, as well as a few other important fixes for Facebook, PayPal & MAPI updates for Mobile 1.5 The release contains: * Many fixes for php 5.4 compatibility. * MAPI updates for Mobile 1.5 * Facebook updates due to changes by Facebook * PayPal updates due to changes by PayPal. * Update to recognise IE11 User Agent * Fix Import/export of Navigation Manager (Open new page flag) * A couple of security updates in the installer & Forum Runner. * Added the Panjo online community marketplace plug-in. * A number of other major bugs held over from 4.2.1 vBulletin 4.2.2 contains a total of 109 bug fixes, improvement requests, and feature requests. A full list of these changes can be found - HERE. |
Благодарность от: | ||
Amaury |
#5
|
|||
|
|||
You are an optimist at heart.
When I read "focused on php 5.4" and "many fixes for php 5.4" I wonder why they did not write "php 5.4 compatible" and "fixed all issues". VB bit me once with their "PHP 5.2.0 or greater" bullshit they state on the requirements page for VB4. |
#6
|
|||
|
|||
Quote:
I think the problem in development has always been when to release software from development to production. As long as they call it an Alpha or a Beta many of the boards will not, should not, run the software in production: Therefore the amount of bugs that can be reported is directly limited by the testing pool. I believe the outcome was expected. I guess they could have prolonged the release and hoped that the testing pool increased and reported more variances with the code, but I doubt there would have been significant gains. I hope I shed some light on the problems developers face. |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|