imap synch

Hi!
I have an installation orocrm version 1.7 everything is ok.
When I activate the daemon and oro command oro:cron in the crontab imap synchronization starts, then every body of each message is synchronized to its turn.
Once all mail synchronized crm becomes slower up to become unusable.
If I reinjected dump of my data before syncro imap everything becomes ok.
Do you have an idea ?

Topic

[Artem LiubeznyiSpectator]

Hi Patrice,

You experience problems during the initial IMAP sync or after its completion? In the former case it’s kinda expected, especially if you have a large mailbox.

[brunpatochParticipant]

Hi Artem,
the problem occurs when the import is complete.

[Artem LiubeznyiSpectator]

That’s weird. I will invite our QA team here so they will help with investigation.

Thank you for the heads up!

[Artem LiubeznyiSpectator]

Patrice,

We have investigated the issue but the root cause remains unclear. Thing is, you are experiencing it at 1.7 version and within our 1.8 release we’ve made a great overhaul of the entire IMAP sync, changing the sync algorithm and expanding its capabilities.

Given that 1.9 release is almost there, and 1.7 is approaching the obsolete status, I would advise you to upgrade to the latest version and check if the issue persists. (We couldn’t reproduce it in the latest stable 1.8 build.)

Please also take into account that we will no longer release bug fixes and patches for the Community Edition releases, meaning that any possible fixes will still come with 1.9 release and you’ll have to upgrade either way.

Please let us know if you will experience the problem on the 1.8 version.

Thank you!

[brunpatochParticipant]

Artem,
I made an update to version 1.8.2, but I am having new problem. All labels of my custom fields have disappeared. For example, I have a custom field ‘classement’ in the ‘Lead’ entity in there interface appears as follows. ‘orocrm.sales.lead.classement.label’.
On top of that I lost the translation (French) of all basic fields of all entities.
Should he run a script?
An idea ?

[brunpatochParticipant]

Other precision in the fields entity management interface (ex:/entity/config/view/1), all field are duplicate.

[Artem LiubeznyiSpectator]

Yes, we are aware about these issues and have already addressed them. Our dev master branch should have fixes, or you can wait for the stable 1.9 release.

[brunpatochParticipant]

Thank you for your answers.

I have some questions:

If I wait for version 1.9 is that it is possible to move from 1.7 directly to version 1.9? If not, I have to go through version 1.8, is that the transition from version 1.8 to 1.9 will fix bugs labels?

Is it possible to apply the master version of the patch then do the update?

Is what I can redo a clean install via compose version 1.8 and point it to my current database in version 1.7?

Thank you.

[Artem LiubeznyiSpectator]

Yes, you should be able to update from any early version to any later version. But a bug with labels will be fixed either way, even if you go via 1.8.

[brunpatochParticipant]

OK thank you.
What is the release date of version 1.9 ?

[Artem LiubeznyiSpectator]

The exact date depends on how long it will take us to fix all the issues to deliver the level of quality we want. It is currently scheduled for January.

[Author]

Replies