Menu

Help installing from Version 1.4.2 to 1.4.6

2008-07-15
2012-09-14
  • Mark Corben

    Mark Corben - 2008-07-15

    Hi,
    Thanks for such a great product!

    I am having trouble going from Version 1.4.2 to 1.4.6.
    In the UPGRADING file I am finding the steps a little cryptic.

    I am installing it locally on my OpenSuSE 10.3 computer.
    I have the current 1.4.2 under "http://127.0.0.1/allocPSA-1.4.2"
    ie it is in /srv/www/htdocs/allocPSA-1.4.2

    It appears that I need to follow the steps under the heading "To upgrade from 1.3.508 to 1.4.0"
    which seems to say :

    However when I run this I am first prompted to login and once I do I get a series of mysql errors displayed amongst the home page.
    I don't get the list of patches as suggested in step 4.

    It does look like the database structure is different between the two versions. I installed a new Ver 1.4.6 as a test.

    What am I doing wrong ?

    I have included the mysql error output below....

    Thanks


    Mysql error messages:


    Query failed: Unknown column 'projectPerson.roleID' in 'on clause'

    SELECT timeSheet.*, sum(timeSheetItem.timeSheetItemDuration * timeSheetItem.rate) as total_dollars
    , COALESCE(projectShortName, projectName) as projectName
    FROM timeSheet
    LEFT JOIN timeSheetItem ON timeSheet.timeSheetID = timeSheetItem.timeSheetID
    LEFT JOIN project on project.projectID = timeSheet.projectID
    LEFT JOIN projectPerson on project.projectID = projectPerson.projectID
    LEFT JOIN role on projectPerson.roleID = role.roleID
    WHERE projectPerson.personID = 2 AND role.roleHandle = 'timeSheetRecipient' AND timeSheet.status='manager'
    GROUP BY timeSheet.timeSheetID
    ORDER BY timeSheet.dateSubmittedToManager

    Unable to connect to database: Unknown column 'projectPerson.roleID' in 'on clause'

    Query failed:

    SELECT personID
    , SUM(timeSheetItemDuration*timeUnitSeconds) AS avg
    FROM timeSheetItem
    LEFT JOIN timeUnit ON timeUnitID = timeSheetItemDurationUnitID
    WHERE dateTimeSheetItem > '2008-07-01'
    AND personID = '2'
    GROUP BY personID


     
    • Alex Lance

      Alex Lance - 2008-07-15

      Hi Mark,

      I think I can see what is happening. The alloc upgrade database patches have definitely not been applied. That is why you are being presented with errors when you log in. Go to this URL again:

      http://127.0.0.1/allocPSA-1.4.6/installation/patch.php

      Try it in Firefox or Opera if it just redirects you to the login screen. The webbrowser you are using may be caching the re-direct for some strange reason, rather that displaying the patch/upgrade screen.

      If it re-directs you to the login screen again without letting you apply the patches, try this URL instead:

      http://127.0.0.1/allocPSA-1.4.6/installation/patch.php?apply_patches=true

      That URL should silently apply all the patches and then re-direct you to the loging screen, so that upon logging in your database errors should have vanished.

      Keep in touch, and let us know how the product is going for you and what problems you encounter etc

      Kind regards,
      Alex Lance
      http://allocPSA.com

       
    • Mark Corben

      Mark Corben - 2008-07-16

      Hi Alex,
      Thanks very much for your prompt reply.

      I tried the first URL (http://127.0.0.1/allocPSA-1.4.6/installation/patch.php) with the following browsers:

      • Firefox 2
      • Firefox 3
      • Opera 9.51
      • Konqueror 3.5.7

      Unfortunately all browsers still sent me to the login screen.
      I tried the second URL (http://127.0.0.1/allocPSA-1.4.6/installation/patch.php?apply_patches=true) with the same browsers and am still getting the mySQL errors occurring.

      Each time I cleared the cache for each browser but the same result occurs.

      Any other suggestions ?

      Thanks,

      Mark

       
      • Alex Lance

        Alex Lance - 2008-07-16

        Gday Mark,

        Perhaps some of the patches got applied and others didn't. Log into your alloc database.

        $ mysql -u root alloc_db

        mysql> select patchName from patchLog;

        You will then get a list of all the patches that have been successfully applied. There should be 106 rows in the result and
        patch-00100-alla.php should be the last one.

        If that is not the case, you will perhaps need to walk through the patches in the patches/ directory and try to apply the ones that aren't there in your list. Here's a hacky little thing that should help you determine which ones are missing, note that you'll need to change the database name from alloc_db to whatever you called your database, and use preferably use a mysql user account that doesn't require a password.

        $ cd allocPSA-1.4.6/patches/

        $ for i in *; do [ -z "$(echo "select * from patchLog where patchName = '$i'" | mysql -u root alloc_db)" ] && echo "Haven't applied $i"; done;

        If the script prints out that it hasn't applied certain patches, then you'll need to manually apply the patchfiles ... let us know how it goes.

        Kind regards,
        Alex Lance
        http://allocPSA.com

         
    • Mark Corben

      Mark Corben - 2008-07-21

      Hi Alex,
      Sorry for the delay in getting back to you.

      Thanks for pointing out the 'patchLog' table. I put in the 'select patchName from patchLog;' and got the listing of 106 rows.
      I also ran the script that you gave me and it showed "Haven't applied" for the last few patches but it still wouldn't let me run
      'http://127.0.0.1/allocPSA-1.4.6/installation/patch.php'

      I ended up deleting the last 10 rows. Once i did this the 'http://127.0.0.1/allocPSA-1.4.6/installation/patch.php' link worked and I was able to apply the patches. I think a couple of times i needed to convert the tables back from 1.4.6 to 1.4.2 to have the patch run.
      (The second time i tried to install 1.4.6 i let it create a 1.4.6 mysql and then imported the 1.4.2 data).

      Basically this seems to have fixed it -- it is much easier to use the patch.php!

      Thanks very much for your help!

      Mark

       

Anonymous
Anonymous

Add attachments
Cancel





Auth0 Logo