Menu

error on upgrade from 2.11 to 3.40

Help
birch
2014-08-15
2014-08-15
  • birch

    birch - 2014-08-15

    I'm attempting to upgrade from 2.11 to 3.40. When I put in my database
    credentials into setup, I get a "Can't connect to specified database
    table!" error on the review page. I tried copying these directly from the
    config.php of my old install.

    I then wrote to the config file even though I had the db error. I compared
    the old config.php with the new one and the user fields are the same. When
    I run update.php on the new site I get:
    Database error: SQLSTATE[42000]: Syntax error or access violation: 1064 You
    have an error in your SQL syntax; check the manual that corresponds to your
    MySQL server version for the right syntax to use near 'TYPE = innoDB
    CHARACTER SET = ' at line 3

    Any thoughts?

    Thanks,
    Birch

     
  • Andrew Simpson

    Andrew Simpson - 2014-08-15

    I'm attempting to upgrade from 2.11 to 3.40. When I put in my database
    credentials into setup, I get a "Can't connect to specified database
    table!" error on the review page. I tried copying these directly from the
    config.php of my old install.

    O.K. looking through the code, that's the error you would get with Version 2.11 trying to be set up for Version 3.40 without upgrading the database.

    So I think are connecting to the database server alright. Presumably you then have InnoDB engine and UTF-8 which is good.

    I then wrote to the config file even though I had the db error. I compared
    the old config.php with the new one and the user fields are the same. When
    I run update.php on the new site I get:
    Database error: SQLSTATE[42000]: Syntax error or access violation: 1064 You
    have an error in your SQL syntax; check the manual that corresponds to your
    MySQL server version for the right syntax to use near 'TYPE = innoDB
    CHARACTER SET = ' at line 3

    Now this is not right. 'TYPE = innoDB' has been deprecated by MySQL and should be 'ENGINE = innoDB'. I know that I found this in upgrade testing a while back and fixed it. Git repo says that it was fixed in March 2014.

    Unfortunately the 3.40 release didn't get this file changed - I don't know why. That's a bit embarrassing.

    Getting the 'upgrade.php' file out of the Git repo should fix that problem.

    Let me know if there are further problems. It sounds as though you got through most of the hurdles (Upgrades of that extent aren't straightforward, since MySQL has changed a lot).

     
  • birch

    birch - 2014-08-15

    That Worked!! Thanks

    However, when I changed the main directory name, and edited config.php to match, none of the graphics showed up when I logged in. Changing the directory back to what it was when I ran update.php fixed it.

    Thanks so much for all your work on such a great tool.

     
  • Andrew Simpson

    Andrew Simpson - 2014-08-15

    Good!

    The temporary problem with graphics is most likely related to CSS style sheets. WebCollab uses them for practically all the graphical schemes.

    The browser will cache the style sheet locally, however when you change something the local caching can cause temporary problems. Often a few reloads fix it, sometimes you have to clear the browser cache manually.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.