3.8.8 won't run on a 'later' spec server

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • chrismk
    Member
    • Aug 2006
    • 44
    • 3.6.x

    3.8.8 won't run on a 'later' spec server

    I am trying to move a vBulletin 3.8.8 to a new server running MySQL 5.6.23 and PHP 5.5.18.
    It won't run; the generic vBulleting error splash screen displays inviting me to check the domain.

    The notes on the version download page state 3.8.8 requires php 5.2.0 or greater and MySQL 4.0.16 or greater.
    Are there any other issues I should be aware of?

    Thanks.
  • donald1234
    Senior Member
    • Oct 2011
    • 1953
    • 4.1.x

    #2
    You need vbulletin 3.8.9 for PHP 5.5 max PHP5.4 for 3.8

    Comment

    • Mark.B
      vBulletin Support
      • Feb 2004
      • 24288
      • 6.0.X

      #3
      As Donald states, you'll need vB 3.8.9 if you're running php 5.6.
      MARK.B
      vBulletin Support
      ------------
      My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
      My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

      Comment

      • chrismk
        Member
        • Aug 2006
        • 44
        • 3.6.x

        #4
        Many thanks!

        Comment

        • Paul M
          Former Lead Developer
          vB.Com & vB.Org
          • Sep 2004
          • 9886

          #5
          Originally posted by chrismk
          I am trying to move a vBulletin 3.8.8 to a new server running MySQL 5.6.23 and PHP 5.5.18.
          It won't run; the generic vBulleting error splash screen displays inviting me to check the domain..
          What generic error exactly is this referring to ?

          While you really need 3.8.9 for php 5.6, I cannot think of anything that would actually cause it to fail with error screens.
          Baby, I was born this way

          Comment

          • chrismk
            Member
            • Aug 2006
            • 44
            • 3.6.x

            #6
            Thanks Paul.

            You were right.
            I got back on to the hosting company relaying what you said and they found a connection error!

            Comment

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