Upgrading Problems

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • havenfriends
    New Member
    • Nov 2007
    • 21

    Upgrading Problems

    After upgrading to 3.7 all was going well until step 6 when I got this message. Can anyone please help

    Step 6) Upgrade to vBulletin 3.7.0 Beta 2 Complete!

    Warning: require_once(/home/theparro/public_html/vbullet/includes/adminfunctions_bookmarksite.php) [function.require-once]: failed to open stream: No such file or directory in /home/theparro/public_html/vbullet/install/upgrade_370b2.php on line 1213

    Fatal error: require_once() [function.require]: Failed opening required '/home/theparro/public_html/vbullet/includes/adminfunctions_bookmarksite.php' (include_path='.:/usr/local/php52/pear') in /home/theparro/public_html/vbullet/install/upgrade_370b2.php on line 1213
    Thank you in advance, The above means absolutely nothing to me I'm afraid.
  • havenfriends
    New Member
    • Nov 2007
    • 21

    #2
    Sorry to double post here, the above problem is sorted, but now I have this message appear, it has worried me a little bit,

    Your vBulletin version does not appear to match with the version for which this script was created (version 3.7.0 Beta 2).
    Please ensure that you are attempting to run the correct script.
    If you are sure this is the script you would like to run, click here.
    I'm not sure what I should be doing here, Please can anyone help.

    Comment

    • Jose Amaral Rego
      Senior Member
      • Feb 2005
      • 11058
      • 1.1.x

      #3
      1. Try uploading original vBulletin version 3.7.0 non-image files in ASCII mode (except install.php) to overwrite those on server
      2. You can just try this to see if you have any files that do not belong or have not been overwritten from an upgrade.
        Admin Control Panel > Maintenance > Diagnostics > Suspect File Versions

        [Note: In some cases you may also need to remove any of the listed .xml files in the includes/xml directory.]
      3. To disable the plugin/hook system completely without accessing the Admin CP options, you need to edit includes/config.php and add the following code after <?php in the next empty line:
        define('DISABLE_HOOKS', true);
      4. Run install/finalupgrade.php


      How did you resolve the other issue?

      Comment

      • havenfriends
        New Member
        • Nov 2007
        • 21

        #4
        Thank you so much Jose

        I have done No. 2 and this is what I got,

        license_agreement.htmlFile not recognized as part of vBulletinvb3_readme.htmlFile not recognized as part of vBulletinvb3_readme.txtFile not recognized as part of vBulletinScanned 50 files
        ./admincpScanned 3 files
        ./archiveScanned 31 files
        ./clientscriptScanned 3 files
        ./clientscript/yuiScanned 2 files
        ./images/regimage/fontsScanned 94 files
        ./includesadminfunctions_bookmarksite.phpFile not recognized as part of vBulletinScanned 18 files
        ./includes/cronScanned 8 files
        ./includes/paymentapiScanned 8 files
        ./includes/xmlbitfield_vbulletin.xmlFile does not contain expected contentscpnav_impex.xmlFile not recognized as part of vBulletincpnav_vbulletin.xmlFile does not contain expected contentshooks_vbulletin.xmlFile does not contain expected contentsjs_safe_phrases.xmlFile does not contain expected contentspodcast_vbulletin.xmlFile does not contain expected contentsspiders_vbulletin.xmlFile does not contain expected contentsScanned 80 files
        ./installauthenticate.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2finalupgrade.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2init.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2install_language_en.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2installcore.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2mysql-schema.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2tableprefix.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300b3.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300b4.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300b5.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300b6.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300b7.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300g.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300rc1.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300rc2.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300rc3.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_300rc4.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_301.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_3010.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_3011.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_3012.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_3013.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_3014.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_3015.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_302.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_303.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_304.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_305.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_306.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_307.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_308.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_309.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_350.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_350b1.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_350b2.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_350b3.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_350b4.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_350rc1.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_350rc2.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_350rc3.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_351.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_352.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_353.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_354.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_355.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_360.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_360b1.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_360b2.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_360b3.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_360b4.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_360rc1.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_360rc2.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_360rc3.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_361.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_362.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_363.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_364.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_365.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_366.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_367.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_368.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgrade_370.phpFile not recognized as part of vBulletinupgrade_370b2.phpFile not recognized as part of vBulletinupgrade_370b3.phpFile not recognized as part of vBulletinupgrade_370b4.phpFile not recognized as part of vBulletinupgrade_370b5.phpFile not recognized as part of vBulletinupgrade_370b6.phpFile not recognized as part of vBulletinupgrade_370rc1.phpFile not recognized as part of vBulletinupgrade_370rc2.phpFile not recognized as part of vBulletinupgrade_370rc3.phpFile not recognized as part of vBulletinupgrade_370rc4.phpFile not recognized as part of vBulletinupgrade_language_en.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2upgradecore.phpFile version mismatch: found 3.7.0, expected 3.6.8 Patch Level 2vbulletin-adminhelp.xmlFile does not contain expected contentsvbulletin-language.xmlFile does not contain expected contentsvbulletin-settings.xmlFile does not contain expected contentsvbulletin-style.xmlFile does not contain expected contentsScanned 10 files
        ./modcp
        All of the above means nothing to me I'm afraid, so I wouldn't have a clue what any of it means.

        The last issue was a case of the file for some reason had not uploaded with all the rest.

        Now tho I'm totally lost and a little scared to do anything else. I apprecieate your help. Thank you

        Comment

        • Jose Amaral Rego
          Senior Member
          • Feb 2005
          • 11058
          • 1.1.x

          #5
          Does not seem you actually ran the install/upgrade.php completely or you did just skip several steps. Please list the step you have down to upgrading your site and if you made a database backup and have tested the backup prior to this upgrade.

          Comment

          • havenfriends
            New Member
            • Nov 2007
            • 21

            #6
            Well I just followed the on screen next buttons, and that took me through, A backup was done, but I'm not sure if it was tested or not, I would say no testing took place? Is this a problem?

            Thank you again Jose I really apprecieate all your help.

            If I have skipped some steps I'm really not sure how I managed this.

            Comment

            • havenfriends
              New Member
              • Nov 2007
              • 21

              #7
              Could I open my board now, or would that cause more problems? It is still shut at the moment.

              Also should I still upload all the non image files in ASCII mode.

              Thank you so much in advance.

              Comment

              • havenfriends
                New Member
                • Nov 2007
                • 21

                #8
                Not sure if this will help at all but, I had a look at the install again and this is what is coming up now.

                Step 2) Altering Table Defaults
                • Altering socialgrouppicture Table (1 of 1)
                • Altering notice Table (1 of 1)
                • Altering noticecriteria Table (1 of 1)
                • Altering tag Table (1 of 1)
                • Altering tagthread Table (1 of 1)
                • Altering tagsearch Table (1 of 1)
                • Altering postedithistory Table (1 of 1)
                • Altering usercsscache Table (1 of 1)
                • Altering visitormessage Table (1 of 1)
                • Altering groupmessage Table (1 of 1)
                • Altering album Table (1 of 1)
                And under that in a little box is this
                Database error in vBulletin 3.7.0:
                Invalid SQL:
                ALTER TABLE album
                CHANGE userid userid INT UNSIGNED NOT NULL DEFAULT '0',
                CHANGE createdate createdate INT UNSIGNED NOT NULL DEFAULT '0',
                CHANGE lastpicturedate lastpicturedate INT UNSIGNED NOT NULL DEFAULT '0',
                CHANGE picturecount picturecount INT UNSIGNED NOT NULL DEFAULT '0',
                CHANGE title title VARCHAR(100) NOT NULL DEFAULT '',
                CHANGE description description TEXT,
                CHANGE coverpictureid coverpictureid INT UNSIGNED NOT NULL DEFAULT '0';
                MySQL Error : Unknown column 'picturecount' in 'album'
                Error Number : 1054
                Date : Monday, May 5th 2008 @ 03:47:37 PM
                Script : http://www.mysite.com/vbullet/instal...0b3.php?step=2
                Referrer : http://www.mysite.com/vbullet/instal...e.php?rand=216
                IP Address : xx.xx.xxx
                username:
                Classname : vB_Database
                Hope this helps. Thank you in advance.

                Comment

                • Steve Machol
                  Former Customer Support Manager
                  • Jul 2000
                  • 154488

                  #9
                  You skipped several steps. Also as per post #4 you have not uploaded all the 3.7.0 files.

                  At this point I would restore a backup of the database that you hopefully made before this upgrade and try again.
                  Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
                  Change CKEditor Colors to Match Style (for 4.1.4 and above)

                  Steve Machol Photography


                  Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


                  Comment

                  • havenfriends
                    New Member
                    • Nov 2007
                    • 21

                    #10
                    Okay thank you so much Steve I'll do that,

                    And thank you Jose for all your help.

                    Comment

                    • GHOwner
                      Senior Member
                      • Jun 2007
                      • 554
                      • 3.8.x

                      #11
                      Originally posted by havenfriends
                      Okay thank you so much Steve I'll do that,

                      And thank you Jose for all your help.
                      When you run /install/upgrade.php be sure to keep hitting the next button until it redirects you to the admincp (or alerts you to remove /install/install.php). It might say "next Step (2/5)" or so, but there are more than just one set of steps

                      Comment

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