Merge account_analytic_default into account Merge account_analytic_default_hr_expense into hr Merge account_analytic_default_purchase into purchase Prevent having to manually install default modules after activating analytics closes odoo/odoo#50816 Task: 2182900 Related: odoo/upgrade#1186 Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com>
The purpose of task is to update the 'user/employee avatar' to the new widget in all the kanban view across all modules. The below new widget are introduced for avatar: - many2one_avatar_user (for user_id fields) - many2one_avatar_employee (for employee_id fields) which displays the avatar (i.e. picture) of a user/employee in front of his name and clicking on the avatar will open a chatbox to message that specific user/employee. So in this commit, For each kanban view with a user or employee avatar, replaced it by the field with the new 'many2one_avatar' widget. TaskID: 2244928 Related Enterprise PR: https://github.com/odoo/enterprise/pull/10420 closes odoo/odoo#50789 Closes: #50789 Related: odoo/enterprise#10420 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Impacted modules: account_analytic_default, crm, event, hr_recruitment, maintenance, mass_mailing, project, purchase_requisition, stock_picking_batch, website_slides The default image displayed when the record is unassigned is confusing, so we are removing it. FP request Task 2234524 closes odoo/odoo#49333 Related: odoo/enterprise#9834 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
- open accounts in a full view instead of a modal - ability to reverse entries at their own accounting date - don't create draft closing entries and reminder if no configuration for tax groups - reordered account menus - improved invoice form view Task ID : 2209497 closes odoo/odoo#48355 Related: odoo/upgrade#1001 Related: odoo/enterprise#9485 Signed-off-by: oco-odoo <oco-odoo@users.noreply.github.com>
1/ When the new database is created without demo data, the admin has a 'silhouette' as a default picture. When a new user is created without picture given by the current user, the new user will have a 'silhouette' as a default profile picture. 2/ web: image for fa-user-slash. This image will be used when a record is unassigned. 3/ web, *: Change placeholder by default when record is unassigned. We want to have a fa-user-slash icon when a record is unassigned instead of 'placeholder.png'. A method is created in the BaseModel to have a generic method to change easily the placeholder for other models. 4/ Adapt kanban test to keep the same behaviour. Attention the behaviour is a bit different. Because, now the default image is given by the server to change easily the default image when a record doesn't have an image. Thus, we don't say if it's the default placeholder, but we can say it's not the same image of the record (in this test, the record, it's the partner). 5/ misc: display 'Unassigned' in the hover on kanban cards if record is unassigned closes odoo/odoo#41356 Taskid: 2060206 Related: odoo/enterprise#7758 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com> Co-authored-by: jdoutreloux <jud@odoo.com> Co-authored-by: Yannick Tivisse <yti@odoo.com>
This reverts commit ff1c35513aecef5fbc30f7c2f3834450e719714e. closes odoo/odoo#41480 X-original-commit: 116057b26e71db4692280463669f3e80d813ddcc Related: odoo/enterprise#7110 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
FontAwesome 5 introduced new names for some icons as described on https://fontawesome.com/how-to-use/on-the-web/setup/upgrading-from-version-4#name-changes This commit replaces the old names to the new ones. closes odoo/odoo#35826 Taskid: 2050241 Related: odoo/enterprise#5180 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
There are too many image sizes. Since they are stored resized this takes time to generate when saving a new image, it's more rows on the attachment table, more files on the disk, ... 64px is close enough to 128px that it can be removed without a big impact on download size. It will even reduce download and number of requests when both images are displayed because now only one has to be downloaded and then benefit from cache. The difference between the two is typically around 1.5kB which is negligible these days, especially when the request overhead is around 0.5kB already, not even taking into account other factors such as latency. If a 64px image must absolutely be returned, it is still possible to pass the size parameters to the image route. But the current guideline is to handle resizing in the views when necessary. Views ===== - remove width and height attributes when existing CSS rules are overriding them (eg. `.oe_kanban_avatar` in the right context) - add CSS rules instead of width and height attributes when possible - use `object-fit: cover;` where width and height are forced to avoid distortion of non-square images - for products, use `object-fit: contain;` instead, keep ratio but without crop - add new CSS rules where the expected size was max 64px*64px before due to the image size itself - remove `img-fluid` where using size classes to avoid conflicting rules task-2060865 closes odoo/odoo#36147 Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>
image_original => image_1920 (now resized to 1920) image_big => image_1024 image_large => image_256 image_medium => image_128 image_small => image_64 image replaced by image_1920 (when writing) or by image_1024 (when displaying what was previously the big size) + add new intermediate format: image_512 PR: #34925
The old tree views don't really exist anymore, this odd pseudo-flag to dispatch between "list" and "tree" tree views has no reason to remain. Task 1937686 closes odoo/odoo#31243 Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>