14.0 mig mail footer notified partner #801
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
dreispt
commented
Nov 16, 2021
dreispt
commented
- [MIG] [10.0] mail_footer_notified_partner (10.0 mig mail_footer_notified_partner #200)
- OCA Transbot updated translations from Transifex
- OCA Transbot updated translations from Transifex
- FIX mail_footer_notified_partner
- [UPD] Update mail_footer_notified_partner.pot
- [MIG] mail_footer_notified_partner: Migration to 11.0
- [IMP] notification should be at the beginning of the body indeed
- [FIX] fix travis
- [MIG] mail_footer_notified_partner: Migration to 12.0
- [MIG] mail_footer_notified_martner: add to use _notify() v12 method
- [MIG] mail_footer_notified_partner: Fix test
- [UPD] Update mail_footer_notified_partner.pot
- [UPD] README.rst
- [ADD] icon.png
- Update translation files
- Update translation files
- Translated using Weblate (French)
- [IMP] mail_footer_notified_partner: black, isort, prettier
- [MIG] mail_footer_notified_partner: Migration to 14.0
* [NEW][mail_footer_notified_partners] This module adds into the footer the partner's name notified by this email * [CHG] Use common.TransactionCase * OCA Transbot updated translations from Transifex OCA Transbot updated translations from Transifex OCA Transbot updated translations from Transifex * [FIX][mail_footer_notified_partners] Use @api.model instead of @api.one. * OCA Transbot updated translations from Transifex * [FIX] remove en.po that was erroneously created by transbot * Pass context * OCA Transbot updated translations from Transifex OCA Transbot updated translations from Transifex * [MIG] mail_footer_notified_partner: Migration to 10.0
|
Hi @dreispt, are you planning to carry on this work? Otherwise I can create a new PR. |
|
@cvinh, thanks I see, but this is not enough to move forward. I think it's quicker open a new PR, do you agree? |
we need to save the complete list of partners because _message_notification_recipients builds recipients grouped by users groups. Thus get_additional_footer would get a partial list of recipients
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: social-12.0/social-12.0-mail_footer_notified_partner Translate-URL: https://translation.odoo-community.org/projects/social-12-0/social-12-0-mail_footer_notified_partner/
Currently translated at 50.0% (1 of 2 strings) Translation: social-12.0/social-12.0-mail_footer_notified_partner Translate-URL: https://translation.odoo-community.org/projects/social-12-0/social-12-0-mail_footer_notified_partner/fr/
dreispt
force-pushed
the
14.0-mig-mail_footer_notified_partner
branch
from
4a12582
to
f7b28a1
Compare
|
Hey @dreispt, thank you for your Pull Request. It looks like some users haven't signed our Contributor License Agreement, yet.
Appreciation of efforts, |
|
/ocabot migration mail_footer_notified_partner |
|
Not deprecated @tafaRU just diferent options for the "same" or similar objetive as Cyril said #855 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.