Announcement

Collapse
No announcement yet.

PHP 7.x not working with 4.2.5

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

  • faquick
    replied
    Yes I know, I remember the way it ended, yet we decided to keep everything as it was, for stability sake. But now time has come that we face the need to change the situation. Thank you for your suggestion, I appreciate that you are helping even if it is something outside the scope of the official vBulletin support

    Leave a comment:


  • Mark.B
    replied
    Originally posted by faquick View Post
    I believe I am having issues after updating to vBulletin 4.2.5 due to the presence of VBSEO. I cannot simply remove it, because the structure of the site has been like that for a long time and I know I would lose a lot if just doing so.

    Have you been able to solve it someway and have it run under PHP 7.x ? Or any other suggestion to stop relaying on old software (vbseo) would be very appreciated. Thank you.
    vBSEO was not our product, it was produced by a third party company which ceased trading years ago.
    The code not only needs updating for php 7, it also needs all the security holes finding and patching. This is way outside the scope of our support.

    My suggestions:
    1. Run php 5.6 for now so vBSEO still works
    Last edited by Mark.B; Fri 28th Dec '18, 10:58am.

    Leave a comment:


  • faquick
    replied
    I believe I am having issues after updating to vBulletin 4.2.5 due to the presence of VBSEO. I cannot simply remove it, because the structure of the site has been like that for a long time and I know I would lose a lot if just doing so.

    Have you been able to solve it someway and have it run under PHP 7.x ? Or any other suggestion to stop relaying on old software (vbseo) would be very appreciated. Thank you.

    Leave a comment:


  • Paul M
    replied
    There *is* a simple explanation.

    Changes for PHP7 will break old (non compliant) code.
    The Recaptcha v.2 mod is a known example, and a fix was posted in its support thread on vb.org.

    Leave a comment:


  • Mark.B
    replied
    Originally posted by dan325ci View Post
    I can definitely say without a doubt that the upgrade to the forums 4.2.5 has cause several modifications to stop working. At first we also upgraded to PHP 7.0 and I thought that was the reason for the mods to suddenly stop working, but after reverting PHP back to 5.6, the mods still didn't work.....therefore, i am pretty sure it has something to do with this latest 4.2.5 update.

    We have completely lost our Vbulletin IBproArcade because of this update. Several other mods such as Recaptcha v.2 do not work anymore also.

    I wish there was a simple explanation for all this.
    New versions of the software can and sometimes do break modifications.
    This is one of the reasons you should never upgrade a live site. Always upgrade a test site first.

    Leave a comment:


  • dan325ci
    replied
    I can definitely say without a doubt that the upgrade to the forums 4.2.5 has cause several modifications to stop working. At first we also upgraded to PHP 7.0 and I thought that was the reason for the mods to suddenly stop working, but after reverting PHP back to 5.6, the mods still didn't work.....therefore, i am pretty sure it has something to do with this latest 4.2.5 update.

    We have completely lost our Vbulletin IBproArcade because of this update. Several other mods such as Recaptcha v.2 do not work anymore also.

    I wish there was a simple explanation for all this.

    Leave a comment:


  • MDawg
    replied
    Originally posted by MDawg View Post

    I looked in WHM under ModSecurity Tools, and
    The Hits List is empty.
    however, the Rules list is also empty - You have no rules.


    Anyway, I believe I found the issue. When I disabled these two mods:

    Title Tag Fetcher (Auto Replace URL with Titletag)
    http://www.vbulletin.org/forum/showthread.php?t=189658

    and
    Automatic Tagger From Message Content and Title
    http://www.vbulletin.org/forum/showthread.php?t=234026

    the message posts seem to work fine again running php 7.

    Those two mods do not affect vb 4.2.5 while running php 5.6, but they cause the problems noted when running php 7. Determined that BOTH must be disabled to eliminate issues.


    Automatic Tagger is no big deal, but the external title fetcher is something that you really get used to having.
    A programmer helped me with minor alterations to the code in these two mods such that they are both now working with vb 4.2.5 running PhP 7.

    Leave a comment:


  • Wayne Luke
    replied
    Originally posted by MDawg View Post
    Those two mods do not affect vb 4.2.5 while running php 5.6, but they cause the problems noted when running php 7. Determined that BOTH must be disabled to eliminate issues.
    PHP 7 has stricter rules on the syntax of code and how things are handled. This is why special versions of vBulletin had to be created to support it. Addons have to be updated as well.

    Leave a comment:


  • Mark.B
    replied
    Any diagnostics should always start by disabling modifications.

    The trouble with modifications is that unless they are updated by their authors, as the world moves on they will eventually break.

    It is always worth checking the relevant modification thread on vBulletin.org to see if there's an updated version, or any manual fixes posted.

    Leave a comment:


  • MDawg
    replied
    Originally posted by Mark.B View Post

    Check mod_security, that can cause the message editor to go blank.
    I looked in WHM under ModSecurity Tools, and
    The Hits List is empty.
    however, the Rules list is also empty - You have no rules.


    Anyway, I believe I found the issue. When I disabled these two mods:

    Title Tag Fetcher (Auto Replace URL with Titletag)
    http://www.vbulletin.org/forum/showthread.php?t=189658

    and
    Automatic Tagger From Message Content and Title
    http://www.vbulletin.org/forum/showthread.php?t=234026

    the message posts seem to work fine again running php 7.

    Those two mods do not affect vb 4.2.5 while running php 5.6, but they cause the problems noted when running php 7. Determined that BOTH must be disabled to eliminate issues.


    Automatic Tagger is no big deal, but the external title fetcher is something that you really get used to having.
    Last edited by MDawg; Thu 11th May '17, 9:50pm.

    Leave a comment:


  • Paul M
    replied
    Originally posted by neal007 View Post
    That does make it work, however, I need my plugins such as Tapatalk and VBSEO. (Mainly tapatalk is key).
    VBSEO is long dead, and doesnt run on PHP 7.
    I dont know about Tapatalk, you would have to contact them.

    vB 4.2.5 runs quite happily on php 7.1 - but it doesnt have special magic powers to make old products and plugins work.

    Leave a comment:


  • Wayne Luke
    replied
    Any addon that hasn't been updated to PHP 7.X, will cause problems. You will need to evaluate each of your addons and make sure they are updated.

    Leave a comment:


  • Mark.B
    replied
    Originally posted by MDawg View Post
    I don't have vbseo on my vb 4.2.5 forum, and when I toggle back and forth between PhP 5.6.30 or 7.0.18 the posts that are made are invisible when running PhP 7, and fine with PhP 5.6 I mean like - blank content. The title will appear on an Advanced Reply to a post, but no post itself. On a Quick Reply if PhP 7 is active, post content blank.

    The forum itself is not blank - just any new posts attempted to be made while running PhP 7.
    Check mod_security, that can cause the message editor to go blank.

    Leave a comment:


  • MDawg
    replied
    I don't have vbseo on my vb 4.2.5 forum, and when I toggle back and forth between PhP 5.6.30 or 7.0.18 the posts that are made are invisible when running PhP 7, and fine with PhP 5.6 I mean like - blank content. The title will appear on an Advanced Reply to a post, but no post itself. On a Quick Reply if PhP 7 is active, post content blank.

    The forum itself is not blank - just any new posts attempted to be made while running PhP 7.

    Leave a comment:


  • Mark.B
    replied
    The problem is likely to be VBSEO.
    VBSEO hasn't even existed for several years, the company behind it ceased trading.

    You should remove it as soon as possible as it contains unpatched security flaws. However, you need to be aware that this will change your URL structure which will cause problems with your existing search engine results.

    Whilst you decide what to do, just run php 5.6.
    Last edited by Mark.B; Fri 28th Dec '18, 10:59am.

    Leave a comment:

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