There was an issue identified in vBulletin 4.1.0 and 4.1.0 PL1 that may potentially break a number of 3rd party plugins and modifications.
Please note, this issue does not affect the core vBulletin product, but changes that were made to the core vBulletin product may potentially break 3rd party plugins and modifications.
As part of our inclusion of the mobile APIÂ’s, the vBulletin templates were re-factored in how they are rendered to support the API.
The $vbulletin variable was placed so that it was not part of the eval process, and subsequently out of scope for the templates of 3rd party plugins and modifications templates.
Here is an example template conditional that would be affected:
Code:
in group 5, 6 or 7
We have released a patch which now exposes the $vbulletin variable to templates, and should enable such plugins/modifications to work as they did previously.
To rectify the issue please download the patch from the members area of vBulletin: Please Log In
Upgrading from 4.1.0/4.1.0 PL1
If you are already running 4.1.0/4.1.0 PL1, the process you will be required to undertake to make your board immune to this issue is the following:
Visit the Patches section of the vBulletin Members' Area and download the patch for 4.1.0/4.1.0 PL1, then extract the files from the archive you downloaded, then upload the files to your board via FTP etc., overwriting the existing files. This will update your version to the PL2 release.
Upgrading from Versions Earlier than 4.1.0
If you are not already running 4.1.0/4.1.0 PL1, we have updated the downloadable version of our software, so you can download 4.1.0/4.1.0 PL1 from the Members' Area and perform an upgrade as normal.
Full instructions for upgrading vBulletin are available here.
Download vBulletin 4.1.0 PL2
As usual, the version released today is available for all customers with valid, active licenses to download from the vBulletin Members' Area.
vBulletin Members Area
You can discuss this patch release in the existing 4.1.0/4.1.0 PL1 release discussion.
We are currently in the process of e-mailing all customers, and updating our admin control panel news to inform all customers.
We would like to thanks user dartho for the original report
More...
Please note, this issue does not affect the core vBulletin product, but changes that were made to the core vBulletin product may potentially break 3rd party plugins and modifications.
As part of our inclusion of the mobile APIÂ’s, the vBulletin templates were re-factored in how they are rendered to support the API.
The $vbulletin variable was placed so that it was not part of the eval process, and subsequently out of scope for the templates of 3rd party plugins and modifications templates.
Here is an example template conditional that would be affected:
Code:
in group 5, 6 or 7
We have released a patch which now exposes the $vbulletin variable to templates, and should enable such plugins/modifications to work as they did previously.
To rectify the issue please download the patch from the members area of vBulletin: Please Log In
Upgrading from 4.1.0/4.1.0 PL1
If you are already running 4.1.0/4.1.0 PL1, the process you will be required to undertake to make your board immune to this issue is the following:
Visit the Patches section of the vBulletin Members' Area and download the patch for 4.1.0/4.1.0 PL1, then extract the files from the archive you downloaded, then upload the files to your board via FTP etc., overwriting the existing files. This will update your version to the PL2 release.
Upgrading from Versions Earlier than 4.1.0
If you are not already running 4.1.0/4.1.0 PL1, we have updated the downloadable version of our software, so you can download 4.1.0/4.1.0 PL1 from the Members' Area and perform an upgrade as normal.
Full instructions for upgrading vBulletin are available here.
Download vBulletin 4.1.0 PL2
As usual, the version released today is available for all customers with valid, active licenses to download from the vBulletin Members' Area.
vBulletin Members Area
You can discuss this patch release in the existing 4.1.0/4.1.0 PL1 release discussion.
We are currently in the process of e-mailing all customers, and updating our admin control panel news to inform all customers.
We would like to thanks user dartho for the original report
More...