Inxmail / inx_magento1

Inxmail Professional Email Marketing für Magento CE und EE (1.x)
0 stars 0 forks source link

Missing attributes are beeing displayed after cronjob execution [INX-33] #36

Closed falco-knapp closed 8 years ago

falco-knapp commented 8 years ago

Problem

Currently, the system displays following error messages after cronjob execution:

image

However, this seems not to have any impact on the synchronisation of the subscribers.

Customers are not able to identify what causes this problem and what the impact is causing unnecessary support calls.

falco-knapp commented 8 years ago

Hi @bjoern-flagbit,

das ist irgendwie unsauber implementiert. Könnt Ihr bitte evaluieren und eine Aufwandschätzung machen?

Danke und Gruß,

Falco

BrocksiNet commented 8 years ago

Unsere Schätzung ergab max. 1 Stunde.

falco-knapp commented 8 years ago

Hi Björn,

Aufwandfreigabe: 1h. Ihr könnt die Implementierung einplanen.

Danke und Gruß,

Falco

falco-knapp commented 8 years ago

Hi Björn,

also, ich weiß nicht was geändert wurde, aber jetzt werden überhaupt keine Fehler mehr im Backoffice angezeigt. Dieses Feature hat glaube ich seit Beauftragung nie richtig funktioniert.

Ist es denn jetzt komplett deaktiviert oder was ist da nun der Stand? Auf jeden Fall gibt es weder in den Logfiles noch im Backoffice einen Hinweis darauf, wenn das Attribut-Mapping nicht passt.

Bitte erneut korrigieren :(

Danke und Gruß,

Falco

AlexanderPok commented 8 years ago

Hi Falco,

the issue was fixed(those "attributes" are not really attributes but columns, and validation mechanism behaved wrong in this case). There still should be errors logged and shown if something is wrong in mapping (for example column in inxmail was deleted or attribute in magento was deleted).

Regards, Alexander

falco-knapp commented 8 years ago

Hi Alexander,

OK, I think I found the issue. The error messages are beeing displayed if the group sync cronjobs is running or if the migration script is running.

No errors are however displayed in the following cases:

  1. manual sync of the groups
  2. if the user changes a corresponding attribute (on his account page for instance)

Can you please explain these cases to me, why they are not "monitored"?

Thanks and regards,

Falco

AlexanderPok commented 8 years ago

Hi Falco,

regarding cases:

  1. check function was added to manual group synchronization process;
  2. users are not able to add/change Magento attributes. Check functiona also added for inxmail mapping configuration save.

Regards, Alexander

falco-knapp commented 8 years ago

Hi Alexander,

regarding point 2: The Problem is not, that the user changes the configuration, but that there is no error message beeing displayed for instance in the following case:

There is a configured mapping for the firstname. This mapping somehow is not working anymore, because the attribute has been renamed or removed in inxmail.

If the Shop-User now edits his Firstname on his account page or during registration, the value cannot be transferred to inxmail because the mapping is not correct anymore. This should lead to the corresponding error message for the administrator.

Is this use-case "monitored"?

Thanks and regards,

Falco

AlexanderPok commented 8 years ago

Hi Falco,

ok I've got it, now any sync will cause mapping recheck.

Regards, Alexander

falco-knapp commented 8 years ago

Thanks, this is working now correctly as far as I could test it.