Skip to content
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

[16.0] mass_mailing_unique: error on install if existing 'mailing.contact' records with no email #1313

Closed
makayabou opened this issue Feb 22, 2024 · 1 comment
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@makayabou
Copy link

Module

mass_mailing_unique

Describe the bug

I installed odoo 16 CE with several apps, with demo records creation activated.
It created a bunch of mailing.contact records, with 3 of them not having email field defined.
Then when i tried to instal mass_mailing_unique, it complains about the existence of these 3 records having similar email: None
odoorpc.error.RPCError: Unable to install module mass_mailing_unique: There are 3 mailing contacts with the same email: None
I added a mail to the 3 mailing contacts that didn't have, then installation worked

To Reproduce

Version: Odoo 16 CE.

Steps to reproduce the behavior:

  1. Try to create mass_mailing records with field 'email' not define
  2. try to install mass_mailing_unique
  3. Installation will fail.
  4. Add email field to those records
  5. Installation works
  6. Once installed, you can create 2 records in mailing.contact with no email, mass_mailing_unique module won't complain.

Expected behavior
Records with email field not defined should not be considered by module mass_mailing_unique as having the same email, and prevent installation of the module.

Additional context
Odoo 16 CE docker image

@makayabou makayabou added the bug label Feb 22, 2024
Copy link

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.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 25, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

1 participant