Server Environment for Printing Server
This module allows the configuration of the fields "Address", "Port", "User" and "Password" on Printing Server from server environment.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets administrators store the printing server address, port, user and password in the server environment configuration instead of typing them in Odoo, so connection details can be managed outside the database.
This module connects the printing server feature with Odoo's server environment mechanism. It does not add new screens or menus; instead it changes where the connection details of a printing server come from.
- The printing server record (
printing.server) now also uses the server environment mixin, so four of its fields can be read from the server environment configuration:address,port,userandpassword. - Administrators can therefore keep the printing server host, port and credentials in the server-side configuration files rather than entering them manually in Odoo.
- This is useful when the same database is deployed on several environments (for example test and production) with different printing servers, since each environment can supply its own values.
- No new menus, buttons, reports, checks or scheduled actions are added by this module; it only extends the existing printing server model.
It depends on the printing server module and on the server environment module, so both must be installed for it to work.
Depends on
Models and fields (1)
- printing.server · new model
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/report-print-send.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.