Saturday, March 2, 2024
5 changes · master
Miscellaneous changes
**Steps**: - Open Project > Task - Add a description > save - Perform 'Action > Restore History' - Observe that the description is set to null - Perform 'Action > Restore History' again **Issue**: - We get a type error and the code crashes **Cause**: - We get the value of field as 'False' which is a boolean value, which is then used further in a replace function which is only applicable for string values. Hence it gives type error **Fix**: - By passing the null value of string
Original PR description
**Steps**: - Open Project > Task - Add a description > save - Perform 'Action > Restore History' - Observe that the description is set to null - Perform 'Action > Restore History' again **Issue**: - We get a type error and the code crashes **Cause**: - We get the value of field as 'False' which is a boolean value, which is then used further in a replace function which is only applicable for string values. Hence it gives type error **Fix**: - By passing the null value of string instead of a 'False' value we can correct this issue. **Technical Explanation**: - In our case the description field becomes empty and hence the value of self[field_name] is set to 'False'. - The same functionality of 'Restore History' is used in Knowledge. In there, this error doesn't occur because for that, the body will never be empty as a default `<br>` is given with when it will not have any value. **Task**-3731400 Forward-Port-Of: odoo/odoo#153582
Before this commit, the POS receipt was added to the bottom of the page after printing. In some browsers, this caused overflow and made the POS interface scrollable. With this commit, we fix this issue by changing the position of the receipt container to 'fixed'. This prevents the receipt from affecting the layout of the page after printing, thus avoiding the overflow issue and keeping the POS interface non-scrollable. opw-3775808 --- I confirm I have signed the CLA and read the PR g
Original PR description
Before this commit, the POS receipt was added to the bottom of the page after printing. In some browsers, this caused overflow and made the POS interface scrollable. With this commit, we fix this issue by changing the position of the receipt container to 'fixed'. This prevents the receipt from affecting the layout of the page after printing, thus avoiding the overflow issue and keeping the POS interface non-scrollable. opw-3775808 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#156025
Office National de Sécurité Sociale (ONNS) should be (ONSS). Forward-Port-Of: odoo/odoo#155828
Original PR description
Office National de Sécurité Sociale (ONNS) should be (ONSS). Forward-Port-Of: odoo/odoo#155828
-User might not know what they going to type in, this commit add a placeholder in the input of industry selection to give a hint for user when in website creation Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#155862
Original PR description
-User might not know what they going to type in, this commit add a placeholder in the input of industry selection to give a hint for user when in website creation Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#155862
Before this commit, since 8df2e440 to avoid fetching the last validated timesheet date when the sample data is displayed, when the user changes the range of the grid view or remove a default filter and get some data. A traceback is occured because `lastValidationDatePerEmployee` is undefined. That attribute in timesheet grid renderer is indeed undefined since we did not fetch the data to populate that attribute. This commit makes sure to fetch the last validated timesheet data once the user l
Original PR description
Before this commit, since 8df2e440 to avoid fetching the last validated timesheet date when the sample data is displayed, when the user changes the range of the grid view or remove a default filter and get some data. A traceback is occured because `lastValidationDatePerEmployee` is undefined. That attribute in timesheet grid renderer is indeed undefined since we did not fetch the data to populate that attribute. This commit makes sure to fetch the last validated timesheet data once the user leaves the sample data. X-original-commit: 8df2e440 Forward-Port-Of: odoo/enterprise#57642 Forward-Port-Of: odoo/enterprise#57535