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.
* move guess_mimetype from ir_attachment to a misc submodule so it can
be used outside of attachments (in base_import in this case)
* fix the broken detection of zip and OpenDocument files (would all be
detected as msword files)
* correctly implement detection of OOXML files (including returning the
right MIME type)
* attempt to correctly detect OLECF Excel files (.xls)
* add PPT detection (untested)
* remove duplicate patterns in GIF detection
If the user provides a known mimetype which doesn't actually match the
file as far as we're concerned, warn and fallback on extension rather
than blow up.
This comes up when a user installs Excel on Windows: it associates CSV
files with itself and sets their mime type to application/vnd.ms-excel,
which is not correct and leads to us trying to load a CSV with xlrd (an
excel-parsing library).
Fixes#9779
DO NOT FORWARD-PORT TO MASTER
When the user wants to edit the translation of a view, a JS traceback
appears. The reason is that the `WebClient.DebugManager.View` tries to
access `view.controller.fields_view.view_id` before the fields_view_get
is actually resolved.
The issue is that the DebugManager is loaded when the dialog is opened.
However, the dialog is opened before its content is actually loaded. The
proper fix would be to open the dialog only when the content is ready.
Since this might imply side effects, this fix will be done in master
branch, not in the stable saas-7.
The workaround is to open the translation window in the current window,
not in a dialog window.
opw-669140
The unsubscribe URL is used within the `mass_mailing` module,
e.g. in `_get_unsubscribe_url` & `send_get_email_dict`.
Basically, there is the possibility to add the unsubscription
link in the mass mailings while having only
`mass_mailing` installed.
But, the unsubscription route is defined within
the module `website_mass_mailing`.
Therefore, if you added the unsubscription link
within your mailings while not having
`website_mass_mailing` installed, trying
to follow the unsubscription link leaded to
a `404 Not Found` page.
We therefore define the route within `mass_mailing`
directly, which does the basic stuff (the basic
unsubscribe and confirmation), and override this route
in `website_mass_mailing`, where the advanced stuff is done
(the mailing lists list unsubscription and the better
looking page).
opw-669425
The button 'mark all as read' used to mark all messages as read, which
is not usually what the user wants when there is an active filter in the
search view. This commit make sure that the domain is send to the
server and used correctly.
The copied textarea used in autoresize was a valid target for focus when
using the tab key. This is a major issue in editable list views,
because when the user leaves a textarea, the list view jumps up, with no
visible focused field.