Upgrade abort (VB 4.1.9 to 4.1.11 PL 1)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • breed
    New Member
    • May 2009
    • 23
    • 3.8.x

    [Forum] Upgrade abort (VB 4.1.9 to 4.1.11 PL 1)

    Hi,
    I wanted upgrade to VB 4.1.11 PL1 but process is aborted. Can you help me? Thank you

    (Forum version is 4.1.10 alpha 1 now)I see this:

    • Upgrading to 4.1.10 Alpha 2
    • Step 2 - Updating forum table
    • Updating usergroup table
    • Updating calendar table
    • Updating setting table
    • An error has occurred with your database. Please contact vBulletin Support for assistance.
      Module: 4110a2, Step 2 Database Error:1054
      Unknown column 'ALLOW_BBCODE_VIDEO' in 'field list'
      Query:

      UPDATE setting SET value = value | ALLOW_BBCODE_VIDEO WHERE varname IN ('sg_allowed_bbcode', 'vm_allowed_bbcode', 'pc_allowed_bbcode') AND value & 1024
    Last edited by breed; Wed 28 Mar '12, 1:14pm.
  • breed
    New Member
    • May 2009
    • 23
    • 3.8.x

    #2
    no idea? :-(
    One more thing. In settings. check blue text in picture. Strange
    Click image for larger version

Name:	bb.jpg
Views:	1
Size:	69.4 KB
ID:	3686948

    Comment

    • Zachery
      Former vBulletin Support
      • Jul 2002
      • 59097

      #3
      What did you start upgrading from?

      Comment

      • breed
        New Member
        • May 2009
        • 23
        • 3.8.x

        #4
        I upgraded from 4.1.9 to 4.1.11 PL1

        Comment

        • Zachery
          Former vBulletin Support
          • Jul 2002
          • 59097

          #5
          That setting should have been added in the 4.1.10 upgrade (at some point) You're going to need to open a ticket and provide phpmyadmin info so we can tinker with the db and get if fixed.

          Comment

          • breed
            New Member
            • May 2009
            • 23
            • 3.8.x

            #6
            Originally posted by Zachery
            That setting should have been added in the 4.1.10 upgrade (at some point) You're going to need to open a ticket and provide phpmyadmin info so we can tinker with the db and get if fixed.
            Thank you for your reply.
            Problem is resolved. Problem was in our server. (probably PHP APC or some bug in PHP 5.3.8 (Now upgraded to PHP 5.3.10))

            Comment

            Related Topics

            Collapse

            Working...