* Remove recursive assets inclusions (i.e. assets_editor was including
assets_common, summernote, ...)
* Better construct the assets (link, then script + type attribute)
* Better include the assets (split js / css, always use t-call-assets)
* Simplifies the number of assets
* Move bootstrap js to assets common
* assets_frontend is now created by web module to allow using it on the
connexion page but also in the web_editor, where colors have to be
bootstrap/theme ones. Note: if a module depends on website, then keep
using the inherit_id="WEBSITE.assets_frontend"
* Convert some CSS to LESS
* Split/Join LESS files
* Remove duplicates between website and web_editor
* UI improvements
* Allow simple customizations thanks to LESS var&mixins for website
Before, the whole editor UI was redefined for web_editor, each
mass_mailing template, website builder, ... Now they all inherit
from the web_editor one.
This makes it so that when you set a customer in the POS frontend it
will automatically apply the fiscal position associated to the customer
on the order.
If the customer has no set fiscal position or if the fiscal position is
not available in the POS nothing will happen.
opw-668155
This was not really possible before. This prepends a dummy undefined
fiscal position to the selection list that'll clear the current fiscal
position when selected.
Also considered was using the "Cancel" button of the selection widget to
clear the fiscal position, but that doesn't make a lot of sense from a
UI point of view. Pressing a "Cancel" button shouldn't change anything
in the underlying model, it should just get rid of the dialog window.
opw-668155
- Hide account_id field and add a required project_id field on timesheet entries
- Remove is_timesheet field: as project_id is only required for timesheet entries and not for other analytic lines, it can be used to determine wether a line is a timeheet entry or not.
- Remove project_timesheet module as all its functionalities are moved to hr_timesheet
- Replace timesheets on contract option on products by timesheets on project
- Small fixes and improvements in timesheets and projects views and groups
- report.transaction.pos
- report.sales.by.user.pos
- report.sales.by.user.pos.month
These reports where not called anywhere and have been replaced by pivot views
Remove order reports that can be easily replaced by use of the pivot view of
report.pos.order
Add a session_id field and a filter on report.pos.order to make it equivalent.
The invoice report is only useful when called from the pos UI so keeping the
report but not added in the print menu
For textual attachments (like assets), the indexed content is the
content itself. Avoid prefetching this potential huge field.
When deleting attachments, only delete files once.
Previous implementation was expecting exactly the same number of
attachments than the number of assets in a bundle. However it's
possible that duplicated assets are created due to concurrent first
generation.
This duplication cannot be avoid, but is cleaned upon next bundle
regeneration.
Joint work with @sle-odoo and @odony
Allow easy modification of ClientListScreenWidget by other modules. If
you get creative you can actually get to it without this, but it's not
clean and needlessly complicated.
opw-669686
On deletion of a pricelist,
the pricelist items were not deleted.
Meaning, if you deleted a pricelist,
and this pricelist was used in the product pricing,
the line with the pricing remained, but without any
pricelist set. Besides, as the field is required
in the view, this prevented to edit anything without
correcting the pricing line first.
opw-669652
1e936c9df4 assumes that website_sale_stock
is installed.
As website_sale_delivery depends on website_sale and delivery (that
depends on sale_stock), website_sale_stock should be auto-installed, but
not always BEFORE website_sale_delivery.
So we mark this dependency as explicit.
Rather than trust the user-controlled mimetype or extension of imported
files which may be incorrect (because the user is lying, because the
system is misconfigured, because software is not installed, because
software is registering non-standard mimetypes, etc...), start by trying
to guess the mimetype *then* fallback on trying the type/ext.
Of note: CSV is becoming less and less great as it's nigh impossible to
guess for it.
qsm-odoo