Closed (fixed)
Project:
Mailjet
Version:
7.x-2.11
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Feb 2016 at 11:23 UTC
Updated:
22 Feb 2017 at 13:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
fagoLet's see whether this fixes the problem.
The patch adds a hidden variable mailjet_user_sync which allows to deactivate the user syncing feature as we only need the mailsystem. I suspect this to cause the issue, while we do not need that feature. I think in general it would be nice to split the module such that one can easily choose which part of the functionality is needed.
It should be noted, that the module totally violates Drupal coding standards and should be overhauled to confirm to Drupal standards.
Comment #3
fagocreated #2663332: Module violates Drupal coding standards
Comment #4
hargobindThanks @fago, this is a very valuable workaround for those who don't need user syncing and avoid the errors that appear with how things are now.
I have attached an updated patch against the latest 2.x-dev branch (and it applies cleanly to 2.10). It simplifies your code by adding the check to the actual sync functions instead of the drupal hooks. Please review so we can get this RTBC.
Comment #5
garphyIt's just really super convenient to be able to disable user information syncing feature.
Patch works correctly.
I also think that all features related to user syncing & campaign management should live in their own submodules.
Comment #6
mailjet plugins commentedHello everyone,
Thanks for identifying this issue and providing a patch for it. We have merged it in the latest version of the plugin 7.x-2.11.
Best regards,
Mailjet team