When a SO creates a task, the chatter message displayed "Task Created",
which was not extremely helpful.
This commit add meaningful messages on the SO and on the task itself
and makes use of the "chatter link" feature to make the references
clickable.
We use summary instead of class as classes are often stripped by gmail or even odoo.
Summary is a commonly kept attribute so it is used in the mail gateway to hide
what is considered as internal content and should not be rendered in the chatter.
A new preprocess method is added to the template engine in order to do
preprocessing/sanitization of the templates before compilation.
This method can be overloaded in order to add new features such as
translation, ...
The website_theme_install needs to reference the module category whose
xml_id is base.module_category_theme_hidden. The problem was that it
needs to do this in a context where the category might not exist (as
auto-created only if a module defines its category as "Theme/Hidden").
To solve the problem, the category was explicitly created by the
website_theme_install module to be able to reference it.
Commit 11812b0b9e removed the "base." part
of the xml_id thinking it was a record which had to be created by the
module. This then wrongly showed the Theme/Hidden modules in the list.
Now the solution came from commit https://github.com/odoo/odoo/commit/c6983137#diff-07193f47475ccdd78f39773a368ce05bL386
which now allows to use the second parameter of ref in a domain
context. This allows to tell the system to not raise an exception if
the ref we want to find does not exist.
When we are creating a database with a country code from the database manager,
the country is not set in the company, so when we install the accounting app, there
is no chart of account installed by default. We have this bug because
we are trying to put a country id in a field that should receive a
'res.country' record.
To fix this bug, we change the call of function read_search by a search
that will return a recordset.
Bug introduced in rev https://github.com/odoo/odoo/commit/1b59643d4b96195edcdbe1b1168a11a3b6d85483
The action was never there but added by overwrite in sale_teams which (wrongly)
shared the same ID. After 11812b0 which splits the menus, this menus had no
longer an action added by sale_team module.
When we create a 'product.product', the 'lst_price' entered is
not saved. This is due to the 'inverse' function of the field
named '_set_product_price' which is shared with 'price' and
'lst_price' and uses 'price' to set the value, even if its called
by 'lst_price' field.
Before the migration in new API, it was possible to have the same
inverse fucntion for different fields because the value was passed as param
to the function. In the new API, we cannot because we have to get the
value from the field.
To fix this error, we had to duplicate function '_set_product_price'
in 'set_product_lst_price' to have on function by field, and use the
value correspondig to the field.
Introducied in rev: https://github.com/odoo/odoo/commit/1aa5bc0fdfa402ac7cccbc3a7203ec5050f6339b
When users switch from one version to another, the localstorage is not
cleared and users can get errors because the tour manager is trying to
load steps (according to the localstorage content) which could not
exist anymore.
This could also happen when a module which extends another module tour
is installed.
When users switch from one version to another, the localstorage is not
cleared and users can get errors because the tour manager is trying to
load steps (according to the localstorage content) which could not
exist anymore.
This could also happen when a module which extends another module tour
is installed.
When selectionning a saved shipping address when setting the shipping
address of an ecommerce order, the country and state should be set
accordingly.
unrelated issue noticed when testing e0d4dd01cc
In 1ef52c9c the code displaying state of a given country was improved
for some incompatibilities.
But, if when setting the billing informations we choose to create a new
shipping address, the shipping state* would not be displayed even when it
should be (currently, if the shipping country is Australia or U.S.).
opw-687948
*a state being a subdivision of a country
Until 9.0 our psycopg2 DSN connection strings do not allow having
spaces within the db name, and passing some can cause duplicate
registries to be loaded.
Stripping spaces is a simple workaround until we actually support
spaces within db names.
Fixes#13078
Issue: An employee submits an expense report and this report is refused by the HR or the accountant (Wrong amount, one line will not be paid,...). Currently the expense fields are readonly except in draft state. In our case, the employee is unable to modify a line and resubmit the expense report.
This fix remove the readonly state on the expense line in refused state.
The sale of the day report was removed during new api migration as it was
thought, it could be replaced by pivot view.
Due to the lack of some options and the problems to be printed, create similar
report.
This commit adds a report in the PoS interface to be printed on ESC/POS printers
and add a JS wizard to restore it in the backend with date selection.
The wizard is made in a new web widget because adding a wizard requires changes
not compatible with stable version.
Creating a proper wizard should be done in v10
opw-681833
Since 9.0, `message_follower_ids` are
`mail.followers` records,
the partner are in `message_partner_ids`.
Therefore, the partner images displayed in the note kanban
were not the images of the right partners.
opw-688100
Do not force the `search_default_product_id`to the current
product variant, as the domain just above could return a
result, a BOM which is set for the template of this variant
but not for the variant istself, that this filter would hide.
This is following the revision
52cba1b563
Because of this, a product variant smart button could
display "1 BOM", but when clicking on it, none would be displayed,
which is not user-friendly at all.
opw-687912
If `method_time` is set to end, `method_number` is not the reference for the number of depreciation lines.
Take directly the number of depreciation lines is more correct.
When creating a task on a project which is accessible to followers only,
an access error pops up.
This comes from the `subtask_project_id` field on the task, which is a
related to a `project.project` field. When a task is created, the ORM
tries to write on the related field, and hence on `project.project`.
opw-687252
The view `sale_team_dashboard` (which extends kanban) has been removed
and replaced by a default kanban view.
To use it in the ViewManager, an option `js_class` is added
on the arch description and this class be used as the View.
This avoids creating a new view type just for one view.
* use a special arg in odoo.py
* note that the previous implementation was relying on the fact that
the openerp-gevent file was located in the same directory than the
odoo.py file. This was no longer true since rev a0eb172cab
This commit brings back this behavior.
This revision removes the context from the action:
afd29b277d
The thing is, in saas-11, the `product.template.type`
no longer has in its selection values `product`,
in the module `product`,
there is only `consu` and `service`.
the type `product` is added in the module `stock`
Therefore, this `product` cannot be used as default value
when only the module `product` is installed and not
`stock`.
We force the empty context for migration purposes,
so bases in ealier releases than saas-11 do not have
`'default_type': 'product'` within this action
when they are upgraded to saas-11.
opw-687986
fix error introduce in commit 7596fa3ee3
The get_format_currencies_js_function return javascript code and the openerp.web should not have been replaced by odoo.web. The result is that reconciliation view was broken.
Commit 06754b32 brings an inconsistency between the PoS frontend, the
pos_order and the account_invoice tax calculation. Part of the commit is
correct since it corrects the matching between the `compute_all`
methods, however.
opw-680891