Announcement

Collapse
No announcement yet.

vBulletin 4.2.5

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Joe D.
    commented on 's reply
    As of the time this thread was current. it worked. At this point there is no longer any point to logging bugs in 4.2.5. Security exploits can be reported to [email protected] but nothing else will be recorded or fixed.

  • Mikethemix
    commented on 's reply
    The snag is that the Jira tracker link posted here is ONLY for v5, not v4.2.5

  • TheLastSuperman
    replied
    Add the disable hooks code to config.php then see if it will run on php7.0, I had one site recently that worked fine on php7.0 just not 7.1 . Needless to say if you disable the mods it should work, then you can simply disable them all (screenshot the active ones first so you know what to run back on) and turn mods back on one-by-one after each other each time checking to see if the mod you turned back on breaks the site or not (sometimes the error will state the file so you can skip adding disable hooks to config and disable the mod related to the file).

    vBSEO can be replaced and mod-rewrite friendly urls used instead with some redirect magic alternatively you can install and run DBSEO (pay for them to install and ask for url hierarchy to be setup the same way note to them that it's important as you wish to retain the old link structure (hierarchy).

    It's more than likely vBSEO. Sometimes though errors can show if for example when you recompiled to PHP7.0/7.1 was mysqli extension active? *If it was required the mod may not work until it's working*. Something can simply be disabled and a quick recompile using easy apache could sort.
    Disabling Modifications OR Plugins via SQL Query - Fix AdminCP/Forum Access vBulletin 4 Articles

    Leave a comment:


  • Mark.B
    replied
    As I mentioned above....old add ons may not be compatible with php 7.

    You should not use vBSEO anyway. It was abandoned years ago, it is riddled with security holes, and it certainly isn't compatible with php 7.

    Leave a comment:


  • faquick
    replied
    I *think* that the problem might be in old add-ons I still have, that I cannot absolutely remove without breaking my site structure and SEO (i.e. the old VBSEO). Still, I am curious to know why I get that syntax error on a core vBulletin file instead of getting another kind of error.

    Leave a comment:


  • faquick
    replied
    actually now I am getting a problem after switching to PHP 7.x

    if I keep it on 5.6.x it works as before, if I use 7.0.x or 7.1.x I get the old syntax error: unexpected '*' in functions.php on line 1576 (that should not happen unless I am running a version lower than 5.6, what could be wrong with php7?)

    Leave a comment:


  • Mark.B
    replied
    Originally posted by faquick View Post
    Yup, that is exactly what I am going to do. Since I have other software running on the server, I hoped I could upgrade the PHP interpreter last, so I am going to alter slightly my plans. But the vBulletin steps will be as you advised.

    Thank you.
    You can always use php 5.6 if that helps. 4.2.5 works with that.

    Leave a comment:


  • faquick
    replied
    Yup, that is exactly what I am going to do. Since I have other software running on the server, I hoped I could upgrade the PHP interpreter last, so I am going to alter slightly my plans. But the vBulletin steps will be as you advised.

    Thank you.

    Leave a comment:


  • Mark.B
    replied
    Originally posted by faquick View Post
    So, the correct path would be FIRST updating to PHP 7.x and THEN upgrading vBulletin, otherwise the upgrade script would not work. Did I understand correctly?
    Yes, that's correct.

    You need to do the two in close succession though, as your existing forum won't work on php 7.

    Best to close the site, back up database, upgrade php, upgrade vBulletin, open site.

    Leave a comment:


  • faquick
    replied
    So, the correct path would be FIRST updating to PHP 7.x and THEN upgrading vBulletin, otherwise the upgrade script would not work. Did I understand correctly?

    Leave a comment:


  • too_cool_3
    replied
    Went from 4.2.1 to 4.2.5 yesterday with ZERO issues!

    I first asked my host, URLJet, to upgrade MySQL to version 5.6.35 > then I downloaded vB 4.2.5 from here and uploaded it to my server > went to run the upgrade script and ran into an error page due to my outdated PHP version (Parse error: syntax error, unexpected '*' in /yoursite/includes/functions.php on line 1576), so popped into my cPanel and used PHP Selector to upgrade to PHP 7.1.4 > then was able to run the vB upgrade script flawlessly without a hiccup > upgraded to vBadvanced CMPS 4.3.0

    Everything works great, noticed a speed boost in page load times and a major drop in server load. Thanks for all your help and answering my questions prior to the upgrade. vB support team, you rock!

    Now to save up a few bucks and upgrade to vB5!
    Last edited by too_cool_3; Tue 30th May '17, 7:36am. Reason: grammar

    Leave a comment:


  • Paul M
    replied
    It works perfectly well on php 7.1.3.

    You must sort out your database error.

    Leave a comment:


  • Alshalan
    replied
    Not working on PHP 7.1.3

    Database error

    Leave a comment:


  • Mark.B
    replied
    Please post your own threads in the support forum so we can assist.

    Helping multiple people in one thread causes confusion.
    This thread is for discussion of the release, rather than support.

    Leave a comment:


  • woodmj
    replied
    Originally posted by bollie View Post
    Parse error: syntax error, unexpected '*' in /home/xxxxx/domains/xxxxx.be/public_html/includes/functions.php on line 1576

    I hit this error too.

    After installing PHP 5.6 my site just white paged and so I had to roll back to VB4.2.4 to get it up again for now. Other non VB sites on the same server seem unaffected.
    $ sudo php -v
    PHP 5.6.30-10+deb.sury.org~trusty+2 (cli)
    Copyright (c) 1997-2016 The PHP Group

    Leave a comment:

widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X