Announcement

Collapse
No announcement yet.

vB 2.2.9 and PHP 5.1.2

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

  • vB 2.2.9 and PHP 5.1.2

    Hello,

    I'm using vB 2.2.9 and it was working just fine.
    My host moved servers and upgraded PHP and MySql.
    PHP 5.1.2 and MySql 4.1.14

    I've been getting a variety of database errors ever since.
    I'm not sure if it's an incompatibility issue with the upgraded PHP and MySql or if it's a problem with the move.

    I can upgrade to the latest vB (and have downloaded it), but will it solve my problems?

    Are there issues with those versions of PHP and MySql in combine with vB 2.2.9?

    Thanks much.
    Thanks,

    DJA

  • #2
    Yes, upgrading should solve your problems.
    vBulletin 2 isn't compatible with MySQL 5.
    Best Regards
    Colin Frei

    Please don't contact me per PM.

    Comment


    • #3
      Right.
      But the host isn't running MySql 5; rather 4.1.14.
      Will that make a difference?
      Thanks,

      DJA

      Comment


      • #4
        Oh sorry, I misread that

        Generally I'd recommend upgrading anyhow, but please post the database errors you are receiving and I can tell you what the problem is.
        Best Regards
        Colin Frei

        Please don't contact me per PM.

        Comment


        • #5
          Thanks very much.
          btw- I am upgrading, I just need to learn the back end. Admin is so different, as is changing styles - I want my site to look like my site.

          In the meantime, I'm hoping that an upgrade will solve this problem. I'd like it to be that simple.
          Database error in vBulletin 2.2.9:

          Invalid SQL: SELECT attachmentid,postid,visible FROM post WHERE threadid='14388' AND username='DJKoolSkip' AND userid='2274' AND title='' AND dateline>1145382699 AND pagetext='lots of text'
          mysql error: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='

          mysql error number: 1267

          Date: Tuesday 18th 2006f April 2006 01:56:39 PM
          Script: http://www.discjockeyamerica.com/for...s/newreply.php
          Referer: http://www.discjockeyamerica.com/forums/newreply.php
          Database error in vBulletin 2.2.9:

          Invalid SQL: SELECT attachmentid,postid,visible FROM post WHERE threadid='14388' AND username='djrobB' AND userid='591' AND title='' AND dateline>1145372072 AND pagetext='I couldn’t help but notice that Jon hasn’t replied to this thread …

          Could it be that he’s the one that got the gig?'
          mysql error: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='

          mysql error number: 1267

          Date: Tuesday 18th 2006f April 2006 10:59:32 AM
          Script: http://www.discjockeyamerica.com/for...s/newreply.php
          Referer: http://www.discjockeyamerica.com/for...threadid=14388
          Database error in vBulletin :

          Link-ID == false, connect failed
          mysql error: Lost connection to MySQL server during query

          mysql error number: 2013

          Date: Thursday 13th 2006f April 2006 09:47:30 AM
          Script: /forums/
          Referer:
          Database error in vBulletin 2.2.9:

          Invalid SQL: SELECT *,INSTR(',9,3,-1,', CONCAT(',', forumid, ',') ) AS ordercontrol FROM forumpermission WHERE usergroupid=17 AND (forumid='9' OR forumid='3' OR forumid='-1') ORDER BY ordercontrol LIMIT 1
          mysql error: Lost connection to MySQL server during query

          mysql error number: 2013

          Date: Thursday 13th 2006f April 2006 09:47:29 AM
          Script: http://www.discjockeyamerica.com/for...p?s=&forumid=9
          Referer: http://discjockeyamerica.com/forums/...threadid=14369
          Of course, there are many more.
          I hope it's not a corrupt database and an upgrade will take care of it.
          Thanks for taking a look at it.
          Thanks,

          DJA

          Comment


          • #6
            The first two look as if the character encoding isn't the same for the old and the new database.
            You or your host should be able to update this in phpMyAdmin.
            Best Regards
            Colin Frei

            Please don't contact me per PM.

            Comment


            • #7
              If the db is the same one used on the old server, wouldn't it be the same on the new server? I'm not sure I understand how they would be different after a migration.

              And (the burning question) is this something that upgrading vB will solve or is it an issue that needs to be addressed prior to the upgrade?

              Thanks.
              Thanks,

              DJA

              Comment


              • #8
                This is something that upgrading most likely won't solve.
                The db seems not to be exactly the same, which is what's causing this error.
                Best Regards
                Colin Frei

                Please don't contact me per PM.

                Comment


                • #9
                  Colin,
                  Thanks for your help with this.
                  I'm in contact with my host.

                  Would you have any suggestions as to whom I could contract with to make style and/or template changes to the new vB 3.5.4 to match my vB 2.2.9 styles?
                  Thanks,

                  DJA

                  Comment


                  • #10
                    No, sorry.
                    I recommend you ask at www.vbulletin.org though, or post in the Service Requests forum there.
                    Best Regards
                    Colin Frei

                    Please don't contact me per PM.

                    Comment


                    • #11
                      Thanks again, Colin.
                      I've upgraded to vB 3.5.4 and am now in the midst of making changes in the sql. It's still a mystery how the sql changed in the first place.

                      But life is full of mysteries.
                      Thanks,

                      DJA

                      Comment

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