| Age | Commit message (Collapse) | Author |
|---|
|
This commit allows the user to link some mail template to activity type
with res_model.
When a activity has template, buttons appears in activity, allowing the user
to send mail based on templates.
Task: #1844563
PR: #25620
|
|
|
|
BS4 "btn-default" class was replaced with "btn-secondary", which makes
more sense.
|
|
This action allowing to send a mass mailing with a default template on a
partner is defined twice in mail on same object, with same xml_id. See in
composer views for the other definition.
This commit is linked to task ID 1843361 (and 1868112) and to PR #25287
(and #25889).
|
|
Add an onboarding panel for invoicing, it appears above the invoice
list.
After going through the steps the system should be all set to send real invoices.
In the payment module, add a payment acquirer step and add it to the invoice onboarding panel.
task: 60668
|
|
Purpose
=======
The Contact form is one of the most used/important view. It is quite
important to find the piece of information easily and to navigate in
a few clicks to the related views.
Specification
=============
Stat buttons
------------
- Restructure stat buttons with the following order:
Opportunities -> sales user
Meetings -> sales users
Sales -> Sales users
POS Sales -> pos users
Subscriptions -> Subscription users
Events -> event user
Tasks -> project user
TIckets -> helpdesk user
Purchases -> purchase user
Due -> billing: user
Invoiced -> billing: user
Vendor Bills -> billing: user
Customer/Vendor Partner Ledger -> accounting: billing
Analytic Accounts -> accounting: billing
Credit Cards -> sales user
Direct Debit Mandates -> accounting: billing user
Publish
- Use better/more relevant icons
- Check that the proper access rights are set
- Remove the bank accounts stat buttons and replace it by a one2many
tree on the Invoicing page.
Fields
------
Move some res.partner fields from the "Accouting" page to the
"sale & Purchase" page:
- Fiscal positions
- Payment terms
Miscellaneous
-------------
- Remove dead code.
- Display nothing instead "Please complete customer's informations and email"
on the popup when sending an email to a contact without email address.
|
|
During first scss convertion, classes called as mixins were changed to
an @extend instruction which was the best approximation given the fact
there is no equivalent in sass to do that. The problem is that the
instruction is slowing the scss computation a lot and might also break
the style in unexpected ways because of the complex unwanted selectors
the instruction induces.
This commit removes the need of extends. This is done case per case.
Sometimes this involves adding classes in xml, sometimes to change the
style a little, ... The button rendering refactoring which was made
at the start of the LESS to SASS merge was also done in prevision of
this.
After this commit, sass computation is like 5-6 times faster than less
computation while it was like 10 times *slower* before this commit.
|
|
|
|
-added tour for invoicing
-allow to set easily the number of the first invoice/bill/refund of a journal, from the invoice screen
-small usability fixes and refactoring
|
|
Purpose
=======
Improve label in full mail composer.
Specification
=============
In full mail composer if it's log than send button string should be "Log".
|
|
It now uses active_ids (checked records) by default. Composer allows you to
change and use active_domain (search criterion) instead.
|
|
Several modules defines records with the external ID `base.foo_bar` while it is
created inside this module (typically menus and groups).
While there is no technical reasons to do so but this may introduce issues:
- these records will not be deleted during uninstall
- if a language is loaded before the installation of the module, it won't be
translated
The uninstallation will only remove the records with an external id linked to
this module (these would only be removed when removing base).
Installing a language before the module will drop the translations not linked
to an existing external id (as it can not be resolved).
This commit correct all the external ids tagged as from base or other incorrect
modules.
|
|
|
|
When selecting contacts from Contacts list views and clicking on
action window "Partner Mass Mailing", the 'active_domain' must be
filled in the wizard with the selecting contacts. In this way,
the right mailing_domain will be set when creating the related
mail.mass_mailing record (in addons/mass_mailing/wizard/mail_compose_message.py
in function get_mail_values).
opw:659383
|
|
|
|
The main button has classnames btn btn-primary.
Other buttons have classnames btn btn-default.
No more 'or' between the buttons.
|
|
'style-inline': true to send email)
|
|
|
|
|
|
invisible
|
|
context to be passed as another argument. An intermediary function screens the arguments before calling send_mail.
|
|
1. The merge of the "email_template" module into the "mail" module.
2. The send action of the mass mailing has been moved from the frontend to a cron, because it was too slow to send over 10,000 mails (the user's browser was blocked for 15 - 20 minutes). Mass mailings have now their own process in the kanban view.
3. Mails sent from the mail form are sent immediatly instead of from the mail queue (for instance, when you go to sales > customers > list view > select 2 -3 customers > More > Partner Mass Mailing).
4. Users have now the choice from which mailing list they want to unsubscribe when they click on the unsubscribe link at the bottom of the mail.
5. Mass mailings inherit from their campaign UTMs and mass mailing campaigns are linked to an UTM campaign.
6. Many little improvements
|
|
|
|
avoid migration issues (adding a 'always False' column is easier than an 'always True').
|
|
|
|
bzr revid: tde@openerp.com-20140415143343-on2d3j92o6zifq59
|
|
bzr revid: tde@openerp.com-20140317132243-7cy089m8thd29y3l
|
|
removed context hack that
did the same thing. Fixed composer form view: internal note, only subject + body is
displayed.
bzr revid: tde@openerp.com-20140317122409-5fd5d5uwc35oq0hb
|
|
- now differentiates mass mailing and mass post.
- mass mailing is a true mass mailing
- using same_thread log a copy in the document, without using message_post
(using notification field, + model and res_id)
- improved form view of composer, adding a filed explaining a bit the various
recipients
- removed unnecessary fields coming from the template (partner_to, ...) because
they are confusing -> composer should be easier to understand and use
- removed some unnecessary code
- removed double body computation when using templates (one for tmeplate, then
the wizard -> not necessary)
This commit will be followed by other to try to improve the mass mailing
and mass post.
bzr revid: tde@openerp.com-20140220152945-ash0hfkzevzamihq
|
|
due to list view header being checked, display
an info in the mass mailing wizard to warn the
user he is about to mail all records matching
its search filter, not only the selected ids.
bzr revid: tde@openerp.com-20131017093830-cvxihr3zwohos9ol
|
|
in mail.compose.message + form view cleanings + some fixes in mail_mail about set_opened/replied/bounced, now checking that ids effectively exist
bzr revid: tde@openerp.com-20130910151901-nhuwvtrkbwekyh7x
|
|
perform a mass post on documents.
bzr revid: tde@openerp.com-20130910124754-jssus6l43nil4qad
|
|
bzr revid: atp@tinyerp.com-20130812043810-y14dmqwvuxrxkuag
|
|
bzr revid: tde@openerp.com-20130726104902-l3ax6ycautky97gh
|
|
bzr revid: tde@openerp.com-20130725135029-mx946vaibvz1rzii
|
|
bzr revid: tde@openerp.com-20130722131725-i30xd4b03nui3hyw
|
|
bzr revid: tde@openerp.com-20130722112306-r1u77tyqzk4bknrb
|
|
bzr revid: trivedi.pariket@gmail.com-20130716085231-8qe107fvcm6rwmj4
|
|
bzr revid: tde@openerp.com-20130319093844-82c95hmwznaprp6t
|
|
a well defined template) + improved form view of mail.compose.message wizard.
bzr revid: tde@openerp.com-20130312133817-y9xztv6gs4ut7ndj
|
|
bzr revid: tde@openerp.com-20130305151408-h6800swy10xnu634
|
|
form vivew.
bzr revid: tde@openerp.com-20130305124259-x3vb5ds2xi9v389d
|
|
email_cc, partner_to even if no template. Mass mailing is a no-subtype post with additional recipients manually notified. Added option (in technical features) to send to followers, or to directly create a mail_mail. Added some default values in mail_message. Added explicit management of email_from and reply_to. Having a reply_to bypasses the 'model-res_id' in message_id behavior allowing to construct threads. Added explicit recipient_ids field on mail_mail that replaces the recipient_ids parameter in mail_mail.send(). Updated tests accordingly.
bzr revid: tde@openerp.com-20130225164857-i635atksj7riq9nd
|
|
selection
bzr revid: odo@openerp.com-20121220172012-f0j24mzljgqs9l0r
|
|
tables. Updated several accesses to bypass the security issues. Updated portal tests to have a more complete test scenario.
bzr revid: tde@openerp.com-20121212125518-k0s07niojr8a1xtu
|
|
the selection box; also cleaned display of recipients when using the wizard in mass mailing mode.
bzr revid: tde@openerp.com-20121211155435-l5s9lpghpxw8bi9o
|
|
content_subtype obsolete and removed
bzr revid: odo@openerp.com-20121116170503-mvsaa0pv5py2b7ri
|
|
These fields were used in pre-7.0 to manage the plaintext variant of the
mail being composed, but as of 7.0 the composition wizard will always
use the HTML/Rich text mode, so they can be dropped.
bzr revid: odo@openerp.com-20121115135634-fcy6mexnctwg0nxb
|
|
recipients, displaying Follows of XXX, when commenting a document, to clarify a bit which partners will receive the email.
bzr revid: tde@openerp.com-20121109135612-xw86jk4jlri8zfxp
|
|
bzr revid: chm@openerp.com-20121109101628-4e8cnjr1lcmt0tdv
|
