* allows portal users to update their password * and manage their API keys * any anything technical / security related we may need to add in the future Also bridge module for the password meter (auth password policy).
Follow up of 61de1c263a7a40a36f2b58b8a107c350de6b6c7f - Remove the dangerous **kw from the route in favor of specifying useful args. - Use the existing method to link attachments to message instead of duplicating the logic in an incomplete manner. - Fix an issue where the actual email would not be sent if the message was empty but an attachment was defined. - Ensure the send attempt is done immediately instead of after the cr commit. The goal is to show potential error messages correctly to the user with the crash manager instead of a generic error page. This also increases the send timeout and prevents the error in the first place in most situations. closes odoo/odoo#35263 Signed-off-by: Christophe Simonis <chs@odoo.com>
Before this commit, it was only possible to add attachments on documents from the backend or by sending them by email. It is now possible to add them also from the portal chatter, including for portal/public users who have a valid access_token. Part of task-37264 closes odoo/odoo#34526 Signed-off-by: Olivier Dony (odo) <odo@openerp.com> Co-authored-by: Pratima Gupta <pgu@odoo.com> Co-authored-by: Sébastien Theys <seb@odoo.com>
Before this commit, the syntax to start a tour was extremely verbose. With this new method, it is possible to start a tour by just giving the essential parameter: the tour name. The full set of features from browser_js are kept by using **kwargs. closes odoo/odoo#32316 Signed-off-by: Christophe Monniez (moc) <moc@odoo.com>
Purpose: When running tests, all the tests for the installed/updated
files are done. This commit adds a 'tagged' decorator that can be used to
tag tests. Combined with a new 'test-tags' CLI option, it adds the ability
to filter which tests are executed. For example, @tagged('slow') will
add a tag 'slow' to the test. The CLI option 'test-tags="slow"' will
only run tests tagged 'slow'.
One can use prefixes to select cases with tags.
'+' or no prefix means that the tests tagged with this tag are selected
for execution. '-' prefix will exclude the tests tagged with this tag.
Exclusion takes precedence over inclusion.
Also, by default, all Odoo tests cases are tagged 'standard' and with
the technical name of the module.
This means that when selecting tests with the 'test-tags'
parameter, if '-standard' is not specified, all tests tags are
going to be executed.
When tagging tests, one can remove such automatic tag by prefixing the
tag name with '-'. E.g. @tagged('-standard') will remove the standard
tag from the test.
Another example, if one wants to test the 'sale' module alone,
even without adding any 'tagged' decorator thos tests can be selected
like that: --test-tags="sale"
Tests are selected or deselected using a TagsSelector. When instanciated,
a string is passed with comma separated tests selectors like
'+slow,-standard'. When the 'check' method is called with a test as argument,
it returns True or False if the test has to be executed or not.
Those belong to mail, not website_portal.
This commit moves the whole customer portal to the portal module. It now completely uses portal and http_routing features and is not dependent on website anymore. An override of web controller is added in portal in order to redirect portal users to /my instead of /web. That way once having the customer portal installed all share users are correctly redirected to their account. All modules defining customer portal templates and controllers are updated accordingly.
The goal is to prepare the removal of 'portal' module. Converting a partner into a portal user, though the wizard is moved in website_portal. 'base' will manage portal user and group, but if website_portal is not installed, there is nothing to display for portal user.
Currently almost all mail tests run on mail.channel model. Indeed it is the only model inheriting from mail.thread and mail.alias when having only mail installed. However channel model have several specific features and is not totally a standard mail.thread model. For example notification recipients are computed a bit differently. Since 4f9105a4ef40bccd3b27a6a10cc612636a6499f7 mail module has a test model allowing to perform tests on a very simple mail.thread-like model. This commit make mail tests use this test model instead of mail.channel everywhere it is possible. Channel model should be used only when tests are channel-dependent.