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.
The page source of the CMS front page of one of the problem styles contains a link to the stylesheet and the directory for that style does exist. It's chmoded 755 and the files within it are chmoded 644.
I've done my best to compare style directories that work properly with those that don't and I can't see any difference at all.
If I create a new style, thereby recreating default templates, the new style works correctly.
I've found a fix for this. It's not the most convenient and doesn't make any sense since only several custom styles are affected, but it's a fix none-the-less. Hopefully it will help someone in the future so they don't have to spend a week trying to figure it out themselves.
If the templates are reverted in the style, the styles load and work properly. I'll need to make a note of the changes I've made in various templates and, if necessary, re-modify those templates. If I discover which modified template was causing the problem I'll post it here.
I want to wrap this up. The problem was in the "headinclude" template of the affected styles. I don't know how, but a closing comment tag was malformed. Instead of closing the comment with
-->
the comment was closed with some kind of special character that looked like an arrow.
I don't have a clue how that happened, but after replacing it with the correct closing the styles now work just fine.
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X
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