vBulletin 4.2.5 is end of life and will not be receiving any future development. Warning: vBulletin 4.2.5 is not compatible with PHP 7.2.0 or higher.
Welcome to the vBulletin support forums! In our community forums you can receive professional support and assistance with any issues you might have with your vBulletin Products.
If you are having problems posting in the relevant areas for your software, please see this topic.
Upgrade to vBulletin 5
We're pleased to announce a special promotion for upgrading your vBulletin 3/4 sites to vBulletin 5. From now until December 31st, we are offering vBulletin 5 license upgrades at $169 each. This promotion is available to all vBulletin 3 (owned) and vBulletin 4 license holders, entitling you to the latest version of vBulletin 5.
If you would like to purchase this upgrade, please log into the vBulletin Members Area and use Promo Code: vB5UPGRADE during checkout to apply the discount.
Thanks for the reply, although I believe I have both steps 1 and 2 covered. 3.6.0 of vbseo, and I downloaded my existing core_class.php to edit, then re-uploaded it. Just changed the 7 to a 9.
I tried a server reboot as suggested by motowebmaster, but had no luck there, I just ended up with every page, even forum home, giving:
Warning: Cannot modify header information - headers already sent by (output started at [path]/includes/class_core.php:1) in [path]/includes/functions.php on line 3904
I also tried disabling VBSEO and vbOptimize (which handles CDN caching of many files), and still had no luck.
1. Make sure you have tyhe latest version of vBSEO installed.
2. Make sure you are uploading the correct version of includes/class_core.php
- I got a similar error when I first tried to change the version but it turned out I was uploading an earlier version that the one I was running (4.13).
I don't get why there is a security patch, so far as it is known, there are only two yui files affected, one isn't in vB3.x and the other one was patched already. An explanation would be appreciated.
I don't get why there is a security patch, so far as it is known, there are only two yui files affected, one isn't in vB3.x and the other one was patched already. An explanation would be appreciated.
The download for 3.8.7 pl1 and my current version yui (3.8.5) are the exact same file sizes on all files. Changing the define in class_core won't do anything for local hosted.
So, why isn't the local instance patched? I have no desire to run remote when i have my own min functionality and cdn serving my js with superior performance of my own server and minimization and skips a dns lookup over remotely hosted.
Should i just download yui from yahoo themselves and find the files to upload on my own? why weren't the files updated?
I don't understand the security patch- it only changes the line in the class_core.php file to 2.9.0. What if your settings were set to use a local copy of the files (like mine were)? How can changing a line in a file upgrade your local copy of your YUI files?
Hmm, so does the 3.8.7 PL1 include the latest YUI, or it doesn't? I serve my own to save a DNS look up, and I combine my .js files to save http requests. I'm not about to revert these improvements. Could a vB staff please confirm the latest YUI is or isn't included?
Hi at vB,
I am planning to update our site Australian Photoholics Forum "ausph.com" to SSL.
Last time we tried this, we broke our site which was down for a week!
Everyone here...
Good afternoon.I set ssl whatever forum was on the https protocol, prescribed in your permanent address offline via https, but do not know how to do so, that would be a http version offline (http://f...
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also consent to the transfer of your data to our servers in the United States, where data protection laws may be different from those in your country.
Comment