[Ivan KlymenkoSpectator]

Hi bojan050,
regarding the issue with memory limit, could you please check is the composer.lock in place after the clone?

[Ivan KlymenkoSpectator]

Hi junaid,
we investigated your case and found the issue in sync when it is executed with command

Shell

oro:magento:initial:sync --integration-id=7 --skip-dictionary -v

1	oro:magento:initial:sync --integration-id=7 --skip-dictionary -v

in the same time

Shell

oro:cron:integration:sync --integration-id=7

1	oro:cron:integration:sync --integration-id=7

works well.

We will include the fix in the upcoming release.

[Ivan KlymenkoSpectator]

Hi Stepan,
thanks for the heads up on this issue. We investigated the problem and will prepare a fix in the upcoming release.

[Ivan KlymenkoSpectator]

Hi modli,
unfortunately we don’t have any cleanup procedure or command for the tracking data. And this will be good improvement, so we added it to our backlog.
For now, you can cleanup this data by SQL query in tables oro_tracking_data and oro_tracking_event. We store raw tracking data there. By default we don’t have any tricky relations there, but in this case if you have some in your instance – you should do this carefully.

[Ivan KlymenkoSpectator]

Hello guys,
we plan to work on the fix during next 3 weeks and include it into closest release.
Thanks for your patience.

[Ivan KlymenkoSpectator]

Hi Rodolfo,
are you able to use these entities and extended fields via create/edit forms?

[Ivan KlymenkoSpectator]

Could you please share install and prod logs. We need to check the error to understand where could be an issue.

[Ivan KlymenkoSpectator]

Hi,
we have these issue in backlog. Thanks for the heads up!

[Ivan KlymenkoSpectator]

Did you run “composer install” or “composer update”?
Recommended way is to run composer install

[Ivan KlymenkoSpectator]

Hi vfbsilva,
we were not able to reproduce the issue described on the CentOS.
Please clone latest stable OroCRM application from GitHub or use these composer.json and composer.lock and try again.

[Ivan KlymenkoSpectator]

Hi Anna,
picture field is extended field, so it should not be present in the mapping of the original entity class. It should be added by migration and then automatically mapped in the EX_OroCRMContactBundle_Contact.php.

If you will add property for the extended field directly to the original entity class, it could lead to an issues if this extended field will be deleted manually from the UI or from a migration.

From my opinion the appropriate migration was not executed, or appropriate proxy class was not generated properly. Could you please check the oro_migration table and tell what version is set for OroCRMContactBundle?

[Ivan KlymenkoSpectator]

Hi abober,
how did you upgrade your OroCRM project to the latest release?

Did you run next command after composer install:

Shell

php app/console oro:platform:update --env=prod

1	php app/console oro:platform:update --env=prod

Because executing oro:migration:load command is not a valid way to upgrade.

[Ivan KlymenkoSpectator]

Hi Brent,
what version you are trying to install?

[Ivan KlymenkoSpectator]

Hi kebugcheck,
for better understanding the case, could you please open the Magento integration for Edit, click on the “Check Connection”, check the “Website” drop down then save the integration. After this please check again – does the issue still appear and tell us did you had websites in the drop-down.

[Ivan KlymenkoSpectator]

Hi andytumilko,
what version of the OroPlatform do you use?

[Author]

Replies