Maintainers
+Maintainers
Current maintainer:
This module is part of the dhongu/deltatech project on GitHub.
+This module is part of the dhongu/deltatech project on GitHub.
You are welcome to contribute.
| Run cron jobs from webhook
[deltatech_data_sheet](deltatech_data_sheet/) | 19.0.1.0.0 | | Data Sheet
[deltatech_data_sheet_website](deltatech_data_sheet_website/) | 19.0.1.0.0 | | Data Sheet
-[deltatech_dc](deltatech_dc/) | 19.0.1.0.11 | | Print Declaration of Conformity
-[deltatech_delivery_status](deltatech_delivery_status/) | 19.0.2.2.0 | | Carrier status on picking
+[deltatech_dc](deltatech_dc/) | 19.0.1.0.12 | | Print Declaration of Conformity
+[deltatech_delivery_status](deltatech_delivery_status/) | 19.0.2.3.0 | | Carrier status on picking
[deltatech_discount_policy](deltatech_discount_policy/) | 19.0.1.0.0 | 
| Bring back Odoo 17 discount policy
[deltatech_download](deltatech_download/) | 19.0.0.1.2 | | Generare fisier
[deltatech_dropshipping](deltatech_dropshipping/) | 19.0.1.1.0 | | Delivery address in picking
@@ -52,6 +52,7 @@ addon | version | maintainers | summary
[deltatech_followup](deltatech_followup/) | 19.0.0.1.1 | 
| Simple invoice followup, with automatic e-mails
[deltatech_generic_partner_restriction](deltatech_generic_partner_restriction/) | 19.0.2.0.0 | 
| Restrict payment journals for the generic partner
[deltatech_gln](deltatech_gln/) | 19.0.1.0.0 | | Partner Global Location Number
+[deltatech_image_optimize](deltatech_image_optimize/) | 19.0.1.8.1 | | Recompress oversized image attachments to reclaim filestore space
[deltatech_invoice_number](deltatech_invoice_number/) | 19.0.1.0.0 | | Renumbering invoice
[deltatech_invoice_picking](deltatech_invoice_picking/) | 19.0.1.0.10 | | Facturare livrari
[deltatech_invoice_picking_automatically](deltatech_invoice_picking_automatically/) | 19.0.0.0.4 | | Generate invoice automatically from picking after validation
@@ -60,7 +61,7 @@ addon | version | maintainers | summary
[deltatech_invoice_report](deltatech_invoice_report/) | 19.0.1.0.8 | | Invoice Report
[deltatech_invoice_to_draft](deltatech_invoice_to_draft/) | 19.0.2.0.1 | | Restricted access to reset account move to draft
[deltatech_invoice_weight](deltatech_invoice_weight/) | 19.0.1.0.2 | | Invoice Weight
-[deltatech_kit_price](deltatech_kit_price/) | 19.0.0.0.1 | | Compute product cost price in sale order line based on kit
+[deltatech_kit_price](deltatech_kit_price/) | 19.0.0.0.2 | | Compute product cost price in sale order line based on kit
[deltatech_ledger](deltatech_ledger/) | 19.0.0.0.1 | | Deltatech Ledger
[deltatech_line_counter](deltatech_line_counter/) | 19.0.1.0.0 | | Count lines of code in selected modules
[deltatech_list_view](deltatech_list_view/) | 19.0.1.0.1 | | List View Select Text
@@ -80,6 +81,7 @@ addon | version | maintainers | summary
[deltatech_no_quick_create](deltatech_no_quick_create/) | 19.0.2.0.1 | | Disable quick_create
[deltatech_notification_sound](deltatech_notification_sound/) | 19.0.2.0.0 | | Notification Sound
[deltatech_partner_generic](deltatech_partner_generic/) | 19.0.1.0.0 | | Gneric partner
+[deltatech_partner_merge](deltatech_partner_merge/) | 19.0.1.0.0 | | Merge partners duplicated on the same VAT number, in bulk, in minutes instead of hours
[deltatech_payment_forecast](deltatech_payment_forecast/) | 19.0.0.0.1 | | Generates a report to estimate payments at a certain date
[deltatech_payment_term](deltatech_payment_term/) | 19.0.2.0.1 | | Term Rate Wizard
[deltatech_picking_restrict](deltatech_picking_restrict/) | 19.0.1.0.0 | | Restrict picking validation to a certain security group
@@ -88,7 +90,7 @@ addon | version | maintainers | summary
[deltatech_picking_transit](deltatech_picking_transit/) | 19.0.0.0.9 | | Automate internal transfer from transit location
[deltatech_pos_fix](deltatech_pos_fix/) | 19.0.1.0.0 | | Fix POS total calculation when using tax-included fiscal position mapping
[deltatech_pos_product_filter](deltatech_pos_product_filter/) | 19.0.1.0.0 | | Searching pos order using product
-[deltatech_pos_stock](deltatech_pos_stock/) | 19.0.1.0.0 | | Display stock in POS
+[deltatech_pos_stock](deltatech_pos_stock/) | 19.0.1.1.0 | | Display stock in POS
[deltatech_price_categ](deltatech_price_categ/) | 19.0.1.0.1 | | Price List: Bronze Silver and Gold in product
[deltatech_pricelist](deltatech_pricelist/) | 19.0.1.0.0 | | Price list currency
[deltatech_pricelist_line_viewer](deltatech_pricelist_line_viewer/) | 19.0.0.0.2 | | Creates a list view for the lines of a price list for search and management
@@ -101,22 +103,23 @@ addon | version | maintainers | summary
[deltatech_product_labels](deltatech_product_labels/) | 19.0.1.1.4 | | Print Labels on Products
[deltatech_product_list](deltatech_product_list/) | 19.0.1.0.1 | | Define products lists
[deltatech_product_mpn](deltatech_product_mpn/) | 19.0.0.0.1 | | Add MPN to product
+[deltatech_product_reordering_limit](deltatech_product_reordering_limit/) | 19.0.1.0.2 | | Custom reordering limits for products
[deltatech_product_trade_markup](deltatech_product_trade_markup/) | 19.0.1.0.1 | | Product trade markup
[deltatech_product_unique_code](deltatech_product_unique_code/) | 19.0.1.0.0 | | Restrict duplicate default_code and barcode including archived products
[deltatech_product_visibility](deltatech_product_visibility/) | 19.0.1.0.0 | | Scor colorat de vizibilitate a produsului pe website (semafor + defalcare pe criterii)
[deltatech_project_price_list](deltatech_project_price_list/) | 19.0.1.0.0 | | Project-level pricelist used when creating Sales Orders from a project
[deltatech_promissory_note](deltatech_promissory_note/) | 19.0.1.0.3 | | Manage Promissory Note
-[deltatech_purchase_add_extra_line](deltatech_purchase_add_extra_line/) | 19.0.1.2.0 | | Purchase Add Extra Line
+[deltatech_purchase_add_extra_line](deltatech_purchase_add_extra_line/) | 19.0.1.3.0 | | Purchase Add Extra Line
[deltatech_purchase_create_bill_button](deltatech_purchase_create_bill_button/) | 19.0.1.0.0 | | Restores the one-click Create Bill button and vendor reference copy on the purchase order form
[deltatech_purchase_mail](deltatech_purchase_mail/) | 19.0.1.1.0 | | Select multiple purchase orders and send an email with XLSX summary and attached PDFs
[deltatech_purchase_phase](deltatech_purchase_phase/) | 19.0.1.2.6 | | Purchase Order Stage
[deltatech_purchase_picking_status](deltatech_purchase_picking_status/) | 19.0.1.0.1 | | Get purchase status from pickings
[deltatech_purchase_price](deltatech_purchase_price/) | 19.0.1.2.8 | | Update vendor price after reception
[deltatech_purchase_stock](deltatech_purchase_stock/) | 19.0.1.0.1 | | Purchase Stock
-[deltatech_purchase_ubl](deltatech_purchase_ubl/) | 19.0.1.2.2 | | Import UBL XML vendor invoices to update prices, validate receipts, and create vendor bills
+[deltatech_purchase_ubl](deltatech_purchase_ubl/) | 19.0.1.2.4 | | Import UBL XML vendor invoices to update prices, validate receipts, and create vendor bills
[deltatech_purchase_xls](deltatech_purchase_xls/) | 19.0.1.0.0 | | Import/export purchase line from/to Excel
[deltatech_putaway_strategy](deltatech_putaway_strategy/) | 19.0.1.0.7 | | Location capacities and enhanced putaway strategy for Inventory
-[deltatech_queue_job](deltatech_queue_job/) | 19.0.1.3.0 | | Deltatech Queue Job
+[deltatech_queue_job](deltatech_queue_job/) | 19.0.1.4.0 | | Deltatech Queue Job
[deltatech_ral](deltatech_ral/) | 19.0.1.0.4 | | RAL
[deltatech_reception_note](deltatech_reception_note/) | 19.0.0.1.2 | | Batch reception note
[deltatech_record_type](deltatech_record_type/) | 19.0.1.1.12 | | Manage multiple record types
@@ -125,21 +128,21 @@ addon | version | maintainers | summary
[deltatech_report_prn](deltatech_report_prn/) | 19.0.1.1.0 | | Raport PRN
[deltatech_restrict_reports](deltatech_restrict_reports/) | 19.0.1.0.0 | | Restrict Sales Analysis and Invoice Analysis reports by group: own records, all records, or no access.
[deltatech_rpc_audit](deltatech_rpc_audit/) | 19.0.1.2.0 | | Log XML-RPC / JSON-RPC calls with the real client IP
-[deltatech_sale_activity_report](deltatech_sale_activity_report/) | 19.0.1.0.0 | | Adds a last modified field to the sale order
+[deltatech_sale_activity_report](deltatech_sale_activity_report/) | 19.0.1.1.0 | | Adds a last modified field to the sale order
[deltatech_sale_activity_search](deltatech_sale_activity_search/) | 19.0.0.0.0 | | Adds a field with the active activity types on that sale order
[deltatech_sale_add_extra_line](deltatech_sale_add_extra_line/) | 19.0.1.4.0 | | Sale Add Extra Line
[deltatech_sale_add_extra_line_pos](deltatech_sale_add_extra_line_pos/) | 19.0.1.0.0 | | POS Add Extra Line
[deltatech_sale_analysis_vat](deltatech_sale_analysis_vat/) | 19.0.1.0.1 | | VAT rate dimension in Invoice Analysis and Point of Sale Analysis
-[deltatech_sale_commission](deltatech_sale_commission/) | 19.0.1.4.5 | | Compute sale commission
+[deltatech_sale_commission](deltatech_sale_commission/) | 19.0.1.5.0 | | Compute sale commission
[deltatech_sale_contact](deltatech_sale_contact/) | 19.0.1.0.21 | | Limit contacts insale order
[deltatech_sale_cost_product](deltatech_sale_cost_product/) | 19.0.0.0.2 | | Sale Cost on Order
[deltatech_sale_currency](deltatech_sale_currency/) | 19.0.0.0.0 | | This module allows you to manage sales orders in a different currency than the invoice currency.
[deltatech_sale_feedback](deltatech_sale_feedback/) | 19.0.1.0.5 | | Sale Feedback
[deltatech_sale_invoice_status](deltatech_sale_invoice_status/) | 19.0.0.0.1 | | Sale Invoice Status will not be To Be Invoiced if services present and products are not delivered
-[deltatech_sale_margin](deltatech_sale_margin/) | 19.0.1.1.1 | | Check price in sale order
+[deltatech_sale_margin](deltatech_sale_margin/) | 19.0.1.2.0 | | Check price in sale order
[deltatech_sale_multiple](deltatech_sale_multiple/) | 19.0.1.1.1 | | Sale quantity multiple
[deltatech_sale_multiple_website](deltatech_sale_multiple_website/) | 19.0.1.1.0 | | Enforce product quantity multiples in eCommerce
-[deltatech_sale_pallet](deltatech_sale_pallet/) | 19.0.1.0.8 | | Sale pallet
+[deltatech_sale_pallet](deltatech_sale_pallet/) | 19.0.1.0.9 | | Sale pallet
[deltatech_sale_pallet_website](deltatech_sale_pallet_website/) | 19.0.1.0.0 | | Sale pallet
[deltatech_sale_payment](deltatech_sale_payment/) | 19.0.1.1.4 | | Payment button in sale order
[deltatech_sale_phone](deltatech_sale_phone/) | 19.0.1.0.2 | | Show partner phone in sale order
@@ -151,7 +154,7 @@ addon | version | maintainers | summary
[deltatech_sale_return_cause](deltatech_sale_return_cause/) | 19.0.0.0.8 | | Return Cause
[deltatech_sale_stage](deltatech_sale_stage/) | 19.0.1.2.5 | | Sale Order Stage
[deltatech_sale_team](deltatech_sale_team/) | 19.0.1.0.2 | | Sale Team Access
-[deltatech_sale_xls](deltatech_sale_xls/) | 19.0.1.0.0 | | Import/export sale line from/to Excel
+[deltatech_sale_xls](deltatech_sale_xls/) | 19.0.1.0.1 | | Import/export sale line from/to Excel
[deltatech_saleorder_pickup_list](deltatech_saleorder_pickup_list/) | 19.0.1.0.0 | | Pickup list report from sale order
[deltatech_saleorder_search](deltatech_saleorder_search/) | 19.0.1.0.2 | | Search sale order by partner e-mail, phone
[deltatech_secondary_uom](deltatech_secondary_uom/) | 19.0.1.1.0 | | Product specific conversion factors between units of measure (SAP MARM style)
@@ -161,16 +164,16 @@ addon | version | maintainers | summary
[deltatech_stock_close](deltatech_stock_close/) | 19.0.1.1.0 | | Close stock operations at date
[deltatech_stock_count_zero](deltatech_stock_count_zero/) | 19.0.0.0.0 | | Set inventory line to 0 when empty count is requested
[deltatech_stock_delivery](deltatech_stock_delivery/) | 19.0.1.0.0 | | Adding button in invoice for display reception or delivery
-[deltatech_stock_inventory](deltatech_stock_inventory/) | 19.0.2.7.2 | | Inventory Old Method
+[deltatech_stock_inventory](deltatech_stock_inventory/) | 19.0.2.7.3 | | Inventory Old Method
[deltatech_stock_inventory_product_display](deltatech_stock_inventory_product_display/) | 19.0.0.0.0 | | Adds product display button on sales and invoices to see the stock of the products in the order
[deltatech_stock_negative](deltatech_stock_negative/) | 19.0.2.0.7 | | Negative stocks are not allowed
-[deltatech_stock_picking_activity_report](deltatech_stock_picking_activity_report/) | 19.0.1.0.0 | | Tracks activities and changes on stock pickings
+[deltatech_stock_picking_activity_report](deltatech_stock_picking_activity_report/) | 19.0.1.1.0 | | Tracks activities and changes on stock pickings
[deltatech_stock_removal_priority](deltatech_stock_removal_priority/) | 19.0.1.0.0 | | Stock Removal Location by Priority
[deltatech_stock_report](deltatech_stock_report/) | 19.0.1.0.4 | | Report with positions from picking lists
[deltatech_stock_reseller](deltatech_stock_reseller/) | 19.0.1.0.2 | | Report report reseller
-[deltatech_tc](deltatech_tc/) | 19.0.1.1.0 | | Base for Terrabit Connect: station registry, outbound job queue, REST endpoints (X-Station-Key) and HTTP calls into the customer's local network.
+[deltatech_tc](deltatech_tc/) | 19.0.1.1.1 | | Base for Terrabit Connect: station registry, outbound job queue, REST endpoints (X-Station-Key) and HTTP calls into the customer's local network.
[deltatech_team_logo](deltatech_team_logo/) | 19.0.1.0.0 | | Logo de firmă în rapoarte în funcție de echipa de vânzare
-[deltatech_test_system](deltatech_test_system/) | 19.0.0.0.8 | | Set system status: test or production
+[deltatech_test_system](deltatech_test_system/) | 19.0.0.0.9 | | Set system status: test or production
[deltatech_transport_change](deltatech_transport_change/) | 19.0.0.1.4 | | Export configuration changes to CSV and manage transport through Git
[deltatech_vendor_stock](deltatech_vendor_stock/) | 19.0.1.1.8 | | Vendor stock availability
[deltatech_warehouse_arrangement](deltatech_warehouse_arrangement/) | 19.0.0.1.2 | | Manages warehouse locations, parallel to standard Odoo locations
@@ -197,6 +200,7 @@ addon | version | maintainers | summary
[deltatech_website_sale_portal](deltatech_website_sale_portal/) | 19.0.1.0.1 | | eCommerce Portal extension
[deltatech_website_sale_sort](deltatech_website_sale_sort/) | 19.0.1.0.2 | | Additional sorting criteria
[deltatech_website_sale_status](deltatech_website_sale_status/) | 19.0.2.0.5 | | Additional filters sales orders by status
+[deltatech_website_searchbar](deltatech_website_searchbar/) | 19.0.1.0.0 | | Reduce autocomplete requests by increasing debounce and adding minimum term length
[deltatech_website_short_description](deltatech_website_short_description/) | 19.0.1.0.3 | | eCommerce short description
[deltatech_website_stock_availability](deltatech_website_stock_availability/) | 19.0.1.0.9 | | eCommerce Stock Availability and lead time
[deltatech_website_vat_validation](deltatech_website_vat_validation/) | 19.0.0.0.1 | | VAT Validation
diff --git a/deltatech_dc/README.rst b/deltatech_dc/README.rst
index 045cde54c..5f176873e 100644
--- a/deltatech_dc/README.rst
+++ b/deltatech_dc/README.rst
@@ -29,6 +29,22 @@ Declaration of Conformity
.. contents::
:local:
+Changelog
+=========
+
+Changelog
+=========
+
+19.0.1.0.12 (2026-08-15)
+------------------------
+
+- Fix: added the missing ``stock_account`` dependency.
+ ``report/report_dc.py`` calls
+ ``account.move._get_invoiced_lot_values()``, which is defined in
+ ``stock_account`` (and extended by ``sale_stock``). The module only
+ worked when another addon in the same database pulled
+ ``stock_account`` in.
+
Bug Tracker
===========
diff --git a/deltatech_dc/static/description/index.html b/deltatech_dc/static/description/index.html
index 4a26c11b2..34e4f266c 100644
--- a/deltatech_dc/static/description/index.html
+++ b/deltatech_dc/static/description/index.html
@@ -8,10 +8,11 @@
/*
:Author: David Goodger (goodger@python.org)
-:Id: $Id: html4css1.css 8954 2022-01-20 10:10:25Z milde $
+:Id: $Id: html4css1.css 9511 2024-01-13 09:50:07Z milde $
:Copyright: This stylesheet has been placed in the public domain.
Default cascading style sheet for the HTML output of Docutils.
+Despite the name, some widely supported CSS2 features are used.
See https://docutils.sourceforge.io/docs/howto/html-stylesheets.html for how to
customize this style sheet.
@@ -274,7 +275,7 @@
margin-left: 2em ;
margin-right: 2em }
-pre.code .ln { color: grey; } /* line numbers */
+pre.code .ln { color: gray; } /* line numbers */
pre.code, code { background-color: #eeeeee }
pre.code .comment, code .comment { color: #5C6576 }
pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
@@ -300,7 +301,7 @@
span.pre {
white-space: pre }
-span.problematic {
+span.problematic, pre.problematic {
color: red }
span.section-subtitle {
diff --git a/deltatech_delivery_status/README.rst b/deltatech_delivery_status/README.rst
index fadab032c..c75c43ef9 100644
--- a/deltatech_delivery_status/README.rst
+++ b/deltatech_delivery_status/README.rst
@@ -118,6 +118,25 @@ and payment processes.
Changelog
=========
+19.0.2.3.0
+==========
+
+- Comenzile cu livrarea amânată pot fi acum **găsite**: filtru „Livrare
+ amânată" în căutarea comenzilor de vânzare și „Amânată" în căutarea
+ transferurilor. Fără ele, un flux care cere eliberare manuală era
+ practic imposibil de operat — butonul „Eliberează" apare doar pe
+ comanda deschisă, iar comenzile care așteptau nu erau vizibile
+ nicăieri.
+- ``sale.order.postponed_delivery`` devine **căutabil** (metodă
+ ``search`` care se traduce în ``picking_ids.postponed``, câmp stocat).
+ Fiind calculat și nestocat, nu putea fi folosit în niciun domeniu —
+ nici în filtre predefinite, nici în filtre personalizate create de
+ utilizator din interfață.
+- Acțiunile server „Postpone Delivery" / „Release Delivery" au acum
+ ``binding_model_id``, deci apar în meniul *Acțiuni* și permit operarea
+ **în masă** din lista de comenzi, nu doar una câte una.
+- Test nou pentru căutarea pe ``postponed_delivery`` (inclusiv negarea).
+
19.0.2.2.0 (2026-08-04)
-----------------------
diff --git a/deltatech_delivery_status/static/description/index.html b/deltatech_delivery_status/static/description/index.html
index 7a315ca36..f98e2cf5f 100644
--- a/deltatech_delivery_status/static/description/index.html
+++ b/deltatech_delivery_status/static/description/index.html
@@ -8,10 +8,11 @@
/*
:Author: David Goodger (goodger@python.org)
-:Id: $Id: html4css1.css 8954 2022-01-20 10:10:25Z milde $
+:Id: $Id: html4css1.css 9511 2024-01-13 09:50:07Z milde $
:Copyright: This stylesheet has been placed in the public domain.
Default cascading style sheet for the HTML output of Docutils.
+Despite the name, some widely supported CSS2 features are used.
See https://docutils.sourceforge.io/docs/howto/html-stylesheets.html for how to
customize this style sheet.
@@ -274,7 +275,7 @@
margin-left: 2em ;
margin-right: 2em }
-pre.code .ln { color: grey; } /* line numbers */
+pre.code .ln { color: gray; } /* line numbers */
pre.code, code { background-color: #eeeeee }
pre.code .comment, code .comment { color: #5C6576 }
pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
@@ -300,7 +301,7 @@
span.pre {
white-space: pre }
-span.problematic {
+span.problematic, pre.problematic {
color: red }
span.section-subtitle {
diff --git a/deltatech_image_optimize/README.rst b/deltatech_image_optimize/README.rst
index de77f5d02..ca9310389 100644
--- a/deltatech_image_optimize/README.rst
+++ b/deltatech_image_optimize/README.rst
@@ -14,7 +14,7 @@ Image Optimizer
:target: https://odoo-community.org/page/development-status
:alt: Beta
.. |badge2| image:: https://img.shields.io/badge/github-dhongu%2Fdeltatech-lightgray.png?logo=github
- :target: https://github.com/dhongu/deltatech/tree/18.0/deltatech_image_optimize
+ :target: https://github.com/dhongu/deltatech/tree/19.0/deltatech_image_optimize
:alt: dhongu/deltatech
|badge1| |badge2|
@@ -30,7 +30,8 @@ For each targeted image the module:
- downscales it to a maximum side of ``max_dim`` pixels (default 1920);
- re-encodes photos without transparency as progressive **JPEG** at the
configured quality (default 85);
-- keeps images with transparency as optimized **PNG** (alpha preserved);
+- keeps genuinely transparent images as **WebP** (alpha preserved), or
+ as optimized **PNG** when the Pillow build has no WebP encoder;
- skips animated GIFs (never flattens the animation);
- keeps the result only when it is actually smaller.
@@ -43,25 +44,127 @@ skipped on the next run. Because Odoo creates a fresh attachment
whenever an image field is updated, newly uploaded or changed images are
picked up automatically.
+How much space you actually get back
+------------------------------------
+
+The batch methods return two figures, and the difference between them
+matters:
+
++----------------+-----------------------------------------------------+
+| Key | Meaning |
++================+=====================================================+
+| ``freed`` | sum of the per-attachment size difference |
++----------------+-----------------------------------------------------+
+| ``freed_disk`` | only the attachments whose filestore file was |
+| | **not** shared |
++----------------+-----------------------------------------------------+
+
+Odoo stores one file per checksum, so attachments with identical content
+share a single file. Recompressing one of them frees nothing while the
+others still point at the old file. On a catalog that reuses the same
+picture across products, ``freed`` therefore overstates the saving — on
+a real deployment it counted **29 GB** where the disk gave back about
+**4 GB**, because 815 000 image attachments lived in 508 000 files.
+
+Use ``freed_disk`` when you report space. Use ``freed`` only to see how
+much lighter the images themselves got — which is the real win on a
+website, since that is bytes off every page load, regardless of
+deduplication.
+
+To measure the whole database rather than one run:
+
+.. code:: sql
+
+ SELECT pg_size_pretty(sum(sz)) FROM (
+ SELECT DISTINCT ON (checksum) file_size AS sz
+ FROM ir_attachment WHERE res_field IS NOT NULL AND checksum IS NOT NULL
+ ORDER BY checksum, id
+ ) t;
+
+Note also that the filestore grows *before* it shrinks: the new file is
+written while the old one is still referenced, and the space comes back
+only when the filestore GC runs (the scheduled action does it at the end
+of each pass).
+
Configuration
-------------
System Parameters (Settings → Technical → System Parameters):
-+--------------------------------------------+-------------------------------+----------------------+
-| Key | Default | Meaning |
-+============================================+===============================+======================+
-| ``deltatech_image_optimize.quality`` | 85 | JPEG quality (1..95) |
-+--------------------------------------------+-------------------------------+----------------------+
-| ``deltatech_image_optimize.max_dim`` | 1920 | max side in pixels |
-+--------------------------------------------+-------------------------------+----------------------+
-| ``deltatech_image_optimize.min_size`` | 102400 | only images larger |
-| | | than this (bytes) |
-+--------------------------------------------+-------------------------------+----------------------+
-| ``deltatech_image_optimize.batch`` | 1000 | images per cron run |
-+--------------------------------------------+-------------------------------+----------------------+
-| ``deltatech_image_optimize.target_fields`` | image_1920,image_variant_1920 | fields to optimize |
-+--------------------------------------------+-------------------------------+----------------------+
++-----------------------------------------------+------------------------------------------+----------------------+
+| Key | Default | Meaning |
++===============================================+==========================================+======================+
+| ``deltatech_image_optimize.quality`` | 85 | JPEG quality (1..95) |
++-----------------------------------------------+------------------------------------------+----------------------+
+| ``deltatech_image_optimize.max_dim`` | 1920 | max side in pixels |
++-----------------------------------------------+------------------------------------------+----------------------+
+| ``deltatech_image_optimize.min_size`` | 102400 | only images larger |
+| | | than this (bytes) |
++-----------------------------------------------+------------------------------------------+----------------------+
+| ``deltatech_image_optimize.batch`` | 50 | images per cron run |
++-----------------------------------------------+------------------------------------------+----------------------+
+| ``deltatech_image_optimize.flush_every`` | 20 | flush/invalidate the |
+| | | ORM cache every N |
+| | | images |
++-----------------------------------------------+------------------------------------------+----------------------+
+| ``deltatech_image_optimize.target_fields`` | image_1920,image_variant_1920 | original fields to |
+| | | optimize |
++-----------------------------------------------+------------------------------------------+----------------------+
+| ``deltatech_image_optimize.webp_quality`` | 85 | WebP quality for |
+| | | transparent images |
++-----------------------------------------------+------------------------------------------+----------------------+
+| ``deltatech_image_optimize.force_jpeg`` | 0 | ignore alpha, always |
+| | | JPEG — |
+| | | **destructive, see |
+| | | below** |
++-----------------------------------------------+------------------------------------------+----------------------+
+| ``deltatech_image_optimize.variant_fields`` | image_1024,image_512,image_256,image_128 | resized variants to |
+| | | recompress in place |
++-----------------------------------------------+------------------------------------------+----------------------+
+| ``deltatech_image_optimize.variant_quality`` | 85 | quality for |
+| | | re-encoding the |
+| | | variants |
++-----------------------------------------------+------------------------------------------+----------------------+
+| ``deltatech_image_optimize.variant_min_size`` | 20480 | only recompress |
+| | | variants larger than |
+| | | this (bytes) |
++-----------------------------------------------+------------------------------------------+----------------------+
+
+⚠ ``force_jpeg`` is destructive — probe before enabling it
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+``force_jpeg=1`` makes the optimizer ignore the alpha channel entirely.
+JPEG has no transparency, so every transparent area is **flattened to
+black**, and the original is gone: the optimized image is written
+through the record, so the previous attachment no longer exists. There
+is no undo — the images have to be re-imported from wherever they came
+from.
+
+Enable it only on a catalog you have *verified* has no real
+transparency. "The originals are stored elsewhere" is not that
+verification: it covers resolution, not the alpha channel. A catalog
+that looks like solid white product shots can still be a third
+transparent PNGs — this is what happened on a real deployment, where 32%
+of a 40-image sample turned out to have real alpha.
+
+Probe it first, without writing anything (``_dt_image_recompress`` is a
+pure function — it returns the bytes and the chosen format, and touches
+nothing):
+
+.. code:: python
+
+ A = env["ir.attachment"].sudo()
+ counts = {}
+ for att in A.search([("res_field", "in", ["image_1920", "image_variant_1920"]),
+ ("mimetype", "=", "image/png"), ("file_size", ">", 51200)], limit=40):
+ _data, fmt = A._dt_image_recompress(att.raw, 78, 1280, 85, False)
+ counts[fmt] = counts.get(fmt, 0) + 1
+ print(counts) # any WEBP/PNG result = images that force_jpeg would destroy
+
+Every ``WEBP`` or ``PNG`` in that count is an image with real
+transparency. If there is even one, leave ``force_jpeg`` at ``0`` — the
+module already sends opaque images to JPEG on its own, so you lose
+almost nothing by keeping it off.
Scheduled action
----------------
@@ -75,7 +178,7 @@ shell:
.. code:: python
- while env["ir.attachment"]._dt_image_optimize_run(limit=2000)["scanned"]:
+ while env["ir.attachment"]._dt_image_optimize_run(limit=200)["scanned"]:
env.cr.commit()
**Table of contents**
@@ -89,6 +192,175 @@ Changelog
Changelog
=========
+19.0.1.8.1 (2026)
+-----------------
+
+- ``data/ir_cron.xml`` is now ``noupdate="1"``. It was not, so **every
+ module upgrade reapplied ``active = False`` and switched the scheduled
+ action back off**, silently, however long ago someone had enabled it.
+ Seen in production: the cron was enabled one day, an upgrade the next
+ morning disabled it again, and nothing in the logs said so -- it
+ simply never ran. ``ir_config_parameter.xml`` already had the flag,
+ which is why the tuned parameters survived the same upgrade while the
+ cron did not.
+- Existing databases: the flag stops future upgrades from touching the
+ record, but it cannot restore a cron already switched off. Check
+ Settings > Technical > Scheduled Actions after upgrading, and
+ re-enable it if it was on before.
+
+19.0.1.8.0 (2026)
+-----------------
+
+- The batch methods now also return ``freed_disk``, and log it next to
+ ``freed``. ``freed`` sums the per-attachment size difference, which
+ **overstates the saving** whenever the same picture is used on several
+ records: Odoo keeps one file per checksum, so recompressing one
+ attachment frees nothing while the others still reference the old
+ file. On a real deployment the run reported **29 GB** where the disk
+ gave back about **4 GB** -- 815 000 image attachments living in 508
+ 000 files. ``freed_disk`` counts only attachments whose file was not
+ shared, so it is the figure to quote when someone asks how much space
+ this recovers.
+- The check reads ``store_fname`` (indexed, and derived from the
+ checksum) before the write, since writing replaces it.
+- ``readme/DESCRIPTION.md`` explains the difference, gives the SQL to
+ measure real occupancy across the whole database, and notes that the
+ filestore grows before it shrinks -- the space returns only once the
+ GC runs.
+
+19.0.1.7.0 (2026)
+-----------------
+
+- **Transparent images now really become WebP.** They were silently
+ falling back to optimized PNG on most databases.
+ ``odoo/tools/image.py`` runs ``Image.preinit()`` and then sets
+ ``Image._initialized = 2``; preinit registers only
+ BMP/GIF/JPEG/PPM/PNG, and the flag makes Pillow believe ``init()``
+ already ran, so ``save(format="WEBP")`` raises ``KeyError: 'WEBP'``
+ even where Pillow is built with libwebp and ``features.check("webp")``
+ returns True. The module now imports ``PIL.WebPImagePlugin``
+ explicitly, which registers the format — ``Image.init()`` alone does
+ not help, it returns early on ``_initialized >= 2``. Same approach
+ already used by ``deltatech_website_watermark``.
+- ``WEBP_OK`` (a constant computed at import time) is replaced by
+ ``_webp_available()``, resolved on first use and cached. The old
+ constant made the module behave **differently from one database to
+ another**: where another module registering the WebP plugin happened
+ to be imported first, transparent images became WebP; everywhere else
+ the identical code produced PNG, with no error anywhere. Import order
+ is not something a result should depend on.
+- The test suite asks the module for WebP support instead of probing at
+ import, so ``test_transparent_image_becomes_webp`` actually runs. It
+ had been skipping itself with "Pillow build lacks WebP support" — on
+ builds that encode WebP fine.
+
+Impact: on catalogs with real transparency, those images now compress as
+WebP (typically ~70% smaller than the PNG fallback) instead of staying
+nearly uncompressed. No change for opaque images.
+
+19.0.1.6.0 (2026)
+-----------------
+
+- Document that ``force_jpeg`` is **destructive**, in both places where
+ it is read: ``readme/DESCRIPTION.md`` and the comment above the
+ parameter in ``data/ir_config_parameter.xml``. It flattens
+ transparency to black and the original cannot be recovered, because
+ the optimized image is written through the record and the previous
+ attachment is gone.
+- Add a probe snippet that measures how much of a catalog has real
+ transparency *before* the parameter is enabled, using
+ ``_dt_image_recompress`` (a pure function — it returns bytes and
+ format, writes nothing).
+- The rationale is a real deployment: ``force_jpeg=1`` was enabled on a
+ catalog believed to have no transparency, and 32% of a 40-image sample
+ turned out to have real alpha. The first 20 optimized images were
+ destroyed before it was caught.
+- Bring the configuration table in ``DESCRIPTION.md`` up to date: it was
+ missing ``flush_every``, ``force_jpeg``, ``webp_quality`` and the
+ three ``variant_*`` keys, and still advertised the old ``batch``
+ default of 1000. Also state that transparent images go to WebP, with
+ PNG as the fallback when the Pillow build has no WebP encoder.
+
+19.0.1.5.1 (2026)
+-----------------
+
+- Migration to Odoo 19.0. No functional change: the module only relies
+ on stable ``ir.attachment`` API (``raw``, ``res_field``,
+ ``_gc_file_store``) which is unchanged in 19.0.
+- Add the Odoo Apps marketing banner
+ (``static/description/main_screenshot.png``).
+
+18.0.1.5.1 (2025)
+-----------------
+
+- Lower the default/installed ``batch`` from 200-1000 to **50**. On
+ production, a large batch of big/high-resolution images could exceed
+ the cron worker's time/CPU limit; the resulting interrupt looked like
+ a normal per-image failure and left the rest of that batch silently
+ flagged as "processed" without actually being optimized. A small batch
+ keeps each cron run well within limits. If you raise it, verify
+ converted images actually shrank.
+
+18.0.1.5.0 (2025)
+-----------------
+
+- New ``force_jpeg`` parameter: when the catalog images are never really
+ transparent (solid colored background), set it to 1 to ignore the
+ alpha channel and always produce JPEG (max savings, no WebP
+ dependency).
+
+18.0.1.4.0 (2025)
+-----------------
+
+- Transparency is now decided by the *actual* alpha content, not the
+ mode: RGBA/palette images that are effectively opaque go to JPEG (big
+ savings), only genuinely transparent images go to WebP. Palette images
+ are normalized first. This fixes "transparent" PNGs that previously
+ stayed uncompressed.
+- Genuinely transparent images with no WebP support keep an optimized
+ PNG (never flattened to a solid background).
+
+18.0.1.3.0 (2025)
+-----------------
+
+- Images with transparency are now converted to **WebP** (alpha
+ preserved, ~70% smaller than PNG) instead of being kept as PNG. New
+ ``webp_quality`` parameter (default 85).
+- Because Odoo cannot resize WebP, a WebP original is written directly
+ on its attachment (never through the record field, which would
+ regenerate full-size variants); the variants are converted in place
+ separately.
+- Opaque images keep going to JPEG.
+
+18.0.1.2.0 (2025)
+-----------------
+
+- Configurable ``flush_every`` parameter (memory flush/invalidate/gc
+ frequency). Lower it to 2-3 for very high-resolution images (e.g. 20
+ MP) so the cron and batch runs stay within memory on heavy images.
+- ``gc.collect()`` at each flush point.
+- The scheduled action now runs a filestore GC at the end (single writer
+ → can grab the lock), so cron-driven runs actually reclaim disk space.
+
+18.0.1.1.0 (2025)
+-----------------
+
+- Step 2 — recompress the stored resized variants
+ (image_1024/512/256/128) in place (``att.write({'raw': ...})``), at a
+ configurable ``variant_quality``, without resizing and without
+ touching the original (no related write-back).
+- New parameters: ``variant_fields``, ``variant_quality``,
+ ``variant_min_size``.
+- The scheduled action now optimizes originals **and** variants.
+
+18.0.1.0.1 (2025)
+-----------------
+
+- Keep memory flat over large batches: flush and invalidate the ORM
+ cache every 20 images (avoids the worker/shell being killed on big
+ batches).
+- Lower the default batch size to 200.
+
18.0.1.0.0 (2025)
-----------------
@@ -133,6 +405,6 @@ Current maintainer:
|maintainer-dhongu|
-This module is part of the `dhongu/deltatech Recompress oversized image attachments to reclaim filestore space
+
Recompresses oversized original image attachments (image_1920 -and image_variant_1920 by default) to reclaim filestore space.
+Recompresses oversized original image attachments (image_1920
+and image_variant_1920 by default) to reclaim filestore space.
For each targeted image the module:
-max_dim pixels (default 1920);The optimized image is written back through the owning record, so
-Odoo regenerates the resized variants (image_1024/512/256/128) from
+Odoo regenerates the resized variants (image_1024/512/256/128) from
the new, smaller original.
Processed attachments are flagged (deltatech_image_optimized) and +
Processed attachments are flagged (deltatech_image_optimized) and
skipped on the next run. Because Odoo creates a fresh attachment
whenever an image field is updated, newly uploaded or changed images are
picked up automatically.
The batch methods return two figures, and the difference between them +matters:
+| Key | +Meaning | +
|---|---|
freed |
+sum of the per-attachment size difference | +
freed_disk |
+only the attachments whose filestore file was +not shared | +
Odoo stores one file per checksum, so attachments with identical content
+share a single file. Recompressing one of them frees nothing while the
+others still point at the old file. On a catalog that reuses the same
+picture across products, freed therefore overstates the saving — on
+a real deployment it counted 29 GB where the disk gave back about
+4 GB, because 815 000 image attachments lived in 508 000 files.
Use freed_disk when you report space. Use freed only to see how
+much lighter the images themselves got — which is the real win on a
+website, since that is bytes off every page load, regardless of
+deduplication.
To measure the whole database rather than one run:
++SELECT pg_size_pretty(sum(sz)) FROM ( + SELECT DISTINCT ON (checksum) file_size AS sz + FROM ir_attachment WHERE res_field IS NOT NULL AND checksum IS NOT NULL + ORDER BY checksum, id +) t; ++
Note also that the filestore grows before it shrinks: the new file is +written while the old one is still referenced, and the space comes back +only when the filestore GC runs (the scheduled action does it at the end +of each pass).
+System Parameters (Settings → Technical → System Parameters):
| Key | @@ -406,90 +457,153 @@|||
|---|---|---|---|
| deltatech_image_optimize.quality | +|||
deltatech_image_optimize.quality |
85 | JPEG quality (1..95) | |
| deltatech_image_optimize.max_dim | +|||
deltatech_image_optimize.max_dim |
1920 | max side in pixels | |
| deltatech_image_optimize.min_size | +|||
deltatech_image_optimize.min_size |
102400 | only images larger than this (bytes) | |
| deltatech_image_optimize.batch | -1000 | +||
deltatech_image_optimize.batch |
+50 | images per cron run | |
| deltatech_image_optimize.target_fields | +|||
deltatech_image_optimize.flush_every |
+20 | +flush/invalidate the +ORM cache every N +images | +|
deltatech_image_optimize.target_fields |
image_1920,image_variant_1920 | -fields to optimize | +original fields to +optimize | +
deltatech_image_optimize.webp_quality |
+85 | +WebP quality for +transparent images | +|
deltatech_image_optimize.force_jpeg |
+0 | +ignore alpha, always +JPEG — +destructive, see +below | +|
deltatech_image_optimize.variant_fields |
+image_1024,image_512,image_256,image_128 | +resized variants to +recompress in place | +|
deltatech_image_optimize.variant_quality |
+85 | +quality for +re-encoding the +variants | +|
deltatech_image_optimize.variant_min_size |
+20480 | +only recompress +variants larger than +this (bytes) |
force_jpeg is destructive — probe before enabling itforce_jpeg=1 makes the optimizer ignore the alpha channel entirely.
+JPEG has no transparency, so every transparent area is flattened to
+black, and the original is gone: the optimized image is written
+through the record, so the previous attachment no longer exists. There
+is no undo — the images have to be re-imported from wherever they came
+from.
Enable it only on a catalog you have verified has no real +transparency. “The originals are stored elsewhere” is not that +verification: it covers resolution, not the alpha channel. A catalog +that looks like solid white product shots can still be a third +transparent PNGs — this is what happened on a real deployment, where 32% +of a 40-image sample turned out to have real alpha.
+Probe it first, without writing anything (_dt_image_recompress is a
+pure function — it returns the bytes and the chosen format, and touches
+nothing):
+A = env["ir.attachment"].sudo() +counts = {} +for att in A.search([("res_field", "in", ["image_1920", "image_variant_1920"]), + ("mimetype", "=", "image/png"), ("file_size", ">", 51200)], limit=40): + _data, fmt = A._dt_image_recompress(att.raw, 78, 1280, 85, False) + counts[fmt] = counts.get(fmt, 0) + 1 +print(counts) # any WEBP/PNG result = images that force_jpeg would destroy ++
Every WEBP or PNG in that count is an image with real
+transparency. If there is even one, leave force_jpeg at 0 — the
+module already sends opaque images to JPEG on its own, so you lose
+almost nothing by keeping it off.
Image Optimizer: recompress oversized images runs daily. It is +
Image Optimizer: recompress oversized images runs daily. It is
disabled by default — review the configuration, test on staging,
then enable it.
For a large one-time backlog you can loop the batch method from the shell:
-while env["ir.attachment"]._dt_image_optimize_run(limit=2000)["scanned"]: +while env["ir.attachment"]._dt_image_optimize_run(limit=200)["scanned"]: env.cr.commit()-
Table of contents
-Bugs are tracked on Terrabit Issues. In case of trouble, please check there if your issue has already been reported.
Do not contact contributors directly about support or help with technical issues.
Current maintainer:
This module is part of the dhongu/deltatech project on GitHub.
+This module is part of the dhongu/deltatech project on GitHub.
You are welcome to contribute.
+ We are an Odoo partner building apps for the Romanian market (SAGA & WinMentor + export; Romanian accounting localization in progress). Direct support from the team + that built the module.
+ Contact Terrabit → +