Someone managed to upgrade ORO to 1.6.1 or 1.6.2 without any errors?

Someone managed to upgrade ORO to 1.6.1 or 1.6.2 without any errors?

I’m following this, but when I try to select an existing database, I always got this error, even passing the –force parameter:

“Property Oro\Bundle\CalendarBundle\Entity\CalendarEvent::$contact_cdc90e7a does not exist ”

So, any suggestion? How to update my platform and preserve all old data?

Adding a new/empty database all works well..

Topic

[RodolfoParticipant]

Hello Ignat!

Thanks again for all your effort!
Passed over almost all the steps. I modified the SQL file because it was generating some errors.
https://gist.githubusercontent.com/rodolfobandeira/339fa6554ea8998660c4/raw/51f6ccd1cbcd1d623fed5745d33c6c9ae3227815/downgrade_master_to_1_6_1.sql

Now I’m getting this error on the final step:
php crm-enterprise-application/app/console oro:platform:update –env=prod –force

Process migrations…
> Oro\Bundle\AddressBundle\Migrations\Schema\v1_2\ChangeAddressPostalCodeLength
> OroCRM\Bundle\ContactBundle\Migrations\Schema\v1_9\ChangeContactAddressPostalCodeLength
> OroCRM\Bundle\MagentoBundle\Migrations\Schema\v1_21\AddFields
> OroCRM\Bundle\MagentoBundle\Migrations\Schema\v1_21\OroCRMMagentoBundle
> OroCRM\Bundle\MagentoBundle\Migrations\Schema\v1_21\DropFields
> OroCRM\Bundle\MagentoBundle\Migrations\Schema\v1_22\ChangeAddressPostalCodeLength
> Oro\Bundle\MigrationBundle\Migration\UpdateBundleVersionMigration
> Oro\Bundle\EntityExtendBundle\Migration\RefreshExtendCacheMigration

[Doctrine\Common\Persistence\Mapping\MappingException]
Class ‘Oro\Bundle\CalendarBundle\Entity\CalendarProperty’ does not exist

[ignatParticipant]

Hi Rodolfo,

Try to add this queries to your sql:
DELETE FROM oro_entity_config_field WHERE entity_id IN (SELECT id FROM oro_entity_config WHERE class_name = 'Oro\Bundle\CalendarBundle\Entity\CalendarProperty');

DELETE FROM oro_entity_config WHERE class_name = 'Oro\Bundle\CalendarBundle\Entity\CalendarProperty';


I see you have commented some queries. Be careful because leaving this data in the schema will make problems to you when you will update to new versions. For example you will get error that table “oro_activity_list” is already exist during update.

Thanks,
Ignat

[RodolfoParticipant]

I just commented some commands because I don’t have some columns or tables on my db.

You are the guy! Thank so much Ignat!

[ignatParticipant]

Thanks, Rodolfo! Glad you finally there!

[RodolfoParticipant]

@ignat Any chance to help me to upgrade to 1.7.0 ?

[Author]

Replies