that calls a new wizard, allowing to select contacts/customers/leads and create a new
mailing list.
Also updated default values in action 'create mailing list' for contact, customer and leads.
Also removed minimal form view on list, using only one view, with technical fields put
in group_no_one.
bzr revid: tde@openerp.com-20140327154606-7zrzi1ri1hfaxtay
- usability improveemnts on the sample document, more clear
- add partner_ids fields, displaying result of email template rendering that now also
generated partner_ids that will be recipient_ids on a mail_mail
- added attachment display
bzr revid: tde@openerp.com-20140327141241-2w2lxj5hkq8nqcu5
- from mass_mailing, creating or editing a template now goes through a wizard to avoid
tweaking too much the email.template view. This allows an easier management of templates
and their link with mailings.
- moved email.template minimal form view from email_tmeplate to mass_mailing, because it
is the sole module to use it. Tweaked it a bit by the way.
- removed dead code about actions not used anymore in mass_mailing
- empty list help on mail.mass_mailing.list
- various small usability fixes
bzr revid: tde@openerp.com-20140327130827-h9dy2m6mq10gzg1s
- uses already-existing template for subscription instead of copy-and-pasting the subscription button code;
- fixes several issues in the layout to ease the reading;
- fixes the broken pager;
- adds the Archives nav that was planned but not really usable
bzr revid: tde@openerp.com-20140326110042-tu9cdtca6sc2iv4r
but use the contact template that display partner-related data fetched
as superuser, to avoid access right issues.
Improved display: author or email-from.
Fixed issues in the pager.
bzr revid: tde@openerp.com-20140326103515-uzv6smwh9q6vyni9
that inherit from email_template; however with the inheritance mechanism of openerp
it is not updated when email_template itself is updated, therefore having to force
an update with a dummy inheritance.
bzr revid: tde@openerp.com-20140325142621-fbxa2gmeo52zf4qw
recipients instead of using template-based values. This should be the default way of using
templates actually, to avoid confusion with mako, ill-defined templates, ...
email_template code has been updated to handle recipient_ids when creating an email, depending
on its generated template values or default recipients.
mail_compose_message has also been updated, delegating the calculation of recipient when
having a template to the template itself, using some context keys to force the use
of partners instead of email_to and email_cc.
Also updated email_template form view to be a bit less confusing.
bzr revid: tde@openerp.com-20140325140324-bljvybigk3zv5ugm
- mail.compose.message: in render_message_batch, compute defaults recipients
for the composer (method called for mass mailing only). This way values are
available for inheriting models.
bzr revid: tde@openerp.com-20140325135347-9v7u4uokffy7ud43
send_mail method of a template is not related to openchatter anymore;
therefore recipients should not be called 'followers of XX', but use
their real name instead. This is already done, but the tests were not
updated.
bzr revid: tde@openerp.com-20140325103955-oc7ob98b1jql7tlz
a form view id in an action; do not use view_id that seems to be used for
that, but changes the view order (always form by default)... bleurg.
bzr revid: tde@openerp.com-20140325093007-g3hy9m8kcac9x1xs
Thibault Delavallée
chm@openerp.com
Kersten Jeremy
Frédéric van der Essen
Antony Lesuisse
Christophe Simonis
Fabien Meghazi