ssossossosso

Forums

Covering OroCRM topics, including community updates and company announcements.  Subscribe

This topic contains 12 replies, has 4 voices, and was last updated by Artem Liubeznyi Artem Liubeznyi 1 year, 2 months ago.

  • Creator
    Topic
  • #4009
    pauldpauld
    pauldpauld
    Participant

    Hi,
    I installed 1.0 OroCRM using the zip file. It’s working well.

    I have tried to upgrade to 1.0.1 (then I want to upgrade to 1.1.0), but without the .git directory (as I installed from zip) I get:
    fatal: Not a git repository
    Which is understandable.

    How can I either;
    create a .git dir with the correct info to allow me to upgrade via Git, or, how can I upgrade manually (cut & paste!) and what files need to be upgraded?

    All thoughts appreciated,
    Thanks. Paul

Viewing 12 replies - 1 through 12 (of 12 total)
  • Author
    Replies
  • #4112

    Alexandr Smaga
    Participant

    Hello. Try to do that via package manager (System -> Package manager). Hope this will help.

    In other case you have to override all files from your current installation by new ones(from archive with new version) and run app/console oro:platform:update command. Also don’t forget to do a DB backup if you already have some data.

    #4123
    pauldpauld
    pauldpauld
    Participant

    Thanks for your help,
    I have installed via git, the new version, and kept my own database, pointing the new version to the old database.
    the platform update failed with; table email_to_folder already exists.

    when I visit the site I get a “500 internal server error”

    in prod.log, I have;
    SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘t0.chart_options’ in ‘field list'”)

    I have backed up the db, but, would prefer not to have to manually input 500 records into the upgraded 1.1 crm
    🙁

    Thanks, Paul

    #4126
    Yevhen Shyshkin
    Yevhen Shyshkin
    Oro Core

    Hello, pauldpauld.

    If I understand you correctly, you have new version code and old version database.

    Please, try do following:
    1) ensure that new code will use old DB in app/config/parameters.yml
    2) manually remove cache: rm -rf app/cache/*
    3) run command php app/console oro:platform:update --env prod, if you’ll get some errors on this step – please, put them here
    4) go to UI and check whether application works

    #15814
    pauldpauld
    pauldpauld
    Participant

    FINALLY, after all this time 🙂

    I decided to try to complete this as now is a quiet time of the year.

    I did a new/clean install of 1.9 (I think it was 1.9) using packet manager and it worked just fine with a new database.

    I cleared the cache then changed parameters.yml to point to my old 1.0 database (all other parameters remain the same).

    The error I received in the log is:
    [2016-01-04 16:35:26] request.CRITICAL: Exception thrown when handling an exception (Doctrine\DBAL\Exception\InvalidFieldNameException: An exception occurred while executing ‘SELECT o0_.id AS id_0, o0_.entity AS entity_1, o0_.record_id AS record_id_2, o1_.id AS id_3, o1_.name AS name_4, o1_.section AS section_5, o1_.text_value AS text_value_6, o1_.object_value AS object_value_7, o1_.array_value AS array_value_8, o1_.type AS type_9, o1_.created_at AS created_at_10, o1_.updated_at AS updated_at_11, o1_.config_id AS config_id_12 FROM oro_config o0_ LEFT JOIN oro_config_value o1_ ON o0_.id = o1_.config_id WHERE o0_.entity = ? AND o0_.record_id = ?’ with params [“user”, 0]: SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘o1_.created_at’ in ‘field list’ at /var/www/alond_charities/crm-application/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php line 71) {“exception”:”[object] (Doctrine\\DBAL\\Exception\\InvalidFieldNameException: An exception occurred while executing ‘SELECT o0_.id AS id_0, o0_.entity AS entity_1, o0_.record_id AS record_id_2, o1_.id AS id_3, o1_.name AS name_4, o1_.section AS section_5, o1_.text_value AS text_value_6, o1_.object_value AS object_value_7, o1_.array_value AS array_value_8, o1_.type AS type_9, o1_.created_at AS created_at_10, o1_.updated_at AS updated_at_11, o1_.config_id AS config_id_12 FROM oro_config o0_ LEFT JOIN oro_config_value o1_ ON o0_.id = o1_.config_id WHERE o0_.entity = ? AND o0_.record_id = ?’ with params [\”user\”, 0]:\n\nSQLSTATE[42S22]: Column not found: 1054 Unknown column ‘o1_.created_at’ in ‘field list’ at /var/www/alond_charities/crm-application/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php:71, Doctrine\\DBAL\\Driver\\PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘o1_.created_at’ in ‘field list’ at /var/www/alond_charities/crm-application/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:93, PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘o1_.created_at’ in ‘field list’ at /var/www/alond_charities/crm-application/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:91)”} []

    Does this mean I can’t use the old db and have it ‘auto” upgraded?
    Is there a way to rebuild the missing tables? OR;
    I am also happy to import customers and accounts into the new db if someone would kindly point me to the tool to do that?

    Thanks and Happy New Year 🙂

    #15815
    pauldpauld
    pauldpauld
    Participant

    UPDATE:

    No quite working;

    I’ve moved dev.log and prod.log here;

    http://charities.alond.com.au/dev.log
    http://charities.alond.com.au/prod.log

    if that helps?

    Regards,

    Paul

    #15822
    Artem Liubeznyi
    Artem Liubeznyi
    Oro Core

    Hi Paul,

    Which version you are trying to migrate from? The 1.0?

    #15828
    pauldpauld
    pauldpauld
    Participant

    Hi Artem,

    yes, I could never get the upgrade to 1.1 working, so I am trying to upgrade from 1.0 to 1.9

    157 tables in the 1.0
    254 tables in the 1.9

    Thanks,
    Paul

    #15860
    Artem Liubeznyi
    Artem Liubeznyi
    Oro Core

    Well, that won’t be easy. The system has changed a lot since 1.0 days and frankly I’m not sure there is a tool for such data migration.

    Can you somehow export your data in the CSV format? Not from the UI obviously, as we have added this feature in 1.3, but straight from the database. If you manage to do that, you then could import your customers and accounts back into the clean install of 1.9 via our CSV import tool.

    #15866
    pauldpauld
    pauldpauld
    Participant

    Hi Artem,

    exporting from DB seems the only option.

    I have not examined the tables closely, which are the Account and which are the contacts?

    I assume that the CSV import tool will be able to recognise the different csv’s? Or, is this manual matching of fields?
    Also, will I have to manually attach the contacts to the accounts?

    Thanks,

    Paul

    #15870
    Artem Liubeznyi
    Artem Liubeznyi
    Oro Core

    Accounts are stored in the orocrm_account table and contacts in the orocrm_contact. Note that contact addresses, emails, and phones are stored separately in orocrm_contact_address, orocrm_contact_address, orocrm_contact_email, and orocrm_contact_phone respectively.

    You should prepare your CSV files in advance according to the import data template. Please refer to our user guide for details.

    Contacts can be linked to accounts and vice versa–simply fill in the Account name column in the Contact CSV file or Contacts First Name and Contacts Last Name in the Accounts CSV file. The related data must already exist in the OroCRM, so I advise you to import “empty” accounts first and then import their contacts with proper relations.

    #15887
    pauldpauld
    pauldpauld
    Participant

    Thanks for your time Artem, it’s appreciated.

    I will do as you suggest.

    ONE final question 🙂

    I used the field in V1.0 Accounts: extend_ownership, to store an “account number”, I can’t seem to find which table that is mapped to in the new V1.9 DB.
    Can you advise where it is, or will I need to re-create it as a “user-defined” field (I am guessing that’s what happens now in V1.9)

    Regards,
    Paul

    #15893
    Artem Liubeznyi
    Artem Liubeznyi
    Oro Core

    Yes, you need to create this field manually first and update schema. To make sure the field is available for import & export set the Exclude Column setting in the Import & Export section to No. (It’s set to No by default, but worth checking anyway.)

Viewing 12 replies - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.