If I'm not using publishing suite (just forum) do I have to upgrade?
New security patch required?
Collapse
X
-
Tags: None
-
The recently released 4.2.2 Patch Level 3 is only really essential for those with the CMS. Although it won't do any harm if you did upload it.
Note that for users already running 4.2.2 it is NOT an upgrade - it's just a patch file.
If however you are running a lower version of vb4 than 4.2.2 then you MUST carry out a FULL upgrade to 4.2.2 PL3. This involves downloading the full package and running the upgrade script.MARK.B
vBulletin Support
------------
My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
My Unofficial vBulletin Cloud Demo: https://www.adminammo.comComment
-
In your case, if you are running 4.2.2 you should apply the patch. If you are running an earlier version than 4.2.2, you should carry out a full upgrade.MARK.B
vBulletin Support
------------
My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
My Unofficial vBulletin Cloud Demo: https://www.adminammo.comComment
-
There's a big difference between NOT HAVING the cms (as in, the old "Forum Only" vB4 license), and simply having it disabled.
In your case, if you are running 4.2.2 you should apply the patch. If you are running an earlier version than 4.2.2, you should carry out a full upgrade.Comment
-
There is no difference between 4.2.1 and 4.2.2 except the latters ability to work on PHP 5.4 so there are no reasons not to upgrade from 4.2.1 to 4.2.2Comment
-
Comment
-
The vast majority of plugins for 4.1 will work with 4.2. The few that don't tend to be related to the navbar, which changed in 4.2. Most such navbar plugins are now unnecessary anyway due to the new navbar manager. Others fail because they aren't compatible with later versions of php, but if you have that issue you cannot stay on 4.1 anyhow.MARK.B
vBulletin Support
------------
My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
My Unofficial vBulletin Cloud Demo: https://www.adminammo.comComment
-
-
There is always a risk running outdated software. Especially software that isn't receiving active development and only security fixes.Translations provided by Google.
Wayne Luke
The Rabid Badger - a vBulletin Cloud demonstration site.
vBulletin 5 APIComment
-
In this case, the two updated cms files have remained largely unchanged across 4.x versions.
I believe that you could upload the fixed 4.2 versions without them causing any obvious issues.
However, you do that at your own risk as I havent checked this, especially as "4.1" actually has 13 sub versions (4.1.0 - 4.1.12).
Baby, I was born this wayComment
-
A link to the 4.2.2 upgrade package would be great.
Comment
-
I have been searching everywhere looking for a 4.2.2 upgrade (I am running 4.1.8) in order to apply the new security patch- where can I find it? In my account, when I click on "Upgrade/Renew" I am only given the option of paying to upgrade to v5 products.
A link to the 4.2.2 upgrade package would be great.
Just go to the members area (https://members.vbulletin.com) and click the download link on the right.MARK.B
vBulletin Support
------------
My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
My Unofficial vBulletin Cloud Demo: https://www.adminammo.comComment
-
When did the policy of providing security patch level updates for previous version of v4 stop? Is there a link to the announcement?
If there are no plans to provide patch level updates for earlier versions - and it appears this is the case based on the comments by the lead devs in this thread and other similar threads from today - would someone please be kind enough to indicate how we would manually patch our older 4.1.10pl3 version? Do we do this by diffing the stock 4.2.2 against the patched version and then manually locate the affected code in our 4.1.10pl3 codebase and affect a patch? (edit: I can't see that this will work since the 4.2.2pl4 patch presumably has all of the patches from pl1 to pl4 rolled into one?)
Thanks.Comment
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Comment