When displaying ir_attachments, show a preview if it is an image; show the icon otherwise
Clicking on the icon/preview should trigger a download
+ Typo correction
When converting an opportunity to a quotation,
the note was forced to the `company_id.sale_note`,
which could be `False`.
This prevented the other possible defaults for note to be set,
e.g. the note from the `website_quote` `template_id`.
Besides, the note forced in this wizard:
`sale_obj.get_salenote`
was almost the same than the defaults of the sale.order:
`company_id.sale_note`
except the language, the note translation in partner lang.
Therefore, the default value of `note` for sale.order has been
changed to use this `get_salenote` method, which handle
the language, so it's no longer required to pass it in
the convertion wizard, the note will now be added
as any default value, giving the possibility
to add another note default value.
opw-650050
Add 'force_display' param for the frontend chatter to allow public user to see the textarea. When submitting his comment, he will be redirect to login page (like it was before generic chatter) in both mode (json and post mode). This required changing the error handeling of json mode : when a login is required, the user switch to post mode to allow http redirect, keeping its submitted params (rating, comment, ...).
If no value given for the widget, use the default ones for the rating. Otherwise 'NaN' is sent to the server, causing crash in website_sale when posting a comment without rating
add option in res_config to have advance mode for call for tender (option was lost in commit: 3d8f7c2f24)
+ fix errors in method that used old po_line state
+ change icon to font-awesome icons
A modification done in the product form has been reverted probably
by accident, leading to linking a removed action. The intended
action has been put back.
In saas-6, the `ir_sequence_date` key in the context
has been introduced, to use this date instead of the
current date for sequences including date variables
(Year, month, day, ...).
So, when an invoice is created for a previous fiscal
year / period, the sequence is built according
to the date of this fiscal year / period.
e.g., for an invoice sequence containing the year,
for an invoice created in 2015, but which
is for the 2014 fiscal year, the sequence
contains 2014 instead of 2015.
Nevertheless, this leads to a retro-compatibility issue:
the impossibiliy to use the current date for your
invoices sequences.
Indeed, some users want to include the current month
and day in their invoices sequences,
e.g. xxx-20150922.
This revision brings the possibility to use both
possible dates, the beginning of the date range
or the current date.
opw-649487
Coming from hr_recruitment, where kanban_state is displayed, but without the customization
Also, remove lingering options in view, and missing fields for project_issue
This option will set a SO automatically to Done when it is confirmed.
The purpose is to prevent a user to modify a SO after confirmation, as
it was the case up to v8.0.
1) Remove unnecessary comparison
If the minimum quantity required by the supplier is not met, the
supplier is not chosen. So it is not necessary to compare the quantity
of the supplier after the browse.
2) Ignore AccessError when adding to new supplier to product
This should not block the user to confirm the PO.
When clicking on the stat_button "Meetings" in a partner formview, the
calendar opened with a filter "Attendees : <the_partner_id>". Now the
same result occurs but with a more explicit filter: the partner name
instead of its id.
In v8, some fields were added for the product.pricelist formview by
template inheritance : after the active field. For v9, this active
field was moved in a button_box button (archive stat_button), so the
added fields (inheritance) landed in the stat_button too.
The journal_id used in a purchase.order created in auto procurement
(by the function make_po) must be the journal_id of the company_id
set on the procurement. The company_id set on the procurement is
the company_id set on the SO (function _prepare_order_line_procurement).
When creating the PO in function make_po, the company_id must be set in the
context to use the right journal_id with the function _get_journal in
"purchase.order" model.
opw:648600
* Group with 6 columns caused problem when inside a dialog because of
wrong use of labels.
* Use o_row to align input followed by a '%' sign.
* col=6 group should not be in a parent group (moreover: this group was
alone in this parent group).
- Change the widget behavior from asynchronous to asynchronous, by adding 3 related fields
on the project.task model, which are the custom labels defined for the stage
- Instead of making a rpc call, we are taking directly the labels on the parent for the kanban view,
or on the view datarecord for the form view
- There are now 2 templates for the kanban view or the form view
- The development has been backported in the community version
- The options attribute has been removed on the project_view.xml file for the kanban_state field
It was preventing pos managers from opening sessions for pos
users. Because pos users cannot open their own sessions, this means they
couldn't do anything anymore.
The reason for it is that the open frontend function checks whether or
not the opened session belongs to the current user. If it doesn't, it
throws a UserError, which prevents the session from being
created. That's all open_frontend_cb did when called from
wkf_action_open anyway, because the action it returns just gets ignored
in the workflow.
This also removes the validate & open session button because the only
reason not to use the new dashboard to create a session is when you want
to create a session for a different user. When doing that, validating
and opening the session yourself makes no sense. When people do want to
create a session for themselves without using the dashboard they can
still do so, they will just have to save the session form and then click
on the continue selling button.
Josse Colpaert