-
-
Notifications
You must be signed in to change notification settings - Fork 867
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] partner_firstname cannot be installed, if the system contains a contact with an empty name #1677
Comments
In my local system I resolved this issue with the following small change:
|
This change fixes this bug: OCA#1677 With that the module can be installed as only partners with names will be processed
I have to wonder if this repository is still maintained? |
@mohs8421 thanks for your contrib.
There are plenty of things to maintain as we have more than 230 repos and more than 5k modules 😉 I'm not a maintainer of that module but I'll have a look at your PR. |
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. |
so how does contributing work here? |
Resolve issue blocking partner_firstname from installation This change fixes this bug: OCA#1677 With that the module can be installed as only partners with names will be processed
Resolve issue blocking partner_firstname from installation This change fixes this bug: OCA#1677 With that the module can be installed as only partners with names will be processed
When trying to install this module, I already get the following error:
It might be an issue referring to the general misconceptions about names also
Besides the edgecases, it might also be relevant for the system to be aware that the information about the firstname might simply be missing and only other details might be available.
Module
partner_firstname
To Reproduce
Affected versions: 16.0
Steps to reproduce the behavior:
Expected behavior
The module should be installable
The text was updated successfully, but these errors were encountered: