Upgrade from 4.2.2 to 4.2.3

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Kenas
    New Member
    • Feb 2011
    • 16
    • 4.1.x

    Upgrade from 4.2.2 to 4.2.3

    Hi, was running vBulletin Version 4.2.2 (PHP 5.4) till i changed my server.
    New server has PHP 5.5 and it started to throw me some internal errors 500 so i decided to upgrade to vBulletin Version 4.2.3

    When i run upgrade.php screen frozes on upgrade 4%

    How should i proceed to repair this ?

  • Wayne Luke
    vBulletin Technical Support Lead
    • Aug 2000
    • 74132

    #2
    Refresh the screen does it pick up where it left off?
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API

    Comment

    • Kenas
      New Member
      • Feb 2011
      • 16
      • 4.1.x

      #3
      No, it skips the installation and tries to install next beta version and again the same for the next one.
      Right now in 4.2.3 beta 3

      Comment

      • Kenas
        New Member
        • Feb 2011
        • 16
        • 4.1.x

        #4
        still cant upgrade to 4.2.3 final and working

        Comment

        • Wayne Luke
          vBulletin Technical Support Lead
          • Aug 2000
          • 74132

          #5
          You'll need to open a support ticket. "500 Server Error" actually provides no information that is helpful in solving issues. This could be that the permissions are incorrect, the server is configured incorrectly, a PHP module is missing, an APACHE module is missing, there is a PHP error, the database isn't available, and many more things. Normally these would be logged and the server administrator could get more information. Seems most hosting providers aren't actually logging them these days though.
          Translations provided by Google.

          Wayne Luke
          The Rabid Badger - a vBulletin Cloud demonstration site.
          vBulletin 5 API

          Comment

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