This revision is related to 6f355623f0.
The above revision had as goal to not allow the partial cancellation
(line per line) of a confirmed bank statement, as it would
prevent the ability to reconcile the statement, as reconcilling
a confirmed statement it not possible.
Nevertheless, cancelling the whole bank statement should be allowed
(using the `Cancel Statement` button), as this cancel all lines
and re-set the statement in draft.
opw-649864
fixes#8568
When invoice_method == 'picking', a po line is invoiced if all the lines
linked to the po line are in invoices with state not in ['draft', 'cancel'].
To keep the same logic than before commit 9b1ab76.
opw:649746
UP and DOWN (keydown event) move the cursor position at begining and end of the input text value. ENTER keypress event add 1 to the cursor position. So these events are now 'preventDefault'.
Since mail.channel user member instead of follower, the frontend widgets required some changes. This commit kind of duplicate follower controller from website_mail for channel member usage. These are now 2 separates widgets. Performance can be improve by removing rpc call when rendering widget, but since this commit is a fix, it does not touch this.
This makes patching much easier. In some cases we can work around some
of these widgets not being exported, but it's ugly and there's just no
real reason to do that.
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.
Joren Van Onder