- Jan 31, 2019
-
-
Christophe Simonis authored
-
Fabien Pinckaers authored
If no Undistributed Profits/Losses account can be found, Odoo tries to create one with number '999999'. However, such an account number might have been created manually by a user. In this case, the account creation fails. opw-1932701 closes odoo/odoo#30719
-
Nicolas Lempereur authored
When a colored kanban tile is colored, and there is a color attribute on the tile HTML element indicating a color field (eg. when a kanban view with color dropdown is created in studio), there was a HTML element over the whole tile preventing to click on links or other sub element of it. This HTML element is just a transparent used for accessibility to contain the tile color intelligible name, so this commit just size it over the area of the color (currently in base bootstrap ~3px at the left of the tile). opw-1932283 closes #30717
-
- Jan 30, 2019
-
-
Christophe Simonis authored
-
Alexandre Kühn authored
Before this commit, when a user had some meetings planned today and open the systray activity menu, the counter would disappear. This was caused by a weak computation of the counter that relies on activity having always a total counter. This was not the case for activity that are today's meetings: Counter would be computed as `NaN`, and since `NaN` is falsy, it won't display the counter. Today's meetings have no reason to have a counter, so this commit fixes the issue by letting those activities not change the computation of the counter. closes odoo/odoo#30695
-
- Jan 31, 2019
-
-
Martin Trigaux authored
If xlwt is not installed on the server, the option is disabled. However, the first element was checked, even if it is disabled. Trying to export record without xlwt was causing a traceback. Introduced at b60de0db where xls is now the first choice closes odoo/odoo#30724
-
- Jan 30, 2019
-
-
Pierre Paridans authored
On mobile, swiping right/left switches to next/previous record. This feature prevents the horizontal scroll of the form notebook's tabs by overtaking the swipe gesture on those elements. This issue had different consequences depending on the platform: - on iOS: the tabs cannot be scrolled at all. - on Android: the tabs can only be scrolled by using a two-fingers gesture This commit restore the horizontal scroll on the tabs but also keep the swipe-gesture to navigate records. opw-1929267 closes odoo/odoo#30658
-
Olivier Dony authored
As of 12.0 the superuser account (UID 1) is only meant to be used for advanced debugging, and non-superuser admin accounts are used for day-to-day administration. Adapts the admin detection system to allow non-superuser admins to select the report layout as well.
-
Olivier Dony authored
The payment reconciliation screen can't be opened if there is no partner on a payment, and currently crashes with a traceback. Rather than hiding the button which could cause surprises for users, we can raise a proper error to explain why it can't work, for the cases where a payment has no related partner. This could happen for example when a customer paid via a direct /website_payment/pay link.
-
Nicolas Lempereur authored
When we use "Send invitation again" on a survey.user_input, it will send the first survey.user_input it finds corresponding to: - the state "new" or "skip", - the partner it must be sent to, - the survey the user_input corresponds to, - the email it must be sent to, or if none found, it could be create a new one. This is an okay behavior in most instance, but in the case of hr_appraisal where a manager could have same survey to fill for "employee A" and "employee B" and when you send them again, we would receive two mails linking to the same employee. With this changeset, the current behavior is kept but when an existing user_input is resent, we prioritize itself before searching a matching one. opw-1934478 closes #30693
-
Denis Ledoux authored
This reverts commit 52906999, reversing changes made to 76e085cb. PR #30690 is a cleaner solution to the problem than PR #30402. closes odoo/odoo#30696
-
Nicolas Martinelli authored
Since PyPDF2 gives bad results for PDF indexing, stop using it since it raises more issues than it helps users. opw-1928446 closes odoo/odoo#30692
-
Christophe Simonis authored
-
Denis Ledoux authored
Following revision 61eef73b the fallback to the standard external layout when the external layout is not set on the company has been removed. It therefore leaded to the raise of the exception ``` The report's template '%s' is wrong, please contact your administrator. Can not separate file to save as attachment because the report's template does not contains the attributes 'data-oe-model' and 'data-oe-id' on the div with 'article' classname.") % self.name) ``` when the external layout was not set, which could happen quite easily in a multi-company environment, if you do not set the company external layout after having created it. This revision simply puts back the fallback as it was before. opw-1931195 closes odoo/odoo#30687
-
Julien (juc) Castiaux authored
When using the "test import" feature to import leaves request, odoo fails with a 500 error and no error message. The only difference with a real import is that the test dry-runs by rollbacking. The issue here is that mails are sent *after* a commit is done hense crashes because they do not exist anymore. opw-1916913 closes odoo/odoo#30523
-
Christophe Monniez authored
When printing a delivery order in waiting state under MS Windows, the produced PDF does not use the proper font for the warning line. This leads to an unreadable line full of small rectangles. The problem comes from the fact that the 'fa' class is applied to a full paragraph. With this commit, the proper 'i' tag is used to display the exclamation triangle. opw-1931892 closes odoo/odoo#30680
-
wan authored
purpose: when creating a writeoff from the manual reconciliation widget (invoices & payment matching), there's no way to specify the date of the writeoff journal entry specs: in v12, add a date field in the js and set the date of the writeoff entry accordingly Was PR #29794 Was OPW 1896593 closes odoo/odoo#30676
-
Quentin De Paoli authored
-
wan authored
OPW 1891131 closes #27497 When creating a new bank account/partner address, the view displays the 'state 'field before the 'country_id' field, which naturally leads users to select the state before selecting the country. But there was problem: in order to select a state, one had to first select a country, which was confusing. Done: - allow the user to select the state before the country (without restriction on country) - remove the state from the form when the country changes, if the state (name) is not in the country - automatically set the country when the state is set - always display the country code in the name_get of res.country.state, to deal with the case where different countries have a state with the same name
-
- Jan 29, 2019
-
-
Quentin De Paoli authored
-
- Jan 30, 2019
-
-
Julien (juc) Castiaux authored
To reproduce: 1) Enable multi-company 2) Create two companies: c1, c2 3) Create two users: bob in c1 and alice in c2 4) Install subscription 5) Remove the ir.rule that forbid users from accessing subscriptions made in other companies: "Subscription multi-company" 6) Using u1, create a new subscription in c1 7) Using u2, follow the chatter of the newly created subscription allowing the user to post messages/log notes. 8) Using u2, send a message with an attachment. Access Error. The problem raises only for the **first** attachment. That attchement is written on the record as the main attachment thus raises an error if the user doesn't have write access. There is no problem to add attachment to any following record or when the user has write access on the model. If the user doesn't have access to the chatter, he is blocked before accessing the write thus it is safe to sudo it. opw-1915606 closes odoo/odoo#30659
-
- Jan 29, 2019
-
-
Nicolas Martinelli authored
- Set the OS in a timezone such as the current day is different from the day in UTC (e.g. America/Nome before 10:00 AM or Australia/Melbourne after 3:00 PM) - Open any datepicker - The 'little triangle' indicating the current day is wrongly set (one day before or after) Knowing that Odoo always creates momentjs date and datetime with the `UTC` flag set to `true`, the `bootstrap-datetimepicker` does something which seems inconsistent. First, it retrieves the `viewDate`, and sets it to the beginning of the month and week in: https://github.com/odoo/odoo/blob/1c6c504215f3ef09e6336c92c9d350e87599eaa1/addons/web/static/lib/bootstrap-datetimepicker/src/js/bootstrap-datetimepicker.js#L725 In this part, it is important to note that each `startOf` functions called sets the hours/minutes/seconds to zero. It means that the reference time is changed. Then, it iterates on this newly created date, and determines `today` by comparing it to `getMoment()` in: https://github.com/odoo/odoo/blob/1c6c504215f3ef09e6336c92c9d350e87599eaa1/addons/web/static/lib/bootstrap-datetimepicker/src/js/bootstrap-datetimepicker.js#L748 However, `getMoment()` returns the current date and time, but with the `UTC` flag set to `false`. Therefore, we compare a UTC datetime on which the reference time has been changed to a non-UTC datetime, which fails to give the appropriate current day. There are two approaches to solve this. The first possibility is to change the way Odoo defines momentjs dates and datetimes, maybe by removing the `UTC` flag at creation. This sounds like a bad idea, since other widgets or views (such as the calendar or the pivot view) make use of them. This is likely to introduce a bunch of new issues with TZ in these views. The second approach is patching the library to fit our use. Although we usually don't do such a thing, this allows to specifically solve this use case, and in particular placing the 'small triangle' at the appropriate date without impacting any other part of the system or the library. It can be easily performed by comparing the dates and the months to make it work. opw-1915251 closes odoo/odoo#30538
-
- Jan 30, 2019
-
-
sbbaro authored
When printing multiple reports with the "Reload from Attachment" option selected, the order of the rendered pdfs was not respected. Using an ordered dictionary instead of a randomized one solves the problem. opw 1915685 closes odoo/odoo#30690
-
- Jan 29, 2019
-
-
Christophe Simonis authored
-
Christophe Simonis authored
-
Jeremy Kersten authored
Before this commit, clicking "Edit in backend" from the website could randomly lead to the backend under another menu or without module, depending on the other modules that are installed or version com/ent used. After this commit, it will always open the backend under the specifiec menu or website menu if not defined. + uses existing website dedicated action for product.template in 'Edit backend' task-1919436 closes #30555 Co-authored by seb@odoo.com closes odoo/odoo#30657
-
Jeremy Kersten authored
Before this commit, if you installed website in community you was not able to install web_enterprise, because the web.login_layout was replaced (by hinerit) by website and break the xpath from enterprise login. Now we apply the Enterprise login xpath before that website replace it.
-
Jeremy Kersten authored
-
Nicolas Martinelli authored
- Install Invoicing - Multi company Set up with no common contact book - Create & validate an invoice with user A in company 1 - Change to company 2 with user A - Connect with user B in company 1 - Send & Print the invoice An error is raised on the template rendering because user B cannot read info from user A. opw-1928676 closes odoo/odoo#30649
-
- Jan 30, 2019
-
-
Nans Lefebvre authored
Steps to reproduce: - Edit a record. - Log a note or send a message with an attachment. - Save the record. Bug: changes made to the record are discarded. Because uploading an attachment triggers a reload without 'keepChanges', the record values are read from database. However displayed values are not updated, so there is no feedback that changes have been discarded. On save, the page is reloaded so the user sees that changes have been lost. Introduced by 7f97c9fc. opw 1923824 closes odoo/odoo#30642
-
Martin Trigaux authored
A sale.order is an authorised model for mass mailing but it does not have an email or email_from field. When trying to send a mass mailing campaign on sale orders, an error was raised as sale_order.email_from does not exists closes odoo/odoo#30220
-
- Jan 29, 2019
-
-
Jorge Pinna Puissant authored
Have a Lead with the contact informations (Customer Name, Street, Street 2, City, State, ZIP, Country) completed in the 'Followup' page. Before this commit, when the base_adress_city module was installed, the informations of the City, State and ZIP where lost when we try to create a new Partner from the Lead. Now, the informations are present in the Partner form; furthermore if the country allows enforce cities, the information is also present in the enforce city form. OPW-1932018 closes odoo/odoo#30644
-
- Jan 30, 2019
-
-
Julien (juc) Castiaux authored
When using the datepicker with norwegian locales, the dates are correctly formatted using the norwegian locale but the name of the months are shown in english. This cause a date validation error and thus it is not possible to change the date. tempusdominus.js uses moment.js to deal with dates, it sometimes copies/creates some and set their option according to the ones given at instantiation time and fallbacks on default options for that are not set. opw-1922437 closes odoo/odoo#30276
-
Jorge Pinna Puissant authored
In stock.picking, in mode show detailed operation, add a product with unique serial number tracking. Before this commit, a warning about the qty is raised. This warning, must be raised only if the qty is different from 1. However this is not the case, the warning is raised at each modification of the line. This issue occurs since the rounding given to the float_compare is 0.0, because self.move_id.product_id is not set. Float_compare with a 0.0 rounding always return different, hence the bug. Now, the warning is only raised when the qty is different from 1. OPW-1932044 closes odoo/odoo#30651
-
- Jan 29, 2019
-
-
Romain Derie authored
Before this commit: 1. If we were editing a template with no xml_id, typically the case when editing a specific view (COW'd), the 'Template ID' label would be left empty as the view does not have an xml_id but only a key. 2. If we were editing a generic view, the template would be COW'd and replaced by the specific one created during the save. After the save, the page would be reload and will try to reopen the edited template (stored in url `res=123`). But as this template would be replaced by the COW'd view, the JS would crash trying to access an inexisting view. The HTML editor would then open in a very thin modal, barely editable. Now: 1. Display the template's key instead of its xml_id. The key is basically a duplicate of the xml_id, mainly used in website. 2. If we are saving a generic view, we search for its newly created specific view to upload the URL hash before reloading. task-1934279 Fix #30447
-
Romain Derie authored
As this behavior was recently broken (fixed in #30403), this commit adds a test tour for that flow. task-1934279 Fix #30447
-
Romain Derie authored
With the following view hierarchy: A | B' (oe_structure_ID view) Before this fix, when saving multiple templates at once from the same hierarchy the COW views (website) would not be saved correctly as the first call to `write` would COW the parent view, then the second concurent call to `write` would create the child specific view under the generic parent view. Instead, the generic parent should have been cloned to a specific parent view and then the child view should be COW under the specific parent. A A' | | B' B*' (This one is the old B', without B' changes in the html editor) Instead of A A' | B' Calling the `write` one after another will do the trick. Indeed, when the second call is fired, the first call has already triggered the COW behavior. Thus, the second call correctly retrieves the COW view. Another issue might still appear, if the parent view write is sent first. Indeed, the parent view will be COW, thus the specific child view (second write waiting to be fired) will be deleted to be added on the new specific hierarchy. Thus, that write will then raise an error since the view does not exist anymore. task-1934279 Fix #30447
-
Christophe Simonis authored
Oversight of previous forward-port.
-
Christophe Simonis authored
Now that urls are shortened by email (and not globally)[1], more queries are executed. Oversight of previous forward-port [1] See #29083
-
Christophe Simonis authored
-