Friday, June 16, 2023
15 changes · master
New functionality added to Odoo
Users can now type an exact font size directly in the editor toolbar while still seeing the recommended size list. This makes content formatting more flexible and also includes small toolbar fixes to keep editing controls working smoothly and avoid sidebar overflow.
Original PR description
With this commit, when a user clicks on the font size number in the editor's toolbar, two things happen: 1. Same as before: the list of recommended sizes opens. 2. The current font size is selected, and the user can type any value they want. They need to confirm with "Enter" to use a custom value. task-3167041 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
The project task calendar now shows a cleaner popover by hiding empty fields and rearranging task details for easier reading. Task calendar filters were also renamed for consistency with other task views, helping users understand options more quickly.
Original PR description
In this PR we are making the popover look less cluttered by hiding fields when they don't have any value and moving fields around in task calendar popover and rename some task filters to be consistent with the terminology used in the other views task. task-3214107
Resolved issues and error corrections
This fix ensures the Indian sales and purchase stock localization modules are correctly tied to the stock-related apps they rely on. If those stock apps are removed, the related Indian localization modules are removed too, preventing server errors when users open sales or purchase records.
Original PR description
* l10n_in_purchase_stock, l10n_in_sale_stock before this commit, if sale_stock or purchase_stock module was uninstalled from db manually, exception will be shown for the users. * create a db with…
Point of Sale restaurant users can now access the Floor Plans configuration link without enabling debug mode, making setup and adjustments easier. The Point of Sale dashboard buttons are also realigned when self-order is configured, improving the dashboard experience.
Original PR description
[IMP] pos_restaurant: Enable Floor Plans Link The link to the `Floor Plans` configuration is only visible in debug mode. This makes for a bad user experience. This PR makes it so the link is always visible to `pos users`, regardless of whether or not the user is in debug mode. [IMP] point_of_sale: Align dashboard buttons When a `pos` is configured as `self order`, the dashboard buttons become misaligned. This PR brings back the buttons into alignment. Task 3357989 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Learners who leave a course can now rejoin later without losing completed lessons or progress. This improves the learning experience and prevents users from repeatedly earning rewards by leaving and retaking the same quiz, while failed certification surveys still require a full retake.
Original PR description
…ing course PURPOSE Before this commit when a user left a course, his progress was lost and he had to retake the whole course from the start. It also allowed people from gaining karma easily by leaving the course and taking the quiz again and again. After this commit the user will keep his progress event after leaving the course and rejoining it later. SPECIFICATION When leaving the course the corresponding 'slide.channel.partner' record is deleted but the 'slide.slide.partner' records are kept unchanged. So when joining the course, a new 'slide.channel.partner' is created again. On the other hand, after failing a survey all the records are deleted so the user has to retake the whole certification course. LINKS Task ID : 2199207 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The self-ordering flow has been reorganized to make orders easier to manage and safer to process. Prices are now calculated on the server, duplicate unchanged submissions are prevented, and customers can receive real-time updates when an order is paid in the restaurant point of sale.
Original PR description
General refactoring of the codebase. Inline of certain components that had no logic in the JS side, the XML of these components was directly added to the place where they were called. Simplification…
General refactoring of the codebase. Inline of certain components that had no logic in the JS side, the XML of these components was directly added to the place where they were called. Simplification of the python controller, inline of many functions and separation of the logic. There is now one function that manages new orders and another that manages and updates existing orders if we are in "pay after meal" mode. In "pay after each" mode, orders cannot be edited. Addition of different models, product, order and orderlines in order to facilitate the use of these objects between the backend and the frontend. Added price calculation on the serverside because we can't trust the data coming from the customer in the self since no identification is required. Management of last change sent added. Thanks to this, users will no longer be able to click on the order button if no changes have been made to the order. Addition of a websocket to receive real-time notifications when an order is paid for from the PoS and not from the self. We then inform the self that the order has been validated and paid for.
Learners who leave an eLearning course now keep their progress if they rejoin later, preventing them from having to restart from scratch. Course managers can choose whether to archive a learner's progress for later recovery or delete it entirely, including related karma gains.
Original PR description
…rse progress PURPOSE Before this commit, when a user left a course, all his progress was lost and he had to retake the whole course from the beginning. The karma gained weren't lost thus gaining karma by retaking the quizzes was possible. After this commit, when a user join a course after leaving it he will keep his progress and all the karma he gained. SPECIFICATION When a user leaves a course by himself the corresponding slide.channel.partner is archived and thus all his progress is kept in database in case he joins the course again. The responsible can either delete an attendee's progress and thus remove all the karma gained from it or he can archive the attendee's progress by archiving it. LINK Task ID : 2199207 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Calendar invitation emails now present event information more clearly, including a bold event name, improved button placement, better detail ordering, and clearer organizer labeling. Attendees also receive updates when key details like location or description change, helping reduce confusion around event changes.
Original PR description
The Purpose of this task is to make improvements in the email invitation template which sends invite for an event in calendar. By this commit following changes are made: -Event name is set to bold -Position of the accept / decline / view buttons is changed -Alignment of the bullet points is changed -Event name is displayed in the header -End date of the event is displayed if the event spans across multiple days -"Organizer" is indicated beside the name of the user assigned to the event -Text for the date-update mail is updated -Details of the events is reordered -Email is sent when location is updated -Email is sent when description is updated -End hour of the event is displayed if the event is not for all day TaskID:2350291 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website editors can now set alternate content to appear when visitors hover over selected page elements. This makes it easier to create interactive page sections while keeping both the original and hover content editable in the website builder.
Original PR description
Add an option in the editor to activate custom content when hovering specific elements. Using this option adds an invisible overlay on top of the original element that will only be shown to the visitor when hovering the original element.
In edit mode the hovering behavior is deactivated, so both the original and the overlay content can be properly edited. A button is provided that allows the end user to quickly toggle between the original and overlay content. The hovering overlay is also added as an invisible snippet entry in the corresponding menu.Large online courses now automatically expand the learner's current section and collapse unrelated sections, making course pages easier to navigate. Completed sections stay open as learners progress, while returning learners are taken back to the section they are currently working on.
Original PR description
Purpose ======= Improve the behavior of the collapse/expand categories in front-end for large courses. Specifications ============== In channel content view and channel fullscreen view: - When following the course, expand the ongoing section and collapse the other ones. - When the section is completed, open the next one and keep the previous one(s) opened. - If an attendee leaves and comes back, only open the ongoing one. Task-3284195 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website editors can now choose whether decorative background shapes appear on mobile pages. Shapes remain hidden by default when added from desktop to preserve small-screen readability, but are shown by default when added while editing on mobile.
Original PR description
[IMP] web_editor: toggle background shape on mobile Currently, all background shapes of snippets are hidden on mobile, because most of them don't look great on small screens. This commit adds a button in the website editor to toggle the shape on mobile. It remains hidden by default if added on desktop, but displayed by default if added on mobile. task-3096132
India payroll now captures ESIC amount and leave allowance directly on employee contracts. It also adds salary rules for gratuity and expenses, helping payroll teams calculate common India-specific components more accurately and consistently.
Original PR description
Add Field on Contract - ESIC amount - Leave Allowance Add Salary rule - Gratuity - Expense task-3328392
Helpdesk ticket buttons now show all related tickets while opening with an open-ticket filter by default, making ticket review easier. Tag creation is streamlined by removing unnecessary create/edit options and allowing duplicate tag names by automatically adding “(copy)”, while customer preview is moved to the header where it better fits.
Original PR description
Improve the following generic UX - Earlier in the ticket stat button shows the total tickets and open tickets now this is changed with it will show all tickets and when we open tickets through the stat button we have default filter of open tickets as this will help users to review tickets easily - create and edit earlier was present when we try to create a tag but we have removed it because it was of no use while creating a tag - earlier in the helpdesk when we create a tag of the same name we got the error which states "A tag with the same name already exists" This is changed with (copy) will add at the end of the tag when we create a tag of the same name that already exists - earlier 'customer preview' was a stat button but it does not really provide any stat so moved it to the header task-3251728
Customers now see clear alerts in the portal when a subscription payment is still pending. This reassures them that their payment attempt was recorded, shows when it started, and prevents duplicate payment attempts while confirmation is in progress.
Original PR description
Before this commit, when a customer had payed a subscription with a method that was not instantly confirmed (pending), it wasn't shown any information about the payment that was just made when going back to the subscription. Now, it is shown an alert informing about the date when the pending payment was started and another alert notifying that there is a pending payment (while hiding the payment form). Task-id: 2848272
* l10n_in_purchase_stock, l10n_in_sale_stock before this commit, if sale_stock or purchase_stock module was uninstalled from db manually, exception will be shown for the users. * create a db with selecting country as india for l10n_in_sale_stock: * install sale and stock module in the db * sale_stock and l10_in_sale_stock will get installed in the db * now uninstall sale_stock module, user will receive 500 internal server error as the l10_in_sale_stock didn't get uninstalled and depends on warehouse_id field from sale_stock module * in l10n_in_sale_stock module, _compute_l10n_in_journal_id function is depending on the field warehouse_id which is added from the sale_stock module Exception: ValueError: Wrong @Depends on _compute_l10n_in_journal_id (compute method of field sale.order.l10n_in_journal_id). Dependency field warehouse_id not found in model sale.order. for l10n_in_purchase_stock: * in fresh db, install purchase and stock module * purchase_stock, l10n_in_purchase_stock will get installed automatically * now uninstall purchase_stock module and try to open the purchase order form,user will get exception * l10_in_purchase_stock module is still installed and depending on a field picking_type_id from purchase_stock module * onchange function l10n_in_onchange_company_id isdepending and using field picking_type_id which is added from purchase_stock module Exception:AttributeError: purchase.order object has no attribute picking_type_id after this commit, on uninstalling sale_stock or purchase_stock module from the db will uninstall l10_in_sale_stock, l10_in_purchase_stock modules respectively. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When users open translations from an existing record, Odoo now saves the record automatically before showing the translation window. This prevents confusing mismatches where translated text is saved but the main record still shows an older unsaved value.
Original PR description
- Be sure to have two languages installed; - Open a record with translations (product, for instance); - Modify the field with translation, from "apple" to "peach"; - Open the translation. - Modify…
- Be sure to have two languages installed; - Open a record with translations (product, for instance); - Modify the field with translation, from "apple" to "peach"; - Open the translation. - Modify the English term, from "peach" to "apricot"; - Save; Before this commit, the field on the record still shows "peach", you need to revert the changes to came back to "apricot" (the last modified term). This occurs because the record is not yet saved, but the translation is. This can create confusing behaviors. Note also, that there is a different behavior when clicking on a translation button between new record and existing records. The first one will ask to save the record before doing the translation, contrariwise, the last one will let you modify the translation without saving. In this commit, to avoid all confusion, and to be coherent between new record and existing record, and to be also coherent with the always save policy. We will save the record automatically before opening the translation dialog. part-of task-id 3179751