-
-
Notifications
You must be signed in to change notification settings - Fork 589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[15.0] mail_tracking blocking adding email on contact when record w/o message_id & partner_id #1209
Labels
Comments
There's mail_tracking_mass_mailing as glue module for that. |
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem?
![image](https://private-user-images.githubusercontent.com/80696963/263749567-a0a2e2e4-c4fc-4ca7-8ff9-10918ccb8ed5.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjExMTk4ODAsIm5iZiI6MTcyMTExOTU4MCwicGF0aCI6Ii84MDY5Njk2My8yNjM3NDk1NjctYTBhMmUyZTQtYzRmYy00Y2E3LThmZjktMTA5MThjY2I4ZWQ1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE2VDA4NDYyMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI4NWExY2U4YTE2ODZlY2I5Mjc2YzI0NTJjMDk1NDIxM2ZjMjdjMDgxMWUyZTI3NmE1MmRlMjk0YjJkMTcxNWImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0._HXkx5l28gURZV1SbOemnEPCpKp9H5IB3y6NClpD9CU)
When sending out newsletter from our e-mail marketing module the mail_tracking records created do not have a message - or a partner_id. I am not exactly sure why, when trying to test we got always message_id false and since I do not have a test mail server I was not able to largly test it on a new newsletter campaign.
Anyways, since we do not need tracking for these mails I did not invest much more time on record creation issue. Now employees noticed when trying to add a Mail which is connected to the record with a non-admin user it is throwing error.
![image](https://private-user-images.githubusercontent.com/80696963/263750625-72b3d04b-f081-43fb-a23d-e33b5b99424a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjExMTk4ODAsIm5iZiI6MTcyMTExOTU4MCwicGF0aCI6Ii84MDY5Njk2My8yNjM3NTA2MjUtNzJiM2QwNGItZjA4MS00M2ZiLWEyM2QtZTMzYjViOTk0MjRhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE2VDA4NDYyMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE3MDdiMmYwZmQyYmM1NjZiZmEwMjQwYWY2MzAwMzU1YzMzNmEwZjlmOTkzODY5OGI0ZjczNGVmZTc4NjNmYjAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Tei-gqfAnvL_DEaFSG-eJnDAXB73AOsNqofItIA91kI)
Describe the solution you'd like
To avoid it we added custom condition in your oca code in _find_allowed_tracking_ids(self): method line 169:
Old Code part:
if (x[1] in msg_ids) # We can read the linked message
New Code part:
if x[1] if (x[1] in msg_ids) # We can read the linked message
Now it's not blocking adding emails on contact where records without message and partner_id exist.
Describe alternatives you've considered
Is this a condition of mail_tracking records that is just not considered (not having a message_id and partner_id)? or is it wanted that for records without these id fields filled it throws error because it's cruical for tracking to work correctly.
Additional context
Maybe you know why these records get created without ID's? Otherwise I think this would be a great feature for emails people do not want to track, but still want to be able to avoid conflicts in other module (like contact).
Thank you in advance!
The text was updated successfully, but these errors were encountered: