diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index dcb8fa92a..46b7eca3c 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-08-10 09:10+0000\n" +"POT-Creation-Date: 2022-03-18 13:48+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -161,8 +161,8 @@ msgstr "" #: ../../content/administration/install/deploy.rst:76 #: ../../content/administration/install/install.rst:325 -#: ../../content/administration/install/install.rst:486 -#: ../../content/administration/install/install.rst:655 +#: ../../content/administration/install/install.rst:488 +#: ../../content/administration/install/install.rst:659 msgid "PostgreSQL" msgstr "" @@ -326,7 +326,7 @@ msgid "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimatio msgstr "" #: ../../content/administration/install/deploy.rst:215 -#: ../../content/administration/install/deploy.rst:370 +#: ../../content/administration/install/deploy.rst:369 msgid "LiveChat" msgstr "" @@ -406,288 +406,288 @@ msgstr "" msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" msgstr "" -#: ../../content/administration/install/deploy.rst:344 +#: ../../content/administration/install/deploy.rst:343 msgid "Odoo as a WSGI Application" msgstr "" -#: ../../content/administration/install/deploy.rst:346 +#: ../../content/administration/install/deploy.rst:345 msgid "It is also possible to mount Odoo as a standard WSGI_ application. Odoo provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. That script should be customized (possibly after copying it from the setup directory) to correctly set the configuration directly in :mod:`odoo.tools.config` rather than through the command-line or a configuration file." msgstr "" -#: ../../content/administration/install/deploy.rst:352 +#: ../../content/administration/install/deploy.rst:351 msgid "However the WSGI server will only expose the main HTTP endpoint for the web client, website and webservice API. Because Odoo does not control the creation of workers anymore it can not setup cron or livechat workers" msgstr "" -#: ../../content/administration/install/deploy.rst:357 +#: ../../content/administration/install/deploy.rst:356 msgid "Cron Workers" msgstr "" -#: ../../content/administration/install/deploy.rst:359 +#: ../../content/administration/install/deploy.rst:358 msgid "To run cron jobs for an Odoo deployment as a WSGI application requires" msgstr "" -#: ../../content/administration/install/deploy.rst:361 +#: ../../content/administration/install/deploy.rst:360 msgid "A classical Odoo (run via ``odoo-bin``)" msgstr "" -#: ../../content/administration/install/deploy.rst:362 +#: ../../content/administration/install/deploy.rst:361 msgid "Connected to the database in which cron jobs have to be run (via :option:`odoo-bin -d`)" msgstr "" -#: ../../content/administration/install/deploy.rst:364 +#: ../../content/administration/install/deploy.rst:363 msgid "Which should not be exposed to the network. To ensure cron runners are not network-accessible, it is possible to disable the built-in HTTP server entirely with :option:`odoo-bin --no-http` or setting ``http_enable = False`` in the configuration file" msgstr "" -#: ../../content/administration/install/deploy.rst:372 +#: ../../content/administration/install/deploy.rst:371 msgid "The second problematic subsystem for WSGI deployments is the LiveChat: where most HTTP connections are relatively short and quickly free up their worker process for the next request, LiveChat require a long-lived connection for each client in order to implement near-real-time notifications." msgstr "" -#: ../../content/administration/install/deploy.rst:377 +#: ../../content/administration/install/deploy.rst:376 msgid "This is in conflict with the process-based worker model, as it will tie up worker processes and prevent new users from accessing the system. However, those long-lived connections do very little and mostly stay parked waiting for notifications." msgstr "" -#: ../../content/administration/install/deploy.rst:382 +#: ../../content/administration/install/deploy.rst:381 msgid "The solutions to support livechat/motifications in a WSGI application are:" msgstr "" -#: ../../content/administration/install/deploy.rst:384 +#: ../../content/administration/install/deploy.rst:383 msgid "Deploy a threaded version of Odoo (instead of a process-based preforking one) and redirect only requests to URLs starting with ``/longpolling/`` to that Odoo, this is the simplest and the longpolling URL can double up as the cron instance." msgstr "" -#: ../../content/administration/install/deploy.rst:388 +#: ../../content/administration/install/deploy.rst:387 msgid "Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting with ``/longpolling/`` to :option:`the longpolling port `." msgstr "" -#: ../../content/administration/install/deploy.rst:393 +#: ../../content/administration/install/deploy.rst:392 msgid "Serving Static Files" msgstr "" -#: ../../content/administration/install/deploy.rst:395 +#: ../../content/administration/install/deploy.rst:394 msgid "For development convenience, Odoo directly serves all static files in its modules. This may not be ideal when it comes to performances, and static files should generally be served by a static HTTP server." msgstr "" -#: ../../content/administration/install/deploy.rst:399 +#: ../../content/administration/install/deploy.rst:398 msgid "Odoo static files live in each module's ``static/`` folder, so static files can be served by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) in the various addons paths." msgstr "" -#: ../../content/administration/install/deploy.rst:403 -#: ../../content/administration/maintain/db_upgrade.rst:196 +#: ../../content/administration/install/deploy.rst:402 +#: ../../content/administration/upgrade/process.rst:138 msgid "Todo" msgstr "" -#: ../../content/administration/install/deploy.rst:403 +#: ../../content/administration/install/deploy.rst:402 msgid "test whether it would be interesting to serve filestored attachments via this, and how (e.g. possibility of mapping ir.attachment id to filestore hash in the database?)" msgstr "" -#: ../../content/administration/install/deploy.rst:410 +#: ../../content/administration/install/deploy.rst:409 msgid "Security" msgstr "" -#: ../../content/administration/install/deploy.rst:412 +#: ../../content/administration/install/deploy.rst:411 msgid "For starters, keep in mind that securing an information system is a continuous process, not a one-shot operation. At any moment, you will only be as secure as the weakest link in your environment." msgstr "" -#: ../../content/administration/install/deploy.rst:416 +#: ../../content/administration/install/deploy.rst:415 msgid "So please do not take this section as the ultimate list of measures that will prevent all security problems. It's only intended as a summary of the first important things you should be sure to include in your security action plan. The rest will come from best security practices for your operating system and distribution, best practices in terms of users, passwords, and access control management, etc." msgstr "" -#: ../../content/administration/install/deploy.rst:422 +#: ../../content/administration/install/deploy.rst:421 msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:" msgstr "" -#: ../../content/administration/install/deploy.rst:425 +#: ../../content/administration/install/deploy.rst:424 msgid "Always set a strong super-admin admin password, and restrict access to the database management pages as soon as the system is set up. See :ref:`db_manager_security`." msgstr "" -#: ../../content/administration/install/deploy.rst:428 +#: ../../content/administration/install/deploy.rst:427 msgid "Choose unique logins and strong passwords for all administrator accounts on all databases. Do not use 'admin' as the login. Do not use those logins for day-to-day operations, only for controlling/managing the installation. *Never* use any default passwords like admin/admin, even for test/staging databases." msgstr "" -#: ../../content/administration/install/deploy.rst:433 +#: ../../content/administration/install/deploy.rst:432 msgid "Do **not** install demo data on internet-facing servers. Databases with demo data contain default logins and passwords that can be used to get into your systems and cause significant trouble, even on staging/dev systems." msgstr "" -#: ../../content/administration/install/deploy.rst:437 +#: ../../content/administration/install/deploy.rst:436 msgid "Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the hostname. See :ref:`db_filter`. You may also use :option:`-d ` to provide your own (comma-separated) list of available databases to filter from, instead of letting the system fetch them all from the database backend." msgstr "" -#: ../../content/administration/install/deploy.rst:444 +#: ../../content/administration/install/deploy.rst:443 msgid "Once your ``db_name`` and ``db_filter`` are configured and only match a single database per hostname, you should set ``list_db`` configuration option to ``False``, to prevent listing databases entirely, and to block access to the database management screens (this is also exposed as the :option:`--no-database-list ` command-line option)" msgstr "" -#: ../../content/administration/install/deploy.rst:450 +#: ../../content/administration/install/deploy.rst:449 msgid "Make sure the PostgreSQL user (:option:`--db_user `) is *not* a super-user, and that your databases are owned by a different user. For example they could be owned by the ``postgres`` super-user if you are using a dedicated non-privileged ``db_user``. See also :ref:`setup/deploy/odoo`." msgstr "" -#: ../../content/administration/install/deploy.rst:455 +#: ../../content/administration/install/deploy.rst:454 msgid "Keep installations updated by regularly installing the latest builds, either via GitHub or by downloading the latest version from https://www.odoo.com/page/download or http://nightly.odoo.com" msgstr "" -#: ../../content/administration/install/deploy.rst:459 +#: ../../content/administration/install/deploy.rst:458 msgid "Configure your server in multi-process mode with proper limits matching your typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." msgstr "" -#: ../../content/administration/install/deploy.rst:462 +#: ../../content/administration/install/deploy.rst:461 msgid "Run Odoo behind a web server providing HTTPS termination with a valid SSL certificate, in order to prevent eavesdropping on cleartext communications. SSL certificates are cheap, and many free options exist. Configure the web proxy to limit the size of requests, set appropriate timeouts, and then enable the :option:`proxy mode ` option. See also :ref:`https_proxy`." msgstr "" -#: ../../content/administration/install/deploy.rst:469 +#: ../../content/administration/install/deploy.rst:468 msgid "If you need to allow remote SSH access to your servers, make sure to set a strong password for **all** accounts, not just `root`. It is strongly recommended to entirely disable password-based authentication, and only allow public key authentication. Also consider restricting access via a VPN, allowing only trusted IPs in the firewall, and/or running a brute-force detection system such as `fail2ban` or equivalent." msgstr "" -#: ../../content/administration/install/deploy.rst:475 +#: ../../content/administration/install/deploy.rst:474 msgid "Consider installing appropriate rate-limiting on your proxy or firewall, to prevent brute-force attacks and denial of service attacks. See also :ref:`login_brute_force` for specific measures." msgstr "" -#: ../../content/administration/install/deploy.rst:479 +#: ../../content/administration/install/deploy.rst:478 msgid "Many network providers provide automatic mitigation for Distributed Denial of Service attacks (DDOS), but this is often an optional service, so you should consult with them." msgstr "" -#: ../../content/administration/install/deploy.rst:483 +#: ../../content/administration/install/deploy.rst:482 msgid "Whenever possible, host your public-facing demo/test/staging instances on different machines than the production ones. And apply the same security precautions as for production." msgstr "" -#: ../../content/administration/install/deploy.rst:487 +#: ../../content/administration/install/deploy.rst:486 msgid "If your public-facing Odoo server has access to sensitive internal network resources or services (e.g. via a private VLAN), implement appropriate firewall rules to protect those internal resources. This will ensure that the Odoo server cannot be used accidentally (or as a result of malicious user actions) to access or disrupt those internal resources. Typically this can be done by applying an outbound default DENY rule on the firewall, then only explicitly authorizing access to internal resources that the Odoo server needs to access. `Systemd IP traffic access control `_ may also be useful to implement per-process network access control." msgstr "" -#: ../../content/administration/install/deploy.rst:498 +#: ../../content/administration/install/deploy.rst:497 msgid "If your public-facing Odoo server is behind a Web Application Firewall, a load-balancer, a transparent DDoS protection service (like CloudFlare) or a similar network-level device, you may wish to avoid direct access to the Odoo system. It is generally difficult to keep the endpoint IP addresses of your Odoo servers secret. For example they can appear in web server logs when querying public systems, or in the headers of emails posted from Odoo. In such a situation you may want to configure your firewall so that the endpoints are not accessible publicly except from the specific IP addresses of your WAF, load-balancer or proxy service. Service providers like CloudFlare usually maintain a public list of their IP address ranges for this purpose." msgstr "" -#: ../../content/administration/install/deploy.rst:509 +#: ../../content/administration/install/deploy.rst:508 msgid "If you are hosting multiple customers, isolate customer data and files from each other using containers or appropriate \"jail\" techniques." msgstr "" -#: ../../content/administration/install/deploy.rst:512 +#: ../../content/administration/install/deploy.rst:511 msgid "Setup daily backups of your databases and filestore data, and copy them to a remote archiving server that is not accessible from the server itself." msgstr "" -#: ../../content/administration/install/deploy.rst:519 +#: ../../content/administration/install/deploy.rst:518 msgid "Blocking Brute Force Attacks" msgstr "" -#: ../../content/administration/install/deploy.rst:520 +#: ../../content/administration/install/deploy.rst:519 msgid "For internet-facing deployments, brute force attacks on user passwords are very common, and this threat should not be neglected for Odoo servers. Odoo emits a log entry whenever a login attempt is performed, and reports the result: success or failure, along with the target login and source IP." msgstr "" -#: ../../content/administration/install/deploy.rst:524 +#: ../../content/administration/install/deploy.rst:523 msgid "The log entries will have the following form." msgstr "" -#: ../../content/administration/install/deploy.rst:526 +#: ../../content/administration/install/deploy.rst:525 msgid "Failed login::" msgstr "" -#: ../../content/administration/install/deploy.rst:530 +#: ../../content/administration/install/deploy.rst:529 msgid "Successful login::" msgstr "" -#: ../../content/administration/install/deploy.rst:535 +#: ../../content/administration/install/deploy.rst:534 msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`." msgstr "" -#: ../../content/administration/install/deploy.rst:537 +#: ../../content/administration/install/deploy.rst:536 msgid "For example, the following fail2ban filter definition should match a failed login::" msgstr "" -#: ../../content/administration/install/deploy.rst:544 +#: ../../content/administration/install/deploy.rst:543 msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)." msgstr "" -#: ../../content/administration/install/deploy.rst:546 +#: ../../content/administration/install/deploy.rst:545 msgid "Here is what it could look like for blocking the IP for 15 minutes when 10 failed login attempts are detected from the same IP within 1 minute::" msgstr "" -#: ../../content/administration/install/deploy.rst:560 +#: ../../content/administration/install/deploy.rst:559 msgid "Database Manager Security" msgstr "" -#: ../../content/administration/install/deploy.rst:562 +#: ../../content/administration/install/deploy.rst:561 msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." msgstr "" -#: ../../content/administration/install/deploy.rst:564 +#: ../../content/administration/install/deploy.rst:563 msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)." msgstr "" -#: ../../content/administration/install/deploy.rst:567 +#: ../../content/administration/install/deploy.rst:566 msgid "If the management screens must not be accessible at all, you should set ``list_db`` configuration option to ``False``, to block access to all the database selection and management screens." msgstr "" -#: ../../content/administration/install/deploy.rst:573 +#: ../../content/administration/install/deploy.rst:572 msgid "It is strongly recommended to disable the Database Manager for any internet-facing system! It is meant as a development/demo tool, to make it easy to quickly create and manage databases. It is not designed for use in production, and may even expose dangerous features to attackers. It is also not designed to handle large databases, and may trigger memory limits." msgstr "" -#: ../../content/administration/install/deploy.rst:579 +#: ../../content/administration/install/deploy.rst:578 msgid "On production systems, database management operations should always be performed by the system administrator, including provisioning of new databases and automated backups." msgstr "" -#: ../../content/administration/install/deploy.rst:582 +#: ../../content/administration/install/deploy.rst:581 msgid "Be sure to setup an appropriate ``db_name`` parameter (and optionally, ``db_filter`` too) so that the system can determine the target database for each request, otherwise users will be blocked as they won't be allowed to choose the database themselves." msgstr "" -#: ../../content/administration/install/deploy.rst:587 +#: ../../content/administration/install/deploy.rst:586 msgid "If the management screens must only be accessible from a selected set of machines, use the proxy server's features to block access to all routes starting with ``/web/database`` except (maybe) ``/web/database/selector`` which displays the database-selection screen." msgstr "" -#: ../../content/administration/install/deploy.rst:591 +#: ../../content/administration/install/deploy.rst:590 msgid "If the database-management screen should be left accessible, the ``admin_passwd`` setting must be changed from its ``admin`` default: this password is checked before allowing database-alteration operations." msgstr "" -#: ../../content/administration/install/deploy.rst:595 +#: ../../content/administration/install/deploy.rst:594 msgid "It should be stored securely, and should be generated randomly e.g." msgstr "" -#: ../../content/administration/install/deploy.rst:601 +#: ../../content/administration/install/deploy.rst:600 msgid "which will generate a 32 characters pseudorandom printable string." msgstr "" -#: ../../content/administration/install/deploy.rst:604 +#: ../../content/administration/install/deploy.rst:603 msgid "Supported Browsers" msgstr "" -#: ../../content/administration/install/deploy.rst:606 +#: ../../content/administration/install/deploy.rst:605 msgid "Odoo supports all the major desktop and mobile browsers available on the market, as long as they are supported by their publishers." msgstr "" -#: ../../content/administration/install/deploy.rst:609 +#: ../../content/administration/install/deploy.rst:608 msgid "Here are the supported browsers:" msgstr "" -#: ../../content/administration/install/deploy.rst:611 +#: ../../content/administration/install/deploy.rst:610 msgid "Google Chrome" msgstr "" -#: ../../content/administration/install/deploy.rst:612 +#: ../../content/administration/install/deploy.rst:611 msgid "Mozilla Firefox" msgstr "" -#: ../../content/administration/install/deploy.rst:613 +#: ../../content/administration/install/deploy.rst:612 msgid "Microsoft Edge" msgstr "" -#: ../../content/administration/install/deploy.rst:614 +#: ../../content/administration/install/deploy.rst:613 msgid "Apple Safari" msgstr "" -#: ../../content/administration/install/deploy.rst:616 +#: ../../content/administration/install/deploy.rst:615 msgid "Please make sure your browser is up-to-date and still supported by its publisher before filing a bug report." msgstr "" -#: ../../content/administration/install/deploy.rst:621 +#: ../../content/administration/install/deploy.rst:620 msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." msgstr "" -#: ../../content/administration/install/deploy.rst:624 +#: ../../content/administration/install/deploy.rst:623 msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software." msgstr "" -#: ../../content/administration/install/deploy.rst:627 +#: ../../content/administration/install/deploy.rst:626 msgid "technically a tool like socat_ can be used to proxy UNIX sockets across networks, but that is mostly for software which can only be used over UNIX sockets" msgstr "" -#: ../../content/administration/install/deploy.rst:631 +#: ../../content/administration/install/deploy.rst:630 msgid "or be accessible only over an internal packet-switched network, but that requires secured switches, protections against `ARP spoofing`_ and precludes usage of WiFi. Even over secure packet-switched networks, deployment over HTTPS is recommended, and possible costs are lowered as \"self-signed\" certificates are easier to deploy on a controlled environment than over the internet." msgstr "" @@ -757,7 +757,7 @@ msgid "`Exim `_" msgstr "" #: ../../content/administration/install/email_gateway.rst:46 -msgid "If you don't have access/manage your email server, use :ref:`inbound messages `." +msgid "If you don't have access/manage your email server, use :ref:`inbound messages `." msgstr "" #: ../../content/administration/install/install.rst:6 @@ -898,7 +898,7 @@ msgid "Odoo will automatically be started at the end of the installation." msgstr "" #: ../../content/administration/install/install.rst:105 -#: ../../content/administration/install/install.rst:416 +#: ../../content/administration/install/install.rst:418 msgid "Linux" msgstr "" @@ -913,8 +913,8 @@ msgstr "" #: ../../content/administration/install/install.rst:113 #: ../../content/administration/install/install.rst:186 #: ../../content/administration/install/install.rst:300 -#: ../../content/administration/install/install.rst:464 -#: ../../content/administration/install/install.rst:633 +#: ../../content/administration/install/install.rst:466 +#: ../../content/administration/install/install.rst:637 msgid "Prepare" msgstr "" @@ -925,8 +925,8 @@ msgstr "" #: ../../content/administration/install/install.rst:123 #: ../../content/administration/install/install.rst:198 #: ../../content/administration/install/install.rst:367 -#: ../../content/administration/install/install.rst:538 -#: ../../content/administration/install/install.rst:700 +#: ../../content/administration/install/install.rst:540 +#: ../../content/administration/install/install.rst:704 msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in version `0.12.5 `_ for it to support headers and footers. See our `wiki `_ for more details on the various versions." msgstr "" @@ -1028,92 +1028,92 @@ msgid "Finally it provides greater control over the system's set up, and allows msgstr "" #: ../../content/administration/install/install.rst:255 -#: ../../content/administration/install/install.rst:419 -#: ../../content/administration/install/install.rst:588 +#: ../../content/administration/install/install.rst:421 +#: ../../content/administration/install/install.rst:592 msgid "Fetch the sources" msgstr "" #: ../../content/administration/install/install.rst:257 -#: ../../content/administration/install/install.rst:421 -#: ../../content/administration/install/install.rst:590 +#: ../../content/administration/install/install.rst:423 +#: ../../content/administration/install/install.rst:594 msgid "There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**." msgstr "" #: ../../content/administration/install/install.rst:260 -#: ../../content/administration/install/install.rst:424 -#: ../../content/administration/install/install.rst:593 +#: ../../content/administration/install/install.rst:426 +#: ../../content/administration/install/install.rst:597 msgid "Archive" msgstr "" #: ../../content/administration/install/install.rst:262 #: ../../content/administration/install/install.rst:279 -#: ../../content/administration/install/install.rst:426 -#: ../../content/administration/install/install.rst:443 -#: ../../content/administration/install/install.rst:595 -#: ../../content/administration/install/install.rst:612 +#: ../../content/administration/install/install.rst:428 +#: ../../content/administration/install/install.rst:445 +#: ../../content/administration/install/install.rst:599 +#: ../../content/administration/install/install.rst:616 msgid "Community Edition:" msgstr "" #: ../../content/administration/install/install.rst:264 #: ../../content/administration/install/install.rst:270 -#: ../../content/administration/install/install.rst:428 -#: ../../content/administration/install/install.rst:434 -#: ../../content/administration/install/install.rst:597 -#: ../../content/administration/install/install.rst:603 +#: ../../content/administration/install/install.rst:430 +#: ../../content/administration/install/install.rst:436 +#: ../../content/administration/install/install.rst:601 +#: ../../content/administration/install/install.rst:607 msgid "`Official download page `_" msgstr "" #: ../../content/administration/install/install.rst:265 -#: ../../content/administration/install/install.rst:429 -#: ../../content/administration/install/install.rst:598 +#: ../../content/administration/install/install.rst:431 +#: ../../content/administration/install/install.rst:602 msgid "`GitHub repository `_" msgstr "" #: ../../content/administration/install/install.rst:266 -#: ../../content/administration/install/install.rst:430 -#: ../../content/administration/install/install.rst:599 +#: ../../content/administration/install/install.rst:432 +#: ../../content/administration/install/install.rst:603 msgid "`Nightly server `_" msgstr "" #: ../../content/administration/install/install.rst:268 -#: ../../content/administration/install/install.rst:432 -#: ../../content/administration/install/install.rst:601 +#: ../../content/administration/install/install.rst:434 +#: ../../content/administration/install/install.rst:605 msgid "Enterprise Edition:" msgstr "" #: ../../content/administration/install/install.rst:271 -#: ../../content/administration/install/install.rst:435 -#: ../../content/administration/install/install.rst:604 +#: ../../content/administration/install/install.rst:437 +#: ../../content/administration/install/install.rst:608 msgid "`GitHub repository `_" msgstr "" #: ../../content/administration/install/install.rst:274 -#: ../../content/administration/install/install.rst:438 -#: ../../content/administration/install/install.rst:607 +#: ../../content/administration/install/install.rst:440 +#: ../../content/administration/install/install.rst:611 msgid "Git" msgstr "" #: ../../content/administration/install/install.rst:276 -#: ../../content/administration/install/install.rst:440 -#: ../../content/administration/install/install.rst:609 +#: ../../content/administration/install/install.rst:442 +#: ../../content/administration/install/install.rst:613 msgid "The following requires git_ to be installed on your machine and that you have basic knowledge of git commands." msgstr "" #: ../../content/administration/install/install.rst:286 -#: ../../content/administration/install/install.rst:450 -#: ../../content/administration/install/install.rst:619 +#: ../../content/administration/install/install.rst:452 +#: ../../content/administration/install/install.rst:623 msgid "Enterprise Edition: (see :ref:`setup/install/editions` to get access)" msgstr "" #: ../../content/administration/install/install.rst:292 -#: ../../content/administration/install/install.rst:456 -#: ../../content/administration/install/install.rst:625 +#: ../../content/administration/install/install.rst:458 +#: ../../content/administration/install/install.rst:629 msgid "**The Enterprise git repository does not contain the full Odoo source code**. It is only a collection of extra add-ons. The main server code is in the Community version. Running the Enterprise version actually means running the server from the Community version with the addons-path option set to the folder with the Enterprise version. You need to clone both the Community and Enterprise repository to have a working Odoo Enterprise installation." msgstr "" #: ../../content/administration/install/install.rst:303 -#: ../../content/administration/install/install.rst:467 -#: ../../content/administration/install/install.rst:636 +#: ../../content/administration/install/install.rst:469 +#: ../../content/administration/install/install.rst:640 msgid "Python" msgstr "" @@ -1126,14 +1126,14 @@ msgid "During installation, check **Add Python 3 to PATH**, then click **Customi msgstr "" #: ../../content/administration/install/install.rst:311 -#: ../../content/administration/install/install.rst:472 -#: ../../content/administration/install/install.rst:641 +#: ../../content/administration/install/install.rst:474 +#: ../../content/administration/install/install.rst:645 msgid "If Python 3 is already installed, make sure that the version is 3.6 or above, as previous versions are not compatible with Odoo." msgstr "" #: ../../content/administration/install/install.rst:318 -#: ../../content/administration/install/install.rst:479 -#: ../../content/administration/install/install.rst:648 +#: ../../content/administration/install/install.rst:481 +#: ../../content/administration/install/install.rst:652 msgid "Verify also that pip_ is installed for this version." msgstr "" @@ -1142,8 +1142,8 @@ msgid "Odoo uses PostgreSQL as database management system. `Download and install msgstr "" #: ../../content/administration/install/install.rst:330 -#: ../../content/administration/install/install.rst:497 -#: ../../content/administration/install/install.rst:660 +#: ../../content/administration/install/install.rst:499 +#: ../../content/administration/install/install.rst:664 msgid "By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to create a new PostgreSQL user:" msgstr "" @@ -1180,8 +1180,8 @@ msgid "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Crea msgstr "" #: ../../content/administration/install/install.rst:346 -#: ../../content/administration/install/install.rst:509 -#: ../../content/administration/install/install.rst:672 +#: ../../content/administration/install/install.rst:511 +#: ../../content/administration/install/install.rst:676 msgid "Dependencies" msgstr "" @@ -1190,14 +1190,14 @@ msgid "Before installing the dependencies, you must download and install the `Bu msgstr "" #: ../../content/administration/install/install.rst:352 -#: ../../content/administration/install/install.rst:523 -#: ../../content/administration/install/install.rst:674 +#: ../../content/administration/install/install.rst:525 +#: ../../content/administration/install/install.rst:678 msgid "Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo community directory." msgstr "" #: ../../content/administration/install/install.rst:355 -#: ../../content/administration/install/install.rst:526 -#: ../../content/administration/install/install.rst:677 +#: ../../content/administration/install/install.rst:528 +#: ../../content/administration/install/install.rst:681 msgid "It can be preferable to not mix python modules packages between different instances of Odoo or with your system. You can use virtualenv_ to create isolated Python environments." msgstr "" @@ -1206,8 +1206,8 @@ msgid "Navigate to the path of your Odoo Community installation (`CommunityPath` msgstr "" #: ../../content/administration/install/install.rst:372 -#: ../../content/administration/install/install.rst:543 -#: ../../content/administration/install/install.rst:705 +#: ../../content/administration/install/install.rst:545 +#: ../../content/administration/install/install.rst:709 msgid "For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is needed:" msgstr "" @@ -1216,8 +1216,8 @@ msgid "Download and install `nodejs `_." msgstr "" #: ../../content/administration/install/install.rst:376 -#: ../../content/administration/install/install.rst:547 -#: ../../content/administration/install/install.rst:709 +#: ../../content/administration/install/install.rst:549 +#: ../../content/administration/install/install.rst:713 msgid "Install `rtlcss`:" msgstr "" @@ -1226,32 +1226,32 @@ msgid "Edit the System Environment's variable `PATH` to add the folder where `rt msgstr "" #: ../../content/administration/install/install.rst:386 -#: ../../content/administration/install/install.rst:554 -#: ../../content/administration/install/install.rst:716 +#: ../../content/administration/install/install.rst:556 +#: ../../content/administration/install/install.rst:720 msgid "Running Odoo" msgstr "" #: ../../content/administration/install/install.rst:388 -#: ../../content/administration/install/install.rst:556 -#: ../../content/administration/install/install.rst:718 +#: ../../content/administration/install/install.rst:558 +#: ../../content/administration/install/install.rst:722 msgid "Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the command-line interface of the server. It is located at the root of the Odoo Community directory." msgstr "" #: ../../content/administration/install/install.rst:391 -#: ../../content/administration/install/install.rst:559 -#: ../../content/administration/install/install.rst:721 +#: ../../content/administration/install/install.rst:561 +#: ../../content/administration/install/install.rst:725 msgid "To configure the server, you can either specify :ref:`command-line arguments ` or a :ref:`configuration file `." msgstr "" #: ../../content/administration/install/install.rst:394 -#: ../../content/administration/install/install.rst:562 -#: ../../content/administration/install/install.rst:724 +#: ../../content/administration/install/install.rst:564 +#: ../../content/administration/install/install.rst:728 msgid "For the Enterprise edition, you must add the path to the `enterprise` addons to the `addons-path` argument. Note that it must come before the other paths in `addons-path` for addons to be loaded correctly." msgstr "" #: ../../content/administration/install/install.rst:398 -#: ../../content/administration/install/install.rst:566 -#: ../../content/administration/install/install.rst:728 +#: ../../content/administration/install/install.rst:568 +#: ../../content/administration/install/install.rst:732 msgid "Common necessary configurations are:" msgstr "" @@ -1260,766 +1260,492 @@ msgid "PostgreSQL user and password." msgstr "" #: ../../content/administration/install/install.rst:401 -#: ../../content/administration/install/install.rst:571 -#: ../../content/administration/install/install.rst:733 +#: ../../content/administration/install/install.rst:573 +#: ../../content/administration/install/install.rst:737 msgid "Custom addon paths beyond the defaults, to load your own modules." msgstr "" #: ../../content/administration/install/install.rst:403 -#: ../../content/administration/install/install.rst:573 -#: ../../content/administration/install/install.rst:735 +#: ../../content/administration/install/install.rst:575 +#: ../../content/administration/install/install.rst:739 msgid "A typical way to run the server would be:" msgstr "" #: ../../content/administration/install/install.rst:410 -msgid "Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password and `mydb` is the default database to serve on `localhost:8069`. You can add other directory paths separated by a comma to ``addons`` at the end of the addons-path option." +msgid "Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password and `mydb` is the default database to serve on `localhost:8069`." msgstr "" -#: ../../content/administration/install/install.rst:469 +#: ../../content/administration/install/install.rst:415 +#: ../../content/administration/install/install.rst:586 +#: ../../content/administration/install/install.rst:750 +msgid ":doc:`The exhaustive list of arguments for odoo-bin `." +msgstr "" + +#: ../../content/administration/install/install.rst:471 msgid "Odoo requires Python 3.6 or later to run. Use your package manager to download and install Python 3 on your machine if it is not already done." msgstr "" -#: ../../content/administration/install/install.rst:488 +#: ../../content/administration/install/install.rst:490 msgid "Odoo uses PostgreSQL as database management system. Use your package manager to download and install PostgreSQL (supported version: 10.0 and later)." msgstr "" -#: ../../content/administration/install/install.rst:491 +#: ../../content/administration/install/install.rst:493 msgid "On Debian/Unbuntu, it can be achieved by executing the following:" msgstr "" -#: ../../content/administration/install/install.rst:505 -#: ../../content/administration/install/install.rst:668 +#: ../../content/administration/install/install.rst:507 +#: ../../content/administration/install/install.rst:672 msgid "Because your PostgreSQL user has the same name as your Unix login, you will be able to connect to the database without password." msgstr "" -#: ../../content/administration/install/install.rst:511 +#: ../../content/administration/install/install.rst:513 msgid "For libraries using native code, it is necessary to install development tools and native dependencies before the Python dependencies of Odoo. They are available in `-dev` or `-devel` packages for Python, PostgreSQL, libxml2, libxslt1, libevent, libsasl2 and libldap2." msgstr "" -#: ../../content/administration/install/install.rst:515 +#: ../../content/administration/install/install.rst:517 msgid "On Debian/Unbuntu, the following command should install all the required libraries:" msgstr "" -#: ../../content/administration/install/install.rst:529 -#: ../../content/administration/install/install.rst:680 +#: ../../content/administration/install/install.rst:531 +#: ../../content/administration/install/install.rst:684 msgid "Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file:" msgstr "" -#: ../../content/administration/install/install.rst:546 +#: ../../content/administration/install/install.rst:548 msgid "Download and install **nodejs** and **npm** with your package manager." msgstr "" -#: ../../content/administration/install/install.rst:568 -#: ../../content/administration/install/install.rst:730 +#: ../../content/administration/install/install.rst:570 +#: ../../content/administration/install/install.rst:734 msgid "PostgreSQL user and password. Odoo has no defaults beyond `psycopg2's defaults `_: connects over a UNIX socket on port `5432` with the current user and no password." msgstr "" -#: ../../content/administration/install/install.rst:580 -#: ../../content/administration/install/install.rst:742 -msgid "Where `CommunityPath` is the path of the Odoo Community installation and `mydb` is the default database to serve on `localhost:8069`. You can add other directory paths separated by a comma to ``addons`` at the end of the addons-path option." +#: ../../content/administration/install/install.rst:582 +#: ../../content/administration/install/install.rst:746 +msgid "Where `CommunityPath` is the path of the Odoo Community installation and `mydb` is the default database to serve on `localhost:8069`." msgstr "" -#: ../../content/administration/install/install.rst:585 +#: ../../content/administration/install/install.rst:589 msgid "Mac OS" msgstr "" -#: ../../content/administration/install/install.rst:638 +#: ../../content/administration/install/install.rst:642 msgid "Odoo requires Python 3.6 or later to run. Use your preferred package manager (homebrew_, macports_) to download and install Python 3 on your machine if it is not already done." msgstr "" -#: ../../content/administration/install/install.rst:657 +#: ../../content/administration/install/install.rst:661 msgid "Odoo uses PostgreSQL as database management system. Use `postgres.app `_ to download and install PostgreSQL (supported version: 10.0 and later)." msgstr "" -#: ../../content/administration/install/install.rst:689 +#: ../../content/administration/install/install.rst:693 msgid "Non-Python dependencies need to be installed with a package manager:" msgstr "" -#: ../../content/administration/install/install.rst:691 +#: ../../content/administration/install/install.rst:695 msgid "Download and install the **Command Line Tools**:" msgstr "" -#: ../../content/administration/install/install.rst:697 +#: ../../content/administration/install/install.rst:701 msgid "Download and install the package manager of your choice (homebrew_, macports_)." msgstr "" -#: ../../content/administration/install/install.rst:698 +#: ../../content/administration/install/install.rst:702 msgid "Install non-python dependencies." msgstr "" -#: ../../content/administration/install/install.rst:708 +#: ../../content/administration/install/install.rst:712 msgid "Download and install **nodejs** with your preferred package manager (homebrew_, macports_)." msgstr "" -#: ../../content/administration/install/install.rst:750 +#: ../../content/administration/install/install.rst:755 #: ../../content/administration/maintain/update.rst:147 msgid "Docker" msgstr "" -#: ../../content/administration/install/install.rst:752 -msgid "The full documentation on how to use Odoo with Docker can be found on the official Odoo `docker image `_ page." +#: ../../content/administration/install/install.rst:757 +msgid "The full documentation on how to use Odoo with Docker can be found on the official Odoo `docker image `_ page." msgstr "" #: ../../content/administration/maintain.rst:5 msgid "Maintain" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:6 -msgid "On-premises Database management" +#: ../../content/administration/maintain/domain_names.rst:3 +msgid "Domain names" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:9 -msgid "Register a database" +#: ../../content/administration/maintain/domain_names.rst:5 +msgid "A **domain name** works as an address for your website. It makes the Internet much more accessible as it allows users to type a meaningful web address, such as ``www.odoo.com``, rather than its server's IP address with a series of numbers." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:11 -msgid "To register your database, you just need to enter your Subscription Code in the banner in the App Switcher. Make sure you do not add extra spaces before or after your subscription code. If the registration is successful, it will turn green and will provide you with the Expiration Date of your freshly-registered database. You can check this Epiration Date in the About menu (Odoo 9) or in the Settings Dashboard (Odoo 10)." +#: ../../content/administration/maintain/domain_names.rst:9 +msgid "You can use a custom domain name to access your Odoo database and websites:" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:19 -msgid "Registration Error Message" +#: ../../content/administration/maintain/domain_names.rst:11 +msgid "By :ref:`registering a free domain name with Odoo ` (for Odoo Online databases)" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:21 -msgid "If you are unable to register your database, you will likely encounter this message:" +#: ../../content/administration/maintain/domain_names.rst:13 +msgid "By :ref:`configuring a custom domain that you already own `." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:30 -#: ../../content/administration/maintain/db_premise.rst:109 -#: ../../content/administration/maintain/db_premise.rst:137 -msgid "Solutions" +#: ../../content/administration/maintain/domain_names.rst:16 +msgid "Odoo Online and Odoo.sh databases, including their websites, use by default a subdomain of ``odoo.com`` for both the URL and the emails (e.g., ``https://example.odoo.com``)." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:32 -msgid "Do you have a valid Enterprise subscription?" +#: ../../content/administration/maintain/domain_names.rst:20 +msgid "Odoo offers a :ref:`free custom domain name ` to all Odoo Online databases for one year. Visitors can then access your website with an address such as ``www.example.com`` rather than the default ``example.odoo.com``." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:34 -msgid "Check if your subscription details get the tag \"In Progress\" on your `Odoo Account `__ or with your Account Manager" +#: ../../content/administration/maintain/domain_names.rst:27 +msgid "About domain names" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:38 -msgid "Have you already linked a database with your subscription reference?" +#: ../../content/administration/maintain/domain_names.rst:29 +msgid "Having a **good domain name** is as important to your branding as the name of your business or organization as it is the first thing your visitors will notice. We recommend you keep them *simple, short, easy to remember and spell*." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:40 -msgid "You can link only one database per subscription. (Need a test or a development database? `Find a partner `__)" +#: ../../content/administration/maintain/domain_names.rst:33 +msgid "A **subdomain** is a domain that is a part of another domain. It often refers to the additional part that comes before the main domain name. Traditionally, most websites use the ``www.`` subdomain, but any string of letters can be used as well. You can use subdomains to direct your visitors to other websites than your main website or to specific pages (e.g., ``experience.odoo.com`` points to a specific page.)" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:44 -msgid "You can unlink the old database yourself on your `Odoo Contract `__ with the button \"Unlink database\"" +#: ../../content/administration/maintain/domain_names.rst:39 +msgid "All domain names are referenced in the **Domain Name System**, or **DNS**, which works as a giant directory for the Internet. There are many DNS servers, so any modification to the DNS can take up to 72 hours to propagate worldwide on all servers." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:51 -msgid "A confirmation message will appear; make sure this is the correct database as it will be deactivated shortly:" +#: ../../content/administration/maintain/domain_names.rst:46 +msgid "Register a free domain name with Odoo" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:58 -msgid "Do you have the updated version of Odoo 9?" +#: ../../content/administration/maintain/domain_names.rst:48 +msgid "You can register a domain name for your Odoo Online database directly from Odoo Website or your database manager." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:60 -#: ../../content/administration/maintain/db_premise.rst:170 -msgid "From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a manual operation is no longer required." +#: ../../content/administration/maintain/domain_names.rst:52 +msgid "Your domain name is **free for one year** if you register it with Odoo!" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:63 -msgid "If it's not the case, you may have multiple databases sharing the same UUID. Please check on your `Odoo Contract `__, a short message will appear specifying which database is problematic:" +#: ../../content/administration/maintain/domain_names.rst:53 +msgid "The domain name is registered with `Gandi `_, the domain name registrar." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:72 -msgid "In this case, you need to change the UUID on your test databases to solve this issue. You will find more information about this in :ref:`this section `." +#: ../../content/administration/maintain/domain_names.rst:55 +msgid "You are the owner of the domain name and can use it for other purposes." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:75 -msgid "For your information, we identify database with UUID. Therefore, each database should have a distinct UUID to ensure that registration and invoicing proceed effortlessly for your and for us." +#: ../../content/administration/maintain/domain_names.rst:56 +msgid "Odoo manages payment and technical support for you." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:79 -msgid "Check your network and firewall settings" +#: ../../content/administration/maintain/domain_names.rst:58 +msgid "To do so, go to :menuselection:`Website --> Go to website --> Promote --> Domain Name`. Alternatively, open your `database manager `_, click on the :guilabel:`settings` button next to your database, then on :guilabel:`Domain names`." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:81 -msgid "The Update notification must be able to reach Odoo's subscription validation servers. In other words, make sure that the Odoo server is able to open outgoing connections towards:" +#: ../../content/administration/maintain/domain_names.rst:66 +msgid "Search for the domain name of your choice to check its availability, then select the one you want to register for your website." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:85 -msgid "services.odoo.com on port 443 (or 80)" +#: ../../content/administration/maintain/domain_names.rst:73 +msgid "Next, fill in the form with your information to become the domain name owner." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:86 -msgid "services.openerp.com on port 443 (or 80) for older deployments" +#: ../../content/administration/maintain/domain_names.rst:75 +msgid "Your domain name is directly linked to your database, but you still have to :ref:`map your domain name with your website `." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:88 -msgid "Once you activated your database, you must keep these ports open, as the Update notification runs once a week." +#: ../../content/administration/maintain/domain_names.rst:79 +msgid "Free domain names are also available for free Odoo Online databases (if you installed one app only, for example). In this case, Odoo reviews your request and your website to avoid abuse. This process may take up to three days." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:94 -msgid "Error message due to too many users" +#: ../../content/administration/maintain/domain_names.rst:82 +msgid "This is not available for Odoo.sh databases yet." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:96 -msgid "If you have more users in your local database than provisionned in your Odoo Enterprise subscription, you may encounter this message:" +#: ../../content/administration/maintain/domain_names.rst:87 +msgid "Manage your domain name registered with Odoo" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:105 -msgid "When the message appears you have 30 days before the expiration. The countdown is updated everyday." +#: ../../content/administration/maintain/domain_names.rst:89 +msgid "To manage the DNS records of your domain name registered with Odoo or to visualize the contacts associated with it, open your `database manager `_, click on the :guilabel:`settings` button next to your database, on :guilabel:`Domain names`, and then on :guilabel:`Contacts` or :guilabel:`DNS`." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:111 -msgid "**Add more users** on your subscription: follow the link and Validate the upsell quotation and pay for the extra users." +#: ../../content/administration/maintain/domain_names.rst:99 +msgid "Please `submit a support ticket `_ if you need further assistance to manage your domain name." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:113 -msgid "**Deactivate users** as explained in this `documentation `_ and **Reject** the upsell quotation." +#: ../../content/administration/maintain/domain_names.rst:105 +msgid "Configure your existing domain name" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:116 -msgid "Once your database has the correct number of users, the expiration message will disappear automatically after a few days, when the next verification occurs. We understand that it can be a bit frightening to see the countdown, so you can :ref:`force an Update Notification ` to make the message disappear right away." +#: ../../content/administration/maintain/domain_names.rst:107 +msgid "If you already own a domain name, you can use it to point to your website." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:123 -msgid "Database expired error message" +#: ../../content/administration/maintain/domain_names.rst:109 +msgid "To avoid any issue with the :ref:`SSL certificate validation `, we highly recommend that you proceed with the following actions in this order:" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:125 -msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:" +#: ../../content/administration/maintain/domain_names.rst:112 +msgid ":ref:`Add a CNAME record ` on your domain name's DNS zone." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:133 -msgid "This **blocking** message appears after a non-blocking message that lasts 30 days. If you fail to take action before the end of the countdown, the database is expired." +#: ../../content/administration/maintain/domain_names.rst:113 +msgid ":ref:`Map your domain name with your Odoo database `." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:141 -msgid "Renew your subscription: follow the link and renew your subscription - note that" +#: ../../content/administration/maintain/domain_names.rst:114 +msgid ":ref:`Map your domain name with your Odoo website `." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:140 -msgid "if you wish to pay by Wire Transfer, your subscription will effectively be renewed only when the payment arrives, which can take a few days. Credit card payments are processed immediately." +#: ../../content/administration/maintain/domain_names.rst:115 +msgid "Optionnally: :ref:`Change the web base address of your database `." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:143 -msgid "Contact our `Support `__" +#: ../../content/administration/maintain/domain_names.rst:120 +msgid "Add a CNAME record" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:145 -msgid "None of those solutions worked for you? Please contact our `Support `__" +#: ../../content/administration/maintain/domain_names.rst:122 +msgid "A **CNAME record** is a type of DNS record that points to the IP address of another website rather than to directly to an IP address." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:154 -msgid "Duplicate a database" +#: ../../content/administration/maintain/domain_names.rst:125 +msgid "You need a CNAME record that points to your Odoo database. The requirements are detailed in your database manager." msgstr "" -#: ../../content/administration/maintain/db_premise.rst:156 -msgid "You can duplicate your database by accessing the database manager on your server (/web/database/manager). In this page, you can easily duplicate your database (among other things)." +#: ../../content/administration/maintain/domain_names.rst:130 +#: ../../content/administration/maintain/domain_names.rst:200 +#: ../../content/administration/maintain/supported_versions.rst:27 +msgid "Odoo Online" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:164 -msgid "When you duplicate a local database, it is **strongly** advised to change the duplicated database's uuid (Unniversally Unique Identifier), since this uuid is how your database identifies itself with our servers. Having two databases with the same uuid could result in invoicing problems or registration problems down the line." +#: ../../content/administration/maintain/domain_names.rst:132 +msgid "The target address is the current address of your database, as defined at its creation (e.g., ``example.odoo.com``)" msgstr "" -#: ../../content/administration/maintain/db_premise.rst:173 -msgid "The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical --> System Parameters`, we advise you to use a `uuid generator `_ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:11 -msgid "Versions upgrade" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:16 -#: ../../content/administration/odoo_sh/advanced/containers.rst:7 -#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 -#: ../../content/administration/odoo_sh/getting_started/branches.rst:7 -#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 -#: ../../content/administration/odoo_sh/getting_started/first_module.rst:7 -#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:7 -#: ../../content/administration/odoo_sh/getting_started/status.rst:7 -#: ../../content/administration/odoo_sh/overview.rst:5 -msgid "Overview" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:21 -msgid "The upgrade process" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:23 -msgid "This documentation is for our *On-Premise* (self-hosted) and *Odoo.sh* customers." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:28 -msgid "Definition" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:30 -msgid "An upgrade is switching to a newer version of Odoo (e.g., Odoo 13.0 to Odoo 14.0)" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:32 -msgid "An upgrade does not cover:" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:34 -msgid "changing :ref:`Editions ` (i.e., Community to Enterprise edition)" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:35 -msgid "switching :ref:`hosting type ` (i.e., On-Premise to Online or Odoo.sh)" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:37 -msgid "migration from another ERP to Odoo" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:39 -#: ../../content/administration/maintain/db_upgrade.rst:97 -#: ../../content/administration/maintain/db_upgrade.rst:228 -#: ../../content/administration/maintain/db_upgrade.rst:358 -#: ../../content/administration/maintain/db_upgrade.rst:367 -#: ../../content/administration/maintain/db_upgrade.rst:379 -msgid "|assistance-contact|" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:44 -msgid "Process workflow" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:46 -msgid "The upgrade process in a nutshell:" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:48 -msgid "You create a test upgrade request." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:0 -msgid "The request is processed by Odoo:" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:0 -msgid "This happens via an automated process that runs the database through an upgrade script and takes between 20 and 120 minutes. Only if an issue(s) arises will we have to intervene manually and adjust the script specifically to your database until the upgrade succeeds." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:53 -msgid "Odoo delivers a test database." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:54 -msgid "You test your database for possible discrepancies (see :ref:`db-upgrade/test-guidance`)" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:55 -msgid "If there are any discrepancies, you report them to the Upgrade support team via the :ref:`Help portal `." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:57 -msgid "We will fix the issues and send you a new test database." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:58 -msgid "Once you completed the testing and are happy with the result, you decide on a date and time when you stop users from accessing Odoo, freeze all data entries and create an upgrade request for the production upgrade." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:61 -msgid "Odoo delivers the production database through the automated process." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:62 -msgid "You restore it in your Production environment a few short hours later and continue working on the newly upgraded database." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:68 -msgid "Service Level Agreement" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:71 -msgid "What is covered by the Enterprise Licence?" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:73 -msgid "Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the following service at all times." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:76 -msgid "The upgrade of:" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:78 -msgid "standard applications" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:79 -msgid "Studio customization (as long as the Studio app is still active)" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:80 -msgid "customizations done by our consulting and developer services *if* they are covered by a ‘Maintenance of Customisations’ subscription" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:83 -msgid "The Upgrade Service is limited to the technical conversion and adaptation of your database (standard modules and data) to make it compatible with the targeted version." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:87 -msgid "What upgrading does NOT cover" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:89 -msgid "The cleaning of pre-existing data & configuration while upgrading" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:90 -msgid "Any new developments and/or upgrade of your own :ref:`custom modules `" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:92 -msgid "`Training `_ on the new version" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:94 -msgid "You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription Agreement ` page." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:102 -#: ../../content/administration/odoo_sh/getting_started.rst:5 -msgid "Get started" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:104 -msgid "The upgrade process varies depending on where your database is hosted." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:109 -msgid "Online (SaaS)" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:111 -msgid "If you are hosted Online, please check your `database manager `_." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:116 -#: ../../content/administration/maintain/supported_versions.rst:24 +#: ../../content/administration/maintain/domain_names.rst:135 +#: ../../content/administration/maintain/domain_names.rst:214 +#: ../../content/administration/maintain/supported_versions.rst:27 #: ../../content/administration/odoo_sh.rst:5 msgid "Odoo.sh" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:118 -msgid "If you are Odoo.sh hosted, check our :doc:`specific instructions to be able to upgrade <../odoo_sh/advanced/upgrade_your_database>`." +#: ../../content/administration/maintain/domain_names.rst:137 +msgid "Your project's main address is defined in :menuselection:`Settings --> Project Name`." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:124 -#: ../../content/administration/maintain/supported_versions.rst:24 -msgid "On-Premise" +#: ../../content/administration/maintain/domain_names.rst:139 +msgid "If you want to target a specific branch (production, staging or development), go to :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, and click on :guilabel:`How to set up my domain?`. A message indicates which address your CNAME record should target." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:126 -msgid "There are two possibilities:" +#: ../../content/administration/maintain/domain_names.rst:144 +#: ../../content/administration/maintain/domain_names.rst:186 +msgid "Open your domain name's manager dashboard." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:128 -msgid "Via the interface of our `website form `_" +#: ../../content/administration/maintain/domain_names.rst:145 +msgid "Open the **DNS zone** management page for the domain name you want to configure." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:0 -msgid "For technically-advanced users and partners, via the following command line (to be used on the machine where your database is hosted):" +#: ../../content/administration/maintain/domain_names.rst:146 +msgid "Create a **CNAME record** pointing to the address of your database." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:0 -msgid "``python <(curl -s beta.upgrade.odoo.com/upgrade) test -d -t 14.0``" +#: ../../content/administration/maintain/domain_names.rst:148 +msgid "While Odoo suggests creating a CNAME record for your ``www.`` subdomain (``www.example.com``, you can of course use any domain name of your choice, with any subdomain (e.g., ``anything.example.com``)." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:134 -msgid "What does it do?" +#: ../../content/administration/maintain/domain_names.rst:153 +msgid "You own the domain name ``example.com``, and you have an Odoo Online database at the address ``example.odoo.com``. You want to access your Odoo database primarily with the domain ``www.example.com`` but also with the :ref:`naked domain ` ``example.com``." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:136 -msgid "The above command will dump your database to a file, then send it to the upgrade platform for upgrade, displaying you the live logs, then restore the upgraded database back on your server as a duplicate test database." +#: ../../content/administration/maintain/domain_names.rst:158 +msgid "To do so, you create a CNAME record for the ``www`` subdomain, with ``example.odoo.com`` as the target. The DNS zone manager generates the following rule and adds it to your DNS zone: ``www IN CNAME example.odoo.com.``" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:143 -msgid "Steps" +#: ../../content/administration/maintain/domain_names.rst:162 +msgid "You also create a redirection from ``example.com`` to ``wwww.example.com``." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:148 -msgid "The testing phase" +#: ../../content/administration/maintain/domain_names.rst:164 +msgid "Your new DNS records are propagated to all DNS servers." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:153 -msgid "Test process" +#: ../../content/administration/maintain/domain_names.rst:167 +msgid "Here are some specific guidelines to create a CNAME record:" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:155 -msgid "Also referred to as the pre-production phase, the test phase allows you to review an upgraded version of your database without affecting your production database in any way." +#: ../../content/administration/maintain/domain_names.rst:169 +msgid "`GoDaddy `_" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:158 -msgid "We suggest that you run the test upgrade process at least once, but you can do it as often as you want (one at a time)." +#: ../../content/administration/maintain/domain_names.rst:170 +msgid "`Namecheap `_" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:161 -msgid "Once you receive your upgraded test database, you should check that all data, processes and functionality are still correct and working as expected." +#: ../../content/administration/maintain/domain_names.rst:171 +msgid "`OVH `_" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:164 -msgid "If you do find discrepancies, you'll be able to:" +#: ../../content/administration/maintain/domain_names.rst:172 +msgid "`CloudFlare `_" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:0 -msgid ":ref:`Report your issues `" +#: ../../content/administration/maintain/domain_names.rst:173 +msgid "`Google Domains `_" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:0 -msgid "and/or" +#: ../../content/administration/maintain/domain_names.rst:178 +msgid "Naked domain" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:168 -msgid "Ask for a new :ref:`test request ` after the reported issues have been fixed in the upgrade script." +#: ../../content/administration/maintain/domain_names.rst:180 +msgid "A **naked domain** is a domain name that doesn't have any subdomain at the beginning of the address (e.g., ``odoo.com`` instead of ``www.odoo.com``)." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:171 -msgid "When you do not find any discrepancies, you'll be able to:" +#: ../../content/administration/maintain/domain_names.rst:183 +msgid "You may want your naked domain to redirect to your website as some visitors may not type the full domain name to access your website." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:173 -msgid "Move on to the upgrade of your :ref:`production database `." +#: ../../content/administration/maintain/domain_names.rst:187 +msgid "Create a **redirection** from the naked domain (``example.com``) to your main domain name (``www.example.com``)." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:178 -msgid "Request a test database" +#: ../../content/administration/maintain/domain_names.rst:191 +msgid "Depending on your domain name registrar, this redirection may be already pre-configured." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:180 -msgid "When filling the `website form `_, select *Testing* purpose." +#: ../../content/administration/maintain/domain_names.rst:196 +msgid "Map your domain name with your Odoo database" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:189 -msgid "Test guidance" +#: ../../content/administration/maintain/domain_names.rst:202 +msgid "Open your `database manager `_, click on the :guilabel:`settings` button next to your database, on :guilabel:`Domain names`, and then on :guilabel:`Use my own domain` at the bottom of the right column." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:191 -msgid "Every business and organization has its own operational needs and will have to test its specific Odoo instance respectively. However, we recommend you look at `the test scenario `_ we created, a high-level idea of what you should test and look out for." +#: ../../content/administration/maintain/domain_names.rst:206 +msgid "Type the domain name you want to add to this database, then click on :guilabel:`Verify` to check if the CNAME record is correctly configured. Once done, click on :guilabel:`I confirm, it's done`." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:196 -msgid "change link \"test scenario\" once the related doc is published" +#: ../../content/administration/maintain/domain_names.rst:216 +msgid "Go to :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, type the domain name you want to add to this database, then click on :guilabel:`Add domain`." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:201 -#: ../../content/administration/maintain/db_upgrade.rst:260 -#: ../../content/administration/maintain/db_upgrade.rst:392 -msgid "Assistance" +#: ../../content/administration/maintain/domain_names.rst:224 +msgid ":ref:`Odoo.sh branches: settings tab `" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:203 -msgid "If you encounter issues or problems in the **test database**, please contact the Odoo Upgrade Support:" +#: ../../content/administration/maintain/domain_names.rst:227 +msgid "Make sure to :ref:`add a CNAME record ` to your domain name's DNS **before** mapping your domain name with your Odoo database." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:206 -#: ../../content/administration/maintain/db_upgrade.rst:265 -msgid "Connect to our `Odoo Support page `_." +#: ../../content/administration/maintain/domain_names.rst:230 +msgid "Failing to do so may impede the validation of the :ref:`SSL certificate ` and would result in a *certificate name mismatch* error. This is often displayed by web browsers as a warning such as *\"Your connection is not private\"*." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:207 -msgid "Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type." +#: ../../content/administration/maintain/domain_names.rst:234 +msgid "If this is the case and you have added the domain name to your database's settings less than five days ago, wait 24 hours as the validation may still happen. Otherwise, please `submit a support ticket `_ including screenshots of your CNAME records." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:214 -msgid "If you choose another *Ticket Description* type, the request will be redirected to another team than the upgrade one and will slow down the processing and response time." +#: ../../content/administration/maintain/domain_names.rst:241 +msgid "SSL encryption (HTTPS protocol)" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:217 -#: ../../content/administration/maintain/db_upgrade.rst:273 -msgid "Please provide as much detail as you can. Where applicable, illustrate the current and previous flows with videos and/or screenshots. This will avoid clarifying questions and speed up the resolution process significantly." +#: ../../content/administration/maintain/domain_names.rst:243 +msgid "**SSL encryption** is an encryption-based Internet security protocol. It allows your visitors to navigate your website through a secure connection, which appears as an ``https://`` protocol at the beginning of your web address, rather than a non-secure ``http://`` protocol." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:226 -msgid "The purpose of the test phase is not to correct existing data or configurations in your database." +#: ../../content/administration/maintain/domain_names.rst:247 +msgid "Odoo generates a separate SSL certificate for each domain :ref:`mapped in the database manager `, using integration with `Let's Encrypt Certificate Authority and ACME protocol `_." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:233 -msgid "The production launch" +#: ../../content/administration/maintain/domain_names.rst:252 +msgid "The certificate generation may take up to 24h." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:238 -msgid "Production goes live" +#: ../../content/administration/maintain/domain_names.rst:253 +msgid "Several attempts to validate your certificate are made during the five days following the moment you add your domain name in your database's settings." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:240 -msgid "The production upgrade request is when you decide to upgrade your current database with all your production data (invoices, VAT returns, inventories, current orders) to a new version of your choice." +#: ../../content/administration/maintain/domain_names.rst:255 +msgid "If you already use another service, you can keep using it or simply change for Odoo." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:243 -msgid "After your :ref:`tests ` are completed to your satisfaction, submit the request to upgrade your production database via our `website form `_. Select *Production* purpose." +#: ../../content/administration/maintain/domain_names.rst:260 +msgid "Web base URL of a database" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:252 -msgid "Going into production without first testing may lead to:" +#: ../../content/administration/maintain/domain_names.rst:262 +msgid "The **web base URL** of a database, or **root URL** affects your main website address and all the links sent to your customers (e.g., quotations, portal links, etc.)." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:254 -msgid "business interruptions (e.g. no longer having the possibility to validate an action)" +#: ../../content/administration/maintain/domain_names.rst:265 +msgid "To configure it, access your Odoo database with your custom address, then log in as an administrator of your database (any user in the *Settings* group) from the login screen." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:255 -msgid "poor customer experiences (e.g. an eCommerce website that does not work correctly)" +#: ../../content/administration/maintain/domain_names.rst:269 +msgid "Connecting to your database with the original Odoo subdomain address (e.g., ``example.odoo.com`` also updates the web base URL of your database. See below to prevent these automatic updates." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:262 -msgid "If you encounter issues or problems in the **production database**, please contact the **Odoo Support**:" +#: ../../content/administration/maintain/domain_names.rst:272 +msgid "Alternatively, you can do it manually. To do so, activate the :ref:`developer mode `, then go to :menuselection:`Settings --> Technical --> System Parameters`." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:266 -msgid "Under the *Ticket Description* section, select the appropriate type related to your issue but **do not select** the option *An issue related to my upgrade*." +#: ../../content/administration/maintain/domain_names.rst:275 +msgid "Find the key called ``web.base.url`` (or create it if it does not exist) and enter the full address of your website as value, such as ``https://www.example.com``." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:270 -msgid "After upgrading to production, the support will be provided by the Support team instead of the Upgrade team." +#: ../../content/administration/maintain/domain_names.rst:279 +msgid "The URL must include the protocol ``https://`` (or ``http://``) and must not end with a slash (``/``)." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:282 -msgid "If you choose *An issue related to my upgrade* as ticket type, the request will be redirected to another team than the support one and will slow down the processing and response time." +#: ../../content/administration/maintain/domain_names.rst:282 +msgid "To prevent the automatic update of the web base URL when an administrator logs in the database, you can create the following System Parameter:" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:288 -msgid "FAQ" +#: ../../content/administration/maintain/domain_names.rst:285 +msgid "key: ``web.base.url.freeze``" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:293 -msgid "Why upgrade?" +#: ../../content/administration/maintain/domain_names.rst:286 +msgid "value: ``True``" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:295 -msgid "You benefit from the latest features of the :ref:`new major version ` released by Odoo." +#: ../../content/administration/maintain/domain_names.rst:291 +msgid "Map your domain name with your website" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:297 -msgid "If you are in an :ref:`unsupported version `, you get a new version with support." +#: ../../content/administration/maintain/domain_names.rst:293 +msgid "Mapping your domain name to your website isn't the same as mapping it with your database:" msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:303 -msgid "When to upgrade?" +#: ../../content/administration/maintain/domain_names.rst:295 +msgid "It defines your domain name as the main one for your website, helping search engines to index your website properly." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:305 -msgid "Whenever you want. You can make your upgrade request as soon as a new version is released on our `website form `_." +#: ../../content/administration/maintain/domain_names.rst:297 +msgid "If you have multiple websites, it maps your domain name with the appropriate website." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:311 -msgid "Availability of the new version" +#: ../../content/administration/maintain/domain_names.rst:299 +msgid "Go to :menuselection:`Website --> Configuration --> Settings --> Website Info`. If you have multiple websites, select the one you want to configure." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:313 -msgid "Please kindly note that as soon as we announce the release of a new major version (usually at the end of year), the Upgrade Service team needs to adapt the upgrade scripts to it, which is why the new version is not immediately available for existing databases." +#: ../../content/administration/maintain/domain_names.rst:302 +msgid "In the :guilabel:`Domain` field, fill in the web address of your website (e.g., ``https://www.example.com``) and click on :guilabel:`Save`." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:320 -msgid "Finalization of the upgrade (:abbr:`ETA (Estimated Time of Arrival)`)" +#: ../../content/administration/maintain/domain_names.rst:310 +msgid "Mapping your domain name with your Odoo website prevents Google from indexing both your custom domain name ``www.example.com`` and your original odoo database address ``example.odoo.com``." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:322 -msgid "Unfortunately, it is impossible to give time estimates for every upgrade request. Odoo offers so many possibilities (e.g. branding, workflows, customization, etc) that it can get tricky to upgrade, and translate to the new structure. If you use multiple apps managing sensitive data (e.g., Accounting, Inventory, etc.), some cases may still require a human intervention, making the process slower." +#: ../../content/administration/maintain/domain_names.rst:313 +msgid "If both addresses are already indexed, it may take some time before Google removes the indexation of the second address. You may also try using the `Google Search Console `_ to fix this." msgstr "" -#: ../../content/administration/maintain/db_upgrade.rst:328 -msgid "This is especially true during the first months following the release of a new major version, which can significantly lengthen the upgrade delay." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:331 -msgid "In general, the ‘smaller’ the database, the quickest the upgrade. A single-user database that uses only CRM will be processed faster than a multi-company, multi-user database that uses Accounting, Sales, Purchase, and Manufacturing." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:335 -msgid "So, in a nutshell, what can impact your upgrade lead time?" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:337 -msgid "Source & targeted versions" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:338 -msgid "Installed apps" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:339 -msgid "Volume of data" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:340 -msgid "Amount of customization (models, fields, methods, workflows, reports, website, etc.)" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:341 -msgid "Installation of new apps or configuration changes after the start of the test phase" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:343 -msgid "Usually, the delays experienced during the first request (waiting time between the time you submitted your first request for a test upgrade) can generally give you an idea of the time to wait for the production request." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:350 -msgid "Upgrade of the custom modules" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:352 -msgid "As stated in our :doc:`/legal/terms/enterprise`, section :ref:`charges_standard`, this optional service is subject to additional fees." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:355 -msgid "If you have a custom code, you can choose to have it upgraded by our services, by one of our `partners `_ or you can do it yourself." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:363 -msgid "Editions change (from Community to Enterprise)" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:365 -msgid "An upgrade does not cover a change of `Editions `_" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:372 -msgid "Switching the hosting types (Self-hosted vs Online vs Odoo.sh)" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:374 -msgid "An upgrade does not cover a change of `Hosting types `_." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:376 -msgid "Open the following link to get :doc:`more information about how to change your hosting type `." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:384 -msgid "Release Notes by version" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:386 -msgid "Open our `Release Note `_ page to get a summary of the new features and improvements made in each version." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:397 -msgid "Contact our Upgrade service support" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:399 -msgid "Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo Upgrade Team `_. We will be very pleased to answer it as soon as possible." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:405 -#: ../../content/administration/maintain/supported_versions.rst:6 -msgid "Supported versions" -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:407 -msgid "Please note that Odoo provides support and bug fixing only for the three last major versions of Odoo." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:409 -msgid "This is a factor to take into consideration before upgrading. If you are on an older version, we suggest you to prefer the most recent version to benefit from a longer support (before having to upgrade again)." -msgstr "" - -#: ../../content/administration/maintain/db_upgrade.rst:413 -msgid "You can get more information about our :doc:`supported versions `." +#: ../../content/administration/maintain/domain_names.rst:318 +msgid ":doc:`/applications/general/email_communication/email_servers`" msgstr "" #: ../../content/administration/maintain/enterprise.rst:6 @@ -2149,7 +1875,6 @@ msgid "**If you have time constraints, contact us earlier to schedule the transf msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:19 -#: ../../content/administration/maintain/hosting_changes.rst:52 msgid "`Create a support ticket `_ and attach the dump (if the file is too large, use any file transfer service and attach the link to your ticket). Also include your subscription number and the URL you want to use for your database (e.g.: my-company.odoo.com)." msgstr "" @@ -2215,6 +1940,10 @@ msgstr "" msgid "Uninstall all the **non-standard apps**: test it in a staging build first, then do it in your production build." msgstr "" +#: ../../content/administration/maintain/hosting_changes.rst:52 +msgid "`Create a support ticket `_ and include your subscription number and the URL you want to use for your database (e.g.: my-company.odoo.com)." +msgstr "" + #: ../../content/administration/maintain/hosting_changes.rst:57 msgid "From Odoo.sh to on-premises" msgstr "" @@ -2223,234 +1952,640 @@ msgstr "" msgid "Grab a :ref:`backup of your Odoo.sh production database `." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:9 +#: ../../content/administration/maintain/on_premise.rst:3 +msgid "On-premise database management" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:6 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:8 +msgid "To register your database, you just need to enter your Subscription Code in the banner in the App Switcher. Make sure you do not add extra spaces before or after your subscription code. If the registration is successful, it will turn green and will provide you with the Expiration Date of your freshly-registered database. You can check this Expiration Date in the About menu (Odoo 9) or in the Settings Dashboard (Odoo 10)." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:16 +msgid "Registration Error Message" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:18 +msgid "If you are unable to register your database, you will likely encounter this message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:27 +#: ../../content/administration/maintain/on_premise.rst:106 +#: ../../content/administration/maintain/on_premise.rst:134 +msgid "Solutions" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:29 +msgid "Do you have a valid Enterprise subscription?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:31 +msgid "Check if your subscription details get the tag \"In Progress\" on your `Odoo Account `__ or with your Account Manager" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:35 +msgid "Have you already linked a database with your subscription reference?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:37 +msgid "You can link only one database per subscription. (Need a test or a development database? `Find a partner `__)" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:41 +msgid "You can unlink the old database yourself on your `Odoo Contract `__ with the button \"Unlink database\"" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:48 +msgid "A confirmation message will appear; make sure this is the correct database as it will be deactivated shortly:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:55 +msgid "Do you have the updated version of Odoo 9?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:57 +#: ../../content/administration/maintain/on_premise.rst:167 +msgid "From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a manual operation is no longer required." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:60 +msgid "If it's not the case, you may have multiple databases sharing the same UUID. Please check on your `Odoo Contract `__, a short message will appear specifying which database is problematic:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:69 +msgid "In this case, you need to change the UUID on your test databases to solve this issue. You will find more information about this in :ref:`this section `." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:72 +msgid "For your information, we identify database with UUID. Therefore, each database should have a distinct UUID to ensure that registration and invoicing proceed effortlessly for your and for us." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:76 +msgid "Check your network and firewall settings" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:78 +msgid "The Update notification must be able to reach Odoo's subscription validation servers. In other words, make sure that the Odoo server is able to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:82 +msgid "services.odoo.com on port 443 (or 80)" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:83 +msgid "services.openerp.com on port 443 (or 80) for older deployments" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:85 +msgid "Once you activated your database, you must keep these ports open, as the Update notification runs once a week." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:91 +msgid "Error message due to too many users" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:93 +msgid "If you have more users in your local database than provisionned in your Odoo Enterprise subscription, you may encounter this message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:102 +msgid "When the message appears you have 30 days before the expiration. The countdown is updated everyday." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:108 +msgid "**Add more users** on your subscription: follow the link and Validate the upsell quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:110 +msgid "**Deactivate users** as explained in this `documentation `_ and **Reject** the upsell quotation." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:113 +msgid "Once your database has the correct number of users, the expiration message will disappear automatically after a few days, when the next verification occurs. We understand that it can be a bit frightening to see the countdown, so you can :ref:`force an Update Notification ` to make the message disappear right away." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:120 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:122 +msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:130 +msgid "This **blocking** message appears after a non-blocking message that lasts 30 days. If you fail to take action before the end of the countdown, the database is expired." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:138 +msgid "Renew your subscription: follow the link and renew your subscription - note that" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:137 +msgid "if you wish to pay by Wire Transfer, your subscription will effectively be renewed only when the payment arrives, which can take a few days. Credit card payments are processed immediately." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:140 +msgid "Contact our `Support `__" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:142 +msgid "None of those solutions worked for you? Please contact our `Support `__" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:151 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:153 +msgid "You can duplicate your database by accessing the database manager on your server (/web/database/manager). In this page, you can easily duplicate your database (among other things)." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:161 +msgid "When you duplicate a local database, it is **strongly** advised to change the duplicated database's uuid (Unniversally Unique Identifier), since this uuid is how your database identifies itself with our servers. Having two databases with the same uuid could result in invoicing problems or registration problems down the line." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:170 +msgid "The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical --> System Parameters`, we advise you to use a `uuid generator `_ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button." +msgstr "" + +#: ../../content/administration/maintain/online.rst:3 +msgid "Online (SaaS) database management" +msgstr "" + +#: ../../content/administration/maintain/online.rst:5 +msgid "To manage a database, sign in to https://www.odoo.com and access the `database management page `_ by clicking on the user icon, then on *My Databases*." +msgstr "" + +#: ../../content/administration/maintain/online.rst:13 +msgid "Make sure you are connected as the administrator of the database you want to manage." +msgstr "" + +#: ../../content/administration/maintain/online.rst:19 +msgid "Open the drop-down menu next to the database you want to manage by clicking on the gear icon." +msgstr "" + +#: ../../content/administration/maintain/online.rst:21 +msgid "Several actions are available:" +msgstr "" + +#: ../../content/administration/maintain/online.rst:23 +msgid ":ref:`online/upgrade`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:24 +msgid ":ref:`online/duplicate`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:25 +msgid ":ref:`online/rename`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:26 +msgid ":ref:`online/download`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:27 +msgid ":ref:`online/domains`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:28 +msgid ":ref:`online/tags`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:29 +msgid ":ref:`online/delete`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:30 +msgid ":ref:`online/contact-support`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:31 +msgid ":ref:`online/users`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:36 +#: ../../content/administration/upgrade.rst:5 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/maintain/online.rst:38 +msgid "If you are *not* on the latest **Online version**, you should receive an invitation to :doc:`upgrade <../upgrade/process>` your database. A **Rolling Release button** on your database's main screen proposes an upgrade to the latest version (e.g., 13.0 to 15.1)." +msgstr "" + +#: ../../content/administration/maintain/online.rst:0 +msgid "**If your Odoo database's version is lower than the latest major release:**" +msgstr "" + +#: ../../content/administration/maintain/online.rst:0 +msgid "You must upgrade your database within two months. After these two months, an automatic upgrade is initiated." +msgstr "" + +#: ../../content/administration/maintain/online.rst:0 +msgid "**If your Odoo database's version is equal to or higher than the latest major release:**" +msgstr "" + +#: ../../content/administration/maintain/online.rst:0 +msgid "You can disregard the invitation to upgrade as you probably wouldn't benefit from new features every two months." +msgstr "" + +#: ../../content/administration/maintain/online.rst:51 +msgid "Versions that are not supported anymore become deprecated and need to be updated to avoid security issues. We recommend you initiate the upgrade of the database yourself, as this method allows you to request a test upgrade of your database to check for any discrepancies." +msgstr "" + +#: ../../content/administration/maintain/online.rst:56 +msgid ":doc:`../upgrade/process`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:57 +msgid ":doc:`supported_versions`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:62 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/maintain/online.rst:64 +msgid "Make an exact copy of the database to be able to perform testing without compromising the daily operations." +msgstr "" + +#: ../../content/administration/maintain/online.rst:68 +msgid "By checking *For testing purposes*, all external communication (emails, payments, delivery orders, etc.) are disabled by default on the duplicated database." +msgstr "" + +#: ../../content/administration/maintain/online.rst:70 +msgid "Duplicate databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/maintain/online.rst:75 +msgid "Rename" +msgstr "" + +#: ../../content/administration/maintain/online.rst:77 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/maintain/online.rst:82 +msgid "Download" +msgstr "" + +#: ../../content/administration/maintain/online.rst:84 +msgid "Download instantly a ZIP file with a backup of the database." +msgstr "" + +#: ../../content/administration/maintain/online.rst:87 +msgid "Databases are backed up daily according to the `Odoo Cloud SLA `_." +msgstr "" + +#: ../../content/administration/maintain/online.rst:93 +msgid "Domains" +msgstr "" + +#: ../../content/administration/maintain/online.rst:95 +msgid "Configure custom domains to access the database via another URL." +msgstr "" + +#: ../../content/administration/maintain/online.rst:98 +msgid ":doc:`domain_names`" +msgstr "" + +#: ../../content/administration/maintain/online.rst:103 +msgid "Tags" +msgstr "" + +#: ../../content/administration/maintain/online.rst:105 +msgid "Add tags to sort your databases out. You can search the tags in the search bar." +msgstr "" + +#: ../../content/administration/maintain/online.rst:110 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "Delete" +msgstr "" + +#: ../../content/administration/maintain/online.rst:112 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/maintain/online.rst:115 +msgid "Deleting a database means that all data is permanently lost. The deletion is instant and for all users. It is recommended to create a backup of the database before deleting it." +msgstr "" + +#: ../../content/administration/maintain/online.rst:118 +msgid "Read carefully the warning message that pops up and proceed only if you fully understand the implications of deleting a database:" +msgstr "" + +#: ../../content/administration/maintain/online.rst:126 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/maintain/online.rst:127 +msgid "The database name is immediately available for a new database." +msgstr "" + +#: ../../content/administration/maintain/online.rst:128 +msgid "It is not possible to delete a database if it is expired or linked to a subscription. If needed, please get in touch with `Odoo Support `_." +msgstr "" + +#: ../../content/administration/maintain/online.rst:130 +msgid "To delete your account, please get in touch with `Odoo Support `_." +msgstr "" + +#: ../../content/administration/maintain/online.rst:135 +msgid "Contact Support" +msgstr "" + +#: ../../content/administration/maintain/online.rst:137 +msgid "Access the Odoo `support page `_ with your database's details already pre-filled." +msgstr "" + +#: ../../content/administration/maintain/online.rst:143 +msgid "Invite / Remove Users" +msgstr "" + +#: ../../content/administration/maintain/online.rst:145 +msgid "To invite users, fill out the email address of the new user and click on *Invite*. To add multiple users, click on *Add more users*." +msgstr "" + +#: ../../content/administration/maintain/online.rst:152 +msgid "To remove users, select the users to remove and click on *Remove*." +msgstr "" + +#: ../../content/administration/maintain/online.rst:155 +msgid ":doc:`/applications/general/users/manage_users`" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:6 +#: ../../content/administration/upgrade/process.rst:241 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:8 msgid "Odoo provides support and bug fixing **for the 3 last major versions** of Odoo." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:11 -msgid "Users hosted on **Odoo Online** may use intermediary versions (sometimes called *SaaS versions*) that are supported as well. These versions are not published for Odoo.sh or On-Premise installations." +msgid "Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online ` hosting every two months. Odoo Online users can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:14 +msgid "Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade/process>` them regularly." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:16 +msgid "Online versions are *not* released for Odoo.sh and On-Premise installations." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:17 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:20 msgid "What's the support status of my Odoo?" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:19 +#: ../../content/administration/maintain/supported_versions.rst:22 msgid "This matrix shows the support status of every version." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:21 +#: ../../content/administration/maintain/supported_versions.rst:24 msgid "**Major releases are in bold type.**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:24 -msgid "Odoo Online" +#: ../../content/administration/maintain/supported_versions.rst:27 +msgid "On-Premise" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:24 +#: ../../content/administration/maintain/supported_versions.rst:27 msgid "Release date" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:26 -msgid "**Odoo 14.0**" +#: ../../content/administration/maintain/supported_versions.rst:27 +msgid "End of support" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:26 -#: ../../content/administration/maintain/supported_versions.rst:26 -#: ../../content/administration/maintain/supported_versions.rst:26 -#: ../../content/administration/maintain/supported_versions.rst:28 -#: ../../content/administration/maintain/supported_versions.rst:30 -#: ../../content/administration/maintain/supported_versions.rst:30 -#: ../../content/administration/maintain/supported_versions.rst:30 -#: ../../content/administration/maintain/supported_versions.rst:32 -#: ../../content/administration/maintain/supported_versions.rst:34 -#: ../../content/administration/maintain/supported_versions.rst:34 -#: ../../content/administration/maintain/supported_versions.rst:34 +#: ../../content/administration/maintain/supported_versions.rst:29 +msgid "Odoo 15.saas~1" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:29 +#: ../../content/administration/maintain/supported_versions.rst:31 +#: ../../content/administration/maintain/supported_versions.rst:31 +#: ../../content/administration/maintain/supported_versions.rst:31 +#: ../../content/administration/maintain/supported_versions.rst:33 +#: ../../content/administration/maintain/supported_versions.rst:33 +#: ../../content/administration/maintain/supported_versions.rst:33 +#: ../../content/administration/maintain/supported_versions.rst:35 +#: ../../content/administration/maintain/supported_versions.rst:35 +#: ../../content/administration/maintain/supported_versions.rst:35 msgid "|green|" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:26 -msgid "October 2020" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:28 -msgid "Odoo 13.saas~4" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:28 -#: ../../content/administration/maintain/supported_versions.rst:28 -#: ../../content/administration/maintain/supported_versions.rst:32 -#: ../../content/administration/maintain/supported_versions.rst:32 -#: ../../content/administration/maintain/supported_versions.rst:36 -#: ../../content/administration/maintain/supported_versions.rst:36 -#: ../../content/administration/maintain/supported_versions.rst:40 -#: ../../content/administration/maintain/supported_versions.rst:40 -#: ../../content/administration/maintain/supported_versions.rst:42 -#: ../../content/administration/maintain/supported_versions.rst:42 -#: ../../content/administration/maintain/supported_versions.rst:46 -#: ../../content/administration/maintain/supported_versions.rst:46 -#: ../../content/administration/maintain/supported_versions.rst:48 -#: ../../content/administration/maintain/supported_versions.rst:50 -#: ../../content/administration/maintain/supported_versions.rst:50 -#: ../../content/administration/maintain/supported_versions.rst:52 +#: ../../content/administration/maintain/supported_versions.rst:29 +#: ../../content/administration/maintain/supported_versions.rst:29 +#: ../../content/administration/maintain/supported_versions.rst:37 +#: ../../content/administration/maintain/supported_versions.rst:37 +#: ../../content/administration/maintain/supported_versions.rst:41 +#: ../../content/administration/maintain/supported_versions.rst:41 +#: ../../content/administration/maintain/supported_versions.rst:45 +#: ../../content/administration/maintain/supported_versions.rst:45 +#: ../../content/administration/maintain/supported_versions.rst:47 +#: ../../content/administration/maintain/supported_versions.rst:47 +#: ../../content/administration/maintain/supported_versions.rst:51 +#: ../../content/administration/maintain/supported_versions.rst:51 +#: ../../content/administration/maintain/supported_versions.rst:53 +#: ../../content/administration/maintain/supported_versions.rst:55 +#: ../../content/administration/maintain/supported_versions.rst:55 +#: ../../content/administration/maintain/supported_versions.rst:57 msgid "N/A" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:28 -#: ../../content/administration/maintain/supported_versions.rst:32 -msgid "August 2019" +#: ../../content/administration/maintain/supported_versions.rst:29 +msgid "February 2022" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:30 +#: ../../content/administration/maintain/supported_versions.rst:31 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:31 +#: ../../content/administration/maintain/supported_versions.rst:39 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:31 +msgid "October 2024 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:33 +msgid "**Odoo 14.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:33 +#: ../../content/administration/maintain/supported_versions.rst:43 +msgid "October 2020" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:33 +msgid "October 2023 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:35 msgid "**Odoo 13.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:30 +#: ../../content/administration/maintain/supported_versions.rst:35 +#: ../../content/administration/maintain/supported_versions.rst:49 msgid "October 2019" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:32 +#: ../../content/administration/maintain/supported_versions.rst:35 +msgid "October 2022 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:37 msgid "Odoo 12.saas~3" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:34 -msgid "**Odoo 12.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:34 -msgid "October 2018" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:34 -msgid "*End-of-support is planned for October 2021*" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:36 -msgid "Odoo 11.saas~3" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:36 -#: ../../content/administration/maintain/supported_versions.rst:38 -#: ../../content/administration/maintain/supported_versions.rst:38 -#: ../../content/administration/maintain/supported_versions.rst:40 -#: ../../content/administration/maintain/supported_versions.rst:42 -#: ../../content/administration/maintain/supported_versions.rst:44 -#: ../../content/administration/maintain/supported_versions.rst:44 -#: ../../content/administration/maintain/supported_versions.rst:46 -#: ../../content/administration/maintain/supported_versions.rst:48 -#: ../../content/administration/maintain/supported_versions.rst:50 -#: ../../content/administration/maintain/supported_versions.rst:52 -msgid "|orange|" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:36 -msgid "April 2018" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:38 -msgid "**Odoo 11.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:38 -#: ../../content/administration/maintain/supported_versions.rst:44 -#: ../../content/administration/maintain/supported_versions.rst:48 -#: ../../content/administration/maintain/supported_versions.rst:52 +#: ../../content/administration/maintain/supported_versions.rst:37 +#: ../../content/administration/maintain/supported_versions.rst:39 +#: ../../content/administration/maintain/supported_versions.rst:39 +#: ../../content/administration/maintain/supported_versions.rst:39 +#: ../../content/administration/maintain/supported_versions.rst:41 +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:45 +#: ../../content/administration/maintain/supported_versions.rst:47 +#: ../../content/administration/maintain/supported_versions.rst:49 +#: ../../content/administration/maintain/supported_versions.rst:49 +#: ../../content/administration/maintain/supported_versions.rst:49 +#: ../../content/administration/maintain/supported_versions.rst:51 +#: ../../content/administration/maintain/supported_versions.rst:53 +#: ../../content/administration/maintain/supported_versions.rst:53 +#: ../../content/administration/maintain/supported_versions.rst:55 +#: ../../content/administration/maintain/supported_versions.rst:57 +#: ../../content/administration/maintain/supported_versions.rst:57 msgid "|red|" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:38 +#: ../../content/administration/maintain/supported_versions.rst:37 +msgid "August 2019" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:39 +msgid "**Odoo 12.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:39 +#: ../../content/administration/maintain/supported_versions.rst:53 +msgid "October 2018" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:41 +msgid "Odoo 11.saas~3" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:41 +msgid "April 2018" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:43 +msgid "**Odoo 11.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:57 msgid "October 2017" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:40 +#: ../../content/administration/maintain/supported_versions.rst:45 msgid "Odoo 10.saas~15" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:40 +#: ../../content/administration/maintain/supported_versions.rst:45 msgid "March 2017" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:42 +#: ../../content/administration/maintain/supported_versions.rst:47 msgid "Odoo 10.saas~14" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:42 +#: ../../content/administration/maintain/supported_versions.rst:47 msgid "January 2017" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:44 +#: ../../content/administration/maintain/supported_versions.rst:49 msgid "**Odoo 10.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:44 +#: ../../content/administration/maintain/supported_versions.rst:49 msgid "October 2016" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:46 +#: ../../content/administration/maintain/supported_versions.rst:51 msgid "Odoo 9.saas~11" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:46 +#: ../../content/administration/maintain/supported_versions.rst:51 msgid "May 2016" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:48 +#: ../../content/administration/maintain/supported_versions.rst:53 msgid "**Odoo 9.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:48 +#: ../../content/administration/maintain/supported_versions.rst:53 msgid "October 2015" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:50 +#: ../../content/administration/maintain/supported_versions.rst:55 msgid "Odoo 8.saas~6" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:50 +#: ../../content/administration/maintain/supported_versions.rst:55 msgid "February 2015" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:52 +#: ../../content/administration/maintain/supported_versions.rst:57 msgid "**Odoo 8.0**" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:52 +#: ../../content/administration/maintain/supported_versions.rst:57 msgid "September 2014" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:58 +#: ../../content/administration/maintain/supported_versions.rst:62 msgid "|green| Supported version" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:60 +#: ../../content/administration/maintain/supported_versions.rst:64 msgid "|red| End-of-support" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:62 +#: ../../content/administration/maintain/supported_versions.rst:66 msgid "N/A Never released for this platform" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:64 -msgid "|orange| Some of our older customers may still run this version on our Odoo Online servers, we provide help only on blocking issues and advise you to upgrade." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:66 +#: ../../content/administration/maintain/supported_versions.rst:68 msgid "🏁 Future version, not released yet" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:79 +#: ../../content/administration/maintain/supported_versions.rst:80 msgid "I run an older version of Odoo/OpenERP/TinyERP" msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:81 +#: ../../content/administration/maintain/supported_versions.rst:82 msgid "OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:83 +#: ../../content/administration/maintain/supported_versions.rst:84 msgid "TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform." msgstr "" -#: ../../content/administration/maintain/supported_versions.rst:85 +#: ../../content/administration/maintain/supported_versions.rst:86 msgid "Even though we don't support older versions, you can always `upgrade from any version `_." msgstr "" @@ -2606,6 +2741,19 @@ msgstr "" msgid "Containers" msgstr "" +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:7 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:7 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:7 +#: ../../content/administration/odoo_sh/getting_started/status.rst:7 +#: ../../content/administration/odoo_sh/overview.rst:5 +#: ../../content/administration/upgrade/process.rst:13 +msgid "Overview" +msgstr "" + #: ../../content/administration/odoo_sh/advanced/containers.rst:9 msgid "Each build is isolated within its own container (Linux namespaced container)." msgstr "" @@ -2946,64 +3094,9 @@ msgstr "" msgid "If you're adding a repository that contains a lot of modules, you may want to ignore some of them in case there are any that are installed automatically. To do so, you can prefix your submodule folder with a :code:`.`. The platform will ignore this folder and you can hand pick your modules by creating symlinks to them from another folder." msgstr "" -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:4 -msgid "Upgrade your database" -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:9 -msgid "Download and Upload your database" -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:11 -msgid "Download a dump of your database (from the :ref:`Builds view `), choose the exact copy and without filestore options. Upload the .sql.gz dump on https://upgrade.odoo.com/upload and select the Testing Purpose. If you have custom code, you can choose to have it upgraded by us, or do it yourself. Once it's processed, you'll get a dump of the database in return." -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:17 -msgid "Do *not* upload *backups* of your production database (found in the Backups tab of the production branch) as these are incompatible with the Upgrade platform - they contain your complete sources, etc. that are not needed for the upgrade. Make sure to download a **Dump** instead - either through the Backups tab using the *Download Dump* button or through the Builds page by using the *Download Dump* entry of the contextual menu of your latest production build." -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:23 -msgid "Test your upgraded database" -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:25 -msgid "Create a staging branch that will run the upgraded database. Either make sure your production branch's code is compatible between the two Odoo versions and fork your production branch, or make a new staging branch containing the upgraded code." -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:29 -msgid "Once the staging build is done (it doesn't matter if it failed due to the version incompatibility), import your upgraded dump in the backups tab of the branch. The platform will automatically detect the version of the dump and change the version of Odoo's source code to the corresponding version for the build." -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:33 -msgid "Test the upgraded database and make sure everything runs as it's supposed to." -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:36 -msgid "Replace your existing production database" -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:38 -msgid "Once you've tested everything and you're satisfied, start the process over to get an up-to-date upgraded dump:" -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:40 -msgid "Make a new dump of your production database (as described in step 1)" -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:41 -msgid "Upload it on upgrade.odoo.com and select the Production purpose" -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:42 -msgid "Receive the newly upgraded dump and import it in your production branch. The build might get marked as failed because the platform will run it with the upgraded databases' Odoo version together with the old custom code." -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:44 -msgid "Merge or commit the upgraded custom code in the production branch" -msgstr "" - -#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:46 -msgid "If anything goes wrong, remember you can restore a backup. The platform will always make one before you make any Odoo.sh operation on the production database. If the restored backup comes from a previous version, the platform will detect it and change the project's Odoo version back if it needs to." +#: ../../content/administration/odoo_sh/getting_started.rst:5 +#: ../../content/administration/upgrade/process.rst:53 +msgid "Get started" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:4 @@ -3245,102 +3338,102 @@ msgstr "" msgid "You can zoom, change the time range or select a specific metric on each graph. On the graphs, annotations help you relate to changes on the build (database import, git push, etc...)." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:217 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 #: ../../content/administration/odoo_sh/getting_started/settings.rst:56 #: ../../content/administration/odoo_sh/getting_started/settings.rst:68 msgid "Logs" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:218 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:220 msgid "A viewer to have a look to your server logs." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:223 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 msgid "Different logs are available:" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 msgid "install.log: The logs of the database installation. In a development branch, the logs of the tests are included." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:226 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:228 msgid "pip.log: The logs of the Python dependencies installation." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:229 msgid "odoo.log: The logs of the running server." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:228 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:230 msgid "update.log: The logs of the database updates." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:229 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:231 msgid "pg_long_queries.log: The logs of psql queries that take an unusual amount of time." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:231 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:233 msgid "If new lines are added in the logs, they will be displayed automatically. If you scroll to the bottom, the browser will scroll automatically each time a new line is added." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 msgid "You can pause the logs fetching by clicking on the according button in the upper right corner of the view. The fetching is automatically stopped after 5 minutes. You can restart it using the play button." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:242 #: ../../content/administration/odoo_sh/getting_started/settings.rst:76 msgid "Backups" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:241 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 msgid "A list of the backups available for download and restore, the ability to perform a manual backup and to import a database." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:247 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 msgid "Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 weekly and 3 monthly backups. Each backup includes the database dump, the filestore (attachments, binary fields), logs and sessions." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:250 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:252 msgid "Staging and development databases are not backed up. You nevertheless have the possibility to restore a backup of the production database in your staging branches, for testing purposes, or to manually recover data that has been deleted by accident from the production database." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:254 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:256 msgid "The list contains the backups kept on the server your production database is hosted on. This server only keeps one month of backups: 7 daily and 4 weekly backups." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:259 msgid "Dedicated backup servers keep the same backups, as well as 3 additional monthly backups. To restore or download one of these monthly backups, please `contact us `_." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:262 msgid "If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list), as either the container will be changed by the installation of new pip packages, either the database itself will be changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially break things." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:266 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:268 msgid "If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course, as an extra precaution, you can make a backup manually before making big changes in your production sources in case something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups to 5 per day." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:272 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:274 msgid "The *import database* feature accepts database archives in the format provided by:" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:274 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 msgid "the standard Odoo databases manager, (available for on-premise Odoo servers under :code:`/web/database/manager`)" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:278 msgid "the Odoo online databases manager," msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:277 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:279 msgid "the Odoo.sh backup download button of this *Backups* tab," msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:278 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:280 msgid "the Odoo.sh dump download button in the :ref:`Builds view `." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:283 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:285 #: ../../content/administration/odoo_sh/getting_started/settings.rst:4 #: ../../content/administration/odoo_sh/getting_started/settings.rst:62 #: ../../content/administration/odoo_sh/getting_started/settings.rst:78 @@ -3348,304 +3441,300 @@ msgstr "" msgid "Settings" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 msgid "Here you can find a couple of settings that only apply to the currently selected branch." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:289 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:291 msgid "**Behaviour upon new commit**" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:291 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 msgid "For development and staging branches, you can change the branch's behavior upon receiving a new commit. By default, a development branch will create a new build and a staging branch will update the previous build (see the :ref:`Production Stage `). This is especially useful should the feature you're working on require a particular setup or configuration, to avoid having to manually set it up again on every commit. If you choose new build for a staging branch, it will make a fresh copy from the production build every time a commit is pushed. A branch that is put back from staging to development will automatically be set to 'Do nothing'." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:299 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:301 msgid "**Modules installation**" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:301 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 msgid "Choose the modules to install automatically for your development builds." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:306 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:308 msgid "*Install only my modules* will install the modules of the branch only. This is the default option. The :ref:`submodules ` are excluded." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:308 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 msgid "*Full installation (all modules)* will install the modules of the branch, the modules included in the submodules and all standard modules of Odoo. When running the full installation, the test suite is disabled." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 msgid "*Install a list of modules* will install the modules specified in the input just below this option. The names are the technical name of the modules, and they must be comma-separated." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:313 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:315 msgid "If the tests are enabled, the standard Odoo modules suite can take up to 1 hour. This setting applies to development builds only. Staging builds duplicate the production build and the production build only installs base." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:318 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 msgid "**Test suite**" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 msgid "For development branches, you can choose to enable or disable the test suite. It's enabled by default. When the test suite is enabled, you can restrict them by specifying test tags :ref:`test tags `." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:324 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:326 msgid "**Odoo Version**" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:326 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:328 msgid "For development branches only, you can change the version of Odoo, should you want to test upgraded code or develop features while your production database is in the process of being upgraded to a newer version." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 msgid "In addition, for each version you have two options regarding the code update." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:333 msgid "You can choose to benefit from the latest bug, security and performance fixes automatically. The sources of your Odoo server will be updated weekly. This is the 'Latest' option." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:333 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:335 msgid "You can choose to pin the Odoo sources to a specific revision by selecting them from a list of dates. Revisions will expire after 3 months. You will be notified by mail when the expiration date approaches and if you don't take action afterwards, you will automatically be set to the latest revision." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:338 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:340 msgid "**Custom domains**" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:340 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:342 msgid "Here you can configure additional domains for the selected branch. It's possible to add other *.odoo.com* domains or your own custom domains. For the latter you have to:" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:343 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 msgid "own or purchase the domain name," msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:344 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:346 msgid "add the domain name in this list," msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 msgid "in your registrar's domain name manager, configure the domain name with a ``CNAME`` record set to your production database domain name." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:348 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 msgid "For instance, to associate *www.mycompany.com* to your database *mycompany.odoo.com*:" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 msgid "in Odoo.sh, add *www.mycompany.com* in the custom domains of your project settings," msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:351 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:353 msgid "in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), configure *www.mycompany.com* with a ``CNAME`` record with as value *mycompany.odoo.com*." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:356 msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:356 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:358 msgid "they can only be configured using ``A`` records," msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:357 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 msgid "``A`` records only accept IP addresses as value," msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:358 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:360 msgid "the IP address of your database can change, following an upgrade, a hardware failure or your wish to host your database in another country or continent." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:363 msgid "Therefore, bare domains could suddenly no longer work because of this change of IP address." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:363 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 msgid "In addition, if you would like both *mycompany.com* and *www.mycompany.com* to work with your database, having the first redirecting to the second is amongst the `SEO best practices `_ (See *Provide one version of a URL to reach a document*) in order to have one dominant URL. You can therefore just configure *mycompany.com* to redirect to *www.mycompany.com*. Most domain managers have the feature to configure this redirection. This is commonly called a web redirection." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:370 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 msgid "**HTTPS/SSL**" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:374 msgid "If the redirection is correctly set up, the platform will automatically generate an SSL certificate with `Let's Encrypt `_ within the hour and your domain will be accessible through HTTPS." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:376 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 msgid "While it is currently not possible to configure your own SSL certificates on the Odoo.sh platform we are considering the feature if there is enough demand." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:380 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 msgid "**SPF and DKIM compliance**" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 -msgid "In case the domain of your users email addresses use SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize Odoo as a sending host in your domain name settings to increase the deliverability of your outgoing emails. The configuration steps are explained in the :ref:`Discuss app documentation `." +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "In case the domain of your users email addresses use SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize Odoo as a sending host in your domain name settings to increase the deliverability of your outgoing emails. The configuration steps are explained in the documentation about :ref:`SPF ` and :ref:`DKIM `." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:388 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:392 msgid "Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host can lead to the delivery of your emails as spam in your contacts inbox." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 msgid "Shell commands" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:394 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:398 msgid "In the top right-hand corner of the view, different shell commands are available." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:399 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 msgid "Each command can be copied in the clipboard to be used in a terminal, and some of them can be used directly from Odoo.sh by clicking the *run* button in such case a popup will prompt the user in order to define eventual placeholders such as ````, ````, ..." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:405 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:409 msgid "Clone" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:406 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 msgid "Download the Git repository." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:412 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 msgid "Clones the repository *odoo/odoo*." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:418 msgid ":code:`--recurse-submodules`: Downloads the submodules of your repository. Submodules included in the submodules are downloaded as well." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:415 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:419 msgid ":code:`--branch`: checks out a specific branch of the repository, in this case *master*." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:417 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 msgid "The *run* button is not available for this command, as it is meant to be used on your machines." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:420 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:424 msgid "Fork" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:425 msgid "Create a new branch based on the current branch." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:431 msgid "Creates a new branch called *feature-1* based on the branch *master*, and then checkouts it." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:433 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 msgid "Uploads the new branch *feature-1* on your remote repository." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:436 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 msgid "Merge" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:441 msgid "Merge the current branch in another branch." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:447 msgid "Merges the branch *staging-1* in the current branch." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:449 -#: ../../content/administration/odoo_sh/getting_started/branches.rst:521 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:453 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:525 msgid "Uploads the changes you just added in the *master* branch on your remote repository." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:452 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:456 msgid "SSH" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:454 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:458 msgid "Setup" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:455 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:459 msgid "In order to use SSH, you have to set up your profile SSH public key (if it is not already done). To do so, follow these steps:" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:458 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 msgid "`Generate a new SSH key `_" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:464 msgid "`Copy the SSH key to your clipboard `_ (only apply the step 1)" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:463 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:467 msgid "Paste the copied content to your profile SSH keys and press \"Add\"" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:472 msgid "The key should appear below" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:478 msgid "Connection" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:476 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 msgid "To connect to your builds using ssh use the following command in a terminal:" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:486 msgid "You will find a shortcut for this command into the SSH tab in the upper right corner." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:491 msgid "Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the build." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:491 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 msgid "Long running ssh connections are not guaranteed. Idle connections will be disconnected in order to free up resources." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:496 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:500 msgid "Submodule" msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:498 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:502 msgid "Add a branch from another repository in your current branch as a *submodule*." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:500 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:504 msgid "*Submodules* allows you to use modules from other repositories in your project." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:502 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:506 msgid "The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:513 msgid "Adds the branch *master* of the repository ** as a submodule under the path ** in your current branch." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:515 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:519 msgid "Commits all your current changes." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 -msgid "Delete" -msgstr "" - -#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:530 msgid "Delete a branch from your repository." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:532 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:536 msgid "Deletes the branch in your remote repository." msgstr "" -#: ../../content/administration/odoo_sh/getting_started/branches.rst:538 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:542 msgid "Deletes the branch in your local copy of the repository." msgstr "" @@ -3990,7 +4079,7 @@ msgid "The imported database is considered a duplicate by default and the enterp msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:185 -msgid "If you plan to make it your production, unlink your former database from the subscription, and register the newly imported database. Read the :ref:`database registration documentation ` for instructions." +msgid "If you plan to make it your production, unlink your former database from the subscription, and register the newly imported database. Read the :doc:`database registration documentation <../../maintain/on_premise>` for instructions." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:4 @@ -4886,3 +4975,608 @@ msgstr "" #: ../../content/administration/odoo_sh/overview/introduction.rst:11 msgid "The documentation will help you go live with your Odoo.sh project in no time." msgstr "" + +#: ../../content/administration/upgrade/faq.rst:8 +msgid "FAQ" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:13 +msgid "Why upgrade" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:15 +msgid "You benefit from the latest features of the :ref:`new major version ` released by Odoo." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:17 +msgid "If you are in an :ref:`unsupported version `, you get a new version with support." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:23 +msgid "When to upgrade" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:25 +msgid "Whenever you want. You can make your upgrade request as soon as a new version is released or when your version turns unsupported, and you still wish to enjoy support." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:31 +msgid "Availability of the new version" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:33 +msgid "As soon as Odoo announces the release of a new major version, you can create a test upgrade request to try the latest version. Please note that at this point, the upgrade scripts will only have been tested with demo data. Please report any issue you might encounter while testing via the `Odoo Support page `_ and make sure to be happy with your test version before requesting the upgrade of your database in production." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:42 +msgid "Duration of the upgrade" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:44 +msgid "It is impossible to give time estimates for every upgrade request." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:46 +msgid "In general, the \"smaller\" the database, the quickest the upgrade request is completed. A single-user database that uses only CRM will be processed faster than a multi-company, multi-user database that uses Accounting, Sales, Purchase, and Manufacturing." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:50 +msgid "You can expect the time it takes for the platform to upgrade the test database will be similar to the production upgrade." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:56 +msgid "The upgrade project" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:58 +msgid "It depends on the user involvement (the time spent on testing, reporting problems, etc.) and the issues encountered that might need to be addressed by our technical team." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:61 +msgid "So, in a nutshell, what can impact your upgrade lead time?" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:63 +msgid "Source & targeted versions" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:64 +msgid "Installed apps" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:65 +msgid "Volume of data" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:66 +msgid "Amount of customization (models, fields, methods, workflows, reports, website, etc.)" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:67 +msgid "Installation of new apps or configuration changes after the start of the test phase" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:68 +msgid "User commitment" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:73 +msgid "Upgrade of the custom modules" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:75 +msgid "As stated in our :doc:`/legal/terms/enterprise`, section :ref:`charges_standard`, this optional service is subject to additional fees." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:78 +msgid "Depending on your situation, the custom code could be upgraded by our services, by one of our partners, or you can do it yourself." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:81 +#: ../../content/administration/upgrade/faq.rst:91 +#: ../../content/administration/upgrade/faq.rst:106 +#: ../../content/administration/upgrade/process.rst:24 +#: ../../content/administration/upgrade/process.rst:168 +#: ../../content/administration/upgrade/service_level.rst:37 +msgid "|assistance-contact|" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:86 +msgid "Editions change (from Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:88 +msgid "The upgrade always returns an Enterprise edition of Odoo, whether the database you sent was a community or enterprise edition. It is required to have an enterprise subscription to upgrade." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:94 +msgid "`Editions `_" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:99 +msgid "Switching the hosting types (Self-Hosting vs. Online Hosting - SaaS vs. Cloud Platform - Odoo.sh)" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:101 +msgid "An upgrade does not cover a change of `Hosting types `_." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:103 +msgid "Open the following link to get :doc:`more information about how to change your hosting type <../maintain/hosting_changes>`." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:111 +msgid "Release Notes by version" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:113 +msgid "Open our `Release Note `_ page to get a summary of the new features and improvements made in each version." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:117 +msgid "How long is my test available for" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:119 +msgid "An Odoo Online (SaaS) test database is available for one month by default. We can extend this trial period upon request. For Odoo.sh or on-premise, there is no restriction." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:123 +msgid "How many tests to perform before upgrading to production?" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:125 +msgid "As many as needed. When you are comfortable with the database, run a last test upgrade 48 hours before requesting your production upgrade and test your workflows one last time." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:129 +msgid "How to/Where to report upgrade issues?" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:131 +msgid "If you encounter issues during the upgrade process, please contact the Odoo Support through the `Odoo Support page `_" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:134 +msgid "To report an issue discovered during the testing phase, please select **An issue related to my upgrade (test phase)**." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:136 +msgid "To report an issue discovered post-upgrade, please select **An issue related to my upgrade (production)**" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:140 +msgid "Upgrading to production" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:142 +msgid "Once you have completed testing and are happy with the result, you decide on a date and time when you stop users from accessing Odoo, freeze all data entries, and create an upgrade request for the production upgrade." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:148 +msgid "How is my data handled in the Upgrade Platform?" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:150 +msgid "The Odoo Upgrade platform uses the same Privacy Policy as the rest of Odoo.com services." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:152 +msgid "Your data is hosted on servers that follow our security guidelines, namely:" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:154 +msgid "SSL - All web connections to client instances are protected with 256-bit SSL encryption (HTTPS with a 2048-bit modulus SSL certificate), and running behind Grade A SSL stacks. All our certificate chains are using SHA-2 already." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:157 +msgid "Safe System - Our servers are running recent Linux distribution with up-to-date security patches, with firewall and intrusion countermeasures (not disclosed for obvious reasons)." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:160 +msgid "Servers are located at the same locations as our Cloud providers with the following services:" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:162 +msgid "Restricted perimeter, physically accessed by authorized data center employees only" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:163 +msgid "Physical access control with security badges or biometrical security" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:164 +msgid "Security cameras monitoring the data center locations 24/7" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:165 +msgid "Security personnel on-site 24/7" +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:167 +msgid "The uploaded and migrated databases uploaded to the Upgrade platform are kept for up to 3 months and are permanently deleted following that period." +msgstr "" + +#: ../../content/administration/upgrade/faq.rst:170 +msgid "You can learn more about privacy and data handling at Odoo by visiting our `General Data Protection Regulation page `_." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:4 +msgid "Odoo.sh version upgrade" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:7 +msgid "Download and Upload your database" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:9 +msgid "Download a dump of your database (from the :ref:`Builds view `), choose the exact copy and without filestore options. Upload the .sql.gz dump on https://upgrade.odoo.com/upload and select the Testing Purpose. If you have custom code, you can choose to have it upgraded by us, or do it yourself. Once it's processed, you'll get a dump of the database in return." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:15 +msgid "Do *not* upload *backups* of your production database (found in the Backups tab of the production branch) as these are incompatible with the Upgrade platform - they contain your complete sources, etc. that are not needed for the upgrade. Make sure to download a **Dump** instead - either through the Backups tab using the *Download Dump* button or through the Builds page by using the *Download Dump* entry of the contextual menu of your latest production build." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:21 +msgid "Test your upgraded database" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:23 +msgid "Create a staging branch that will run the upgraded database. Either make sure your production branch's code is compatible between the two Odoo versions and fork your production branch, or make a new staging branch containing the upgraded code." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:27 +msgid "Once the staging build is done (it doesn't matter if it failed due to the version incompatibility), import your upgraded dump in the backups tab of the branch. The platform will automatically detect the version of the dump and change the version of Odoo's source code to the corresponding version for the build." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:31 +msgid "Test the upgraded database and make sure everything runs as it's supposed to." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:34 +msgid "Replace your existing production database" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:36 +msgid "Once you've tested everything and you're satisfied, start the process over to get an up-to-date upgraded dump:" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:38 +msgid "Make a new dump of your production database (as described in step 1)" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:39 +msgid "Upload it on upgrade.odoo.com and select the Production purpose" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:40 +msgid "Receive the newly upgraded dump and import it in your production branch. The build might get marked as failed because the platform will run it with the upgraded databases' Odoo version together with the old custom code." +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:42 +msgid "Merge or commit the upgraded custom code in the production branch" +msgstr "" + +#: ../../content/administration/upgrade/odoo_sh.rst:44 +msgid "If anything goes wrong, remember you can restore a backup. The platform will always make one before you make any Odoo.sh operation on the production database. If the restored backup comes from a previous version, the platform will detect it and change the project's Odoo version back if it needs to." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:8 +msgid "Upgrade process" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:15 +msgid "An upgrade is switching to a newer version of Odoo (e.g., Odoo 14.0 to Odoo 15.0)." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:17 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:19 +msgid "Changing :ref:`editions ` (i.e., Community to Enterprise edition)" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:20 +msgid "Switching :ref:`hosting type ` (i.e., On-Premise to Online or Odoo.sh)" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:22 +msgid "Migration from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:29 +msgid "Process workflow" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:31 +msgid "The upgrade process in a nutshell:" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:33 +msgid "You create a test upgrade request." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:0 +msgid "Odoo processes the request:" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:0 +msgid "This happens via an automated process that runs the database through an upgrade script and takes between 20 and 120 minutes. Only if an issue(s) arises will we have to intervene manually and adjust the script specifically to your database until the upgrade succeeds." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:38 +msgid "Odoo delivers a test database." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:39 +msgid "You test your database for possible discrepancies (see :ref:`upgrade/test-guidance`)" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:40 +msgid "If there are any discrepancies, you report them to the Upgrade support team via the help portal (see :ref:`upgrade/test-assistance`)." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:42 +msgid "We will fix the issues and send you a new test database." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:43 +msgid "Once you have completed the testing and are happy with the result, you decide on a date and time when you stop users from accessing Odoo, freeze all data entries, and create an upgrade request for the production upgrade." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:46 +msgid "Odoo delivers the production database through the automated process." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:47 +msgid "You restore it in your Production environment a few short hours later and continue working on the newly upgraded database (this is done automatically on SaaS)." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:55 +msgid "The upgrade process varies depending on where your database is hosted." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:60 +msgid "Online Hosting (SaaS)" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:62 +msgid "The upgrade request is made via your `database manager `_." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:75 +msgid "Cloud Platform (Odoo.sh)" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:77 +#: ../../content/administration/upgrade/process.rst:254 +msgid ":doc:`odoo_sh`" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:82 +msgid "Self-Hosting (On-Premise)" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:84 +msgid "There are two possibilities:" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:86 +msgid "Via `Odoo Upgrade service `_" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:0 +msgid "For technically advanced users and partners, via the following command line on the machine where your database is hosted:" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:0 +msgid "``python <(curl -s https://upgrade.odoo.com/upgrade) test -d -t ``" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:92 +msgid "The above command will dump your database to a file, send it to the upgrade platform for an upgrade, display you the live logs, and restore the upgraded database back on your server as a duplicate test database." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:99 +msgid "Testing Phase (pre-production phase)" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:101 +msgid "This phase allows you to review an upgraded version of your database without affecting your production database in any way." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:104 +msgid "We suggest that you run the test upgrade process at least once, but you can do it as many times as you need (one at a time)." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:107 +msgid "Once you receive your upgraded test database, check that all data, processes, and functionality are still correct and working as expected." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:110 +msgid "If you do find discrepancies, report your issues (see :ref:`upgrade/test-assistance`) and request a new test database (see :ref:`upgrade/test-db-request`) when the reported issues are fixed in the upgrade script." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:114 +msgid "If you do not find any discrepancies, you'll be able to move on to the upgrade of your :ref:`production database `." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:120 +msgid "Request a test database" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:122 +msgid "When filling the `website form `_, select *Testing* purpose." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:131 +msgid "Test guidance" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:133 +msgid "Every business and organization has its own operational needs and has to test its specific Odoo instance respectively. We recommend you look at `the test scenario ` for further information." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:138 +msgid "change link \"test scenario\" once the related doc is published" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:143 +#: ../../content/administration/upgrade/process.rst:201 +#: ../../content/administration/upgrade/process.rst:228 +msgid "Assistance" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:145 +msgid "If you encounter an issue in the **test database**, please get in touch with Odoo Upgrade Support via the `Odoo Support page `_." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:148 +msgid "Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:155 +msgid "If you choose another *Ticket Description* type, the request will be redirected to another team. This will slow down the processing and response time." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:158 +#: ../../content/administration/upgrade/process.rst:214 +msgid "Please provide as much detail as you can (i.e., videos and screenshots to illustrate your issue). This will avoid clarifying questions and speed up the resolution process significantly." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:166 +msgid "The purpose of the test phase is not to correct existing data or configurations in your database." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:173 +msgid "The production launch" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:178 +msgid "Production goes live" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:180 +msgid "The production upgrade request is when you decide to upgrade your current database with all your production data (invoices, VAT returns, inventories, current orders) to a new version of your choice." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:184 +msgid "After your :ref:`tests ` are completed to your satisfaction, submit the request to upgrade your production database via our `website form `_. Select *Production* purpose." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:193 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:195 +msgid "business interruptions (e.g., no longer having the possibility to validate an action)" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:196 +msgid "poor customer experiences (e.g., an eCommerce website that does not work correctly)" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:203 +msgid "If you encounter issues or problems in the **production database**, please get in touch with **Odoo Support**:" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:206 +msgid "Connect to our `Odoo Support page `_." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:207 +msgid "Under the *Ticket Description* section, select the appropriate type related to your issue but **do not select** the option *An issue related to my upgrade*." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:211 +msgid "After upgrading to production, the support will be provided by the Support team instead of the Upgrade team." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:222 +msgid "If you choose *An issue related to my upgrade* as ticket type, the request will be redirected to another team than the support one and will slow down the processing and response time." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:233 +msgid "Contact our Upgrade service support" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:235 +msgid "Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo Upgrade Team `_. We will be happy to answer it as soon as possible." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:243 +msgid "Please note that Odoo provides support and bug fixing only for the three last major versions of Odoo." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:246 +msgid "This is a factor to take into consideration before upgrading. If you are on an older version, we suggest you to prefer the most recent version to benefit from longer support (before having to upgrade again)." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:250 +msgid "You can get more information about our :doc:`supported versions <../maintain/supported_versions>`." +msgstr "" + +#: ../../content/administration/upgrade/process.rst:253 +msgid ":doc:`faq`" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:255 +msgid ":doc:`service_level`" +msgstr "" + +#: ../../content/administration/upgrade/process.rst:256 +msgid ":doc:`../maintain/supported_versions`" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:8 +msgid "Service Level Agreement" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:11 +msgid "What is covered by the Enterprise Licence?" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:13 +msgid "Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the following service at all times." +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:16 +msgid "The upgrade of:" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:18 +msgid "standard applications" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:19 +msgid "Studio customization (as long as the Studio app is still active)" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:20 +msgid "customizations done by our consulting and developer services *if* they are covered by a ‘Maintenance of Customisations’ subscription" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:23 +msgid "The Upgrade Service is limited to your database's technical conversion and adaptation (standard modules and data) to make it compatible with the targeted version." +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:27 +msgid "What upgrading does NOT cover" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:29 +msgid "The cleaning of pre-existing data & configuration while upgrading" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:30 +msgid "Any new developments and/or upgrades of your own :ref:`custom modules `" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:32 +msgid "`Training `_ on the latest version" +msgstr "" + +#: ../../content/administration/upgrade/service_level.rst:34 +msgid "You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription Agreement ` page." +msgstr "" diff --git a/locale/sources/contributing.pot b/locale/sources/contributing.pot index ec98a03c7..f87a776c8 100644 --- a/locale/sources/contributing.pot +++ b/locale/sources/contributing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-08-10 09:10+0000\n" +"POT-Creation-Date: 2022-03-18 13:48+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -88,23 +88,23 @@ msgstr "" msgid "Verify that you are browsing the documentation in the version that you intend to change. The version can be selected from the dropdown in the top menu." msgstr "" -#: ../../content/contributing/documentation.rst:75 -msgid "Head over to the page that you want to change and click on the **Edit on GitHub** button in the bottom of the left menu." +#: ../../content/contributing/documentation.rst:73 +msgid "Head over to the page that you want to change and click on the **Edit on GitHub** button in the top right corner of the page." msgstr "" -#: ../../content/contributing/documentation.rst:80 +#: ../../content/contributing/documentation.rst:76 msgid "If you do not have edit rights on the repository (`odoo/documentation `_), you need to fork it by clicking on the appropriate button. In other terms, you create a copy of the entire repository on your own account. If you do have the edit rights, skip this step." msgstr "" -#: ../../content/contributing/documentation.rst:87 +#: ../../content/contributing/documentation.rst:83 msgid "Make the appropriate changes while taking care of following the :doc:`content ` and :doc:`RST ` guidelines." msgstr "" -#: ../../content/contributing/documentation.rst:90 +#: ../../content/contributing/documentation.rst:86 msgid "Click on the **Preview changes** button to review your contribution in a more human-readable format. Be aware that the preview is not able to handle all markups correctly. Notes and tips, for instance, are not correctly rendered. The version of your content published to the website will be, however." msgstr "" -#: ../../content/contributing/documentation.rst:95 +#: ../../content/contributing/documentation.rst:91 msgid "Go to the bottom of the page to create a commit (:dfn:`what packs your changes together and labels them with a commit message`) of your changes." msgstr "" @@ -116,256 +116,259 @@ msgstr "" msgid "In the second text box, justify *why* you made these changes, if you feel that it is not obvious." msgstr "" -#: ../../content/contributing/documentation.rst:102 +#: ../../content/contributing/documentation.rst:98 msgid "Select the option \"Create a new branch for this commit and start a pull request.\" if you have the choice (if you have partial or full edit writes on the repository). If not, skip this step." msgstr "" -#: ../../content/contributing/documentation.rst:105 +#: ../../content/contributing/documentation.rst:101 msgid "Click on the green button. It is either labelled \"Commit changes\" or \"Propose file change\"." msgstr "" -#: ../../content/contributing/documentation.rst:109 +#: ../../content/contributing/documentation.rst:105 msgid "In the dropdown for the selection of the base branch (i.e., the version of the documentation that your changes concern), make sure to select the same version as in the first step of this guide and click on the **Create pull request** button." msgstr "" -#: ../../content/contributing/documentation.rst:115 +#: ../../content/contributing/documentation.rst:111 msgid "Double-check your :abbr:`PR (Pull Request)` and, when ready, click again on the **Create pull request** button to submit your changes for review by a content writer at Odoo." msgstr "" -#: ../../content/contributing/documentation.rst:120 -#: ../../content/contributing/documentation.rst:399 +#: ../../content/contributing/documentation.rst:116 +#: ../../content/contributing/documentation.rst:395 msgid "You're done! If your changes are approved straight away they will appear in the documentation the very next day. It may also be the case that the reviewer has a question or a remark, so make sure to check your notifications or your emails, depending on your account settings." msgstr "" -#: ../../content/contributing/documentation.rst:127 +#: ../../content/contributing/documentation.rst:123 msgid "Use the canonical Git workflow" msgstr "" -#: ../../content/contributing/documentation.rst:132 +#: ../../content/contributing/documentation.rst:128 msgid "Prepare your machine" msgstr "" -#: ../../content/contributing/documentation.rst:137 +#: ../../content/contributing/documentation.rst:133 msgid "Install Git" msgstr "" -#: ../../content/contributing/documentation.rst:139 +#: ../../content/contributing/documentation.rst:135 msgid "We use `Git `_ to manage the files of the user documentation. It is a tool that allows to track the history of changes made to a file and, more importantly, to work on different versions of those files at the same time. It means that you do not need to worry about overwriting someone else’s pending work when you start editing the documentation." msgstr "" -#: ../../content/contributing/documentation.rst:144 +#: ../../content/contributing/documentation.rst:140 msgid "You must then configure Git to identify yourself as the author of your future contribution. Enter the same email address as the one you used to register on GitHub." msgstr "" -#: ../../content/contributing/documentation.rst:147 +#: ../../content/contributing/documentation.rst:143 msgid "Download and install **Git** on your machine." msgstr "" -#: ../../content/contributing/documentation.rst:148 +#: ../../content/contributing/documentation.rst:144 msgid "Verify that `the installation folder of Git is included in your system's PATH variable `_." msgstr "" -#: ../../content/contributing/documentation.rst:150 -#: ../../content/contributing/documentation.rst:175 -#: ../../content/contributing/documentation.rst:323 -#: ../../content/contributing/documentation.rst:340 -#: ../../content/contributing/documentation.rst:371 +#: ../../content/contributing/documentation.rst:146 +#: ../../content/contributing/documentation.rst:171 +#: ../../content/contributing/documentation.rst:319 +#: ../../content/contributing/documentation.rst:336 +#: ../../content/contributing/documentation.rst:367 msgid "Execute the following commands in a terminal:" msgstr "" -#: ../../content/contributing/documentation.rst:160 +#: ../../content/contributing/documentation.rst:156 msgid "Fetch the sources" msgstr "" -#: ../../content/contributing/documentation.rst:162 +#: ../../content/contributing/documentation.rst:158 msgid "As stated earlier, our documentation (in all its versions) is maintained on GitHub at `github.com/odoo/documentation `_. A modification is made by the mean of a :abbr:`PR (Pull Request)` (:dfn:`proposal of content changes`) to allow for a review of the changes before updating the sources of the documentation." msgstr "" -#: ../../content/contributing/documentation.rst:167 +#: ../../content/contributing/documentation.rst:163 msgid "Prior to submitting a modification, you need to make a copy of the sources and download that copy on your machine." msgstr "" -#: ../../content/contributing/documentation.rst:170 +#: ../../content/contributing/documentation.rst:166 msgid "Go to `github.com/odoo/documentation `_ and click on the **Fork** button in the top right corner." msgstr "" -#: ../../content/contributing/documentation.rst:183 +#: ../../content/contributing/documentation.rst:179 msgid "If you do not have edit rights on the repository owned by Odoo, replace \"odoo\" with your Github username in the URL of the command above. If you do have edit rights, it is not necessary to fork the repository." msgstr "" -#: ../../content/contributing/documentation.rst:187 +#: ../../content/contributing/documentation.rst:183 msgid "In order to ease the collaboration between writers coming from many different systems and teams, execute the following group of commands that correspond to your :abbr:`OS (Operating System)` in a terminal." msgstr "" -#: ../../content/contributing/documentation.rst:191 +#: ../../content/contributing/documentation.rst:187 msgid "Windows:" msgstr "" -#: ../../content/contributing/documentation.rst:199 +#: ../../content/contributing/documentation.rst:195 msgid "Linux or Mac OS:" msgstr "" -#: ../../content/contributing/documentation.rst:210 +#: ../../content/contributing/documentation.rst:206 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:742 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:744 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:760 msgid "Python" msgstr "" -#: ../../content/contributing/documentation.rst:212 +#: ../../content/contributing/documentation.rst:208 msgid "Because the documentation is written in :abbr:`RST (reStructuredText)`, it needs to be built (:dfn:`converted to HTML`) in order to display nicely. This is done by the documentation generator which takes the original :abbr:`RST (reStructuredText)` files as input, transforms the markups in a human-readable format, and outputs HTML files to be read in your web browser." msgstr "" -#: ../../content/contributing/documentation.rst:217 +#: ../../content/contributing/documentation.rst:213 msgid "The documentation generator that we use is called `Sphinx `_. and is written in `Python `_. You have to install Python in order to use Sphinx. For the record, Sphinx is the program and Python the programming language, but you do not need to know much more about them so don't panic!" msgstr "" -#: ../../content/contributing/documentation.rst:222 +#: ../../content/contributing/documentation.rst:218 msgid "Python comes with its own package manager: `pip `_. It allows installing Python dependencies in a single command." msgstr "" -#: ../../content/contributing/documentation.rst:226 +#: ../../content/contributing/documentation.rst:222 msgid "Download and install the recommended release (`see README file `_) of **Python 3** on your machine." msgstr "" -#: ../../content/contributing/documentation.rst:228 +#: ../../content/contributing/documentation.rst:224 msgid "Make sure to have **pip** installed on your machine (on Windows, you can install pip alongside Python)." msgstr "" -#: ../../content/contributing/documentation.rst:230 +#: ../../content/contributing/documentation.rst:226 msgid "Execute the following commands in a terminal to verify that both installations finished successfully:" msgstr "" -#: ../../content/contributing/documentation.rst:238 +#: ../../content/contributing/documentation.rst:234 msgid "Execute the following commands in a terminal to install the Python dependencies of the documentation:" msgstr "" -#: ../../content/contributing/documentation.rst:247 +#: ../../content/contributing/documentation.rst:243 msgid "Depending on your :abbr:`OS (Operating System)`, you may need to run the commands ``python`` and ``pip`` instead of ``python3`` and ``pip3``" msgstr "" -#: ../../content/contributing/documentation.rst:253 +#: ../../content/contributing/documentation.rst:249 msgid "Make" msgstr "" -#: ../../content/contributing/documentation.rst:255 +#: ../../content/contributing/documentation.rst:251 msgid "`Make `_ is a tool that packs a bunch of command-lines into one to be easier to remember and to type. In our case, it is used to execute complex Sphinx build commands by using a single and simpler one instead." msgstr "" -#: ../../content/contributing/documentation.rst:259 +#: ../../content/contributing/documentation.rst:255 msgid "Download and install **Make** on your machine." msgstr "" -#: ../../content/contributing/documentation.rst:260 +#: ../../content/contributing/documentation.rst:256 msgid "Verify that `the installation folder of Make is included in your system's PATH variable `_." msgstr "" -#: ../../content/contributing/documentation.rst:266 +#: ../../content/contributing/documentation.rst:262 msgid "pngquant" msgstr "" -#: ../../content/contributing/documentation.rst:268 +#: ../../content/contributing/documentation.rst:264 msgid "`pngquant `_ is a tool that we use to compress PNG images so that the documentation does not end up weighting several Gigabytes in a few year span." msgstr "" -#: ../../content/contributing/documentation.rst:271 +#: ../../content/contributing/documentation.rst:267 msgid "Download and install **pngquant** on your machine." msgstr "" -#: ../../content/contributing/documentation.rst:272 +#: ../../content/contributing/documentation.rst:268 msgid "Verify that `the installation folder of pngquant is included in your system's PATH variable `_." msgstr "" -#: ../../content/contributing/documentation.rst:278 +#: ../../content/contributing/documentation.rst:274 msgid "Prepare your version" msgstr "" -#: ../../content/contributing/documentation.rst:280 +#: ../../content/contributing/documentation.rst:276 msgid "Now that your machine is all set up, it is time to do the same for your version of the documentation files. As it would not be convenient to have several people working on the version 13.0 in parallel (conflicts of content would occur all the time), and in order to be able to create a :abbr:`PR (Pull Request)`, you must `create a new branch `_ starting from the branch 13.0. In other words, you copy the entirety of this version’s files and give it another name. For this example, we will go with ``13.0-my_contribution``." msgstr "" -#: ../../content/contributing/documentation.rst:288 +#: ../../content/contributing/documentation.rst:284 msgid "Execute the following commands in a terminal to..." msgstr "" -#: ../../content/contributing/documentation.rst:290 +#: ../../content/contributing/documentation.rst:286 msgid "Navigate to the documentation folder:" msgstr "" -#: ../../content/contributing/documentation.rst:296 +#: ../../content/contributing/documentation.rst:292 msgid "Switch to the version 13.0:" msgstr "" -#: ../../content/contributing/documentation.rst:302 +#: ../../content/contributing/documentation.rst:298 msgid "Create your own branch which will be a copy of 13.0:" msgstr "" -#: ../../content/contributing/documentation.rst:311 +#: ../../content/contributing/documentation.rst:307 msgid "Perform your changes" msgstr "" -#: ../../content/contributing/documentation.rst:313 +#: ../../content/contributing/documentation.rst:309 msgid "You can now perform any change you want to the documentation files. These changes must be compliant with :abbr:`RST (reStructuredText)` syntax (see :doc:`documentation/rst_cheat_sheet`) and with our :doc:`content ` and :doc:`RST ` guidelines." msgstr "" -#: ../../content/contributing/documentation.rst:319 +#: ../../content/contributing/documentation.rst:315 msgid "If your changes include the addition of a new image, for instance :file:`my_image.png`, proceed as follows:" msgstr "" -#: ../../content/contributing/documentation.rst:322 +#: ../../content/contributing/documentation.rst:318 msgid "Make sure that the image is in ``.png`` format." msgstr "" -#: ../../content/contributing/documentation.rst:330 +#: ../../content/contributing/documentation.rst:326 msgid "Delete :file:`my_image.png`." msgstr "" -#: ../../content/contributing/documentation.rst:331 +#: ../../content/contributing/documentation.rst:327 msgid "Rename :file:`my_image-fs8.png` to :file:`my_image.png`." msgstr "" -#: ../../content/contributing/documentation.rst:336 +#: ../../content/contributing/documentation.rst:332 msgid "Preview your changes" msgstr "" -#: ../../content/contributing/documentation.rst:338 +#: ../../content/contributing/documentation.rst:334 msgid "To preview your changes in a generated documentation, proceed as follows:" msgstr "" -#: ../../content/contributing/documentation.rst:349 +#: ../../content/contributing/documentation.rst:345 msgid "You can omit the :command:`make clean` command when no recent change has been made to the hierarchy of documentation files." msgstr "" -#: ../../content/contributing/documentation.rst:352 +#: ../../content/contributing/documentation.rst:348 msgid "Fix any error or warning shown in the logs of the build." msgstr "" -#: ../../content/contributing/documentation.rst:353 +#: ../../content/contributing/documentation.rst:349 msgid "Open the file :file:`documentation/_build/html/index.html` with your default web browser." msgstr "" -#: ../../content/contributing/documentation.rst:356 +#: ../../content/contributing/documentation.rst:352 msgid "These steps have for only purpose to show you the final results of your changes. They have no impact on the documentation source files." msgstr "" -#: ../../content/contributing/documentation.rst:362 +#: ../../content/contributing/documentation.rst:358 msgid "Submit your changes" msgstr "" -#: ../../content/contributing/documentation.rst:365 +#: ../../content/contributing/documentation.rst:361 msgid "We expect you to have basic knowledge of Git, which should be enough to cover the basic flow of a one-time contribution. If you plan on submitting several contributions, work on older versions of the documentation or perform any other advanced action, we recommend you to be confident with Git. Help yourself with `this manual of Git `_ and `this interactive tutorial `_." msgstr "" -#: ../../content/contributing/documentation.rst:379 +#: ../../content/contributing/documentation.rst:375 msgid "Go to `github.com/odoo/documentation/pulls `_ and click on the **New pull request** button." msgstr "" -#: ../../content/contributing/documentation.rst:384 +#: ../../content/contributing/documentation.rst:380 msgid "If you forked the base repository in the section :ref:`contributing/fetch-sources`, click on the link **compare across forks** If not, skip this step." msgstr "" -#: ../../content/contributing/documentation.rst:389 +#: ../../content/contributing/documentation.rst:385 msgid "In the dropdown for the selection of the base branch (i.e., the version of the documentation that your changes concern), make sure to select the version that your changes target (here **13.0**)." msgstr "" -#: ../../content/contributing/documentation.rst:394 +#: ../../content/contributing/documentation.rst:390 msgid "Double-check your :abbr:`PR (Pull Request)` and, when ready, click again on the **Create pull request** button to submit your changes for review by a redactor at Odoo." msgstr "" @@ -889,7 +892,7 @@ msgid "*Text*" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:60 -msgid "\\`\\`Text\\`\\`" +msgid "\\`Text\\`" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:60 @@ -935,6 +938,7 @@ msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:264 #: ../../content/contributing/documentation/rst_cheat_sheet.rst:289 #: ../../content/contributing/documentation/rst_cheat_sheet.rst:314 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:409 #: ../../content/contributing/documentation/rst_guidelines.rst:17 msgid "Example" msgstr "" @@ -979,9 +983,15 @@ msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:412 #: ../../content/contributing/documentation/rst_cheat_sheet.rst:431 #: ../../content/contributing/documentation/rst_cheat_sheet.rst:450 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:471 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:469 #: ../../content/contributing/documentation/rst_cheat_sheet.rst:490 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:550 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:509 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:530 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:570 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:613 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:690 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:786 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:876 msgid "RST" msgstr "" @@ -996,10 +1006,16 @@ msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:401 #: ../../content/contributing/documentation/rst_cheat_sheet.rst:420 #: ../../content/contributing/documentation/rst_cheat_sheet.rst:439 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:459 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:479 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:499 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:559 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:458 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:478 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:498 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:518 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:540 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:589 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:648 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:734 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:810 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:885 msgid "Render" msgstr "" @@ -1147,88 +1163,236 @@ msgstr "" msgid "Use this admonition to inform the reader about a useful trick that requires an action." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:409 -msgid "Exercise" -msgstr "" - #: ../../content/contributing/documentation/rst_cheat_sheet.rst:423 -msgid "Use this admonition to suggest an exercise to the reader." +msgid "Use this admonition to show an example." msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:428 -msgid "Important" +msgid "Exercise" msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:442 -msgid "Use this admonition to notify the reader about an important information." +msgid "Use this admonition to suggest an exercise to the reader." msgstr "" #: ../../content/contributing/documentation/rst_cheat_sheet.rst:447 +msgid "Important" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:461 +msgid "Use this admonition to notify the reader about an important information." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:466 msgid "Warning" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:462 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:481 msgid "Use this admonition to require the reader to proceed with caution with what is described in the warning." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:468 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:487 msgid "Danger" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:482 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:501 msgid "Use this admonition to bring the reader's attention to a serious threat." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:487 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:506 msgid "Custom" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:501 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:520 msgid "Title" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:503 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:522 msgid "Customize this admonition with a **Title** of your choice." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:508 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:527 +msgid "Code blocks" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:550 +msgid "Content tabs" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:553 +msgid "The `tabs` directive may not work well in some situations. In particular:" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:555 +msgid "The tabs' headers cannot be translated." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:556 +msgid "A tab cannot contain :ref:`headings `." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:557 +msgid "An :ref:`admonition ` cannot contain tabs." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:558 +msgid "A tab cannot contain :ref:`internal hyperlink targets `." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:564 +msgid "Basic tabs" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:566 +msgid "Basic tabs are useful to split content into multiple options. The `tabs` directive is used to define a sequence of tabs. Each tab is then defined with the `tab` directive followed by a label." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:593 +msgid "Odoo Online" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:595 +msgid "Content dedicated to Odoo Online users." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:597 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:599 +msgid "Alternative for Odoo.sh users." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:601 +msgid "On-premise" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:603 +msgid "Third version for On-premise users." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:608 +msgid "Nested tabs" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:610 +msgid "Tabs can be nested inside one another." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:652 +msgid "Stars" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:656 +msgid "The Sun" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:658 +msgid "The closest star to us." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:660 +msgid "Proxima Centauri" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:662 +msgid "The second closest star to us." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:664 +msgid "Polaris" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:666 +msgid "The North Star." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:668 +msgid "Moons" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:672 +msgid "The Moon" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:674 +msgid "Orbits the Earth." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:676 +msgid "Titan" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:678 +msgid "Orbits Jupiter." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:683 +msgid "Group tabs" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:685 +msgid "Group tabs are special tabs that synchronize based on a group label. The last selected group is remembered and automatically selected when the user returns on the page or visits another page with the tabs group. The `group-tab` directive is used to define group tabs." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:738 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:740 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:752 +msgid "C++" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:746 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:748 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:767 +msgid "Java" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:778 +msgid "Code tabs" +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:780 +msgid "Code tabs are essentially :ref:`group tabs ` that treat the content as a :ref:`code block `. The `code-tab` directive is used to define a code tab. Just as for the `code-block` directive, the language defines the syntax highlighting of the tab. If set, the label is used instead of the language for grouping tabs." +msgstr "" + +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:834 msgid "Document metadata" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:510 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:836 msgid "Sphinx supports document-wide metadata directives that specify a behavior for the entire page." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:511 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:837 msgid "They must be placed between colons (`:`) at the top of the source file." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:514 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:840 msgid "**Metadata**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:514 -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:593 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:840 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:919 msgid "**Purpose**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:516 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:842 msgid "`show-content`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:516 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:842 msgid "Make a toctree page accessible from the navigation menu." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:518 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:844 msgid "`show-toc`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:518 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:844 msgid "Show the table of content on a page that has the `show-content` metadata directive." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:521 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:847 msgid "`code-column`" msgstr "" @@ -1240,203 +1404,203 @@ msgstr "" msgid "For example, see :doc:`/applications/finance/accounting/getting_started/memento`." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:526 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:852 msgid "`hide-page-toc`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:526 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:852 msgid "Hide the \"On this page\" sidebar and use full page width for the content." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:528 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:854 msgid "`custom-css`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:528 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:854 msgid "Link CSS files (comma-separated) to the document." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:530 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:856 msgid "`custom-js`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:530 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:856 msgid "Link JS files (comma-separated) to the document." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:532 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:858 msgid "`classes`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:532 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:858 msgid "Assign the specified classes to the `
` element of the document." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:534 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:860 msgid "`orphan`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:534 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:860 msgid "Suppress the need to include the document in a toctree." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:536 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:862 msgid "`nosearch`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:536 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:862 msgid "Exclude the document from search results." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:542 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:868 msgid "Formatting tips" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:547 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:873 msgid "Break the line but not the paragraph" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:562 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:888 msgid "First super long line that you break in two… here is rendered as a single line." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:563 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:889 msgid "Second line that follows a line break." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:568 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:894 msgid "Add comments" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:570 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:896 msgid "If you made a particular choice of writing or formatting that a future writer should be able to understand and take into account, consider writing a comment. Comments are blocks of text that do not count as a part of the documentation and that are used to pass a message to writers of the source code. They consist of a line starting with two dots and a space, followed by the comment." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:575 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:901 msgid "``.. For instance, this line will not be rendered in the documentation.``" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:580 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:906 msgid "Use tables" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:582 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:908 msgid "Make use of `this convenient table generator `_ to build your tables. Then, copy-paste the generated formatting into your document." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:588 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:914 msgid "Spice up your writing with specialized directives" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:590 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:916 msgid "Use these additional directives to fine-tune your content:" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:593 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:919 msgid "**Directive**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:593 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:919 msgid "**Example**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:595 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:921 msgid "**RST**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:595 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:921 msgid "**HTML**" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:597 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:923 msgid "``abbr``" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:597 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:923 msgid "Self-defining abbreviations" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:597 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:923 msgid "``:abbr:`SO (Sales Order)```" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:597 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:923 msgid ":abbr:`SO (Sales Order)`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:599 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:925 msgid "``command``" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:599 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:925 msgid "Highlight a command" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:599 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:925 msgid "``:command:`python example.py```" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:599 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:925 msgid ":command:`python example.py`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:601 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:927 msgid "``dfn``" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:601 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:927 msgid "Define a term" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:601 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:927 msgid "``:dfn:`a definition for a new term```" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:601 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:927 msgid ":dfn:`a definition for a new term`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:603 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:929 msgid "``file``" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:603 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:929 msgid "Indicate a file path" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:603 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:929 msgid "``:file:`~/odoo/odoo-bin```" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:603 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:929 msgid ":file:`~/odoo/odoo-bin`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:605 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:931 msgid "``menuselection``" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:605 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:931 msgid "Guide a user through a sequence of menus" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:605 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:931 msgid "``:menuselection:`Sales --> Configuration --> Settings```" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:605 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:931 msgid ":menuselection:`Sales --> Configuration --> Settings`" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:611 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:937 msgid "Escape markup symbols (Advanced)" msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:613 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:939 msgid "Markup symbols escaped with backslashes (``\\``) are rendered normally. For instance, ``this \\*\\*line of text\\*\\* with \\*markup\\* symbols`` is rendered as “this \\*\\*line of text\\*\\* with \\*markup\\* symbols”." msgstr "" -#: ../../content/contributing/documentation/rst_cheat_sheet.rst:617 +#: ../../content/contributing/documentation/rst_cheat_sheet.rst:943 msgid "When it comes to backticks (`````), which are used in many case such as :ref:`hyperlink references `, using backslashes for escaping is no longer an option because the outer backticks interpret enclosed backslashes and thus prevent them from escaping inner backticks. For instance, ```\\`this formatting\\```` produces an ``[UNKNOWN NODE title_reference]`` error. Instead, `````this formatting````` should be used to produce the following result: ```this formatting```." msgstr "" diff --git a/locale/sources/developer.pot b/locale/sources/developer.pot index db9b717d3..b127cf218 100644 --- a/locale/sources/developer.pot +++ b/locale/sources/developer.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 14.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-05-18 07:12+0200\n" +"POT-Creation-Date: 2022-03-18 13:49+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,10 +16,14 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../../content/developer.rst:3 +#: ../../content/developer.rst:9 msgid "Developer" msgstr "" +#: ../../content/developer.rst:11 +msgid "Learn through tutorials and get help using reference guides." +msgstr "" + #: ../../content/developer/glossary.rst:5 msgid "Glossary" msgstr "" @@ -80,7 +84,7 @@ msgstr "" msgid "process of removing extraneous/non-necessary sections of files (comments, whitespace) and possibly recompiling them using equivalent but shorter structures (`ternary operator`_ instead of ``if/else``) in order to reduce network traffic" msgstr "" -#: ../../content/developer/howtos.rst:3 +#: ../../content/developer/howtos.rst:5 msgid "Tutorials" msgstr "" @@ -129,6 +133,7 @@ msgid "Everything in Odoo thus starts and ends with modules." msgstr "" #: ../../content/developer/howtos/backend.rst:48 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:52 msgid "Composition of a module" msgstr "" @@ -145,6 +150,7 @@ msgid "Declared as Python classes, these resources are automatically persisted b msgstr "" #: ../../content/developer/howtos/backend.rst:57 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:62 msgid ":ref:`Object views `" msgstr "" @@ -153,6 +159,7 @@ msgid "Definition of business objects UI display" msgstr "" #: ../../content/developer/howtos/backend.rst:65 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:70 msgid ":ref:`Data files `" msgstr "" @@ -161,30 +168,37 @@ msgid "XML or CSV files declaring the model metadata :" msgstr "" #: ../../content/developer/howtos/backend.rst:62 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:67 msgid ":ref:`views ` or :ref:`reports `," msgstr "" #: ../../content/developer/howtos/backend.rst:63 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:68 msgid "configuration data (modules parametrization, :ref:`security rules `)," msgstr "" #: ../../content/developer/howtos/backend.rst:64 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:69 msgid "demonstration data" msgstr "" #: ../../content/developer/howtos/backend.rst:65 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:70 msgid "and more" msgstr "" #: ../../content/developer/howtos/backend.rst:68 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:73 msgid ":ref:`Web controllers `" msgstr "" #: ../../content/developer/howtos/backend.rst:68 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:73 msgid "Handle requests from web browsers" msgstr "" #: ../../content/developer/howtos/backend.rst:71 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:76 msgid "Static web data" msgstr "" @@ -193,11 +207,13 @@ msgid "Images, CSS or javascript files used by the web interface or website" msgstr "" #: ../../content/developer/howtos/backend.rst:74 -#: ../../content/developer/reference/guidelines.rst:32 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:85 +#: ../../content/developer/misc/other/guidelines.rst:32 msgid "Module structure" msgstr "" #: ../../content/developer/howtos/backend.rst:76 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:87 msgid "Each module is a directory within a *module directory*. Module directories are specified by using the :option:`--addons-path ` option." msgstr "" @@ -206,6 +222,7 @@ msgid "most command-line options can also be set using :ref:`a configuration fil msgstr "" #: ../../content/developer/howtos/backend.rst:86 +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:91 msgid "An Odoo module is declared by its :ref:`manifest `." msgstr "" @@ -234,6 +251,7 @@ msgid "Use the command line above to create an empty module Open Academy, and i msgstr "" #: ../../content/developer/howtos/backend.rst:116 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:17 msgid "Object-Relational Mapping" msgstr "" @@ -250,6 +268,7 @@ msgid "Models can be configured by setting a number of attributes at their defin msgstr "" #: ../../content/developer/howtos/backend.rst:137 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:107 msgid "Model fields" msgstr "" @@ -258,6 +277,7 @@ msgid "Fields are used to define what the model can store and where. Fields are msgstr "" #: ../../content/developer/howtos/backend.rst:150 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:212 msgid "Common Attributes" msgstr "" @@ -266,6 +286,7 @@ msgid "Much like the model itself, its fields can be configured, by passing conf msgstr "" #: ../../content/developer/howtos/backend.rst:157 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:236 msgid "Some attributes are available on all fields, here are the most common ones:" msgstr "" @@ -274,10 +295,12 @@ msgid ":attr:`~odoo.fields.Field.string` (``unicode``, default: field's name)" msgstr "" #: ../../content/developer/howtos/backend.rst:160 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:239 msgid "The label of the field in UI (visible by users)." msgstr "" #: ../../content/developer/howtos/backend.rst:162 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:241 msgid ":attr:`~odoo.fields.Field.required` (``bool``, default: ``False``)" msgstr "" @@ -294,10 +317,12 @@ msgid "Long-form, provides a help tooltip to users in the UI." msgstr "" #: ../../content/developer/howtos/backend.rst:167 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:246 msgid ":attr:`~odoo.fields.Field.index` (``bool``, default: ``False``)" msgstr "" #: ../../content/developer/howtos/backend.rst:167 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:246 msgid "Requests that Odoo create a `database index`_ on the column." msgstr "" @@ -322,6 +347,7 @@ msgid "Odoo creates a few fields in all models\\ [#autofields]_. These fields ar msgstr "" #: ../../content/developer/howtos/backend.rst:186 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:272 msgid ":attr:`~odoo.fields.Model.id` (:class:`~odoo.fields.Id`)" msgstr "" @@ -330,30 +356,37 @@ msgid "The unique identifier for a record in its model." msgstr "" #: ../../content/developer/howtos/backend.rst:188 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:274 msgid ":attr:`~odoo.fields.Model.create_date` (:class:`~odoo.fields.Datetime`)" msgstr "" #: ../../content/developer/howtos/backend.rst:189 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:275 msgid "Creation date of the record." msgstr "" #: ../../content/developer/howtos/backend.rst:190 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:276 msgid ":attr:`~odoo.fields.Model.create_uid` (:class:`~odoo.fields.Many2one`)" msgstr "" #: ../../content/developer/howtos/backend.rst:191 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:277 msgid "User who created the record." msgstr "" #: ../../content/developer/howtos/backend.rst:192 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:278 msgid ":attr:`~odoo.fields.Model.write_date` (:class:`~odoo.fields.Datetime`)" msgstr "" #: ../../content/developer/howtos/backend.rst:193 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:279 msgid "Last modification date of the record." msgstr "" #: ../../content/developer/howtos/backend.rst:195 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:282 msgid ":attr:`~odoo.fields.Model.write_uid` (:class:`~odoo.fields.Many2one`)" msgstr "" @@ -434,14 +467,17 @@ msgid "Actions and menus are regular records in database, usually declared throu msgstr "" #: ../../content/developer/howtos/backend.rst:262 +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:63 msgid "by clicking on menu items (linked to specific actions)" msgstr "" #: ../../content/developer/howtos/backend.rst:263 +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:64 msgid "by clicking on buttons in views (if these are connected to actions)" msgstr "" #: ../../content/developer/howtos/backend.rst:264 +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:65 msgid "as contextual actions on object" msgstr "" @@ -519,6 +555,7 @@ msgid "Form views" msgstr "" #: ../../content/developer/howtos/backend.rst:353 +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:85 msgid "Forms are used to create and edit single records." msgstr "" @@ -590,7 +627,7 @@ msgid "Create a model for *sessions*. A session has a name, a start date, a dura msgstr "" #: ../../content/developer/howtos/backend.rst:460 -#: ../../content/developer/reference/javascript_reference.rst:2053 +#: ../../content/developer/reference/javascript/javascript_reference.rst:2054 msgid "Relational fields" msgstr "" @@ -675,8 +712,8 @@ msgid "Using the relational field many2many, modify the *Session* model to relat msgstr "" #: ../../content/developer/howtos/backend.rst:522 -#: ../../content/developer/reference/javascript_reference.rst:411 -#: ../../content/developer/reference/views.rst:184 +#: ../../content/developer/reference/addons/views.rst:184 +#: ../../content/developer/reference/javascript/javascript_reference.rst:412 msgid "Inheritance" msgstr "" @@ -685,6 +722,7 @@ msgid "Model inheritance" msgstr "" #: ../../content/developer/howtos/backend.rst:527 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:108 msgid "Odoo provides two *inheritance* mechanisms to extend an existing model in a modular way." msgstr "" @@ -737,22 +775,27 @@ msgid "An extension view references its parent using the ``inherit_id`` field, a msgstr "" #: ../../content/developer/howtos/backend.rst:579 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:197 msgid "``expr``" msgstr "" #: ../../content/developer/howtos/backend.rst:579 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:197 msgid "An XPath_ expression selecting a single element in the parent view. Raises an error if it matches no element or more than one" msgstr "" #: ../../content/developer/howtos/backend.rst:595 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:213 msgid "``position``" msgstr "" #: ../../content/developer/howtos/backend.rst:582 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:200 msgid "Operation to apply to the matched element:" msgstr "" #: ../../content/developer/howtos/backend.rst:584 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:202 msgid "``inside``" msgstr "" @@ -761,38 +804,45 @@ msgid "appends ``xpath``'s body at the end of the matched element" msgstr "" #: ../../content/developer/howtos/backend.rst:587 -#: ../../content/developer/reference/qweb.rst:528 -#: ../../content/developer/reference/views.rst:282 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:205 +#: ../../content/developer/reference/addons/views.rst:282 +#: ../../content/developer/reference/javascript/qweb.rst:530 msgid "``replace``" msgstr "" #: ../../content/developer/howtos/backend.rst:587 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:205 msgid "replaces the matched element with the ``xpath``'s body, replacing any ``$0`` node occurrence in the new body with the original element" msgstr "" #: ../../content/developer/howtos/backend.rst:589 -#: ../../content/developer/reference/qweb.rst:522 -#: ../../content/developer/reference/views.rst:288 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:207 +#: ../../content/developer/reference/addons/views.rst:288 +#: ../../content/developer/reference/javascript/qweb.rst:524 msgid "``before``" msgstr "" #: ../../content/developer/howtos/backend.rst:590 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:208 msgid "inserts the ``xpath``'s body as a sibling before the matched element" msgstr "" #: ../../content/developer/howtos/backend.rst:591 -#: ../../content/developer/reference/qweb.rst:524 -#: ../../content/developer/reference/views.rst:285 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:209 +#: ../../content/developer/reference/addons/views.rst:285 +#: ../../content/developer/reference/javascript/qweb.rst:526 msgid "``after``" msgstr "" #: ../../content/developer/howtos/backend.rst:592 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:210 msgid "inserts the ``xpaths``'s body as a sibling after the matched element" msgstr "" #: ../../content/developer/howtos/backend.rst:595 -#: ../../content/developer/reference/qweb.rst:533 -#: ../../content/developer/reference/views.rst:308 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:213 +#: ../../content/developer/reference/addons/views.rst:308 +#: ../../content/developer/reference/javascript/qweb.rst:535 msgid "``attributes``" msgstr "" @@ -817,6 +867,7 @@ msgid "Using view inheritance, display this fields in the partner form view" msgstr "" #: ../../content/developer/howtos/backend.rst:621 +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:193 msgid "Domains" msgstr "" @@ -877,6 +928,7 @@ msgid "Iterating over ``self`` gives the records one by one, where each record i msgstr "" #: ../../content/developer/howtos/backend.rst:699 +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:59 msgid "Dependencies" msgstr "" @@ -909,30 +961,37 @@ msgid "Any field can be given a default value. In the field definition, add the msgstr "" #: ../../content/developer/howtos/backend.rst:738 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:115 msgid "The object ``self.env`` gives access to request parameters and other useful things:" msgstr "" #: ../../content/developer/howtos/backend.rst:741 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:118 msgid "``self.env.cr`` or ``self._cr`` is the database *cursor* object; it is used for querying the database" msgstr "" #: ../../content/developer/howtos/backend.rst:743 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:120 msgid "``self.env.uid`` or ``self._uid`` is the current user's database id" msgstr "" #: ../../content/developer/howtos/backend.rst:744 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:121 msgid "``self.env.user`` is the current user's record" msgstr "" #: ../../content/developer/howtos/backend.rst:745 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:122 msgid "``self.env.context`` or ``self._context`` is the context dictionary" msgstr "" #: ../../content/developer/howtos/backend.rst:746 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:123 msgid "``self.env.ref(xml_id)`` returns the record corresponding to an XML id" msgstr "" #: ../../content/developer/howtos/backend.rst:747 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:124 msgid "``self.env[model_name]`` returns an instance of the given model" msgstr "" @@ -977,6 +1036,7 @@ msgid "Model constraints" msgstr "" #: ../../content/developer/howtos/backend.rst:804 +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:12 msgid "Odoo provides two ways to set up automatically verified invariants: :func:`Python constraints ` and :attr:`SQL constraints `." msgstr "" @@ -1033,39 +1093,39 @@ msgid "Tree views can take supplementary attributes to further customize their b msgstr "" #: ../../content/developer/howtos/backend.rst:885 -#: ../../content/developer/reference/views.rst:978 -#: ../../content/developer/reference/views.rst:1411 -#: ../../content/developer/reference/views.rst:1532 +#: ../../content/developer/reference/addons/views.rst:978 +#: ../../content/developer/reference/addons/views.rst:1413 +#: ../../content/developer/reference/addons/views.rst:1534 msgid "``decoration-{$name}``" msgstr "" #: ../../content/developer/howtos/backend.rst:861 -#: ../../content/developer/reference/views.rst:965 -#: ../../content/developer/reference/views.rst:1407 +#: ../../content/developer/reference/addons/views.rst:965 +#: ../../content/developer/reference/addons/views.rst:1409 msgid "allow changing the style of a row's text based on the corresponding record's attributes." msgstr "" #: ../../content/developer/howtos/backend.rst:864 -#: ../../content/developer/reference/views.rst:104 -#: ../../content/developer/reference/views.rst:968 +#: ../../content/developer/reference/addons/views.rst:104 +#: ../../content/developer/reference/addons/views.rst:968 msgid "Values are Python expressions. For each record, the expression is evaluated with the record's attributes as context values and if ``true``, the corresponding style is applied to the row. Here are some of the other values available in the context:" msgstr "" #: ../../content/developer/howtos/backend.rst:869 -#: ../../content/developer/reference/views.rst:109 -#: ../../content/developer/reference/views.rst:973 +#: ../../content/developer/reference/addons/views.rst:109 +#: ../../content/developer/reference/addons/views.rst:973 msgid "``uid``: the id of the current user," msgstr "" #: ../../content/developer/howtos/backend.rst:870 -#: ../../content/developer/reference/views.rst:110 -#: ../../content/developer/reference/views.rst:974 +#: ../../content/developer/reference/addons/views.rst:110 +#: ../../content/developer/reference/addons/views.rst:974 msgid "``today``: the current local date as a string of the form ``YYYY-MM-DD``," msgstr "" #: ../../content/developer/howtos/backend.rst:871 -#: ../../content/developer/reference/views.rst:111 -#: ../../content/developer/reference/views.rst:975 +#: ../../content/developer/reference/addons/views.rst:111 +#: ../../content/developer/reference/addons/views.rst:975 msgid "``now``: same as ``today`` with the addition of the current time. This value is formatted as ``YYYY-MM-DD hh:mm:ss``." msgstr "" @@ -1074,7 +1134,7 @@ msgid "``{$name}`` can be ``bf`` (``font-weight: bold``), ``it`` (``font-style: msgstr "" #: ../../content/developer/howtos/backend.rst:890 -#: ../../content/developer/reference/views.rst:1391 +#: ../../content/developer/reference/addons/views.rst:1393 msgid "``editable``" msgstr "" @@ -1099,9 +1159,9 @@ msgid "Displays records as calendar events. Their root element is ```` msgstr "" #: ../../content/developer/howtos/backend.rst:907 -#: ../../content/developer/reference/views.rst:410 -#: ../../content/developer/reference/views.rst:962 -#: ../../content/developer/reference/views.rst:1342 +#: ../../content/developer/reference/addons/views.rst:410 +#: ../../content/developer/reference/addons/views.rst:962 +#: ../../content/developer/reference/addons/views.rst:1344 msgid "``color``" msgstr "" @@ -1126,13 +1186,13 @@ msgid "record's field holding the end date/time for the event" msgstr "" #: ../../content/developer/howtos/backend.rst:914 -#: ../../content/developer/reference/views.rst:897 -#: ../../content/developer/reference/views.rst:1017 -#: ../../content/developer/reference/views.rst:1435 -#: ../../content/developer/reference/views.rst:1493 -#: ../../content/developer/reference/views.rst:1682 -#: ../../content/developer/reference/views.rst:1727 -#: ../../content/developer/reference/views.rst:1843 +#: ../../content/developer/reference/addons/views.rst:897 +#: ../../content/developer/reference/addons/views.rst:1019 +#: ../../content/developer/reference/addons/views.rst:1437 +#: ../../content/developer/reference/addons/views.rst:1495 +#: ../../content/developer/reference/addons/views.rst:1684 +#: ../../content/developer/reference/addons/views.rst:1729 +#: ../../content/developer/reference/addons/views.rst:1845 msgid "``string``" msgstr "" @@ -1153,13 +1213,14 @@ msgid "Search view ```` elements can have a ``@filter_domain`` that overr msgstr "" #: ../../content/developer/howtos/backend.rst:935 +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:180 msgid "Search views can also contain ```` elements, which act as toggles for predefined searches. Filters must have one of the following attributes:" msgstr "" #: ../../content/developer/howtos/backend.rst:938 -#: ../../content/developer/reference/views.rst:850 -#: ../../content/developer/reference/views.rst:1801 -#: ../../content/developer/reference/views.rst:1878 +#: ../../content/developer/reference/addons/views.rst:850 +#: ../../content/developer/reference/addons/views.rst:1803 +#: ../../content/developer/reference/addons/views.rst:1880 msgid "``domain``" msgstr "" @@ -1168,15 +1229,15 @@ msgid "add the given domain to the current search" msgstr "" #: ../../content/developer/howtos/backend.rst:942 -#: ../../content/developer/howtos/web.rst:1707 -#: ../../content/developer/reference/data.rst:72 -#: ../../content/developer/reference/views.rst:852 -#: ../../content/developer/reference/views.rst:1273 -#: ../../content/developer/reference/views.rst:1481 -#: ../../content/developer/reference/views.rst:1606 -#: ../../content/developer/reference/views.rst:1803 -#: ../../content/developer/reference/views.rst:1871 -#: ../../content/developer/reference/views.rst:1973 +#: ../../content/developer/howtos/web.rst:1710 +#: ../../content/developer/reference/addons/data.rst:72 +#: ../../content/developer/reference/addons/views.rst:852 +#: ../../content/developer/reference/addons/views.rst:1275 +#: ../../content/developer/reference/addons/views.rst:1483 +#: ../../content/developer/reference/addons/views.rst:1608 +#: ../../content/developer/reference/addons/views.rst:1805 +#: ../../content/developer/reference/addons/views.rst:1873 +#: ../../content/developer/reference/addons/views.rst:1975 msgid "``context``" msgstr "" @@ -1201,7 +1262,7 @@ msgid "Add a button to group courses by responsible user." msgstr "" #: ../../content/developer/howtos/backend.rst:977 -#: ../../content/developer/reference/views.rst:945 +#: ../../content/developer/reference/addons/views.rst:945 msgid "Gantt" msgstr "" @@ -1270,8 +1331,8 @@ msgid "Graph views contain ```` with a mandatory ``@type`` attribute taki msgstr "" #: ../../content/developer/howtos/backend.rst:1029 -#: ../../content/developer/reference/views.rst:1151 -#: ../../content/developer/reference/views.rst:1733 +#: ../../content/developer/reference/addons/views.rst:1153 +#: ../../content/developer/reference/addons/views.rst:1735 msgid "``row`` (default)" msgstr "" @@ -1280,8 +1341,8 @@ msgid "the field should be aggregated by default" msgstr "" #: ../../content/developer/howtos/backend.rst:1032 -#: ../../content/developer/reference/views.rst:1156 -#: ../../content/developer/reference/views.rst:1737 +#: ../../content/developer/reference/addons/views.rst:1158 +#: ../../content/developer/reference/addons/views.rst:1739 msgid "``measure``" msgstr "" @@ -1302,7 +1363,7 @@ msgid "Add a Graph view in the Session object that displays, for each course, th msgstr "" #: ../../content/developer/howtos/backend.rst:1052 -#: ../../content/developer/reference/views.rst:1175 +#: ../../content/developer/reference/addons/views.rst:1177 msgid "Kanban" msgstr "" @@ -1475,6 +1536,7 @@ msgid "Modify the wizard model so that attendees can be registered to multiple s msgstr "" #: ../../content/developer/howtos/backend.rst:1224 +#: ../../content/developer/misc/i18n.rst:5 msgid "Internationalization" msgstr "" @@ -1535,7 +1597,7 @@ msgid "the standard rendering context provides a number of elements, the most im msgstr "" #: ../../content/developer/howtos/backend.rst:1320 -#: ../../content/developer/reference/reports.rst:70 +#: ../../content/developer/reference/addons/reports.rst:70 msgid "``docs``" msgstr "" @@ -1544,7 +1606,8 @@ msgid "the records for which the report is printed" msgstr "" #: ../../content/developer/howtos/backend.rst:1323 -#: ../../content/developer/reference/reports.rst:31 +#: ../../content/developer/reference/addons/reports.rst:31 +#: ../../content/developer/reference/addons/security.rst:124 msgid "``user``" msgstr "" @@ -1677,6 +1740,7 @@ msgid "https://github.com/abhishek-jaiswal/php-openerp-lib" msgstr "" #: ../../content/developer/howtos/backend.rst:1517 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:288 msgid "it is possible to :ref:`disable the automatic creation of some fields `" msgstr "" @@ -1780,6 +1844,137 @@ msgstr "" msgid "The field `company_id` must not be defined with `check_company=True`." msgstr "" +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel._check_company:1 +msgid "Check the companies of the values of the given field names." +msgstr "" + +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel._check_company:0 +#: ../../content/developer/misc/api/iap.rst:0 +#: ../../content/developer/misc/api/iap.rst:0 +#: ../../content/developer/misc/api/iap.rst:0 +#: ../../content/developer/misc/api/iap.rst:0 +#: ../../content/developer/misc/api/iap.rst:0 +#: ../../content/developer/misc/api/iap.rst:0 +#: ../../content/developer/misc/api/iap.rst:0 +#: ../../../odoo/odoo/http.py:docstring of odoo.http.route:0 +#: ../../../odoo/odoo/http.py:docstring of odoo.http.WebRequest:0 +#: ../../../odoo/odoo/http.py:docstring of odoo.http.WebRequest.csrf_token:0 +#: ../../../odoo/odoo/http.py:docstring of odoo.http.HttpRequest.make_response:0 +#: ../../../odoo/odoo/http.py:docstring of odoo.http.HttpRequest.render:0 +#: ../../../odoo/odoo/http.py:docstring of odoo.http.Response:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../content/developer/reference/addons/mixins.rst:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Field:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Field:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Char:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Float:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Binary:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Html:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Image:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Monetary:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Selection:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Text:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.tools.date_utils.add:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Date.context_today:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.tools.date_utils.end_of:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.tools.date_utils.start_of:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.tools.date_utils.subtract:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Date.to_date:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Date.to_string:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.tools.date_utils.add:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Datetime.context_timestamp:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.tools.date_utils.end_of:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.tools.date_utils.start_of:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.tools.date_utils.subtract:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Datetime.to_datetime:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Datetime.to_string:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Many2one:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.One2many:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Many2many:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Many2many:0 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Many2oneReference:0 +#: ../../../odoo/odoo/api.py:docstring of odoo.api.returns:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.with_company:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.with_env:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.invalidate_cache:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.create:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.copy:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.default_get:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.name_create:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.write:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.flush:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.browse:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.search:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.name_search:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.read:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.read_group:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.fields_get:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.fields_view_get:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.filtered:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.mapped:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.sorted:0 +#: ../../../odoo/odoo/exceptions.py:docstring of odoo.exceptions.RedirectWarning:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.BaseCase.browse_ref:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.BaseCase.ref:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.BaseCase.browse_ref:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.BaseCase.ref:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.BaseCase.browse_ref:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.BaseCase.ref:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.Form:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel._populate:0 +#: ../../../odoo/odoo/tools/populate.py:docstring of odoo.tools.populate.cartesian:0 +#: ../../../odoo/odoo/tools/populate.py:docstring of odoo.tools.populate.compute:0 +#: ../../../odoo/odoo/tools/populate.py:docstring of odoo.tools.populate.iterate:0 +#: ../../../odoo/odoo/tools/populate.py:docstring of odoo.tools.populate.randint:0 +#: ../../../odoo/odoo/tools/populate.py:docstring of odoo.tools.populate.randomize:0 +#: ../../content/developer/reference/javascript/qweb.rst:0 +msgid "Parameters" +msgstr "" + +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel._check_company:3 +msgid "names of relational fields to check" +msgstr "" + +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel._check_company:0 +#: ../../../odoo/odoo/api.py:docstring of odoo.api.Environment.company:0 +#: ../../../odoo/odoo/api.py:docstring of odoo.api.Environment.companies:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.create:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.write:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.search:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.read:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.read_group:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.fields_view_get:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.unlink:0 +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel.ensure_one:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.Form.save:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.O2MProxy.edit:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.O2MProxy.new:0 +#: ../../../odoo/odoo/tests/common.py:docstring of odoo.tests.common.O2MProxy.remove:0 +msgid "Raises" +msgstr "" + +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel._check_company:4 +msgid "if the `company_id` of the value of any field is not in `[False, self.company_id]` (or `self` if :class:`~odoo.addons.base.models.res_company`)." +msgstr "" + +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel._check_company:8 +msgid "For :class:`~odoo.addons.base.models.res_users` relational fields, verifies record company is in `company_ids` fields." +msgstr "" + +#: ../../../odoo/odoo/models.py:docstring of odoo.models.BaseModel._check_company:11 +msgid "User with main company A, having access to company A and B, could be assigned or linked to records in company B." +msgstr "" + #: ../../content/developer/howtos/company.rst:132 msgid "The `check_company` feature performs a strict check ! It means that if a record has no `company_id` (i.e. the field is not required), it cannot be linked to a record whose `company_id` is set." msgstr "" @@ -1797,8 +1992,8 @@ msgid "When the field `company_id` is made required on a model, a good practice msgstr "" #: ../../content/developer/howtos/company.rst:168 -#: ../../content/developer/reference/javascript_reference.rst:1421 -#: ../../content/developer/reference/views.rst:6 +#: ../../content/developer/reference/addons/views.rst:6 +#: ../../content/developer/reference/javascript/javascript_reference.rst:1422 msgid "Views" msgstr "" @@ -1819,39 +2014,39 @@ msgid "This is achieved with security rules based on `company_ids`, which contai msgstr "" #: ../../content/developer/howtos/company.rst:229 -#: ../../content/developer/howtos/web.rst:134 -#: ../../content/developer/howtos/web.rst:1875 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:96 +#: ../../content/developer/howtos/web.rst:137 +#: ../../content/developer/howtos/web.rst:1878 #: ../../content/developer/howtos/website.rst:490 -#: ../../content/developer/reference/actions.rst:176 -#: ../../content/developer/reference/orm.rst:605 -#: ../../content/developer/reference/orm.rst:607 -#: ../../content/developer/reference/orm.rst:722 -#: ../../content/developer/reference/orm.rst:879 -#: ../../content/developer/reference/qweb.rst:340 -#: ../../content/developer/reference/qweb.rst:421 -#: ../../content/developer/reference/security.rst:91 -#: ../../content/developer/reference/translations.rst:21 -#: ../../content/developer/reference/views.rst:13 -#: ../../content/developer/reference/views.rst:70 -#: ../../content/developer/reference/views.rst:81 -#: ../../content/developer/reference/views.rst:179 -#: ../../content/developer/reference/views.rst:241 -#: ../../content/developer/reference/views.rst:818 -#: ../../content/developer/reference/views.rst:938 -#: ../../content/developer/reference/views.rst:940 -#: ../../content/developer/reference/views.rst:1221 -#: ../../content/developer/reference/views.rst:1300 -#: ../../content/developer/reference/views.rst:1316 -#: ../../content/developer/reference/views.rst:1483 -#: ../../content/developer/reference/views.rst:2125 -#: ../../content/developer/webservices/iap.rst:121 -#: ../../content/developer/webservices/iap.rst:225 -#: ../../content/developer/webservices/iap.rst:407 -#: ../../content/developer/webservices/iap.rst:409 -#: ../../content/developer/webservices/iap.rst:510 -#: ../../content/developer/webservices/odoo.rst:400 -#: ../../content/developer/webservices/odoo.rst:996 -#: ../../content/developer/webservices/odoo.rst:1187 +#: ../../content/developer/misc/api/iap.rst:121 +#: ../../content/developer/misc/api/iap.rst:225 +#: ../../content/developer/misc/api/iap.rst:407 +#: ../../content/developer/misc/api/iap.rst:409 +#: ../../content/developer/misc/api/iap.rst:510 +#: ../../content/developer/misc/i18n/translations.rst:21 +#: ../../content/developer/reference/addons/actions.rst:176 +#: ../../../odoo/odoo/api.py:docstring of odoo.api:3 +#: ../../content/developer/reference/addons/orm.rst:620 +#: ../../content/developer/reference/addons/orm.rst:622 +#: ../../content/developer/reference/addons/orm.rst:737 +#: ../../content/developer/reference/addons/orm.rst:894 +#: ../../content/developer/reference/addons/security.rst:28 +#: ../../content/developer/reference/addons/security.rst:186 +#: ../../content/developer/reference/addons/views.rst:13 +#: ../../content/developer/reference/addons/views.rst:70 +#: ../../content/developer/reference/addons/views.rst:81 +#: ../../content/developer/reference/addons/views.rst:179 +#: ../../content/developer/reference/addons/views.rst:241 +#: ../../content/developer/reference/addons/views.rst:818 +#: ../../content/developer/reference/addons/views.rst:938 +#: ../../content/developer/reference/addons/views.rst:940 +#: ../../content/developer/reference/addons/views.rst:1223 +#: ../../content/developer/reference/addons/views.rst:1302 +#: ../../content/developer/reference/addons/views.rst:1318 +#: ../../content/developer/reference/addons/views.rst:1485 +#: ../../content/developer/reference/addons/views.rst:2127 +#: ../../content/developer/reference/javascript/qweb.rst:342 +#: ../../content/developer/reference/javascript/qweb.rst:423 msgid "Todo" msgstr "" @@ -1904,7 +2099,7 @@ msgid "Dump stack" msgstr "" #: ../../content/developer/howtos/profilecode.rst:85 -msgid "Sending the SIGQUIT signal to an Odoo process (only available on POSIX) makes this process output the current stack trace to log, with info level. When an odoo process seems stucked, sending this signal to the process permit to know what the process is doing, and letting the process continue his job." +msgid "Sending the SIGQUIT signal to an Odoo process (only available on POSIX) makes this process output the current stack trace to log, with info level. When an odoo process seems stuck, sending this signal to the process permit to know what the process is doing, and letting the process continue his job." msgstr "" #: ../../content/developer/howtos/profilecode.rst:91 @@ -1939,6 +2134,5749 @@ msgstr "" msgid "To open profile.svg you should use browser, because other viewer may not support interactive part." msgstr "" +#: ../../content/developer/howtos/rdtraining.rst:32 +#: ../../content/developer/howtos/rdtraining.rst:60 +#: ../../content/developer/howtos/rdtraining.rst:32 +#: ../../content/developer/howtos/rdtraining.rst:60 +msgid "Advanced Topics" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:7 +msgid "Getting Started" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:9 +msgid "Welcome to the Getting Started Odoo tutorial! If you reached this page that means you are interested in the development of your own Odoo module. It might also mean that you recently joined the Odoo company for a rather technical position. In any case, your journey to the technical side of Odoo starts here." +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:14 +msgid "This training is split in two parts. The first part is the 'Core Training': its objective is to give you an insight of the most important parts of the Odoo development framework. The chapters should be followed in their given order since they cover the development of a new Odoo application from scratch in an incremental way. In other words, each chapter depends on the previous one." +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:20 +msgid "The second part covers a set of 'Advanced' topics. Each topic can be followed independently, but requires the 'Core Training'. Note that some advanced topics cover basic features of an Odoo module, so it's a good idea to give them a quick look." +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:24 +msgid "All topics are built around a business case we will enhance along the way. The reader is expected to actively take part in the training by writing the solution for each exercise." +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:27 +msgid "Ready? Let's get started!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:30 +msgid "Core Training" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:40 +msgid ":doc:`rdtraining/01_architecture`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:41 +msgid ":doc:`rdtraining/02_setup`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:42 +msgid ":doc:`rdtraining/03_newapp`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:43 +msgid ":doc:`rdtraining/04_basicmodel`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:44 +msgid ":doc:`rdtraining/05_securityintro`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:45 +msgid ":doc:`rdtraining/06_firstui`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:46 +msgid ":doc:`rdtraining/07_basicviews`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:47 +msgid ":doc:`rdtraining/08_relations`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:48 +msgid ":doc:`rdtraining/09_compute_onchange`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:49 +msgid ":doc:`rdtraining/10_actions`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:50 +msgid ":doc:`rdtraining/11_constraints`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:51 +msgid ":doc:`rdtraining/12_sprinkles`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:52 +msgid ":doc:`rdtraining/13_inheritance`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:53 +msgid ":doc:`rdtraining/14_other_module`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:54 +msgid ":doc:`rdtraining/15_qwebintro`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:55 +msgid ":doc:`rdtraining/16_guidelines_pr`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:58 +msgid "Advanced topics" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:70 +msgid ":doc:`rdtraining/B_acl_irrules`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:71 +msgid ":doc:`rdtraining/C_data`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:72 +msgid ":doc:`rdtraining/E_unittest`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:73 +msgid ":doc:`rdtraining/J_reports`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining.rst:74 +msgid ":doc:`rdtraining/K_dashboard`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:5 +msgid "Chapter 1: Architecture Overview" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:8 +msgid "Multitier application" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:10 +msgid "Odoo follows a `multitier architecture`_, meaning that the presentation, the business logic and the data storage are separated. More specifically, it uses a three-tier architecture (image from Wikipedia):" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:18 +msgid "The presentation tier is a combination of HTML5, JavaScript and CSS. The logic tier is exclusively written in Python, while the data tier only supports PostgreSQL as an RDBMS." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:21 +msgid "Depending on the scope of your module, Odoo development can be done in any of these tiers. Therefore, before going any further, it may be a good idea to refresh your memory if you don't have an intermediate level in these topics." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:25 +msgid "In order to go through this tutorial, you will need a very basic knowledge of HTML and an intermediate level of Python. Advanced topics will require more knowledge in the other subjects. There are plenty of tutorials freely accessible, so we cannot recommend one over another since it depends on your background." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:30 +msgid "For reference this is the official `Python tutorial`_." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:33 +msgid "Odoo modules" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:35 +msgid "Both server and client extensions are packaged as *modules* which are optionally loaded in a *database*. A module is a collection of functions and data that target a single purpose." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:39 +msgid "Odoo modules can either add brand new business logic to an Odoo system or alter and extend existing business logic. One module can be created to add your country's accounting rules to Odoo's generic accounting support, while a different module can add support for real-time visualisation of a bus fleet." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:44 +msgid "Everything in Odoo starts and ends with modules." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:46 +msgid "Terminology: developers group their business features in Odoo *modules*. The main user-facing modules are flagged and exposed as *Apps*, but a majority of the modules aren't Apps. *Modules* may also be referred to as *addons* and the directories where the Odoo server finds them form the ``addons_path``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:54 +msgid "An Odoo module **can** contain a number of elements:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:59 +msgid ":ref:`Business objects `" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:57 +msgid "A business object (e.g. an invoice) is declared as a Python class. The fields defined in these classes are automatically mapped to database columns thanks to the :abbr:`ORM (Object-Relational Mapping)` layer." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:62 +msgid "Define UI display" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:65 +msgid "XML or CSV files declaring the model data:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:76 +msgid "Images, CSS or JavaScript files used by the web interface or website" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:78 +msgid "None of these elements are mandatory. Some modules may only add data files (e.g. country-specific accounting configuration), while others may only add business objects. During this training, we will create business objects, object views and data files. :ref:`Web controllers ` and :ref:`static web data ` are advanced topics." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:93 +msgid "When an Odoo module includes business objects (i.e. Python files), they are organized as a `Python package `_ with a ``__init__.py`` file. This file contains import instructions for various Python files in the module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:98 +msgid "Here is a simplified module directory:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:112 +msgid "Odoo Editions" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:114 +msgid "Odoo is available in `two versions`_: Odoo Enterprise (licensed & shared sources) and Odoo Community (open-source). In addition to services such as support or upgrades, the Enterprise version provides extra functionalities to Odoo. From a technical point-of-view, these functionalities are simply new modules installed on top of the modules provided by the Community version." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/01_architecture.rst:119 +msgid "Ready to start? Before writing actual code, let's go to the :ref:`next chapter ` to review the Odoo installation process. Even if Odoo is already running on your system, we strongly suggest you go through this chapter to make sure we start on the same page during the development of our new application." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:5 +msgid "Chapter 2: Development Environment Set-up" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:7 +msgid "There are multiple ways to install Odoo depending on the intended use case." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:9 +msgid "This document attempts to describe the installation options for an internal Odoo R&D developer. We assume that you are installing your development environment on a standard Odoo laptop with Linux Mint installed and up-to-date. At the time of writing, we are using a vanilla Linux Mint 20 (Ubuntu 20.04) as a starting point." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:15 +msgid "If you are using another environment, you can refer to :ref:`setup/install/source`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:19 +msgid "Fetch the sources & configure git" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:22 +msgid "Install and configure git" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:24 +msgid "The very first step of the installation process is to install the `git version control system `__ because the Odoo source code is managed on GitHub. Once installed, you can set your name and email:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:34 +msgid "Configure GitHub" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:36 +msgid "To fetch the sources and contribute to Odoo's development you will need a GitHub account. We recommend using your trigram (xyz) followed by '-odoo' as your username: 'xyz-odoo'. If you prefer, you can also use your personal GitHub account." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:41 +msgid "The easiest way to authenticate with GitHub is to use an SSH connection. Using the SSH authentication will allow you to connect to GitHub without supplying your username and password every time." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:46 +msgid "The following instructions are based on the official `GitHub documentation `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:49 +msgid "Here is a step-by-step procedure:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:52 +msgid "Generate a new SSH key, add it to the ssh-agent and copy the SSH key to your clipboard." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:62 +msgid "In Github:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:65 +msgid "In the upper-right corner of any page, click your profile photo, then click Settings" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:69 +msgid "In the user settings sidebar, click SSH and GPG keys." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:73 +msgid "Click New SSH key or Add SSH key." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:77 +msgid "In the \"Title\" field, add a descriptive label for the new key." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:78 +msgid "Paste your key into the \"Key\" field." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:82 +msgid "Click Add SSH key." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:86 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:88 +msgid "All the Odoo sources will be located in `$HOME/src/`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:97 +msgid "Cloning the repositories will take a while, enjoy a cup of coffee while you wait." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:99 +msgid "You may need to ask your manager for read rights to fetch the enterprise repository." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:104 +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:34 +msgid "Configure development repository" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:106 +msgid "To contribute to Odoo's development you will need to `fork the repository `__, create a branch containing your code in the fork and submit a `Pull Request `__ to the Odoo repository." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:112 +msgid "If you are lucky enough to work at Odoo, the forks already exist. They are called `odoo-dev/odoo` and `odoo-dev/enterprise`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:129 +msgid "Useful git commands" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:131 +msgid "Here are some useful git commands for your day-to-day work." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:133 +msgid "Change branch: When you change branches, both repositories (odoo and enterprise) must be synchronized, i.e. both need to be in the same branch." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:145 +msgid "Fetch and rebase:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:159 +msgid "Install the dependencies" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:162 +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:69 +#: ../../content/developer/misc/other/guidelines.rst:397 +#: ../../content/developer/reference/addons/security.rst:450 +#: ../../content/developer/reference/addons/security.rst:452 +#: ../../content/developer/reference/addons/testing.rst:665 +#: ../../content/developer/reference/javascript/qweb.rst:334 +msgid "Python" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:164 +msgid "Odoo requires Python 3.6 or later, if your computer is up-to-date you should already be at this version or higher." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:167 +msgid "You can check your Python version with:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:174 +msgid "Install pip3 and libraries" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:176 +msgid "For libraries using native code, installation of development tools and native dependencies is required before installing the Python dependencies of Odoo." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:185 +msgid "Install odoo requirements" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:195 +msgid "Install wkhtmltopdf" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:197 +msgid "wkhtmltopdf is a library to render HTML into PDF. Odoo uses it to create PDF reports. wkhtmltopdf is not installed through pip and must be installed manually in version 0.12.5 to support headers and footers." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:210 +msgid "Right-to-left interface support" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:212 +msgid "In order to support right-to-left (RTL) languages, we need `rtlcss` to convert the CSS files:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:220 +msgid "Install PostgreSQL" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:222 +msgid "As seen in :ref:`howto/rdtraining/01_architecture`, Odoo uses PostgreSQL as a RDBMS. In the context of a development machine, the easiest approach is to install it locally. Then we can create a PostgreSQL user corresponding to our current user:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:232 +msgid "Some useful SQL commands:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:246 +msgid "Run the server" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:249 +msgid "Running odoo-bin" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:251 +msgid "Once all dependencies are set up, Odoo can be launched by running odoo-bin, the command-line interface of the server." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:258 +msgid "There are multiple :ref:`command-line arguments ` that you can use to configure the server. In this training you will only need some of them." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:263 +msgid "The database that is going to be used." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:267 +msgid "A comma-separated list of directories in which modules are stored. These directories are scanned for modules." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:272 +msgid "Prevents the worker from using more than CPU seconds for each request." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:276 +msgid "Prevents the worker from taking longer than seconds to process a request." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:278 +msgid "The last two can be used to prevent the worker from being killed when debugging the source code." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:280 +msgid "You may face an error similar to `AttributeError: module '$MODULE_NAME' has no attribute '$ATTRIBUTE'`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:282 +msgid "In this case you may need to re-install the module with `$ pip install --upgrade --force-reinstall $MODULE_NAME`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:284 +msgid "If this error occurs with more than one module then you may need to re-install all the requirements with `$ pip3 install --upgrade --force-reinstall -r requirements.txt`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:287 +msgid "You can also clear the python cache to solve the issue" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:296 +msgid "Log in to Odoo" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:298 +msgid "Open `http://localhost:8069/` on your browser. We recommend you use: `Firefox `__, `Chrome `__ (`Chromium `__ the open source equivalent) or any other browser with development tools." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:304 +msgid "To log in as the administrator user, you can use the following credentials:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:306 +msgid "email = `admin`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:307 +msgid "password = `admin`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:310 +msgid "The developer mode" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:312 +msgid "The Developer or Debug Mode gives you access to additional (advanced) tools." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:314 +msgid "This is useful for training and we assume that the user is in developer mode for the rest of the tutorials." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:316 +msgid "To activate the developer or debug mode you can follow the steps `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:319 +msgid "Extra tools" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:322 +msgid "Code Editor" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:324 +msgid "If you are working at Odoo, many of your colleagues are using `VSCode`_ (`VSCodium`_ the open source equivalent), `Sublime Text`_, `Atom`_ or `PyCharm`_. However you are free to choose your preferred editor." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:328 +msgid "Don't forget to configure your linters correctly. Using a linter can help you by showing syntax and semantic warnings or errors. Odoo source code tries to respect Python and JavaScript standards, but some of them can be ignored." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:332 +msgid "For Python, we use PEP8 with these options ignored:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:334 +#: ../../content/developer/misc/other/guidelines.rst:410 +msgid "E501: line too long" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:335 +#: ../../content/developer/misc/other/guidelines.rst:411 +msgid "E301: expected 1 blank line, found 0" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:336 +#: ../../content/developer/misc/other/guidelines.rst:412 +msgid "E302: expected 2 blank lines, found 1" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:338 +msgid "For JavaScript, we use ESLint and you can find a `configuration file example here`_." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:348 +msgid "Administrator tools for PostgreSQL" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:350 +msgid "You can manage your PostgreSQL databases using the command line as demonstrated earlier or using a GUI application such as `pgAdmin `__ or `DBeaver `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:353 +msgid "To connect the GUI application to your database we recommend you connect using the Unix socket." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:355 +msgid "Host name/address = /var/run/postgresql" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:356 +msgid "Port = 5432" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:357 +msgid "Username = $USER" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:361 +msgid "Python Debugging" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:363 +msgid "When facing a bug or trying to understand how the code works, simply printing things out can go a long way, but a proper debugger can save a lot of time." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:366 +msgid "You can use a classic Python library debugger (`pdb `__, `pudb `__ or `ipdb `__) or you can use your editor's debugger. To avoid difficult configurations in the beginning, it is easier if you use a library debugger." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:371 +msgid "In the following example we use ipdb, but the process is similar with other libraries." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:373 +msgid "Install the library:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:379 +msgid "Trigger (breakpoint):" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:385 +#: ../../content/developer/reference/addons/views.rst:159 +#: ../../content/developer/reference/addons/views.rst:1903 +#: ../../content/developer/reference/addons/views.rst:1940 +#: ../../content/developer/reference/addons/views.rst:1966 +msgid "Example:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:398 +msgid "Here is a list of commands:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:402 +msgid "Without an argument, print the list of available commands. With a command as an argument, print help about that command." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:407 +msgid "The value of the ``expression`` is pretty-printed using the ``pprint`` module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:411 +msgid "Print a stack trace, with the most recent frame at the bottom." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:415 +msgid "Move the current frame one level down in the stack trace (to a newer frame)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:419 +msgid "Move the current frame one level up in the stack trace (to an older frame)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:423 +msgid "Continue the execution until the next line in the current function is reached or it returns." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:427 +msgid "Continue the execution and only stop when a breakpoint is encountered." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:431 +msgid "Execute the current line, stop at the first possible occasion (either in a function that is called or on the next line in the current function)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:436 +msgid "Quit the debugger. The program being executed is aborted." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:440 +msgid "To avoid killing the worker when debugging, you can add these arguments when launching the server: `--limit-time-cpu=9999 --limit-time-real=9999` Another solution is to add them directly in the `~/.odoorc` file:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/02_setup.rst:451 +msgid "Now that your server is running, it's time to start :ref:`writing your own application `!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:5 +msgid "Chapter 3: A New Application" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:7 +msgid "The purpose of this chapter is to lay the foundation for the creation of a completely new Odoo module. We will start from scratch with the minimum needed to have our module recognized by Odoo. In the upcoming chapters, we will progressively add features to build a realistic business case." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:12 +msgid "The Real Estate Advertisement module" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:14 +msgid "Our new module will cover a business area which is very specific and therefore not included in the standard set of modules: real estate. It is worth noting that before developing a new module, it is good practice to verify that Odoo doesn't already provide a way to answer the specific business case." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:19 +msgid "Here is an overview of the main list view containing some advertisements:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:25 +msgid "The top area of the form view summarizes important information for the property, such as the name, the property type, the postcode and so on. The first tab contains information describing the property: bedrooms, living area, garage, garden..." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:33 +msgid "The second tab lists the offers for the property. We can see here that potential buyers can make offers above or below the expected selling price. It is up to the seller to accept an offer." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:40 +msgid "Here is a quick video showing the workflow of the module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:42 +msgid "Hopefully, this video will be recorded soon :-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:45 +msgid "Prepare the addon directory" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:47 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`manifest `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:52 +msgid "**Goal**: the goal of this section is to have Odoo recognize our new module, which will be an empty shell for now. It will be listed in the Apps:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:59 +msgid "The first step of module creation is to create a new directory. To ease the development, we suggest you first create the directory ``/home/$USER/src/custom``. In this directory we add another directory ``estate``, which is our module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:63 +msgid "A module must contain at least 2 files: the ``__manifest__.py`` file and a ``__init__.py`` file. The ``__init__.py`` file can remain empty for now and we'll come back to it in the next chapter. On the other hand, the ``__manifest__.py`` file must describe our module and cannot remain empty. Its only required field is the ``name``, but it usually contains much more information." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:68 +msgid "Take a look at the `CRM file `__ as an example. In addition to providing the description of the module (``name``, ``category``, ``summary``, ``website``...), it lists its dependencies (``depends``). A dependency means that the Odoo framework will ensure that these modules are installed before our module is installed. Moreover, if one of these dependencies is uninstalled, then our module and **any other that depends on it will also be uninstalled**. Think about your favorite Linux distribution package manager (``apt``, ``dnf``, ``pacman``...): Odoo works in the same way." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:77 +msgid "Create the required addon files." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:79 +msgid "Create the following folders and files:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:81 +msgid "``/home/$USER/src/custom/estate/__init__.py``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:82 +msgid "``/home/$USER/src/custom/estate/__manifest__.py``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:84 +msgid "The ``__manifest__.py`` file should only define the name and the dependencies of our modules. The only necessary framework module for now is ``base``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:88 +msgid "Restart the Odoo server and add the ``custom`` folder to the ``addons-path``:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:94 +msgid "Go to Apps, click on Update Apps List, search for ``estate`` and... tadaaa, your module appears! Did it not appear? Maybe try removing the default 'Apps' filter ;-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:97 +msgid "Make your module an 'App'." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:99 +msgid "Add the appropriate key to your ``__manifest__.py`` so that the module appears when the 'Apps' filter is on." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:102 +msgid "You can even install the module! But obviously it's an empty shell, so no menu will appear." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/03_newapp.rst:104 +msgid "All good? If yes, then let's :ref:`create our first model `!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:5 +msgid "Chapter 4: Models And Basic Fields" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:7 +msgid "At the end of the :ref:`previous chapter `, we were able to create an Odoo module. However, at this point it is still an empty shell which doesn't allow us to store any data. In our real estate module, we want to store the information related to the properties (name, description, price, living area...) in a database. The Odoo framework provides tools to facilitate database interactions." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:13 +msgid "Before moving forward in the exercise, make sure the ``estate`` module is installed, i.e. it must appear as 'Installed' in the Apps list." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:19 +msgid "**Reference**: the documentation related to this topic can be found in the :ref:`reference/orm/model` API." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:24 +msgid "**Goal**: at the end of this section, the table ``estate_property`` should be created:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:35 +msgid "A key component of Odoo is the `ORM`_ layer. This layer avoids having to manually write most `SQL`_ and provides extensibility and security services\\ [#rawsql]_." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:39 +msgid "Business objects are declared as Python classes extending :class:`~odoo.models.Model`, which integrates them into the automated persistence system." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:43 +msgid "Models can be configured by setting attributes in their definition. The most important attribute is :attr:`~odoo.models.Model._name`, which is required and defines the name for the model in the Odoo system. Here is a minimum definition of a model::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:54 +msgid "This definition is enough for the ORM to generate a database table named ``test_model``. The ``.`` in the model ``_name`` is automatically converted into a ``_`` by the ORM. By convention all models are located in a ``models`` directory and each model is defined in its own Python file." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:59 +msgid "Take a look at how the ``crm_recurring_plan`` table is defined and how the corresponding Python file is imported:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:62 +msgid "The model is defined in the file ``crm/models/crm_recurring_plan.py`` (see `here `__)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:64 +msgid "The file ``crm_recurring_plan.py`` is imported in ``crm/models/__init__.py`` (see `here `__)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:66 +msgid "The folder ``models`` is imported in ``crm/__init__.py`` (see `here `__)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:69 +msgid "Define the real estate properties model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:71 +msgid "Based on example given in the CRM module, create the appropriate files and folder for the ``estate_property`` table." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:74 +msgid "When the files are created, add a minimum definition for the ``estate.property`` model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:77 +msgid "Any modification of the Python files requires a restart of the Odoo server. When we restart the server, we will add the parameters ``-d`` and ``-u``:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:84 +msgid "``-u estate`` means we want to upgrade the ``estate`` module, i.e. the ORM will apply database schema changes. In this case it creates a new table. ``-d rd-demo`` means that the upgrade should be performed on the ``rd-demo`` database. ``-u`` should always be used in combination with ``-d``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:89 +msgid "During the startup you should see the following warnings:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:99 +msgid "If this is the case, then you should be good! To be sure, double check with ``psql`` as demonstrated in the **Goal**." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:102 +msgid "Add a description." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:104 +msgid "Add a ``_description`` to your model to get rid of one of the warnings." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:109 +msgid "**Reference**: the documentation related to this topic can be found in the :ref:`reference/orm/fields` API." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:112 +msgid "Fields are used to define what the model can store and where they are stored. Fields are defined as attributes in the model class::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:123 +msgid "The ``name`` field is a :class:`~odoo.fields.Char` which will be represented as a Python unicode ``str`` and a SQL ``VARCHAR``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:127 +#: ../../content/developer/misc/api/iap.rst:636 +msgid "Types" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:131 +msgid "**Goal**: at the end of this section, several basic fields should have been added to the table ``estate_property``:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:167 +msgid "There are two broad categories of fields: 'simple' fields, which are atomic values stored directly in the model's table, and 'relational' fields, which link records (of the same or different models)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:171 +msgid "Simple field examples are :class:`~odoo.fields.Boolean`, :class:`~odoo.fields.Float`, :class:`~odoo.fields.Char`, :class:`~odoo.fields.Text`, :class:`~odoo.fields.Date` and :class:`~odoo.fields.Selection`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:175 +msgid "Add basic fields to the Real Estate Property table." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:177 +msgid "Add the following basic fields to the table:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:180 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:253 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:71 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:178 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:241 +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:173 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:215 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:262 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:149 +#: ../../content/developer/howtos/rdtraining/C_data.rst:175 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:300 +msgid "Field" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:180 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:71 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:178 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:241 +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:173 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:215 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:262 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:149 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:300 +msgid "Type" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:182 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:255 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:73 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:180 +#: ../../content/developer/howtos/rdtraining/C_data.rst:177 +#: ../../content/developer/reference/addons/static/res.country.state.csv:1 +msgid "name" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:182 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:184 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:73 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:180 +msgid "Char" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:183 +#: ../../content/developer/howtos/rdtraining/C_data.rst:179 +msgid "description" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:183 +msgid "Text" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:184 +#: ../../content/developer/howtos/rdtraining/C_data.rst:180 +msgid "postcode" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:185 +#: ../../content/developer/howtos/rdtraining/C_data.rst:181 +msgid "date_availability" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:185 +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:176 +msgid "Date" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:186 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:256 +#: ../../content/developer/howtos/rdtraining/C_data.rst:182 +msgid "expected_price" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:186 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:187 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:243 +msgid "Float" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:187 +#: ../../content/developer/howtos/rdtraining/C_data.rst:183 +msgid "selling_price" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:188 +#: ../../content/developer/howtos/rdtraining/C_data.rst:184 +msgid "bedrooms" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:188 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:189 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:190 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:193 +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:175 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:217 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:264 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:302 +msgid "Integer" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:189 +#: ../../content/developer/howtos/rdtraining/C_data.rst:185 +msgid "living_area" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:190 +#: ../../content/developer/howtos/rdtraining/C_data.rst:186 +msgid "facades" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:191 +#: ../../content/developer/howtos/rdtraining/C_data.rst:187 +msgid "garage" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:191 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:192 +msgid "Boolean" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:192 +#: ../../content/developer/howtos/rdtraining/C_data.rst:188 +msgid "garden" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:193 +#: ../../content/developer/howtos/rdtraining/C_data.rst:189 +msgid "garden_area" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:194 +#: ../../content/developer/howtos/rdtraining/C_data.rst:190 +msgid "garden_orientation" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:194 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:244 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:303 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:305 +msgid "Selection" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:197 +msgid "The ``garden_orientation`` field must have 4 possible values: 'North', 'South', 'East' and 'West'. The selection list is defined as a list of tuples, see `here `__ for an example." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:202 +msgid "When the fields are added to the model, restart the server with ``-u estate``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:208 +msgid "Connect to ``psql`` and check the structure of the table ``estate_property``. You'll notice that a couple of extra fields were also added to the table. We will revisit them later." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:216 +msgid "**Goal**: at the end of this section, the columns ``name`` and ``expected_price`` should be not nullable in the table ``estate_property``:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:231 +msgid "Much like the model itself, fields can be configured by passing configuration attributes as parameters::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:238 +msgid ":attr:`~odoo.fields.Field.string` (``str``, default: field's name)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:241 +msgid "If ``True``, the field can not be empty. It must either have a default value or always be given a value when creating a record." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:243 +msgid ":attr:`~odoo.fields.Field.help` (``str``, default: ``''``)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:244 +msgid "Provides long-form help tooltip for users in the UI." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:248 +msgid "Set attributes for existing fields." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:250 +msgid "Add the following attributes:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:253 +#: ../../content/developer/reference/javascript/javascript_reference.rst:2024 +msgid "Attribute" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:255 +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:256 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:73 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:180 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:245 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:246 +msgid "required" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:259 +msgid "After restarting the server, both fields should be not nullable." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:262 +msgid "Automatic Fields" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:264 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/fields/automatic`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:267 +msgid "You may have noticed your model has a few fields you never defined. Odoo creates a few fields in all models\\ [#autofields]_. These fields are managed by the system and can't be written to, but they can be read if useful or necessary:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:273 +msgid "The unique identifier for a record of the model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:281 +msgid "User who last modified the record." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:284 +msgid "Now that we have created our first model, let's :ref:`add some security `!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/04_basicmodel.rst:290 +msgid "writing raw SQL queries is possible, but requires caution as this bypasses all Odoo authentication and security mechanisms." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:5 +msgid "Chapter 5: Security - A Brief Introduction" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:7 +msgid "In the :ref:`previous chapter `, we created our first table intended to store business data. In a business application such as Odoo, one of the first questions to consider is who\\ [#who]_ can access the data. Odoo provides a security mechanism to allow access to the data for specific groups of users." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:12 +msgid "The topic of security is covered in more detail in :ref:`howto/rdtraining/B_acl_irrules`. This chapter aims to cover the minimum required for our new module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:16 +msgid "Data Files (CSV)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:18 +msgid "Odoo is a highly data driven system. Although behavior is customized using Python code, part of a module's value is in the data it sets up when loaded. One way to load data is through a CSV file. One example is the `list of country states `__ which is loaded at installation of the ``base`` module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:33 +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:83 +msgid "``id`` is an :term:`external identifier`. It can be used to refer to the record (without knowing its in-database identifier)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:35 +msgid "``country_id:id`` refers to the country by using its :term:`external identifier`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:36 +msgid "``name`` is the name of the state." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:37 +msgid "``code`` is the code of the state." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:39 +msgid "These three fields are `defined `__ in the ``res.country.state`` model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:43 +msgid "By convention, a file importing data is located in the ``data`` folder of a module. When the data is related to security, it is located in the ``security`` folder. When the data is related to views and actions (we will cover this later), it is located in the ``views`` folder. Additionally, all of these files must be declared in the ``data`` list within the ``__manifest__.py`` file. Our example file is defined `in the manifest of the base module `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:50 +msgid "Also note that the content of the data files is only loaded when a module is installed or updated." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:55 +msgid "The data files are sequentially loaded following their order in the ``__manifest__.py`` file. This means that if data ``A`` refers to data ``B``, you must make sure that ``B`` is loaded before ``A``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:59 +msgid "In the case of the country states, you will note that the `list of countries `__ is loaded **before** the `list of country states `__. This is because the states refer to the countries." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:65 +msgid "Why is all this important for security? Because all the security configuration of a model is loaded through data files, as we'll see in the next section." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:69 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:137 +#: ../../content/developer/reference/addons/security.rst:45 +msgid "Access Rights" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:71 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/security/acl`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:76 +msgid "**Goal**: at the end of this section, the following warning should not appear anymore:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:82 +msgid "When no access rights are defined on a model, Odoo determines that no users can access the data. It is even notified in the log:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:89 +msgid "Access rights are defined as records of the model ``ir.model.access``. Each access right is associated with a model, a group (or no group for global access) and a set of permissions: create, read, write and unlink\\ [#unlink]_. Such access rights are usually defined in a CSV file named ``ir.model.access.csv``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:95 +msgid "Here is an example for our previous ``test.model``:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:102 +msgid "``id`` is an :term:`external identifier`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:103 +msgid "``name`` is the name of the ``ir.model.access``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:104 +msgid "``model_id/id`` refers to the model which the access right applies to. The standard way to refer to the model is ``model_``, where ```` is the ``_name`` of the model with the ``.`` replaced by ``_``. Seems cumbersome? Indeed it is..." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:107 +msgid "``group_id/id`` refers to the group which the access right applies to. We will cover the concept of groups in the :ref:`advanced topic ` dedicated to the security." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:109 +msgid "``perm_read,perm_write,perm_create,perm_unlink``: read, write, create and unlink permissions" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:111 +msgid "Add access rights." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:113 +msgid "Create the ``ir.model.access.csv`` file in the appropriate folder and define it in the ``__manifest__.py`` file." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:116 +msgid "Give the read, write, create and unlink permissions to the group ``base.group_user``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:118 +msgid "Tip: the warning message in the log gives you most of the solution ;-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:120 +msgid "Restart the server and the warning message should have disappeared!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:122 +msgid "It's now time to finally :ref:`interact with the UI `!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:124 +msgid "meaning which Odoo user (or group of users)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/05_securityintro.rst:126 +msgid "'unlink' is the equivalent of 'delete'" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:5 +msgid "Chapter 6: Finally, Some UI To Play With" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:7 +msgid "Now that we've created our new :ref:`model ` and its corresponding :ref:`access rights `, it is time to interact with the user interface." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:11 +msgid "At the end of this chapter, we will have created a couple of menus in order to access a default list and form view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:15 +msgid "Data Files (XML)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:17 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/data`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:20 +msgid "In :ref:`howto/rdtraining/05_securityintro`, we added data through a CSV file. The CSV format is convenient when the data to load has a simple format. When the format is more complex (e.g. load the structure of a view or an email template), we use the XML format. For example, this `help field `__ contains HTML tags. While it would be possible to load such data through a CSV file, it is more convenient to use an XML file." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:28 +msgid "The XML files must be added to the same folders as the CSV files and defined similarly in the ``__manifest__.py``. The content of the data files is also sequentially loaded when a module is installed or updated, therefore all remarks made for CSV files hold true for XML files. When the data is linked to views, we add them to the ``views`` folder." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:33 +msgid "In this chapter we will load our first action and menus though an XML file. Actions and menus are standard records in the database." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:38 +msgid "When performance is important, the CSV format is preferred over the XML format. This is the case in Odoo where loading a CSV file is faster than loading an XML file." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:41 +msgid "In Odoo, the user interface (actions, menus and views) is largely defined by creating and composing records defined in an XML file. A common pattern is Menu > Action > View. To access records the user navigates through several menu levels; the deepest level is an action which triggers the opening of a list of the records." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:47 +#: ../../content/developer/misc/other/iot.rst:138 +#: ../../content/developer/reference/addons/actions.rst:6 +msgid "Actions" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:49 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/actions`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:54 +msgid "**Goal**: at the end of this section, an action should be loaded in the system. We won't see anything yet in the UI, but the file should be loaded in the log:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:61 +msgid "Actions can be triggered in three ways:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:67 +msgid "We will only cover the first case in this chapter. The second case will be covered in a :ref:`later chapter ` while the last is the focus of an advanced topic. In our Real Estate example, we would like to link a menu to the ``estate.property`` model, so we are able to create a new record. The action can be viewed as the link between the menu and the model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:73 +msgid "A basic action for our ``test.model`` is:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:85 +msgid "``model`` has a fixed value of ``ir.actions.act_window`` (:ref:`reference/actions/window`)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:86 +msgid "``name`` is the name of the action." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:87 +msgid "``res_model`` is the model which the action applies to." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:88 +msgid "``view_mode`` are the views that will be available; in this case they are the list (tree) and form views. We'll see :ref:`later ` that there can be other view modes." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:91 +msgid "Examples can be found everywhere in Odoo, but `this `__ is a good example of a simple action. Pay attention to the structure of the XML data file since you will need it in the following exercise." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:96 +msgid "Add an action." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:98 +msgid "Create the ``estate_property_views.xml`` file in the appropriate folder and define it in the ``__manifest__.py`` file." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:101 +msgid "Create an action for the model ``estate.property``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:103 +msgid "Restart the server and you should see the file loaded in the log." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:106 +msgid "Menus" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:108 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/data/shortcuts`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:113 +msgid "**Goal**: at the end of this section, three menus should be created and the default view is displayed:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:128 +msgid "To reduce the complexity in declaring a menu (``ir.ui.menu``) and connecting it to the corresponding action, we can use the ```` shortcut ." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:131 +msgid "A basic menu for our ``test_model_action`` is:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:137 +msgid "The menu ``test_model_menu_action`` is linked to the action ``test_model_action``, and the action is linked to the model ``test.model``. As previously mentioned, the action can be seen as the link between the menu and the model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:141 +msgid "However, menus always follow an architecture, and in practice there are three levels of menus:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:143 +msgid "The root menu, which is displayed in the App switcher (the Odoo Community App switcher is a dropdown menu)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:145 +msgid "The first level menu, displayed in the top bar" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:146 +msgid "The action menus" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:156 +msgid "The easiest way to define the structure is to create it in the XML file. A basic structure for our ``test_model_action`` is:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:167 +msgid "The name for the third menu is taken from the name of the ``action``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:169 +msgid "Add menus." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:171 +msgid "Create the ``estate_menus.xml`` file in the appropriate folder and define it in the ``__manifest__.py`` file. Remember the sequential loading of the data files ;-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:174 +msgid "Create the three levels of menus for the ``estate.property`` action created in the previous exercise. Refer to the **Goal** of this section for the expected result." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:177 +msgid "Restart the server and **refresh the browser**\\ [#refresh]_. You should now see the menus, and you'll even be able to create your first real estate property advertisement!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:181 +msgid "Fields, Attributes And View" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:185 +msgid "**Goal**: at the end of this section, the selling price should be read-only and the number of bedrooms and the availability date should have default values. Additionally the selling price and availability date values won't be copied when the record is duplicated." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:193 +msgid "The reserved fields ``active`` and ``state`` are added to the ``estate.property`` model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:195 +msgid "So far we have only used the generic view for our real estate property advertisements, but in most cases we want to fine tune the view. There are many fine-tunings possible in Odoo, but usually the first step is to make sure that:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:199 +msgid "some fields have a default value" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:200 +msgid "some fields are read-only" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:201 +msgid "some fields are not copied when duplicating the record" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:203 +msgid "In our real estate business case, we would like the following:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:205 +msgid "The selling price should be read-only (it will be automatically filled in later)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:206 +msgid "The availability date and the selling price should not be copied when duplicating a record" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:207 +msgid "The default number of bedrooms should be 2" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:208 +msgid "The default availability date should be in 3 months" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:211 +msgid "Some New Attributes" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:213 +msgid "Before moving further with the view design, let's step back to our model definition. We saw that some attributes, such as ``required=True``, impact the table schema in the database. Other attributes will impact the view or provide default values." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:217 +msgid "Add new attributes to the fields." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:219 +msgid "Find the appropriate attributes (see :class:`~odoo.fields.Field`) to:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:221 +msgid "set the selling price as read-only" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:222 +msgid "prevent copying of the availability date and the selling price values" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:224 +msgid "Restart the server and refresh the browser. You should not be able to set any selling prices. When duplicating a record, the availability date should be empty." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:228 +msgid "Default Values" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:230 +msgid "Any field can be given a default value. In the field definition, add the option ``default=X`` where ``X`` is either a Python literal value (boolean, integer, float, string) or a function taking a model and returning a value::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:237 +msgid "The ``name`` field will have the value 'Unknown' by default while the ``last_seen`` field will be set as the current time." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:240 +msgid "Set default values." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:242 +msgid "Add the appropriate default attributes so that:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:244 +msgid "the default number of bedrooms is 2" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:245 +msgid "the default availability date is in 3 months" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:247 +msgid "Tip: this might help you: :meth:`~odoo.fields.Date.today`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:249 +msgid "Check that the default values are set as expected." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:252 +msgid "Reserved Fields" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:254 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/orm/fields/reserved`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:257 +msgid "A few field names are reserved for pre-defined behaviors. They should be defined on a model when the related behavior is desired." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:260 +msgid "Add active field." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:262 +msgid "Add the ``active`` field to the ``estate.property`` model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:264 +msgid "Restart the server, create a new property, then come back to the list view... The property will not be listed! ``active`` is an example of a reserved field with a specific behavior: when a record has ``active=False``, it is automatically removed from any search. To display the created property, you will need to specifically search for inactive records." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:273 +msgid "Set a default value for active field." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:275 +msgid "Set the appropriate default value for the ``active`` field so it doesn't disappear anymore." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:277 +msgid "Note that the default ``active=False`` value was assigned to all existing records." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:279 +msgid "Add state field." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:281 +msgid "Add a ``state`` field to the ``estate.property`` model. Five values are possible: New, Offer Received, Offer Accepted, Sold and Canceled. It must be required, should not be copied and should have its default value set to 'New'." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:285 +msgid "Make sure to use the correct type!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:287 +msgid "The ``state`` will be used later on for several UI enhancements." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:289 +msgid "Now that we are able to interact with the UI thanks to the default views, the next step is obvious: we want to define :ref:`our own views `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/06_firstui.rst:292 +msgid "A refresh is needed since the web client keeps a cache of the various menus and views for performance reasons." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:5 +msgid "Chapter 7: Basic Views" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:7 +msgid "We have seen in the :ref:`previous chapter ` that Odoo is able to generate default views for a given model. In practice, the default view is **never** acceptable for a business application. Instead, we should at least organize the various fields in a logical manner." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:12 +msgid "Views are defined in XML files with actions and menus. They are instances of the ``ir.ui.view`` model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:15 +msgid "In our real estate module, we need to organize the fields in a logical way:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:17 +msgid "in the list (tree) view, we want to display more than just the name." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:18 +msgid "in the form view, the fields should be grouped." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:19 +msgid "in the search view, we must be able to search on more than just the name. Specifically, we want a filter for the 'Available' properties and a shortcut to group by postcode." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:23 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:317 +#: ../../content/developer/reference/addons/views.rst:1374 +msgid "List" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:25 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/views/list`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:30 +msgid "**Goal**: at the end of this section, the list view should look like this:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:36 +msgid "List views, also called tree views, display records in a tabular form." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:38 +msgid "Their root element is ````. The most basic version of this view simply lists all the fields to display in the table (where each field is a column):" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:48 +msgid "A simple example can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:51 +msgid "Add a custom list view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:53 +msgid "Define a list view for the ``estate.property`` model in the appropriate XML file. Check the **Goal** of this section for the fields to display." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:56 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:378 +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:117 +msgid "Tips:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:58 +msgid "do not add the ``editable=\"bottom\"`` attribute that you can find in the example above. We'll come back to it later." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:60 +msgid "some field labels may need to be adapted to match the reference." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:63 +msgid "As always, you need to restart the server (do not forget the ``-u`` option) and refresh the browser to see the result." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:68 +msgid "You will probably use some copy-paste in this chapter, therefore always make sure that the ``id`` remains unique for each view!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:72 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:234 +#: ../../content/developer/reference/addons/views.rst:728 +msgid "Form" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:74 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/views/form`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:79 +msgid "**Goal**: at the end of this section, the form view should look like this:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:87 +msgid "Their root element is ``
``. They are composed of high-level structure elements (groups and notebooks) and interactive elements (buttons and fields):" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:110 +msgid "It is possible to use regular HTML tags such as ``div`` and ``h1`` as well as the the ``class`` attribute (Odoo provides some built-in classes) to fine-tune the look." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:113 +msgid "A simple example can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:116 +msgid "Add a custom form view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:118 +msgid "Define a form view for the ``estate.property`` model in the appropriate XML file. Check the **Goal** of this section for the expected final design of the page." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:121 +msgid "This might require some trial and error before you get to the expected result ;-) It is advised that you add the fields and the tags one at a time to help understand how it works." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:124 +msgid "In order to avoid relaunching the server every time you do a modification to the view, it can be convenient to use the ``--dev xml`` parameter when launching the server:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:131 +msgid "This parameter allows you to just refresh the page to view your view modifications." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:134 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:385 +#: ../../content/developer/reference/addons/views.rst:1822 +msgid "Search" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:136 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/views/search`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:141 +msgid "**Goal**: at the end of this section, the search view should look like this:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:155 +msgid "Search views are slightly different from the list and form views since they don't display *content*. Although they apply to a specific model, they are used to filter other views' content (generally aggregated views such as :ref:`reference/views/list`). Beyond the difference in use case, they are defined the same way." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:160 +msgid "Their root element is ````. The most basic version of this view simply lists all the fields for which a shortcut is desired:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:170 +msgid "The default search view generated by Odoo provides a shortcut to filter by ``name``. It is very common to add the fields which the user is likely to filter on in a customized search view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:173 +msgid "Add a custom search view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:175 +msgid "Define a search view for the ``estate.property`` model in the appropriate XML file. Check the first image of this section's **Goal** for the list of fields." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:178 +msgid "After restarting the server, it should be possible to filter on the given fields." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:183 +msgid "``domain``: adds the given domain to the current search" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:184 +msgid "``context``: adds some context to the current search; uses the key ``group_by`` to group results on the given field name" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:187 +msgid "A simple example can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:190 +msgid "Before going further in the exercise, it is necessary to introduce the 'domain' concept." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:195 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/orm/domains`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:198 +msgid "In Odoo, a domain encodes conditions on records: a domain is a list of criteria used to select a subset of a model's records. Each criterion is a triplet with a *field name*, an *operator* and a *value*. A record satisfies a criterion if the specified field meets the condition of the operator applied to the value." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:203 +msgid "For instance, when used on the *Product* model the following domain selects all *services* with a unit price greater than *1000*::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:208 +msgid "By default criteria are combined with an implicit AND, meaning *every* criterion needs to be satisfied for a record to match a domain. The logical operators ``&`` (AND), ``|`` (OR) and ``!`` (NOT) can be used to explicitly combine criteria. They are used in prefix position (the operator is inserted before its arguments rather than between). For instance, to select products 'which are services *OR* have a unit price which is *NOT* between 1000 and 2000'::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:221 +msgid "Add filter and Group By." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:223 +msgid "The following should be added to the previously created search view:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:225 +msgid "a filter which displays available properties, i.e. the state should be 'New' or 'Offer Received'." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:227 +msgid "the ability to group results by postcode." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/07_basicviews.rst:229 +msgid "Looking good? At this point we are already able to create models and design a user interface which makes sense business-wise. However, a key component is still missing: the :ref:`link between models `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:5 +msgid "Chapter 8: Relations Between Models" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:7 +msgid "The :ref:`previous chapter ` covered the creation of custom views for a model containing basic fields. However, in any real business scenario we need more than one model. Moreover, links between models are necessary. One can easily imagine one model containing the customers and another one containing the list of users. You might need to refer to a customer or a user on any existing business model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:13 +msgid "In our real estate module, we want the following information for a property:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:15 +msgid "the customer who bought the property" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:16 +msgid "the real restate agent who sold the property" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:17 +msgid "the property type: house, apartment, penthouse, castle..." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:18 +msgid "a list of tags characterizing the property: cozy, renovated..." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:19 +msgid "a list of the offers received" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:22 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:304 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:306 +msgid "Many2one" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:24 +msgid "**Reference**: the documentation related to this topic can be found in :class:`~odoo.fields.Many2one`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:29 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:136 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:199 +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:26 +#: ../../content/developer/howtos/rdtraining/10_actions.rst:27 +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:24 +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:20 +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:18 +msgid "**Goal**: at the end of this section:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:31 +msgid "a new ``estate.property.type`` model should be created with the corresponding menu, action and views." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:37 +msgid "three Many2one fields should be added to the ``estate.property`` model: property type, buyer and seller." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:43 +msgid "In our real estate module, we want to define the concept of property type. A property type is, for example, a house or an apartment. It is a standard business need to categorize properties according to their type, especially to refine filtering." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:47 +msgid "A property can have **one** type, but the same type can be assigned to **many** properties. This is supported by the **many2one** concept." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:50 +msgid "A many2one is a simple link to another object. For example, in order to define a link to the ``res.partner`` in our test model, we can write::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:55 +msgid "By convention, many2one fields have the ``_id`` suffix. Accessing the data in the partner can then be easily done with::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:62 +msgid "`foreign keys `_" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:64 +msgid "In practice a many2one can be seen as a dropdown list in a form view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:66 +msgid "Add the Real Estate Property Type table." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:68 +msgid "Create the ``estate.property.type`` model and add the following field:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:71 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:178 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:241 +#: ../../content/developer/reference/addons/views.rst:68 +msgid "Attributes" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:76 +#: ../../content/developer/howtos/rdtraining/08_relations.rst:183 +msgid "Add the menus as displayed in this section's **Goal**" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:77 +msgid "Add the field ``property_type_id`` into your ``estate.property`` model and its form, tree and search views" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:80 +msgid "This exercise is a good recap of the previous chapters: you need to create a :ref:`model `, set the :ref:`model `, add an :ref:`action and a menu `, and :ref:`create a view `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:86 +msgid "Tip: do not forget to import any new Python files in ``__init__.py``, add new data files in ``__manifest.py__`` or add the access rights ;-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:89 +msgid "Once again, restart the server and refresh to see the results!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:91 +msgid "In the real estate module, there are still two missing pieces of information we want on a property: the buyer and the salesperson. The buyer can be any individual, but on the other hand the salesperson must be an employee of the real estate agency (i.e. an Odoo user)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:95 +msgid "In Odoo, there are two models which we commonly refer to:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:97 +msgid "``res.partner``: a partner is a physical or legal entity. It can be a company, an individual or even a contact address." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:99 +msgid "``res.users``: the users of the system. Users can be 'internal', i.e. they have access to the Odoo backend. Or they can be 'portal', i.e. they cannot access the backend, only the frontend (e.g. to access their previous orders in eCommerce)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:103 +msgid "Add the buyer and the salesperson." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:105 +msgid "Add a buyer and a salesperson to the ``estate.property`` model using the two common models mentioned above. They should be added in a new tab of the form view, as depicted in this section's **Goal**." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:108 +msgid "The default value for the salesperson must be the current user. The buyer should not be copied." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:110 +msgid "Tip: to get the default value, check the note below or look at an example `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:126 +msgid "Now let's have a look at other types of links." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:129 +msgid "Many2many" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:131 +msgid "**Reference**: the documentation related to this topic can be found in :class:`~odoo.fields.Many2many`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:138 +msgid "a new ``estate.property.tag`` model should be created with the corresponding menu and action." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:144 +msgid "tags should be added to the ``estate.property`` model:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:150 +msgid "In our real estate module, we want to define the concept of property tags. A property tag is, for example, a property which is 'cozy' or 'renovated'." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:153 +msgid "A property can have **many** tags and a tag can be assigned to **many** properties. This is supported by the **many2many** concept." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:156 +msgid "A many2many is a bidirectional multiple relationship: any record on one side can be related to any number of records on the other side. For example, in order to define a link to the ``account.tax`` model on our test model, we can write::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:162 +msgid "By convention, many2many fields have the ``_ids`` suffix. This means that several taxes can be added to our test model. It behaves as a list of records, meaning that accessing the data must be done in a loop::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:169 +msgid "A list of records is known as a *recordset*, i.e. an ordered collection of records. It supports standard Python operations on collections, such as ``len()`` and ``iter()``, plus extra set operations like ``recs1 | recs2``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:173 +msgid "Add the Real Estate Property Tag table." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:175 +msgid "Create the ``estate.property.tag`` model and add the following field:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:184 +msgid "Add the field ``tag_ids`` to your ``estate.property`` model and in its form and tree views" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:186 +msgid "Tip: in the view, use the ``widget=\"many2many_tags\"`` attribute as demonstrated `here `__. The ``widget`` attribute will be explained in detail in :ref:`a later chapter of the training `. For now, you can try to adding and removing it and see the result ;-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:192 +msgid "One2many" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:194 +msgid "**Reference**: the documentation related to this topic can be found in :class:`~odoo.fields.One2many`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:201 +msgid "a new ``estate.property.offer`` model should be created with the corresponding form and tree view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:202 +msgid "offers should be added to the ``estate.property`` model:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:208 +msgid "In our real estate module, we want to define the concept of property offers. A property offer is an amount a potential buyer offers to the seller. The offer can be lower or higher than the expected price." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:212 +msgid "An offer applies to **one** property, but the same property can have **many** offers. The concept of **many2one** appears once again. However, in this case we want to display the list of offers for a given property so we will use the **one2many** concept." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:216 +msgid "A one2many is the inverse of a many2one. For example, we defined on our test model a link to the ``res.partner`` model thanks to the field ``partner_id``. We can define the inverse relation, i.e. the list of test models linked to our partner::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:222 +msgid "The first parameter is called the ``comodel`` and the second parameter is the field we want to inverse." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:225 +msgid "By convention, one2many fields have the ``_ids`` suffix. They behave as a list of records, meaning that accessing the data must be done in a loop::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:233 +msgid "Because a :class:`~odoo.fields.One2many` is a virtual relationship, there *must* be a :class:`~odoo.fields.Many2one` field defined in the comodel." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:236 +msgid "Add the Real Estate Property Offer table." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:238 +msgid "Create the ``estate.property.offer`` model and add the following fields:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:241 +#: ../../content/developer/howtos/rdtraining/C_data.rst:175 +#: ../../content/developer/howtos/rdtraining/C_data.rst:175 +msgid "Values" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:243 +msgid "price" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:244 +msgid "status" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:244 +msgid "no copy" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:244 +msgid "Accepted, Refused" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:245 +msgid "partner_id" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:245 +msgid "Many2one (``res.partner``)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:246 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:304 +msgid "property_id" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:246 +msgid "Many2one (``estate.property``)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:249 +msgid "Create a tree view and a form view with the ``price``, ``partner_id`` and ``status`` fields. No need to create an action or a menu." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:251 +msgid "Add the field ``offer_ids`` to your ``estate.property`` model and in its form view as depicted in this section's **Goal**." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:254 +msgid "There are several important things to notice here. First, we don't need an action or a menu for all models. Some models are intended to be accessed only through another model. This is the case in our exercise: an offer is always accessed through a property." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:258 +msgid "Second, despite the fact that the ``property_id`` field is required, we did not include it in the views. How does Odoo know which property our offer is linked to? Well that's part of the magic of using the Odoo framework: sometimes things are defined implicitly. When we create a record through a one2many field, the corresponding many2one is populated automatically for convenience." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/08_relations.rst:264 +msgid "Still alive? This chapter is definitely not the easiest one. It introduced a couple of new concepts while relying on everything that was introduced before. The :ref:`next chapter ` will be lighter, don't worry ;-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:5 +msgid "Chapter 9: Computed Fields And Onchanges" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:7 +msgid "The :ref:`relations between models ` are a key component of any Odoo module. They are necessary for the modelization of any business case. However, we may want links between the fields within a given model. Sometimes the value of one field is determined from the values of other fields and other times we want to help the user with data entry." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:13 +msgid "These cases are supported by the concepts of computed fields and onchanges. Although this chapter is not technically complex, the semantics of both concepts is very important. This is also the first time we will write Python logic. Until now we haven't written anything other than class definitions and field declarations." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:19 +#: ../../../odoo/odoo/fields.py:docstring of odoo.fields.Field:89 +#: ../../content/developer/reference/addons/orm.rst:232 +msgid "Computed Fields" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:21 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/fields/compute`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:28 +msgid "In the property model, the total area and the best offer should be computed:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:34 +msgid "In the property offer model, the validity date should be computed and can be updated:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:40 +msgid "In our real estate module, we have defined the living area as well as the garden area. It is then natural to define the total area as the sum of both fields. We will use the concept of a computed field for this, i.e. the value of a given field will be computed from the value of other fields." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:44 +msgid "So far fields have been stored directly in and retrieved directly from the database. Fields can also be *computed*. In this case, the field's value is not retrieved from the database but computed on-the-fly by calling a method of the model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:49 +msgid "To create a computed field, create a field and set its attribute :attr:`~odoo.fields.Field.compute` to the name of a method. The computation method should set the value of the computed field for every record in ``self``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:54 +msgid "By convention, :attr:`~odoo.fields.Field.compute` methods are private, meaning that they cannot be called from the presentation tier, only from the business tier (see :ref:`howto/rdtraining/01_architecture`). Private methods have a name starting with an underscore ``_``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:61 +msgid "The value of a computed field usually depends on the values of other fields in the computed record. The ORM expects the developer to specify those dependencies on the compute method with the decorator :func:`~odoo.api.depends`. The given dependencies are used by the ORM to trigger the recomputation of the field whenever some of its dependencies have been modified::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:80 +msgid "``self`` is a collection." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:83 +msgid "The object ``self`` is a *recordset*, i.e. an ordered collection of records. It supports the standard Python operations on collections, e.g. ``len(self)`` and ``iter(self)``, plus extra set operations such as ``recs1 | recs2``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:88 +msgid "Iterating over ``self`` gives the records one by one, where each record is itself a collection of size 1. You can access/assign fields on single records by using the dot notation, e.g. ``record.name``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:92 +msgid "Many examples of computed fields can be found in Odoo. `Here `__ is a simple one." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:96 +msgid "Compute the total area." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:98 +msgid "Add the ``total_area`` field to ``estate.property``. It is defined as the sum of the ``living_area`` and the ``garden_area``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:101 +msgid "Add the field in the form view as depicted on the first image of this section's **Goal**." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:103 +msgid "For relational fields it's possible to use paths through a field as a dependency::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:113 +msgid "The example is given with a :class:`~odoo.fields.Many2one`, but it is valid for :class:`~odoo.fields.Many2many` or a :class:`~odoo.fields.One2many`. An example can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:117 +msgid "Let's try it in our module with the following exercise!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:119 +msgid "Compute the best offer." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:121 +msgid "Add the ``best_price`` field to ``estate.property``. It is defined as the highest (i.e. maximum) of the offers' ``price``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:124 +msgid "Add the field to the form view as depicted in the first image of this section's **Goal**." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:126 +msgid "Tip: you might want to try using the :meth:`~odoo.models.BaseModel.mapped` method. See `here `__ for a simple example." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:131 +msgid "Inverse Function" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:133 +msgid "You might have noticed that computed fields are read-only by default. This is expected since the user is not supposed to set a value." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:136 +msgid "In some cases, it might be useful to still be able to set a value directly. In our real estate example, we can define a validity duration for an offer and set a validity date. We would like to be able to set either the duration or the date with one impacting the other." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:140 +msgid "To support this Odoo provides the ability to use an ``inverse`` function::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:159 +msgid "An example can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:162 +msgid "A compute method sets the field while an inverse method sets the field's dependencies." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:165 +msgid "Note that the ``inverse`` method is called when saving the record, while the ``compute`` method is called at each change of its dependencies." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:168 +msgid "Compute a validity date for offers." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:170 +msgid "Add the following fields to the ``estate.property.offer`` model:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:173 +msgid "Default" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:175 +msgid "validity" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:175 +msgid "7" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:176 +msgid "date_deadline" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:179 +msgid "Where ``date_deadline`` is a computed field which is defined as the sum of two fields from the offer: the ``create_date`` and the ``validity``. Define an appropriate inverse function so that the user can set either the date or the validity." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:183 +msgid "Tip: the ``create_date`` is only filled in when the record is created, therefore you will need a fallback to prevent crashing at time of creation." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:186 +msgid "Add the fields in the form view and the list view as depicted on the second image of this section's **Goal**." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:189 +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:275 +msgid "Additional Information" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:191 +msgid "Computed fields are **not stored** in the database by default. Therefore it is **not possible** to search on a computed field unless a ``search`` method is defined. This topic is beyond the scope of this training, so we won't cover it. An example can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:196 +msgid "Another solution is to store the field with the ``store=True`` attribute. While this is usually convenient, pay attention to the potential computation load added to your model. Lets re-use our example::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:208 +msgid "Every time the partner ``name`` is changed, the ``description`` is automatically recomputed for **all the records** referring to it! This can quickly become prohibitive to recompute when millions of records need recomputation." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:212 +msgid "It is also worth noting that a computed field can depend on another computed field. The ORM is smart enough to correctly recompute all the dependencies in the right order... but sometimes at the cost of degraded performance." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:216 +msgid "In general performance must always be kept in mind when defining computed fields. The more complex is your field to compute (e.g. with a lot of dependencies or when a computed field depends on other computed fields), the more time it will take to compute. Always take some time to evaluate the cost of a computed field beforehand. Most of the time it is only when your code reaches a production server that you realize it slows down a whole process. Not cool :-(" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:223 +msgid "Onchanges" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:225 +msgid "**Reference**: the documentation related to this topic can be found in :func:`~odoo.api.onchange`:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:230 +msgid "**Goal**: at the end of this section, enabling the garden will set a default area of 10 and an orientation to North." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:237 +msgid "In our real estate module, we also want to help the user with data entry. When the 'garden' field is set, we want to give a default value for the garden area as well as the orientation. Additionally, when the 'garden' field is unset we want the garden area to reset to zero and the orientation to be removed. In this case, the value of a given field modifies the value of other fields." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:243 +msgid "The 'onchange' mechanism provides a way for the client interface to update a form without saving anything to the database whenever the user has filled in a field value. To achieve this, we define a method where ``self`` represents the record in the form view and decorate it with :func:`~odoo.api.onchange` to specify which field it is triggered by. Any change you make on ``self`` will be reflected on the form::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:264 +msgid "In this example, changing the partner will also change the name and the description values. It is up to the user whether or not to change the name and description values afterwards. Also note that we do not loop on ``self``, this is because the method is only triggered in a form view, where ``self`` is always a single record." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:269 +msgid "Set values for garden area and orientation." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:271 +msgid "Create an ``onchange`` in the ``estate.property`` model in order to set values for the garden area (10) and orientation (North) when garden is set to True. When unset, clear the fields." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:277 +msgid "Onchanges methods can also return a non-blocking warning message (`example `__)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:281 +msgid "How to use them?" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:283 +msgid "There is no strict rule for the use of computed fields and onchanges." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:285 +msgid "In many cases, both computed fields and onchanges may be used to achieve the same result. Always prefer computed fields since they are also triggered outside of the context of a form view. Never ever use an onchange to add business logic to your model. This is a **very bad** idea since onchanges are not automatically triggered when creating a record programmatically; they are only triggered in the form view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:291 +msgid "The usual pitfall of computed fields and onchanges is trying to be 'too smart' by adding too much logic. This can have the opposite result of what was expected: the end user is confused from all the automation." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:295 +msgid "Computed fields tend to be easier to debug: such a field is set by a given method, so it's easy to track when the value is set. Onchanges, on the other hand, may be confusing: it is very difficult to know the extent of an onchange. Since several onchange methods may set the same fields, it easily becomes difficult to track where a value is coming from." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:300 +msgid "When using stored computed fields, pay close attention to the dependencies. When computed fields depend on other computed fields, changing a value can trigger a large number of recomputations. This leads to poor performance." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/09_compute_onchange.rst:304 +msgid "In the :ref:`next chapter`, we'll see how we can trigger some business logic when buttons are clicked." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:5 +msgid "Chapter 10: Ready For Some Action?" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:7 +msgid "So far we have mostly built our module by declaring fields and views. We just introduced business logic in the :ref:`previous chapter ` thanks to computed fields and onchanges. In any real business scenario, we would want to link some business logic to action buttons. In our real estate example, we would like to be able to:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:12 +msgid "cancel or set a property as sold" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:13 +msgid "accept or refuse an offer" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:15 +msgid "One could argue that we can already do these things by changing the state manually, but this is not really convenient. Moreover, we want to add some extra processing: when an offer is accepted we want to set the selling price and the buyer for the property." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:20 +msgid "Action Type" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:22 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/actions` and :ref:`reference/exceptions`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:29 +msgid "You should be able to cancel or set a property as sold:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:35 +msgid "A canceled property cannot be sold and a sold property cannot be canceled. For the sake of clarity, the ``state`` field has been added on the view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:38 +msgid "You should be able to accept or refuse an offer:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:44 +msgid "Once an offer is accepted, the selling price and the buyer should be set:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:50 +msgid "In our real estate module, we want to link business logic with some buttons. The most common way to do this is to:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:53 +msgid "Add a button in the view, for example in the ``header`` of the view:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:66 +msgid "and link this button to business logic:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:82 +msgid "By assigning ``type=\"object\"`` to our button, the Odoo framework will execute a Python method with ``name=\"action_do_something\"`` on the given model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:85 +msgid "The first important detail to note is that our method name isn't prefixed with an underscore (``_``). This makes our method a **public** method, which can be called directly from the Odoo interface (through an RPC call). Until now, all methods we created (compute, onchange) were called internally, so we used **private** methods prefixed by an underscore. You should always define your methods as private unless they need to be called from the user interface." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:91 +msgid "Also note that we loop on ``self``. Always assume that a method can be called on multiple records; it's better for reusability." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:94 +msgid "Finally, a public method should always return something so that it can be called through XML-RPC. When in doubt, just ``return True``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:97 +msgid "There are hundreds of examples in the Odoo source code. One example is this `button in a view `__ and its `corresponding Python method `__" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:102 +msgid "Cancel and set a property as sold." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:104 +msgid "Add the buttons 'Cancel' and 'Sold' to the ``estate.property`` model. A canceled property cannot be set as sold, and a sold property cannot be canceled." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:107 +msgid "Refer to the first image of the **Goal** for the expected result." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:109 +msgid "Tip: in order to raise an error, you can use the :ref:`UserError` function. There are plenty of examples in the Odoo source code ;-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:112 +msgid "Add the buttons 'Accept' and 'Refuse' to the ``estate.property.offer`` model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:114 +msgid "Refer to the second image of the **Goal** for the expected result." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:116 +msgid "Tip: to use an icon as a button, have a look `at this example `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:119 +msgid "When an offer is accepted, set the buyer and the selling price for the corresponding property." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:121 +msgid "Refer to the third image of the **Goal** for the expected result." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:123 +msgid "Pay attention: in real life only one offer can be accepted for a given property!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:126 +msgid "Object Type" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:128 +msgid "In :ref:`howto/rdtraining/06_firstui`, we created an action that was linked to a menu. You may be wondering if it is possible to link an action to a button. Good news, it is! One way to do it is:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:136 +msgid "We use ``type=\"action\"`` and we refer to the :term:`external identifier` in the ``name``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/10_actions.rst:138 +msgid "In the :ref:`next chapter ` we'll see how we can prevent encoding incorrect data in Odoo." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:5 +msgid "Chapter 11: Constraints" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:7 +msgid "The :ref:`previous chapter ` introduced the ability to add some business logic to our model. We can now link buttons to business code, but how can we prevent users from entering incorrect data? For example, in our real estate module nothing prevents users from setting a negative expected price." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:17 +msgid "SQL" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:19 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/orm/models` and in the `PostgreSQL's documentation`_." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:26 +msgid "Amounts should be (strictly) positive" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:32 +msgid "Property types and tags should have a unique name" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:38 +msgid "SQL constraints are defined through the model attribute :attr:`~odoo.models.Model._sql_constraints`. This attribute is assigned a list of triples containing strings ``(name, sql_definition, message)``, where ``name`` is a valid SQL constraint name, ``sql_definition`` is a table_constraint_ expression and ``message`` is the error message." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:44 +msgid "You can find a simple example `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:47 +msgid "Add SQL constraints." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:49 +msgid "Add the following constraints to their corresponding models:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:51 +msgid "A property expected price must be strictly positive" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:52 +msgid "A property selling price must be positive" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:53 +msgid "An offer price must be strictly positive" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:54 +msgid "A property tag name and property type name must be unique" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:56 +msgid "Tip: search for the ``unique`` keyword in the Odoo codebase for examples of unique names." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:58 +msgid "Restart the server with the ``-u estate`` option to see the result. Note that you might have data that prevents a SQL constraint from being set. An error message similar to the following might pop up:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:65 +msgid "For example, if some offers have a price of zero, then the constraint can't be applied. You can delete the problematic data in order to apply the new constraints." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:71 +msgid "**Reference**: the documentation related to this topic can be found in :func:`~odoo.api.constrains`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:76 +msgid "**Goal**: at the end of this section, it will not possible to accept an offer lower than 90% of the expected price." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:83 +msgid "SQL constraints are an efficient way of ensuring data consistency. However it may be necessary to make more complex checks which require Python code. In this case we need a Python constraint." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:86 +msgid "A Python constraint is defined as a method decorated with :func:`~odoo.api.constrains` and is invoked on a recordset. The decorator specifies which fields are involved in the constraint. The constraint is automatically evaluated when any of these fields are modified . The method is expected to raise an exception if its invariant is not satisfied::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:103 +msgid "A simple example can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:106 +msgid "Add Python constraints." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:108 +msgid "Add a constraint so that the selling price cannot be lower than 90% of the expected price." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:110 +msgid "Tip: the selling price is zero until an offer is validated. You will need to fine tune your check to take this into account." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:115 +msgid "Always use the :meth:`~odoo.tools.float_utils.float_compare` and :meth:`~odoo.tools.float_utils.float_is_zero` methods when working with floats!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:118 +msgid "Ensure the constraint is triggered every time the selling price or the expected price is changed!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:120 +msgid "SQL constraints are usually more efficient than Python constraints. When performance matters, always prefer SQL over Python constraints." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/11_constraints.rst:123 +msgid "Our real estate module is starting to look good. We added some business logic, and now we make sure the data is consistent. However, the user interface is still a bit rough. Let's see how we can improve it in the :ref:`next chapter `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:5 +msgid "Chapter 12: Add The Sprinkles" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:7 +msgid "Our real estate module now makes sense from a business perspective. We created :ref:`specific views `, added several :ref:`action buttons ` and :ref:`constraints `. However our user interface is still a bit rough. We would like to add some colors to the list views and make some fields and buttons conditionally disappear. For example, the 'Sold' and 'Cancel' buttons should disappear when the property is sold or canceled since it is no longer allowed to change the state at this point." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:15 +msgid "This chapter covers a very small subset of what can be done in the views. Do not hesitate to read the reference documentation for a more complete overview." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:18 +msgid "**Reference**: the documentation related to this chapter can be found in :ref:`reference/views`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:22 +msgid "Inline Views" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:26 +msgid "**Goal**: at the end of this section, a specific list of properties should be added to the property type view:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:33 +msgid "In the real estate module we added a list of offers for a property. We simply added the field ``offer_ids`` with:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:40 +msgid "The field uses the specific view for ``estate.property.offer``. In some cases we want to define a specific list view which is only used in the context of a form view. For example, we would like to display the list of properties linked to a property type. However, we only want to display 3 fields for clarity: name, expected price and state." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:45 +msgid "To do this, we can define *inline* list views. An inline list view is defined directly inside a form view. For example:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:81 +msgid "In the form view of the ``test.model``, we define a specific list view for ``test.model.line`` with fields ``field_1`` and ``field_2``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:84 +msgid "An example can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:87 +msgid "Add an inline list view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:89 +msgid "Add the ``One2many`` field ``property_ids`` to the ``estate.property.type`` model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:90 +msgid "Add the field in the ``estate.property.type`` form view as depicted in the **Goal** of this section." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:94 +#: ../../content/developer/reference/javascript/javascript_reference.rst:491 +msgid "Widgets" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:96 +msgid "**Reference**: the documentation related to this section can be found in :ref:`reference/js/widgets`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:101 +msgid "**Goal**: at the end of this section, the state of the property should be displayed using a specific widget:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:108 +msgid "Four states are displayed: New, Offer Received, Offer Accepted and Sold." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:110 +msgid "Whenever we've added fields to our models, we've (almost) never had to worry about how these fields would look like in the user interface. For example, a date picker is provided for a ``Date`` field and a ``One2many`` field is automatically displayed as a list. Odoo chooses the right 'widget' depending on the field type." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:115 +msgid "However, in some cases, we want a specific representation of a field which can be done thanks to the ``widget`` attribute. We already used it for the ``tag_ids`` field when we used the ``widget=\"many2many_tags\"`` attribute. If we hadn't used it, then the field would have displayed as a list." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:120 +msgid "Each field type has a set of widgets which can be used to fine tune its display. Some widgets also take extra options. An exhaustive list can be found in :ref:`reference/js/widgets`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:123 +msgid "Use the status bar widget." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:125 +msgid "Use the ``statusbar`` widget in order to display the ``state`` of the ``estate.property`` as depicted in the **Goal** of this section." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:128 +msgid "Tip: a simple example can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:131 +msgid "Same field multiple times in a view" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:133 +msgid "Add a field only **once** to a list or a form view. Adding it multiple times is not supported." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:137 +msgid "List Order" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:139 +msgid "**Reference**: the documentation related to this section can be found in :ref:`reference/orm/models`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:144 +msgid "**Goal**: at the end of this section, all lists should display by default in a deterministic order. Property types can be ordered manually." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:147 +msgid "During the previous exercises, we created several list views. However, at no point did we specify which order the records had to be listed in by default. This is a very important thing for many business cases. For example, in our real estate module we would want to display the highest offers on top of the list." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:153 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:182 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:215 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:262 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:248 +#: ../../content/developer/reference/addons/orm.rst:90 +msgid "Model" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:155 +msgid "Odoo provides several ways to set a default order. The most common way is to define the ``_order`` attribute directly in the model. This way, the retrieved records will follow a deterministic order which will be consistent in all views including when records are searched programmatically. By default there is no order specified, therefore the records will be retrieved in a non-deterministic order depending on PostgreSQL." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:161 +msgid "The ``_order`` attribute takes a string containing a list of fields which will be used for sorting. It will be converted to an order_by_ clause in SQL. For example:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:175 +msgid "Our records are ordered by descending ``id``, meaning the highest comes first." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:177 +msgid "Add model ordering." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:179 +msgid "Define the following orders in their corresponding models:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:182 +msgid "Order" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:184 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:304 +msgid "``estate.property``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:184 +msgid "Descending ID" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:185 +msgid "``estate.property.offer``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:185 +msgid "Descending Price" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:186 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:264 +msgid "``estate.property.tag``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:186 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:187 +msgid "Name" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:187 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:217 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:306 +msgid "``estate.property.type``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:191 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:318 +msgid "View" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:193 +msgid "Ordering is possible at the model level. This has the advantage of a consistent order everywhere a list of records is retrieved. However, it is also possible to define a specific order directly in a view thanks to the ``default_order`` attribute (`example `__)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:199 +msgid "Manual" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:201 +msgid "Both model and view ordering allow flexibility when sorting records, but there is still one case we need to cover: the manual ordering. A user may want to sort records depending on the business logic. For example, in our real estate module we would like to sort the property types manually. It is indeed useful to have the most used types appear at the top of the list. If our real estate agency mainly sells houses, it is more convenient to have 'House' appear before 'Apartment'." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:207 +msgid "To do so, a ``sequence`` field is used in combination with the ``handle`` widget. Obviously the ``sequence`` field must be the first field in the ``_order`` attribute." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:210 +msgid "Add manual ordering." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:212 +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:259 +msgid "Add the following field:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:217 +msgid "Sequence" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:220 +msgid "Add the sequence to the ``estate.property.type`` list view with the correct widget." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:222 +msgid "Tip: you can find an example here: `model `__ and `view `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:228 +msgid "Attributes and options" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:230 +msgid "It would be prohibitive to detail all the available features which allow fine tuning of the look of a view. Therefore, we'll stick to the most common ones." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:238 +msgid "**Goal**: at the end of this section, the property form view will have:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:240 +msgid "Conditional display of buttons and fields" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:241 +msgid "Tag colors" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:248 +msgid "In our real estate module, we want to modify the behavior of some fields. For example, we don't want to be able to create or edit a property type from the form view. Instead we expect the types to be handled in their appropriate menu. We also want to give tags a color. In order to add these behavior customizations, we can add the ``options`` attribute to several field widgets." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:253 +msgid "Add widget options." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:255 +msgid "Add the appropriate option to the ``property_type_id`` field to prevent the creation and the editing of a property type from the property form view. Have a look at the :ref:`Many2one widget documentation ` for more info." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:264 +msgid "Color" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:267 +msgid "Then add the appropriate option to the ``tag_ids`` field to add a color picker on the tags. Have a look at the :ref:`FieldMany2ManyTags widget documentation ` for more info." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:271 +msgid "In :ref:`howto/rdtraining/06_firstui`, we saw that reserved fields were used for specific behaviors. For example, the ``active`` field is used to automatically filter out inactive records. We added the ``state`` as a reserved field as well. It's now time to use it! A ``state`` field is used in combination with a ``states`` attribute in the view to display buttons conditionally." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:277 +msgid "Add conditional display of buttons." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:279 +msgid "Use the ``states`` attribute to display the header buttons conditionally as depicted in this section's **Goal** (notice how the 'Sold' and 'Cancel' buttons change when the state is modified)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:282 +msgid "Tip: do not hesitate to search for ``states=`` in the Odoo XML files for some examples." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:284 +msgid "More generally, it is possible to make a field ``invisible``, ``readonly`` or ``required`` based on the value of other fields thanks to the ``attrs`` attribute. Note that ``invisible`` can also be applied to other elements of the view such as ``button`` or ``group``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:288 +msgid "The ``attrs`` is a dictionary with the property as a key and a domain as a value. The domain gives the condition in which the property applies. For example:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:298 +msgid "This means that the ``description`` field is invisible when ``is_partner`` is ``False``. It is important to note that a field used in an ``attrs`` **must** be present in the view. If it should not be displayed to the user, we can use the ``invisible`` attribute to hide it." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:302 +msgid "Use ``attrs``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:304 +msgid "Make the garden area and orientation invisible in the ``estate.property`` form view when there is no garden." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:306 +msgid "Make the 'Accept' and 'Refuse' buttons invisible once the offer state is set." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:307 +msgid "Do not allow adding an offer when the property state is 'Offer Accepted', 'Sold' or 'Canceled'. To do this use the ``readonly`` ``attrs``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:312 +msgid "Using a (conditional) ``readonly`` attribute in the view can be useful to prevent data entry errors, but keep in mind that it doesn't provide any level of security! There is no check done server-side, therefore it's always possible to write on the field through a RPC call." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:321 +msgid "**Goal**: at the end of this section, the property and offer list views should have color decorations. Additionally, offers and tags will be editable directly in the list, and the availability date will be hidden by default." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:333 +msgid "When the model only has a few fields, it can be useful to edit records directly through the list view and not have to open the form view. In the real estate example, there is no need to open a form view to add an offer or create a new tag. This can be achieved thanks to the ``editable`` attribute." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:337 +msgid "Make list views editable." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:339 +msgid "Make the ``estate.property.offer`` and ``estate.property.tag`` list views editable." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:341 +msgid "On the other hand, when a model has a lot of fields it can be tempting to add too many fields in the list view and make it unclear. An alternative method is to add the fields, but make them optionally hidden. This can be achieved thanks to the ``optional`` attribute." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:345 +msgid "Make a field optional." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:347 +msgid "Make the field ``date_availability`` on the ``estate.property`` list view optional and hidden by default." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:350 +msgid "Finally, color codes are useful to visually emphasize records. For example, in the real estate module we would like to display refused offers in red and accepted offers in green. This can be achieved thanks to the ``decoration-{$name}`` attribute (see :ref:`reference/js/widgets` for a complete list):" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:362 +msgid "The records where ``is_partner`` is ``True`` will be displayed in green." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:364 +msgid "Add some decorations." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:366 +msgid "On the ``estate.property`` list view:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:368 +msgid "Properties with an offer received are green" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:369 +msgid "Properties with an offer accepted are green and bold" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:370 +msgid "Properties sold are muted" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:372 +msgid "On the ``estate.property.offer`` list view:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:374 +msgid "Refused offers are red" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:375 +msgid "Accepted offers are green" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:376 +msgid "The state should not be visible anymore" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:380 +msgid "Keep in mind that **all** fields used in attributes must be in the view!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:381 +msgid "If you want to test the color of the \"Offer Received\" and \"Offer Accepted\" states, add the field in the form view and change it manually (we'll implement the business logic for this later)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:387 +msgid "**Reference**: the documentation related to this section can be found in :ref:`reference/views/search` and :ref:`reference/views/search/defaults`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:392 +msgid "**Goal**: at the end of this section, the available properties will be filtered by default, and searching on the living area returns results where the area is larger than the given number." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:400 +msgid "Last but not least, there are some tweaks we would like to apply when searching. First of all, we want to have our 'Available' filter applied by default when we access the properties. To make this happen, we need to use the ``search_default_{$name}`` action context, where ``{$name}`` is the filter name. This means that we can define which filter(s) will be activated by default at the action level." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:405 +msgid "Here is an example of an `action `__ with its `corresponding filter `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:410 +msgid "Add a default filter." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:412 +msgid "Make the 'Available' filter selected by default in the ``estate.property`` action." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:414 +msgid "Another useful improvement in our module would be the ability to search efficiently by living area. In practice, a user will want to search for properties of 'at least' the given area. It is unrealistic to expect users would want to find a property of an exact living area. It is always possible to make a custom search, but that's inconvenient." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:419 +msgid "Search view ```` elements can have a ``filter_domain`` that overrides the domain generated for searching on the given field. In the given domain, ``self`` represents the value entered by the user. In the example below, it is used to search on both ``name`` and ``description`` fields." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:432 +msgid "Change the living area search." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:434 +msgid "Add a ``filter_domain`` to the living area to include properties with an area equal to or greater than the given value." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:438 +msgid "Stat Buttons" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:442 +msgid "**Goal**: at the end of this section, there will be a stat button on the property type form view which shows the list of all offers related to properties of the given type when it is clicked on." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:449 +msgid "If you've already used some functional modules in Odoo, you've probably already encountered a 'stat button'. These buttons are displayed on the top right of a form view and give a quick access to linked documents. In our real estate module, we would like to have a quick link to the offers related to a given property type as depicted in the **Goal** of this section." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:454 +msgid "At this point of the tutorial we have already seen most of the concepts to do this. However, there is not a single solution and it can still be confusing if you don't know where to start from. We'll describe a step-by-step solution in the exercise. It can always be useful to find some examples in the Odoo codebase by looking for ``oe_stat_button``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:459 +msgid "The following exercise might be a bit more difficult than the previous ones since it assumes you are able to search for examples in the source code on your own. If you are stuck there is probably someone nearby who can help you ;-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:463 +msgid "The exercise introduces the concept of :ref:`reference/fields/related`. The easiest way to understand it is to consider it as a specific case of a computed field. The following definition of the ``description`` field:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:474 +msgid "is equivalent to:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:488 +msgid "Every time the partner name is changed, the description is modified." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:490 +msgid "Add a stat button to property type." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:492 +msgid "Add the field ``property_type_id`` to ``estate.property.offer``. We can define it as a related field on ``property_id.property_type_id`` and set it as stored." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:495 +msgid "Thanks to this field, an offer will be linked to a property type when it's created. You can add the field to the list view of offers to make sure it works." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:498 +msgid "Add the field ``offer_ids`` to ``estate.property.type`` which is the One2many inverse of the field defined in the previous step." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:501 +msgid "Add the field ``offer_count`` to ``estate.property.type``. It is a computed field that counts the number of offers for a given property type (use ``offer_ids`` to do so)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:504 +msgid "At this point, you have all the information necessary to know how many offers are linked to a property type. When in doubt, add ``offer_ids`` and ``offer_count`` directly to the view. The next step is to display the list when clicking on the stat button." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:508 +msgid "Create a stat button on ``estate.property.type`` pointing to the ``estate.property.offer`` action. This means you should use the ``type=\"action\"`` attribute (go back to the end of :ref:`howto/rdtraining/10_actions` if you need a refresher)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:512 +msgid "At this point, clicking on the stat button should display all offers. We still need to filter out the offers." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:515 +msgid "On the ``estate.property.offer`` action, add a domain that defines ``property_type_id`` as equal to the ``active_id`` (= the current record, `here is an example `__)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/12_sprinkles.rst:519 +msgid "Looking good? If not, don't worry, the :ref:`next chapter ` doesn't require stat buttons ;-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:5 +msgid "Chapter 13: Inheritance" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:7 +msgid "A powerful aspect of Odoo is its modularity. A module is dedicated to a business need, but modules can also interact with one another. This is useful for extending the functionality of an existing module. For example, in our real estate scenario we want to display the list of a salesperson's properties directly in the regular user view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:12 +msgid "But before going through the specific Odoo module inheritance, let's see how we can alter the behavior of the standard CRUD (Create, Retrieve, Update or Delete) methods." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:16 +msgid "Python Inheritance" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:22 +msgid "It should not be possible to delete a property which is not new or canceled." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:28 +msgid "When an offer is created, the property state should change to 'Offer Received'" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:29 +msgid "It should not be possible to create an offer with a lower price than an existing offer" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:35 +msgid "In our real estate module, we never had to develop anything specific to be able to do the standard CRUD actions. The Odoo framework provides the necessary tools to do them. In fact, such actions are already included in our model thanks to classical Python inheritance::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:48 +msgid "Our ``class TestModel`` inherits from :class:`~odoo.models.Model` which provides :meth:`~odoo.models.Model.create`, :meth:`~odoo.models.Model.read`, :meth:`~odoo.models.Model.write` and :meth:`~odoo.models.Model.unlink`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:52 +msgid "These methods (and any other method defined on :class:`~odoo.models.Model`) can be extended to add specific business logic::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:70 +msgid "The decorator :func:`~odoo.api.model` is necessary for the :meth:`~odoo.models.Model.create` method because the content of the recordset ``self`` is not relevant in the context of creation, but it is not necessary for the other CRUD methods." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:74 +msgid "In Python 3, ``super()`` is equivalent to ``super(TestModel, self)``. The latter may be necessary when you need to call the parent method with a modified recordset." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:79 +msgid "It is very important to **always** call ``super()`` to avoid breaking the flow. There are only a few very specific cases where you don't want to call it." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:81 +msgid "Make sure to **always** return data consistent with the parent method. For example, if the parent method returns a ``dict()``, your override must also return a ``dict()``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:84 +msgid "Add business logic to the CRUD methods." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:86 +msgid "Prevent deletion of a property if its state is not 'New' or 'Canceled'" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:88 +msgid "Tip: override :meth:`~odoo.models.Model.unlink` and remember that ``self`` can be a recordset with more than one record." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:91 +msgid "At offer creation, set the property state to 'Offer Received'. Also raise an error if the user tries to create an offer with a lower amount than an existing offer." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:94 +msgid "Tip: the ``property_id`` field is available in the ``vals``, but it is an ``int``. To instantiate an ``estate.property`` object, use ``self.env[model_name].browse(value)`` (`example `__)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:99 +msgid "Model Inheritance" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:101 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/orm/inheritance`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:104 +msgid "In our real estate module, we would like to display the list of properties linked to a salesperson directly in the Settings / Users & Companies / Users form view. To do this, we need to add a field to the ``res.users`` model and adapt its view to show it." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:110 +msgid "The first inheritance mechanism allows modules to modify the behavior of a model defined in an another module by:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:113 +msgid "adding fields to the model," +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:114 +msgid "overriding the definition of fields in the model," +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:115 +msgid "adding constraints to the model," +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:116 +msgid "adding methods to the model," +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:117 +msgid "overriding existing methods in the model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:119 +msgid "The second inheritance mechanism (delegation) allows every record of a model to be linked to a parent model's record and provides transparent access to the fields of this parent record." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:127 +msgid "In Odoo, the first mechanism is by far the most used. In our case, we want to add a field to an existing model, which means we will use the first mechanism. For example::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:137 +msgid "A practical example where two fields are added to a model can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:141 +msgid "By convention, each inherited model is defined in its own Python file. In our example, it would be ``models/inherited_model.py``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:144 +msgid "Add a field to Users." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:146 +msgid "Add the following field to ``res.users``:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:151 +msgid "property_ids" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:151 +msgid "One2many inverse of ``user_id`` to ``estate.property``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:154 +msgid "Add a domain to the field so it only lists the available properties." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:156 +msgid "Now let's add the field to the view and check that everything is working well!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:159 +msgid "View Inheritance" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:161 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/views/inheritance`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:166 +msgid "**Goal**: at the end of this section, the list of available properties linked to a salesperson should be displayed in their user form view" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:173 +msgid "Instead of modifying existing views in place (by overwriting them), Odoo provides view inheritance where children 'extension' views are applied on top of root views. These extension can both add and remove content from their parent view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:177 +msgid "An extension view references its parent using the ``inherit_id`` field. Instead of a single view, its ``arch`` field contains a number of ``xpath`` elements that select and alter the content of their parent view:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:203 +msgid "appends ``xpath``'s body to the end of the matched element" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:212 +msgid "alters the attributes of the matched element using the special ``attribute`` elements in the ``xpath``'s body" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:215 +msgid "When matching a single element, the ``position`` attribute can be set directly on the element to be found. Both inheritances below have the same result." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:228 +msgid "An example of a view inheritance extension can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:231 +msgid "Add fields to the Users view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:233 +msgid "Add the ``property_ids`` field to the ``base.view_users_form`` in a new notebook page." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:235 +msgid "Tip: an example an inheritance of the users' view can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:238 +msgid "Inheritance is extensively used in Odoo due to its modular concept. Do not hesitate to read the corresponding documentation for more info!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/13_inheritance.rst:241 +msgid "In the :ref:`next chapter `, we will learn how to interact with other modules." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:5 +msgid "Chapter 14: Interact With Other Modules" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:7 +msgid "In the :ref:`previous chapter `, we used inheritance to modify the behavior of a module. In our real estate scenario, we would like to go a step further and be able to generate invoices for our customers. Odoo provides an Invoicing module, so it would be neat to create an invoice directly from our real estate module, i.e. once a property is set to 'Sold', an invoice is created in the Invoicing application." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:14 +msgid "Concrete Example: Account Move" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:20 +msgid "A new module ``estate_account`` should be created" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:21 +msgid "When a property is sold, an invoice should be issued for the buyer" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:27 +msgid "Any time we interact with another module, we need to keep in mind the modularity. If we intend to sell our application to real estate agencies, some may want the invoicing feature but others may not want it." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:32 +msgid "Link Module" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:34 +msgid "The common approach for such use cases is to create a 'link' module. In our case, the module would depend on ``estate`` and ``account`` and would include the invoice creation logic of the estate property. This way the real estate and the accounting modules can be installed independently. When both are installed, the link module provides the new feature." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:39 +msgid "Create a link module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:41 +msgid "Create the ``estate_account`` module, which depends on the ``estate`` and ``account`` modules. For now, it will be an empty shell." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:44 +msgid "Tip: you already did this at the :ref:`beginning of the tutorial `. The process is very similar." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:47 +msgid "When the ``estate_account`` module appears in the list, go ahead and install it! You'll notice that the Invoicing application is installed as well. This is expected since your module depends on it. If you uninstall the Invoicing application, your module will be uninstalled as well." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:54 +msgid "Invoice Creation" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:56 +msgid "It's now time to generate the invoice. We want to add functionality to the ``estate.property`` model, i.e. we want to add some extra logic for when a property is sold. Does that sound familiar? If not, it's a good idea to go back to the :ref:`previous chapter ` since you might have missed something ;-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:61 +msgid "As a first step, we need to extend the action called when pressing the :ref:`'Sold' button ` on a property. To do so, we need to create a :ref:`model inheritance ` in the ``estate_account`` module for the ``estate.property`` model. For now, the overridden action will simply return the ``super`` call. Maybe an example will make things clearer::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:75 +msgid "A practical example can be found `here `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:78 +msgid "Add the first step of invoice creation." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:80 +msgid "Create a ``estate_property.py`` file in the correct folder of the ``estate_account`` module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:81 +msgid "``_inherit`` the ``estate.property`` model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:82 +msgid "Override the ``action_sold`` method (you might have named it differently) to return the ``super`` call." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:85 +msgid "Tip: to make sure it works, add a ``print`` or a debugger breakpoint in the overridden method." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:87 +msgid "Is it working? If not, maybe check that all Python files are correctly imported." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:89 +msgid "If the override is working, we can move forward and create the invoice. Unfortunately, there is no easy way to know how to create any given object in Odoo. Most of the time, it is necessary to have a look at its model to find the required fields and provide appropriate values." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:93 +msgid "A good way to learn is to look at how other modules already do what you want to do. For example, one of the basic flows of Sales is the creation of an invoice from a sales order. This looks like a good starting point since it does exactly what we want to do. Take some time to read and understand the `_create_invoices `__ method. When you are done crying because this simple task looks awfully complex, we can move forward in the tutorial." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:100 +msgid "To create an invoice, we need the following information:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:102 +msgid "a ``partner_id``: the customer" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:103 +msgid "a ``move_type``: it has several `possible values `__" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:104 +msgid "a ``journal_id``: the accounting journal" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:106 +msgid "This is enough to create an empty invoice." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:108 +msgid "Add the second step of invoice creation." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:110 +msgid "Create an empty ``account.move`` in the override of the ``action_sold`` method:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:112 +msgid "the ``partner_id`` is taken from the current ``estate.property``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:113 +msgid "the ``move_type`` should correspond to a 'Customer Invoice'" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:114 +msgid "the ``journal_id`` must be a ``sale`` journal (when in doubt, have a look `here `__)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:119 +msgid "to create an object, use ``self.env[model_name].create(values)``, where ``values`` is a ``dict``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:121 +msgid "the ``create`` method doesn't accept recordsets as field values." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:123 +msgid "When a property is set to 'Sold', you should now have a new customer invoice created in Invoicing / Customers / Invoices." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:126 +msgid "Obviously we don't have any invoice lines so far. To create an invoice line, we need the following information:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:129 +msgid "``name``: a description of the line" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:130 +msgid "``quantity``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:131 +msgid "``price_unit``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:133 +msgid "Moreover, an invoice line needs to be linked to an invoice. The easiest and most efficient way to link a line to an invoice is to include all lines at invoice creation. To do this, the ``invoice_line_ids`` field is included in the ``account.move`` creation, which is a :class:`~odoo.fields.One2many`. One2many and Many2many use special 'commands' described in :ref:`reference/orm/models/crud`. This format is a list of triplets executed sequentially, where each triplet is a command to execute on the set of records. Here is a simple example to include a One2many field ``line_ids`` at creation of a ``test.model``::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:159 +msgid "Add the third step of invoice creation." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:161 +msgid "Add two invoice lines during the creation of the ``account.move``. Each property sold will be invoiced following these conditions:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:164 +msgid "6% of the selling price" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:165 +msgid "an additional 100.00 from administrative fees" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:167 +msgid "Tip: Add the ``invoice_line_ids`` at creation following the example above. For each line, we need a ``name``, ``quantity`` and ``price_unit``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/14_other_module.rst:170 +msgid "This chapter might be one of the most difficult that has been covered so far, but it is the closest to what Odoo development will be in practice. In the :ref:`next chapter `, we will introduce the templating mechanism used in Odoo." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:5 +msgid "Chapter 15: A Brief History Of QWeb" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:7 +msgid "So far the interface design of our real estate module has been rather limited. Building a list view is straightforward since only the list of fields is necessary. The same holds true for the form view: despite the use of a few tags such as ```` or ````, there is very little to do in terms of design." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:12 +msgid "However, if we want to give a unique look to our application, it is necessary to go a step further and be able to design new views. Moreover, other features such as PDF reports or website pages need another tool to be created with more flexibility: a templating_ engine." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:16 +msgid "You might already be familiar with existing engines such as Jinja (Python), ERB (Ruby) or Twig (PHP). Odoo comes with its own built-in engine: :ref:`reference/qweb`. QWeb is the primary templating engine used by Odoo. It is an XML templating engine and used mostly to generate HTML fragments and pages." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:21 +msgid "You probably already have come across the `kanban board`_ in Odoo where the records are displayed in a card-like structure. We will build such a view for our real estate module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:25 +msgid "Concrete Example: A Kanban View" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:27 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`reference/views/kanban`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:32 +msgid "**Goal**: at the end of this section a Kanban view of the properties should be created:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:38 +msgid "In our estate application, we would like to add a Kanban view to display our properties. Kanban views are a standard Odoo view (like the form and list views), but their structure is much more flexible. In fact, the structure of each card is a mix of form elements (including basic HTML) and QWeb. The definition of a Kanban view is similar to the definition of the list and form views, except that their root element is ````. In its simplest form, a Kanban view looks like:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:57 +msgid "Let's break down this example:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:59 +msgid "````: defines a list of :ref:`reference/qweb` templates. Kanban views *must* define at least one root template ``kanban-box``, which will be rendered once for each record." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:61 +msgid "````: ```` is a placeholder element for QWeb directives. In this case, it is used to set the ``name`` of the template to ``kanban-box``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:63 +msgid "``
``: the ``oe_kanban_global_click`` makes the ``
`` clickable to open the record." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:65 +msgid "````: this will add the ``name`` field to the view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:67 +msgid "Make a minimal kanban view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:69 +msgid "Using the simple example provided, create a minimal Kanban view for the properties. The only field to display is the ``name``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:72 +msgid "Tip: you must add ``kanban`` in the ``view_mode`` of the corresponding ``ir.actions.act_window``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:75 +msgid "Once the Kanban view is working, we can start improving it. If we want to display an element conditionally, we can use the ``t-if`` directive (see :ref:`reference/qweb/conditionals`)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:94 +msgid "We added a few things:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:96 +msgid "``t-if``: the ``
`` element is rendered if the condition is true." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:97 +msgid "``record``: an object with all the requested fields as its attributes. Each field has two attributes ``value`` and ``raw_value``. The former is formatted according to current user parameters and the latter is the direct value from a :meth:`~odoo.models.Model.read`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:101 +msgid "In the above example, the field ``name`` was added in the ```` element, but ``state`` is outside of it. When we need the value of a field but don't want to display it in the view, it is possible to add it outside of the ```` element." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:105 +msgid "Improve the Kanban view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:107 +msgid "Add the following fields to the Kanban view: expected price, best price, selling price and tags. Pay attention: the best price is only displayed when an offer is received, while the selling price is only displayed when an offer is accepted." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:111 +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:121 +msgid "Refer to the **Goal** of the section for a visual example." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:113 +msgid "Let's give the final touch to our view: the properties must be grouped by type by default. You might want to have a look at the various options described in :ref:`reference/views/kanban`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:116 +msgid "Add default grouping." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:118 +msgid "Use the appropriate attribute to group the properties by type by default. You must also prevent drag and drop." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:123 +msgid "Kanban views are a typical example of how it is always a good idea to start from an existing view and fine tune it instead of starting from scratch. There are many options and classes available, so... read and learn!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/15_qwebintro.rst:127 +msgid "It is now time to add the :ref:`final touches to our application and submit it on GitHub `!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:5 +msgid "Chapter 16: Polish Your Code And Submit Your PR" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:7 +msgid "In the previous chapters we saw how to create a fully functional business application. Now we will prepare our code to be shared and learn how to share it." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:11 +msgid "Coding guidelines" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:13 +msgid "We will start refactoring the code to match to the Odoo coding guidelines. The guidelines aim to improve the quality of the Odoo Apps code." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:17 +msgid "**Reference**: you will find the Odoo coding guidelines in :ref:`reference/guidelines`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:19 +msgid "Polish your code." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:21 +msgid "Refactor your code to respect the coding guidelines. Don't forget to respect the module structure, the variable names, the method name convention, the model attribute order and the xml ids." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:26 +msgid "Your first Pull Request (PR)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:28 +msgid "**The following is intended to be used by Odoo staff members only. All repositories mentioned are not accessible for third-parties.**" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:31 +msgid "Now that your code respects the Odoo code guidelines and is polished up, let's share it with others." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:36 +msgid "We will start by creating a git development environment for the 'custom' folder, like we did in the beginning for 'odoo' and 'enterprise'. The PR will target the `odoo/technical-training-sandbox` repository." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:39 +msgid "To do this the first step is to `fork `__ in GitHub `this repository `__ to create your own development repository." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:44 +msgid "After you successfully created your development repository, we will configure your existing `$HOME/src/custom` folder to be able to commit your work." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:59 +msgid "Note that if your work is already in a :ref:`Git and GitHub configured folder ` the previous steps are not needed. This is the case when you start working in the 'odoo' or 'enterprise' folders." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:64 +msgid "Branch, Commit & Push" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:66 +msgid "Before creating the PR, a new working branch has to be created and used to commit the code. Afterwards the branch will be pushed to the development repository." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:69 +msgid "Create your working branch:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:75 +msgid "Your branch name must follow the following name structure : --" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:77 +msgid "Example: The branch master-sale-fixes-abc on odoo-dev/odoo is a branch containing fixes for the sales app in the odoo/odoo repository, to be deployed in master and done by ABC." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:80 +msgid "Commit your code:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:89 +msgid "**Everyone reads your commit messages!**" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:91 +msgid "The commit message is very important, follow the :ref:`Developer guidelines `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:94 +msgid "Push your new branch to your development repository:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:100 +msgid "NEVER use `git push --force` (or `git push -f`) with a branch that does not belong to you or in a stable branch. Never, never, never!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:103 +msgid "Remember that you can use `git status` at any point to check the current status of your branch" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:104 +msgid "You can create git aliases to shorten some of these commands. Ask your colleagues if they use git aliases and get inspired by their work." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:108 +msgid "Create your first PR" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:110 +msgid "After pushing your branch to your development repository you will see an output similar to:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:128 +msgid "There are two ways to create the PR:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:130 +msgid "Click on the link displayed in the output of the push command." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:131 +msgid "Open a browser in your development repository `https://github.com/xyz-odoo/technical-training-sandbox`. There will be a button to create a new pull request." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:136 +msgid "You will notice that your commit message is used as the pull request message. This occurs if you have only 1 commit. If you have multiple commits, you can either make a summary of the commits as the PR message or if there aren't that many commits you can just copy/paste your commit messages as the PR message." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:143 +msgid "Additional Info for Odoo Staff" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:145 +msgid "Now that you know the basics, here are some more useful pages if you haven't seen them already:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:147 +msgid "Our `welcome `__ page has extra info about working at Odoo as well as additional `tutorials `__ that are both language and Odoo specific." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:151 +msgid "Once you are ready to start doing tasks, it is important to note that Odoo follows a `rebasing workflow instead of merging `__ for your PRs. `This cheatsheet `__ describes how to do this flow. If you want to become more of a rebasing master, then `this tutorial `__ is extra useful." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:159 +msgid "Test on the runbot" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:161 +msgid "Odoo has its own :abbr:`CI (Continuous integration)` server named `runbot `__. All commits, branches and PR will be tested to avoid regressions or breaking of the stable versions. All the runs that pass the tests are deployed on their own server with demo data." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:165 +msgid "Play with the runbot." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/16_guidelines_pr.rst:167 +msgid "Feel free to go to the runbot website and open the last stable version of Odoo to check out all the available applications and functionalities." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/A_i18n.rst:7 +msgid "Advanced A: Internationalization" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/A_i18n.rst:9 +#: ../../content/developer/howtos/rdtraining/D_mixins.rst:9 +#: ../../content/developer/howtos/rdtraining/F_jstour.rst:9 +#: ../../content/developer/howtos/rdtraining/G_website.rst:9 +#: ../../content/developer/howtos/rdtraining/H_adv_views.rst:9 +#: ../../content/developer/howtos/rdtraining/I_jswidget.rst:9 +#: ../../content/developer/howtos/rdtraining/L_cron.rst:9 +#: ../../content/developer/howtos/rdtraining/M_migration.rst:9 +#: ../../content/developer/howtos/rdtraining/N_security.rst:9 +#: ../../content/developer/howtos/rdtraining/O_perf.rst:9 +msgid "Hopefully, this topic will be written soon :-)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:5 +msgid "Advanced B: ACL and Record Rules" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:9 +msgid "This tutorial assumes you have completed the :ref:`Core Training `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:12 +#: ../../content/developer/howtos/rdtraining/J_reports.rst:12 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:12 +msgid "To follow the exercise, it is recommended that you fetch the branch 14.0-core from the repository XXX, it contains a version of the module created during the core training we can use as a starting point." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:17 +msgid "So far we have mostly concerned ourselves with implementing useful features. However in most business scenarios *security* quickly becomes a concern: currently," +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:21 +msgid "Any employee (which is what ``group_user`` stands for) can create, read, update or delete properties, property types, or property tags." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:23 +msgid "If ``estate_account`` is installed then only agents allowed to interact with invoicing can confirm sales as that's necessary to :ref:`create an invoice `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:27 +msgid "However:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:29 +msgid "We do not want third parties to be able to access properties directly." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:30 +msgid "Not all our employees may be real-estate agents (e.g. administrative personnel, property managers, ...), we don't want non-agents to see the available properties." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:33 +msgid "Real-estate agents don't need or get to decide what property types or tags are *available*." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:35 +msgid "Real-estate agents can have *exclusive* properties, we do not want one agent to be able to manage another's exclusivities." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:37 +msgid "All real-estate agents should be able to confirm the sale of a property they can manage, but we do not want them to be able to validate or mark as paid any invoice in the system." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:43 +msgid "We may actually be fine with some or most of these for a small business." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:45 +msgid "Because it's easier for users to disable unnecessary security rules than it is to create them from nothing, it's better to err on the side of caution and limiting access: users can relax that access if necessary or convenient." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:50 +msgid "Groups" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:54 +msgid "The documentation related to this topic can be found in :ref:`the security reference `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:57 +msgid ":ref:`The guidelines ` document the format and location of master data items." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:60 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:142 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:207 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:276 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:320 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:401 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:472 +msgid "**Goal**" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:62 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:144 +msgid "At the end of this section," +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:64 +msgid "We can make employees *real-estate agents* or *real-estate managers*." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:65 +msgid "The ``admin`` user is a real-estate manager." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:66 +msgid "We have a new *real-estate agent* employee with no access to invoicing or administration." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:69 +msgid "It would not be practical to attach individual security rules to employees any time we need a change so *groups* link security rules and users. They correspond to roles that can be assigned to employees." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:73 +msgid "For most Odoo applications [#app]_ a good baseline is to have *user* and *manager* (or administrator) roles: the manager can change the configuration of the application and oversee the entirety of its use while the user can well, use the application [#appuser]_." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:78 +msgid "This baseline seems sufficient for us:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:80 +msgid "Real estate managers can configure the system (manage available types and tags) as well as oversee every property in the pipeline." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:82 +msgid "Real estate agents can manage the properties under their care, or properties which are not specifically under the care of any agent." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:85 +msgid "In keeping with Odoo's data-driven nature, a group is no more than a record of the ``res.groups`` model. They are normally part of a module's :ref:`master data `, defined in one of the module's data files." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:89 +msgid "As simple example `can be found here `_." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:91 +msgid "what is the *category_id*?" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:93 +msgid "``category_id`` a *module category*, it is automatically generated from the :ref:`category defined in module manifest files `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:96 +msgid "the demo module needs to have the category set, to *Real Estate/Brokerage*, ideally the newapp part would already do that" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:102 +msgid "Create the ``security.xml`` file in the appropriate folder and add it to the ``__manifest__.py`` file." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:105 +msgid "Add a record creating a group with the id ``estate_group_user``, the name \"Agent\" and the category ``base.module_category_real_estate_brokerage``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:108 +msgid "Below that, add a record creating a group with the id ``estate_group_manager``, the name \"Manager\" and the category ``base.module_category_real_estate_brokerage``. The ``estate_group_manager`` group needs to imply ``estate_group_user``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:115 +msgid "Since we modified data files, remember to restart Odoo and update the module using ``-u estate``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:118 +msgid "If you go to :menuselection:`Settings --> Manage Users` and open the ``admin`` user (\"Mitchell Admin\"), you should see a new section:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:123 +msgid "Set the admin user to be a *Real Estate manager*." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:127 +msgid "Via the web interface, create a new user with only the \"real estate agent\" access. The user should not have any Invoicing or Administration access." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:130 +msgid "Use a private tab or window to log in with the new user (remember to set a password), as the real-estate agent you should only see the real estate application, and possibly the Discuss (chat) application:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:139 +msgid "The documentation related to this topic can be found at :ref:`reference/security/acl`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:146 +msgid "Employees who are not at least real-estate agents will not see the real-estate application." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:148 +msgid "Real-estate agents will not be able to update the property types or tags." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:150 +msgid "Access rights were first introduced in :ref:`howto/rdtraining/05_securityintro`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:152 +msgid "Access rights are a way to give users access to models *via* groups: associate an access right to a group, then all users with that group will have the access." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:155 +msgid "For instance we don't want real-estate agents to be able to modify what property types are available, so we would not link that access to the \"user\" group." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:158 +msgid "Access rights can only give access, they can't remove it: when access is checked, the system looks to see if *any* access right associated with the user (via any group) grants that access." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:163 +msgid "group" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:163 +msgid "create" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:163 +msgid "read" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:163 +msgid "update" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:163 +msgid "delete" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:165 +msgid "A" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:165 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:165 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:166 +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:167 +msgid "X" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:166 +msgid "B" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:167 +msgid "C" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:170 +msgid "A user with the groups A and C will be able to do anything but delete the object while one with B and C will be able to read or update, but not search or read." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:175 +msgid "The group of an access right can be omitted, this means the ACL applies to *every user*, this is a useful but risky fallback as depending on the applications installed it can grant even non-users access to the model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:178 +msgid "If no access right applies to a user, they are not granted access (default-deny)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:180 +msgid "If a menu item points to a model to which a user doesn't have access and has no submenus which the user can see, the menu will not be displayed." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:183 +msgid "Update the access rights file to:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:185 +msgid "Give full access to all objects to your Real Estate Manager group." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:186 +msgid "Give agents (real estate users) only read access to types and tags." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:187 +msgid "Give nobody the right to delete properties." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:188 +msgid "Check that your agent user is not able to alter types or tags, or to delete properties, but that they can otherwise create or update properties." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:194 +msgid "Remember to give different xids to your ``ir.model.access`` records otherwise they will overwrite one another." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:197 +msgid "Since the \"demo\" user was not made a real-estate agent or manager, they should not even be able to see the real-estate application. Use a private tab or window to check for this (the \"demo\" user has the password \"demo\")." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:202 +#: ../../content/developer/reference/addons/security.rst:83 +msgid "Record Rules" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:204 +msgid "The documentation related to this topic can be found at :ref:`reference/security/rules`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:209 +msgid "At the end of this section, agents will not be able to see the properties exclusive to their colleagues; but managers will still be able to see everything." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:213 +msgid "Access rights can grant access to an entire model but often we need to be more specific: while an agent can interact with properties in general we may not want them to update or even see properties managed by one of their colleagues." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:217 +msgid "Record *rules* provide that precision: they can grant or reject access to individual records:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:233 +msgid "The :ref:`reference/orm/domains` is how access is managed: if the record passes then access is granted, otherwise access is rejected." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:238 +msgid "Because rules tends to be rather complex and not created in bulk, they're usually created in XML rather than the CSV used for access rights." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:241 +msgid "The rule above:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:243 +msgid "Only applies to the \"create\", \"update\" (write) and \"delete\" (unlink) operations: here we want every employee to be able to see other users' records but only the author / assignee can update a record." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:246 +msgid "Is :ref:`non-global ` so we can provide an additional rule for e.g. managers." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:248 +msgid "Allows the operation if the current user (``user.id``) is set (e.g. created, or is assigned) on the record, or if the record has no associated user at all." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:253 +msgid "If no rule is defined or applies to a model and operation, then the operation is allowed (*default-allow*), this can have odd effects if access rights are not set up correctly (are too permissive)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:259 +msgid "Define a rule which limits agents to only being able to see or modify properties which have no salesperson, or for which they are the salesperson." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:262 +msgid "You may want to create a second real-estate agent user, or create a few properties for which the salesperson is a manager or some other user." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:265 +msgid "Verify that your real estate manager(s) can still see all properties. If not, why not? Remember:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:268 +msgid "The ``estate_group_manager`` group needs to imply ``estate_group_user``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:271 +msgid "Security Override" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:274 +msgid "Bypassing Security" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:278 +msgid "At the end of this section, agents should be able to confirm property sales without needing invoicing access." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:281 +msgid "If you try to mark a property as \"sold\" as the real estate agent, you should get an access error:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:286 +msgid "This happens because ``estate_account`` tries to create an invoice during the process, but creating an invoice requires the right to all invoice management." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:289 +msgid "We want agents to be able to confirm a sale without them having full invoicing access, which means we need to *bypass* the normal security checks of Odoo in order to create an invoice *despite* the current user not having the right to do so." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:294 +msgid "There are two main ways to bypass existing security checks in Odoo, either wilfully or as a side-effect:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:297 +msgid "The ``sudo()`` method will create a new recordset in \"sudo mode\", this ignores all access rights and record rules (although hard-coded group and user checks may still apply)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:300 +msgid "Performing raw SQL queries will bypass access rights and record rules as a side-effect of bypassing the ORM itself." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:305 +msgid "Update ``estate_account`` to bypass access rights and rules when creating the invoice." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:310 +msgid "These features should generally be avoided, and only used with extreme care, after having checked that the current user and operation should be able to bypass normal access rights validation." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:314 +msgid "Operations performed in such modes should also rely on user input as little as possible, and should validate it to the maximum extent they can." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:318 +msgid "Programmatically checking security" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:322 +msgid "At the end of this section, the creation of the invoice should be resilient to security issues regardless to changes to ``estate``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:325 +msgid "In Odoo, access rights and record rules are only checked *when performing data access via the ORM* e.g. creating, reading, searching, writing, or unlinking a record via ORM methods. Other methods do *not* necessarily check against any sort of access rights." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:330 +msgid "In the previous section, we bypassed the record rules when creating the invoice in ``action_sold``. This bypass can be reached by any user without any access right being checked:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:334 +msgid "Add a print to ``action_sold`` in ``estate_account`` before the creation of the invoice (as creating the invoice accesses the property, therefore triggers an ACL check) e.g.::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:340 +msgid "Execute ``bypass.py`` in ``estate_account``, giving it the name of your database, and the name of your version of ``action_sold`` (unless you named it ``action_sold`` then it's fine)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:344 +msgid "You should see ``reached`` in your Odoo log, followed by an access error." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:346 +msgid "Just because you're already in Python code does not mean any access right or rule has or will be checked." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:349 +msgid "*Currently* the accesses are implicitly checked by accessing data on ``self`` as well as calling ``super()`` (which does the same and *updates* ``self``), triggering access errors and cancelling the transaction \"uncreating\" our invoice." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:354 +msgid "*However* if this changes in the future, or we add side-effects to the method (e.g. reporting the sale to a government agency), or bugs are introduced in ``estate``, ... it would be possible for non-agents to trigger operations they should not have access to." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:359 +msgid "Therefore when performing non-CRUD operations, or legitimately bypassing the ORM or security, or when triggering other side-effects, it is extremely important to perform *explicit security checks*." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:363 +msgid "Explicit security checks can be performed by:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:365 +msgid "Checking who the current user is (``self.env.user``) and match them against specific models or records." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:367 +msgid "Checking that the current user has specific groups hard-coded to allow or deny an operation (``self.env.user.has_group``)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:369 +msgid "Calling the ``check_access_rights(operation)`` method on a recorset, this verifies whether the current user has access to the model itself." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:371 +msgid "Calling ``check_access_rule(operations)`` on a non-empty recorset, this verifies that the current user is allowed to perform the operation on *every* record of the set." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:375 +msgid "Checking access rights and checking record rules are separate operations, if you're checking record rules you usually want to also check access rights beforehand." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:381 +msgid "Before creating the invoice, use ``check_access_rights`` and ``check_access_rule`` to ensure that the current user can update properties in general, and this specific property in particular." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:385 +msgid "Re-run the bypass script, check that the error occurs before the print." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:390 +msgid "Multi-company security" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:394 +msgid ":ref:`reference/howtos/company` for an overview of multi-company facilities in general, and :ref:`multi-company security rules ` this in particular." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:398 +msgid "Documentation on rules in general can, again, be found at :ref:`reference/security/rules`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:403 +msgid "At the end of this section, agents should only have access to properties of their agency (or agencies)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:406 +msgid "For one reason or an other we might need to manage our real-estate business as multiple companies e.g. we might have largely autonomous agencies, or a franchise setup, or multiple brands (possibly from having acquired other real-estate businesses) which remain legally or financially separate from one another." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:412 +msgid "Odoo can be used to manage multiple companies inside the same system, however the actual handling is up to individual modules: Odoo itself provides the tools to manage the issue like company-dependent fields and *multi-company rules*, which is what we're going to concern ourselves with." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:417 +msgid "We want different agencies to be \"siloed\" from one another, with properties belonging to a given agency and users (whether agents or managers) only able to see properties linked to their agency." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:421 +msgid "As before, because this is based on non-trivial records it's easier for a user to relax rules than to tighten them so it makes sense to default to a relatively stronger security model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:425 +msgid "Multi-company rules are simply record rules based on the ``company_ids`` or ``company_id`` fields:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:428 +msgid "``company_ids`` is all the companies to which the current user has access" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:429 +msgid "``company_id`` is the currently active company (the one the user is currently working in / for)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:432 +msgid "Multi-company rules will *usually* use the former i.e. check if the record is associated with *one* of the companies the user has access to:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:448 +msgid "Multi-company rules are usually :ref:`global `, otherwise there is a high risk that additional rules would allow bypassing the muti-company rules." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:454 +msgid "Add a ``company_id`` field to ``estate.property``, it should be required (we don't want agency-less properties), and should default to the current user's current company." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:457 +msgid "Create a new company, with a new estate agent in that company." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:458 +msgid "The manager should be a member of both companies." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:459 +msgid "The old agent should only be a member of the old company." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:460 +msgid "Create a few properties in each company (either use the company selector as the manager or use the agents). Unset the default salesman to avoid triggering *that* rule." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:463 +msgid "All agents can see all companies, which is not desirable, add the record rule restricting this behaviour." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:466 +msgid "remember to ``--update`` your module when you change its model or data" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:470 +msgid "Visibility != security" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:474 +msgid "At the end of this section, real-estate agents should not see the Settings menu of the rea-estate application, but should still be able to set the property type or tags." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:478 +msgid "Specific Odoo models can be associated directly with groups (or companies, or users). It is important to figure out whether this association is a *security* or a *visibility* feature before using it:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:482 +msgid "*Visibility* features mean a user can still access the model or record otherwise, either through an other part of the interface or by :doc:`perform operations remotely using RPC <../../misc/api/odoo>`, things might just not be visible in the web interface in some contexts." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:486 +msgid "*Security* features mean a user can not access records, fields or operations." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:488 +msgid "Here are some examples:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:490 +msgid "Groups on *model fields* (in Python) are a security feature, users outside the group will not be able to retrieve the field, or even know it exists." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:493 +msgid "Example: in server actions, `only system users can see or update Python code `_." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:495 +msgid "Groups on *view elements* (in XML) are a visibility feature, users outside the group will not be able to see the element or its content in the form but they will otherwise be able to interact with the object (including that field)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:499 +msgid "Example: `only managers have an immediate filter to see their teams' leaves `_." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:501 +msgid "Groups on menus and actions are visibility features, the menu or action will not be shown in the interface but that doesn't prevent directly interacting with the underlying object." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:505 +msgid "Example: `only system administrators can see the elearning settings menu `_." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:510 +msgid "Real Estate agents can not add property types or tags, and can see their options from the Property form view when creating it." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:513 +msgid "The Settings menu just adds noise to their interface, it should only be visible to managers." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:516 +msgid "Despite not having access to the Property Types and Property Tags menus anymore, agents can still access the underlying objects since they can still select tags or a type to set on their properties." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:520 +msgid "An Odoo Application is a group of related modules covering a business area or field, usually composed of a base module and a number of expansions on that base to add optional or specific features, or link to other business areas." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/B_acl_irrules.rst:525 +msgid "For applications which would be used by most or every employees, the \"application user\" role might be done away with and its abilities granted to all employees directly e.g. generally all employees can submit expenses or take time off." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:5 +msgid "Advanced C: Master and Demo Data" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:7 +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:7 +msgid "This tutorial assumes you followed the Core Training." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:9 +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:9 +msgid "To do the exercise, fetch the branch 14.0-core from the repository XXX. It contains a basic module we will use as a starting point" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:13 +msgid "Data Types" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:16 +msgid "Master Data" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:18 +msgid "Master data is usually part of the technical or business requirements for the module. In other words, such data is often necessary for the module to work properly. This data will always be installed when installing the module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:22 +msgid "We already met technical data previously since we have defined :ref:`security rules`, :ref:`views` and :ref:`actions`. Those are one kind of master data." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:26 +msgid "On top of technical data, business data can be defined: countries, currencies, units of measure but also complete country localization (legal reports, tax definitions, chart of account), and much more..." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:31 +msgid "Demo Data" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:33 +msgid "Next to master data which are requirements for the modules to work properly, we also like having data for demonstration purpose setups:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:36 +msgid "Help the sales representatives to make their demos quickly." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:37 +msgid "Have a set of working data for developers to test the new features and see what it looks like with something they might not have created without it." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:39 +msgid "Test that the data is loaded correctly, without raising an error." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:40 +msgid "Be ready to use most of the features quickly when creating a new database." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:42 +msgid "Demo data is automatically loaded when you start the server if you didn't say explicitly you don't want it. This can be done in the database manager or with the command line." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:65 +msgid "Data Declaration" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:68 +#: ../../content/developer/reference/addons/module.rst:11 +msgid "Manifest" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:70 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`Module Manifests`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:73 +msgid "The data is declared either in CSV either in XML. Each file containing data must be added in the manifest for them to be loaded." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:76 +msgid "The keys to use in the manifest to add new data are ``data`` for the master data and ``demo`` for the demo data. Both values should be a list of strings representing the relative path to the files declaring the data." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:80 +msgid "Usually, the demo data is set in a ``demo`` folder, the views and actions are put in a ``views`` folder, the security related data is put in a ``security`` folder, and the other data is set in a ``data`` folder." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:84 +msgid "If your work tree looks like this:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:103 +msgid "Your manifest should look like this:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:126 +msgid "CSV" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:128 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`CSV data files`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:131 +msgid "The easiest way to declare simple data is by using the CSV format. This is however limited in terms of features: use it for long lists of simple models, but prefer XML in the other cases." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:140 +msgid "Your IDE has probably an extension to have a syntax highlighting of the CSV files" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:142 +msgid "`Atom `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:143 +msgid "`PyCharm/IntelliJ `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:144 +msgid "`Vim `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:145 +msgid "`Visual Studio `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:147 +msgid "Add some standard Real Estate Property Types for the `estate` module: Residential, Commercial, Industrial and Land. These should always be installed." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:151 +msgid "XML" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:153 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`Data Files`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:156 +msgid "When the data to create is a bit more complex it can be useful, or even needed, to do it in XML." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:172 +msgid "Create some demo data for the `estate` module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:177 +#: ../../content/developer/howtos/rdtraining/C_data.rst:241 +#: ../../content/developer/howtos/rdtraining/C_data.rst:242 +#: ../../content/developer/howtos/rdtraining/C_data.rst:243 +msgid "Big Villa" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:177 +msgid "Trailer home" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:178 +msgid "state" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:178 +msgid "New" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:178 +msgid "Canceled" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:179 +msgid "A nice and big villa" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:179 +msgid "Home in a trailer park" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:180 +msgid "12345" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:180 +msgid "54321" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:181 +msgid "2020-02-02" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:181 +msgid "1970-01-01" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:182 +msgid "1,600,000" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:182 +msgid "100,000" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:183 +msgid "120,000" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:184 +#: ../../content/developer/misc/api/extract_api.rst:122 +msgid "6" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:184 +#: ../../content/developer/misc/api/extract_api.rst:199 +msgid "1" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:185 +msgid "100" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:185 +msgid "10" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:186 +#: ../../content/developer/howtos/rdtraining/C_data.rst:186 +msgid "4" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:187 +#: ../../content/developer/howtos/rdtraining/C_data.rst:188 +#: ../../content/developer/reference/addons/mixins.rst:154 +#: ../../content/developer/reference/addons/mixins.rst:182 +#: ../../content/developer/reference/addons/mixins.rst:192 +msgid "True" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:187 +msgid "False" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:189 +msgid "100000" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:190 +msgid "South" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:194 +msgid "Data Extension" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:196 +msgid "During the Core Training, we saw in the :ref:`howto/rdtraining/13_inheritance` chapter we could inherit (extend) an existing view. This was a special case of data extension: any data can be extended in a module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:200 +msgid "When you are adding new fields to an existing model in a new module, you might want to populate those fields on the records created in the modules you are depending on. This is done by giving the `xml_id` of the record you want to extend. It won't replace it, in this case we will set the ``field_c`` to the given value for both records." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:219 +#: ../../content/developer/reference/addons/data.rst:104 +msgid "``ref``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:221 +msgid "Related fields can be set using the ``ref`` key. The value of that key is the ``xml_id`` of the record you want to link. Remember the ``xml_id`` is composed of the name of the module where the data is first declared, followed by a dot, followed by the ``id`` of the record (just the ``id`` works too if you are in the module declaring it)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:234 +msgid "Create some demo data offers for the properties you created." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:236 +msgid "Create offers using the partners defined in ``base``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:239 +msgid "Partner" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:239 +msgid "Estate" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:239 +msgid "Price" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:239 +msgid "Validity" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:241 +#: ../../content/developer/howtos/rdtraining/C_data.rst:242 +msgid "Azure Interior" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:241 +msgid "10000" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:241 +#: ../../content/developer/howtos/rdtraining/C_data.rst:242 +#: ../../content/developer/howtos/rdtraining/C_data.rst:243 +msgid "14" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:242 +msgid "1500000" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:243 +msgid "Deco Addict" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:243 +msgid "1500001" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:246 +msgid "Both properties should be Residential properties." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:249 +#: ../../content/developer/reference/addons/data.rst:145 +msgid "``eval``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:251 +msgid "The value to assign to a field is not always a simple string and you might need to compute it. It can also be used to optimize the insertion of related values, or because a constraint forces you to add the related values in batch. See ::ref:`Add X2many fields `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:263 +msgid "The offers you added should always be in a date relative to the installation of the module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:267 +#: ../../content/developer/reference/addons/data.rst:98 +#: ../../content/developer/reference/addons/data.rst:159 +msgid "``search``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:269 +msgid "Sometimes, you need to call the ORM to do a ``search``. This is not feasible with the CSV format." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:282 +msgid "In this code snippet, it is needed because the master data actually depends on the localization installed." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:286 +#: ../../content/developer/reference/addons/data.rst:164 +msgid "``function``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:288 +msgid "You might also need to execute python code when loading the data." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:296 +msgid "Validate one of the demo data offers by using the \"Accept Offer\" button. Refuse the others." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:303 +msgid "Add X2many fields" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:305 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`Common ORM methods`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:308 +msgid "If you need to add related data in a One2many or a Many2many field, you can do so by using the common ORM methods." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:334 +msgid "Create one new Property, but this time with some offers created directly inside the One2many field linking to the Offers." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:338 +#: ../../content/developer/howtos/website.rst:234 +msgid "Accessing the data" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:340 +msgid "You should never access demo data outside of the demo data declaration, not even in tests." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:343 +msgid "There are multiple ways to access the master/demo data." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:345 +msgid "In python code, you can use the ``env.ref(self, xml_id, raise_if_not_found=True)`` method. It returns the recordset linked to the ``xml_id`` you specify." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:348 +msgid "In XML, you can use the `ref` key like this" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:358 +msgid "It will call the ref method, and store the id of the record returned on the field ``related_id`` of the record of type ``tutorial.example`` with id ``id1``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:361 +msgid "In CSV, the title of the column must be suffixed with ``:id`` or ``/id``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:370 +msgid "In SQL, it is more complicated, see :ref:`the advanced section`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:372 +msgid "Data can always be deleted by the user. Always code defensively, taking this into account." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:379 +msgid "Advanced" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:384 +msgid "What is the XML id?" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:386 +msgid "Because we don't want a column ``xml_id`` in every single SQL table of the database, we need a mechanism to store it. This is done with the ``ir.model.data`` model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:389 +msgid "It contains the name of the record (the ``xml_id``) along with the module in which it is defined, the model defining it, and the id of it." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:393 +msgid "No update" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:395 +msgid "The records created with the ``noupdate`` flag won't be updated when upgrading the module that created them, but it will be created if it didn't exist yet." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:398 +msgid "``odoo-bin -i module`` will bypass this setting and always load the data. But normally one shouldn't do this on a production database." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:411 +msgid "Import as SQL" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:413 +msgid "In some cases, it makes sense to do the import directly in SQL. This is however discouraged as it bypasses all the features of the ORM, computed fields (including metadata) and python constraints." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:416 +msgid "Generally using raw SQL also bypasses ACLs and increases the risks of injections." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:418 +msgid "**Reference**: :ref:`Security in Odoo`" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:420 +msgid "It can help to speed the import time by a lot `with huge files `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:422 +msgid "For more complex imports like for the `translations `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/C_data.rst:424 +msgid "It can be necessary to `initialize the database `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/D_mixins.rst:7 +msgid "Advanced D: Mixins" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:5 +msgid "Advanced E: Python Unit Tests" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:12 +msgid "**Reference**: `Odoo's Test Framework: Learn Best Practices `__ (Odoo Experience 2020) on Youtube." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:16 +msgid "Writing tests is a necessity for multiple reasons. Here is a non exhaustive list:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:18 +msgid "Ensure it will not be broken in the future" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:19 +msgid "Define the scope of your code" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:20 +msgid "Give examples of use cases" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:21 +msgid "It is one way to technically document the code" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:22 +msgid "Help you develop by defining your goal before working towards it" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:25 +msgid "Running Tests" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:27 +msgid "Before knowing how to write tests, we need to know how to run them." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:79 +msgid "Integration Bots" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:81 +msgid "This section is only for Odoo employees and people that are contributing to `github.com/odoo`. We highly recommend having your own CI if it is not the case." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:84 +msgid "When a test is written, it is important to make sure it always passes when modifications are applied to the source code. To automate this task, we use a development practice called Continuous Integration (CI). This is why we have some bots running all the tests at different moments. Whether you are working at Odoo or not, if you are trying to merge something inside `odoo/odoo`, `odoo/enterprise`, `odoo/upgrade` or on odoo.sh, you will have to go through the CI. If you are working on another project, you should think of adding your own CI." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:93 +msgid "Runbot" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:95 +msgid "**Reference**: the documentation related to this topic can be found in `Runbot FAQ `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:98 +msgid "Most of the tests are run on `Runbot `__ every time a commit is pushed on GitHub." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:101 +msgid "You can see the state of a commit/branch by filtering on the runbot dashboard." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:103 +msgid "A **bundle** is created for each branch. A bundle consists of a configuration and contains the batches." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:106 +msgid "A **batch** is a set of builds, depending on the parameters of the bundle. A batch is green (i.e. passes the tests) if all the builds are green." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:109 +msgid "A **build** is when we launch a server. It can be divided in sub-builds. Usually there are builds for the community version, the enterprise version (only if there is an enterprise branch but you can force the build), and the migration of the branch. A build is green if every sub-build is green." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:114 +msgid "A **sub-build** only does some parts of what a full build does. It is used to speed up the CI process. Generally it is used to split the post install tests in 4 parallel instances. A sub-build is green if all the tests are passing and there are no errors/warnings logged." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:119 +msgid "All tests are run whatever the modifications done. Correcting a typo in an error message or refactoring a whole module triggers the same tests. It will install all the modules. This means something might not work if Runbot green but your changes depend on something you don't depend on." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:123 +msgid "The localization modules (i.e. country-specific modules) are not installed on Runbot (except the generic one), some modules with external dependencies can be excluded also." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:125 +msgid "There is a nightly build running additional tests, like module operations, localization, single module installs, multi-builds for nondeterministic bugs, etc. These are not kept in the standard CI to shorten the time of execution." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:129 +msgid "You can also login on a build built by Runbot. There are 3 users usable: `admin`, `demo` and `portal`. The password is the same as the login. This is useful to quickly test things on different versions without having to build it locally. The full logs are also available; these are used for monitoring." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:135 +msgid "Robodoo" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:137 +msgid "You will most likely have to gain a little bit more experience before having the rights to summon robodoo, but here are a few remarks anyways." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:140 +msgid "Robodoo is the guy spamming the CI status as tags on your PRs, but he is also the guy that kindly integrates your commits on the main repositories." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:143 +msgid "When the last batch is green, the reviewer can ask robodoo to merge your PR (actually it is more a `rebase` than a `merge`). It will then go to the mergebot." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:147 +msgid "Mergebot" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:149 +msgid "`Mergebot `__ is the last testing phase before merging a PR." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:151 +msgid "It will take the commits in your branch not yet present on the target, stage it and rerun the tests one more time, including the enterprise version even if you are only changing something in community." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:155 +msgid "This step can fail with a `Staging failed` error message. This could be due to" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:157 +msgid "a nondeterministic bug that is already on the target. If you are an Odoo employee, you can check those here: https://runbot.odoo.com/runbot/errors" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:159 +msgid "a nondeterministic bug that you introduced but wasn't detected in the CI before" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:160 +msgid "an incompatibility with another commit merged right before and what you are trying to merge" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:161 +msgid "an incompatibility with the enterprise repository if you only did changes in the community repo" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:163 +msgid "Always check that the issue does not come from you before asking the merge bot to retry: rebase your branch on the target and rerun the tests locally." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:167 +msgid "Modules" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:169 +msgid "Because Odoo is modular, the tests need to be modular also. This means the modules are defined in the module that adds the functionality you add; and that tests cannot depend on functionality coming from modules your module doesn't depend on." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:173 +msgid "**Reference**: the documentation related to this topic can be found in :ref:`Special Tags`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:194 +msgid "If the behavior you want to test can be changed by the installation of another module, you need to ensure that the tag `at_install` is set; otherwise you can use the tag `post_install` to speed up the CI, and ensure it is not changed if it shouldn't." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:199 +msgid "Writing a test" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:201 +msgid "**Reference**: the documentation related to this topic can be found in `Python unittest `__. and :ref:`Testing Odoo`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:205 +msgid "Here are a few things to take into consideration before writing a test" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:207 +msgid "The tests should be independent from the data currently in the database (including demo data)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:208 +msgid "Tests should not impact the database by leaving/changing residual data. This is usually done by the test framework by doing a rollback. This is why you must never call ``cr.commit`` in a test (nor anywhere else in the business code)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:211 +msgid "For a bug fix, the test should fail before applying the fix and pass after." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:212 +msgid "Don't test something that is already tested elsewhere; you can trust the ORM. Most of the tests in business modules should only test the business flows." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:214 +msgid "You shouldn't need to flush data into the database." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:216 +msgid "Remember that ``onchange`` only applies in the Form views, not by changing the attributes in python. This also applies in the tests. If you want to emulate a Form view, you can use ``odoo.tests.common.Form``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:220 +msgid "The tests should be located in a ``tests`` folder in the root of your module. Each test file name should start with `test_` and be imported in the ``__init__.py`` of the test folder. You shouldn't import the test folder/module in the ``__init__.py`` of the module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:236 +msgid "Some older tests are extending ``odoo.tests.common.TransactionCase``, but they are less scalable. The difference is that the setup is done per test method and not per test class. The data changed are rollbacked between each test in `SavepointCase` to have the same behavior as in `TransactionCase`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:241 +msgid "All the tests should extend ``odoo.tests.common.SavepointCase``. You usually define a ``setUpClass``, and the tests. After doing the `setUpClass`, you have an `env` available on the class and can start interacting with the ORM." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:245 +msgid "These test classes are built on top of the ``unittest`` python module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:288 +msgid "For more readability, split your tests into multiple files depending on the scope of the tests. You can also have a Common class that most of the tests should inherit from; that common class can define the whole set up for the module. For instance in `account `__." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:293 +msgid "Ensure no one can create an offer for a sold Property, and create a test for it." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:296 +msgid "Someone keeps breaking the reset of Garden Area and Orientation when you uncheck the Garden checkbox. Make sure it doesn't happen again." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/E_unittest.rst:299 +msgid "Tip: remember the note about `Form` a little bit above." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/F_jstour.rst:7 +msgid "Advanced F: JS Tours" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/G_website.rst:7 +msgid "Advanced G: Controllers & Website" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/H_adv_views.rst:7 +msgid "Advanced H: Advanced Views" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/I_jswidget.rst:7 +msgid "Advanced I: Custom JS Widget" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:5 +msgid "Advanced J: PDF Reports" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:9 +msgid "This tutorial assumes you have completed the :ref:`Core Training ` and have installed :ref:`wkhtmltopdf `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:17 +msgid "We were previously :ref:`introduced to QWeb ` in the Core Training where it was used to build a kanban view. Now we will expand on one of QWeb's other main uses: creating PDF reports. A common business requirement is the ability to create documents to send to customers and to use internally. These reports can be used to summarize and display information in an organized template to support the business in different ways. Odoo can additionally add our company's header and footer to our reports with minimal extra effort." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:24 +msgid "The documentation related to this topic can be found in :ref:`reference/qweb`, :ref:`reference/reports/report` and the :ref:`reference/actions/report` section of the Actions reference." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:29 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:34 +msgid "File Structure" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:31 +msgid "The bulk of a PDF report is its QWeb template. It also typically needs a corresponding ``ir.actions.report`` to include the report within a module's business logic. There is no strict rule for the file names or where they are located, but these two parts are typically stored in 2 separate files within a ``report`` folder in the top level of your module's directory. If a module has many or multiple long report templates, then they are often organized in a logical manner across different files named after the report(s) they contain. All actions for the reports are usually stored in the same file ending with ``_report_views.xml`` regardless of the number of reports it contains." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:40 +msgid "Therefore it is expected that your work tree will look something like:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:58 +msgid "Note that you will often see other non-QWeb and non-XML files containing \"report\" in their name also within the report folder. These are unrelated to the reports covered in this tutorial and are covered in :ref:`another advanced topic `. For now you can think of them as customized views that use direct SQL queries (sometimes referred to as SQL Views)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:63 +msgid "Don't forget to add whatever files your template and action view will be located in to your ``__manifest__.py``. In this case you will want to add the files to the ``data`` list and remember that the files listed in a manifest are loaded sequentially!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:68 +msgid "Basic Report" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:72 +msgid "**Goal**: at the end of this section, we will can print a report that displays all offers for a property." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:79 +msgid "In our real estate example there are many useful reports that we could create. One simple report we can create is one that displays all of a property's offers." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:83 +msgid "Report Data" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:85 +msgid "Before we do anything we first need some data to populate our reports or else this tutorial won't be very interesting. When creating reports, you will need some data to test your report code and check that the resulting look is as expected. It is a good idea to test with data that will cover most or all of your expected use cases. A good representation set for our simple report is:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:90 +msgid "At least 3 properties where 1 is \"sold\", 1 is \"offer received\" and 1 is \"new\"." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:91 +msgid "At least 2-3 offers for our \"sold\" and \"offer received\" properties" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:93 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:116 +msgid "If you don't have a set of data like this already, you can either:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:95 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:118 +msgid "Complete :ref:`howto/rdtraining/C_data` (if you haven't done so already) and add the extra cases to your demo data (you may need to create a new database to load in the demo data)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:97 +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:120 +msgid "Manually create the data in your database." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:98 +msgid "Copy this `data file `__ into a new directory (data) in your estate module and copy `these lines `__ into your __manifest__.py file (you may need to create a new database to load in the demo data)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:103 +msgid "Before continuing, click through your data in your database and make sure your data is as expected. Of course you can add the data after you write your report code, but then you will not be able to incrementally test portions of your code as you write it. This can make checking for mistakes and debugging your code more difficult in the long run for complicated reports." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:109 +msgid "Minimal Template" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:111 +msgid "A minimal viable template is viewable under the \"Minimal viable template\" section of the :ref:`reference/reports/templates` documentation. We can modify this example to build our minimal property offers template file:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:153 +msgid "Most of the Odoo specific (i.e. non-HTML) items in our file are explained in the minimal viable template section. Some additional features in our template are:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:156 +msgid "The use of the ``class=\"table\"`` attribute so our table has some nice formatting. Twitter Bootstrap (we're using its table class in this case) and FontAwesome (useful for adding icons) classes can be used in your report template." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:159 +msgid "The use of ``t-set``, ``t-value``, ``t-foreach`` and ``t-as`` so that we can loop over all of the ``offer_ids``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:161 +msgid "If you are already familiar with website templating engines, then the QWeb directives (i.e. the `t-` commands) probably don't need much explanation and you can just look at its :ref:`documentation ` and skip ahead to the next subsection." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:165 +msgid "Otherwise you are encouraged to read more about them ( `Wikipedia `__ has a good high level description), but the general idea is that QWeb provides the ability to dynamically generate web code based on Odoo data and simple commands. I.e. QWeb can access recordset data (and methods) and process simple programming operations such as setting and accessing temporary variables. For example, in the above example:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:171 +msgid "``t-set`` creates a temporary variable called \"offers\" that has its value set by ``t-value`` to the current ``estate.property`` recordset's ``offer_ids``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:173 +msgid "the ``t-foreach`` and ``t-as`` usage is the equivalent to the Python:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:180 +msgid "Report Action" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:182 +msgid "Now that we have a template, we need to make it accessible in our app via a ``ir.actions.report``. A practical example of ``ir.actions.report`` is `here `__ corresponding to `this template `__. Its contents are all explained in :ref:`the documentation `." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:189 +msgid "An ``ir.actions.report`` is primarily used via the Print menu of a model's view. In the practical example, the ``binding_model_id`` specifies which model's views the report should show in and Odoo will auto-magically add it for you. Another common use case of the report action is to link it to a button like we learned in :ref:`howto/rdtraining/10_actions`. This is handy for reports that only make sense under specific conditions. For example, if we wanted to make a \"Final Sale\" report, then we can link it to a \"Print Sale Info\" button that appears in the form view only when the property is \"Sold\"." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:201 +msgid "You may have noticed or are wondered why our report template loops through a recordset. When our template is passed more than one record, it can produce one PDF report for all of the records. Using the Print menu in the list view with multiple records selected will demonstrate this." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:206 +msgid "Make a Report" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:208 +msgid "Finally, you now know where to create your files and how the content of the files should look. Happy report making!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:210 +msgid "Make a report." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:212 +msgid "Add the property offers report from the minimal template subsection to the Print menu of the Property views." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:214 +msgid "Improve the report by adding more data. Refer to the **Goal** of this section to see what additional data you can add and feel free to add even more." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:217 +msgid "Bonus: Make an extra flexible report by adding in some logic so that when there are no offers on a property then we don't create a table and instead write something about how there are no offers yet. Hint: you will need to use ``t-if`` and ``t-else``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:221 +msgid "Remember to check that your PDF reports match your data as expected." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:225 +msgid "Sub-templates" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:229 +msgid "**Goal**: at the end of this section, we will have a sub-template that we use in 2 reports." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:235 +msgid "There are two main reasons for using sub-templates. One is to make the code easier to read when working with extra long or complicated templates. The other is to reuse code where possible. Our simple property offers report is useful, but listing property offers information can be useful for more than just one report template. One example is a report that lists all of a salesman's properties' offers." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:240 +msgid "See if you can understand how to call a sub-template by reading the :ref:`documentation ` on it and/or by looking at an `example `__ (remember QWeb uses the same control flows regardless if it is for a report or a view in Odoo.)" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:245 +msgid "Create and use a sub-template." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:247 +msgid "Split the table portion of the offers into its own template. Remember to check that your original report still prints correctly afterwards." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:250 +msgid "Add a new report for ``res.users`` that allows you to print all of the Real Estate Properties that are visible in their form view (i.e. in the \"Settings\" app). Include the offers for each of those saleman's properties in the same report. Hint: since the ``binding_model_id`` in this case will not be within the estate module, you will need to use ``ref=\"base.model_res_users\"``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:255 +msgid "Your end result should look similar to the image in the **Goal** of this section." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:257 +msgid "Remember to check that your reports match your data as expected!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:260 +msgid "Report Inheritance" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:264 +msgid "**Goal**: at the end of this section, we will inherit the property report in the ``estate_account`` module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:271 +msgid "Inheritance in QWeb uses the same ``xpath`` elements as :ref:`views inheritance `. A QWeb template refers to its parent template in a different way though. It is even easier to do by just adding the ``inherit_id`` attribute to the ``template`` element and setting it equal to the *module.parent_template_id*." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:275 +msgid "We didn't add any new fields to any of the estate models in `estate_account`, but we can still add information to our existing property report. For example, we know that any \"Sold\" properties will already have an invoice created for them, so we can add this information to our report." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:279 +msgid "Inherit a report." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:281 +msgid "Extend the property report to include some information about the invoice. You can look at the **Goal** of this section for inspiration (i.e. print a line when the property is Done, otherwise print nothing)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:284 +msgid "Again, remember to check that your reports match your data as expected!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:287 +msgid "Additional Features" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:289 +msgid "All of the following extra features are described further in the :ref:`reference/reports/report` documentation, including how to implement each of them." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:293 +#: ../../content/developer/howtos/web.rst:1227 +msgid "Translations" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:295 +msgid "We all know Odoo is used in multiple languages thanks to automated and manual translating. QWeb reports are no exception! Note that sometimes the translations do not work properly if there are unnecessary spaces in your template's text content so try to avoid them when possible (especially leading spaces)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:300 +#: ../../content/developer/reference/addons/reports.rst:309 +msgid "Reports are web pages" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:302 +msgid "You probably are tired of hearing that QWeb creates HTML, but we're saying it again! One of the neat features about reports being written in QWeb is they can be viewed within the web browser. This can be useful if you want to embed a hyperlink that leads to a specific report. Note that the usual security checks will still apply to prevent unauthorized users from accessing the reports." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:308 +#: ../../content/developer/reference/addons/reports.rst:148 +msgid "Barcodes" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/J_reports.rst:310 +msgid "Odoo has a built-in barcode image creator that allows for barcodes to be embedded in your reports. Check out the corresponding `code `__ to see all the supported barcode types." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:5 +msgid "Advanced K: Dashboards" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:9 +msgid "This tutorial assumes you have completed the :ref:`Core Training ` and have access to Odoo Enterprise features." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:17 +msgid "The term \"Dashboard\" is used in Odoo for objects that display data, but involves different implementations. This tutorial will only focus on the Enterprise view that is used to provide aggregated data visualization. They can be added as a ``view_mode`` to an existing model (i.e. a view you can switch to via the view buttons in the top right of a view), but they are also often used as a view for to a special model customized for data visualization. You may hear these special views referred to as SQL views." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:24 +msgid "It is useful to note there is a \"Dashboard\" app in Odoo Community. This app allows users to create their own customized view of data, but the customization is only visible to each user and can only be viewed within the \"Dashboard\" app. Technically it is possible to make global dashboards using this ``board`` module, but it is much easier to do as an Enterprise view. Plus it looks nicer and has extra features not available in ``board``. Some other dashboards within Odoo also exist, but they are custom made and are beyond the scope of this tutorial." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:31 +msgid "The documentation related to this topic can be found in :ref:`reference/views/dashboard`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:36 +msgid "You probably have already guessed that since dashboard views are an Enterprise view, they must have a dependency on an Enterprise module. The Enterprise module is ``web_dashboard``. Don't forget to add it to your manifest file! It is standard to add dashboards intended to be used as a ``view_mode`` for one of your module's models (in the ``model`` folder``) to the views directory (i.e. the same file that contains the other views for the same model)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:42 +msgid "It is standard to create a separate Enterprise module to add extra Enterprise views and features to a Community module. This is done in a similar manner as the module link technique covered within :ref:`howto/rdtraining/14_other_module`. The difference is that instead of linking 2 different modules, we are extending our `estate` module. We do this by creating a new module and adding both the Community module and its necessary Enterprise module dependencies to its manifest. You will commonly see \"enterprise\" in the module's directory name. To keep this tutorial simple, we will add dashboards to our existing ``estate`` module." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:50 +msgid "SQL Views have 2 parts: their xml file (don't forget to add it to your manifest file) and their Python file (don't forget to add it to the appropriate ``__init.py__`` files). The former is the same format as the ``view_mode`` xml while the latter contains a custom model and SQL code to populate its fields. It is standard to add SQL view files to the ``report/`` directory. It is also common to include \"report\" in the name of the SQL view's files. You may be wondering why do we put the files in a report directory? We saw earlier that the dashboard is for data visualization, therefore it is not editable. You can think of dashboards as interactive reports where you can click on statistics, graphs, and charts to see the specific data contributing to them. Note it is also standard to store the xml code for :ref:`PDF report templates ` in the report directory." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:61 +msgid "It is expected that your work tree will look something like:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:82 +msgid "Dashboard View" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:86 +msgid "**Goal**: at the end of this section, we will have a new dashboard view that displays different property statistics." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:93 +msgid "Dashboards can display data in different ways, including:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:95 +msgid "showing an ``aggregate`` of a field" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:96 +msgid "using aggregated fields in a ``formula``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:97 +msgid "using a ``widget``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:98 +msgid "using another ``view`` as a subview" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:100 +msgid "There are many useful statistics and visuals we can provide for our real estate example using these options. A full example to reference while doing the exercises in this section is `viewable here `__ (restricted github repository link)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:106 +msgid "Data" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:107 +msgid "To fully enjoy our dashboard view, we will need good test data to populate it. Test data will allow us to check that the resulting look and statistics are correct. It is a good idea to test with data that will cover most or all of your expected use cases, but is also easy to verify with that your statistics are correct. In our goal's case we are looking at count, sum, average, minimum, and maximum statistics, therefore a good representation set for our dashboard is:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:113 +msgid "At least 3 properties with different property types, expected prices, and average living area." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:114 +msgid "At least 1 sold property and at least 1 canceled property" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:121 +msgid "Copy this `data file `__ into a new directory called ``data`` in your estate module and copy `these lines `__ into your __manifest__.py file (you may need to create a new database to load in the demo data)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:126 +msgid "Click through your database data and make sure it is what you expect. Of course you can add the data after you write your dashboard code and then test that your view is working as expected." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:130 +msgid "Aggregations" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:131 +msgid "Building a dashboard view is very similar to what you have previously done in :ref:`howto/rdtraining/07_basicviews`. For the dashboard view, we use the `dashboard` root element and choose from its possible tags (see all the possibilities and their attributes in the :ref:`reference/views/dashboard` documentation). So a simple dashboard example is:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:145 +msgid "In this example, ```` adds styling and ```` declares an aggregation. We indicate which ``field`` we want to aggregate, what ``string`` to display with the value, and how to aggregate it with the `group_operator` attribute. The `group_operator` can use any valid PostgreSQL aggregate function plus the special Odoo defined ``count_distinct``." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:150 +msgid "Hopefully you remember how to add views to a window action `view_mode` (hint, it was covered in :ref:`howto/rdtraining/06_firstui`). Now let's make some dashboards!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:153 +msgid "Make a dashboard view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:155 +msgid "Create a dashboard of aggregated values for the ``estate.property`` model. You can look at the **Goal** of this section for some inspiration. Remember to check that your statistics are calculating as you expect and note that the calculated values take into consideration any applied view filters!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:160 +msgid "Bonus: Add in some aggregations that need a `domain` to make sense (remember domains were also covered in :ref:`howto/rdtraining/07_basicviews`)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:164 +msgid "Pie Charts" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:165 +msgid "Adding pie charts to dashboards is a piece of cake using the `` element. An example is:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:175 +msgid "In this example, we indicate that we're using the `pie_chart` widget with the `name` attribute, the ``title`` for the pie chart, and that we're grouping it by property type." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:178 +msgid "Add some pie charts." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:180 +msgid "Add the pie charts from the **Goal** of this section to your dashboard. Hint: you will need to add `'measure': selling_price` to your pie chart `attrs` if you want to show selling prices grouped by property type." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:184 +msgid "Hover over and click on the pie charts to check your charts counts values and don't forget that filters will also apply to the charts." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:187 +msgid "Bonus: Add a domain to your selling price pie chart to only include \"sold\" properties (i.e. not \"offer_accepted\" ones). Note that the `'` will need to be escaped since it is declared as part of the `attrs`." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:192 +msgid "Subviews" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:193 +msgid "Similar to how we can use the list view within the form view (we saw this automatically happen for One2many relationships in :ref:`howto/rdtraining/08_relations`), we can add other views within our dashboard view. The most commonly added are the pivot and graph views, but the cohort view is also an option. These views are covered in more depth in :ref:`howto/rdtraining/H_adv_views`. For this topic you are only required to know their names. A dashboard with only subviews is:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:206 +msgid "The `ref` attribute can be added to `` elements to use a specific xml id for that view. If no xml id is provided for a graph or pivot view then the default view will be used. The cohort view will not work in the dashboard without a specific xml id. If you have already created some of these views then you are welcome to add them to your dashboard! Sample graph and pivot views are included in the `solution code `__ that you are welcome to use as well." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:214 +msgid "Add subviews." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:216 +msgid "Add in a graph and a pivot view to your dashboard. Try playing around with the layout of your subviews in relation to your pie charts and aggregated values and refer to the **Goal** of this section for an often used layout. Remember to check that your subviews are displaying your data as expected (and yes, they are also affected by the filters!)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:222 +msgid "SQL Views" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:226 +msgid "This section expects you to have a basic knowledge of SQL. If you have little to no SQL knowledge then `this is a good tutorial to start with `__ and these `exercises `__ are good for those who need a refresher or extra practice." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:233 +msgid "**Goal**: at the end of this section, we will have a new SQL view that displays different property statistics." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:241 +msgid "Occasionally we want to show data that goes beyond what our model already has in it. We could add a lot of stored computed or related fields (non-stored fields cannot be aggregated or displayed in pie charts), but it would be impractical to store a bunch of fields only for this purpose. We can instead add a custom SQL view to minimize the computational load and keep our model clean of unnecessary fields." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:249 +msgid "We will start with the more difficult part: our special report model. This file starts the same as any other model except that we add 2 attributes ``_auto`` and ``_rec_name``::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:261 +msgid "``_auto = False`` indicates that we do not want to store the model in the database and we will create a custom table by overriding the ``BaseModel.init()`` method. ``_rec_name`` indicates which of the model's fields represents a record's name (i.e. the name that will be used in the navigation breadcrumb when opening a record's form view). In this case I left it as 'id' because our property offers don't have a name. We will need the `tools` import later (i.e. ``odoo/odoo/tools``, which is full of all sort of useful helper methods you will probably use in the future). Note that it is standard to include ``report`` in the model name." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:269 +msgid "Remember your new model will need to be added to your security file like you learned in :ref:`howto/rdtraining/05_securityintro`!" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:272 +msgid "Then we define the fields we need for our dashboard the same way as any other model (like you learned in :ref:`howto/rdtraining/04_basicmodel`), except that every field is ``readonly=True``. After all, our model is for readonly purposes only." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:276 +msgid "Now we override the ``BaseModel.init()`` method mentioned earlier::" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:287 +msgid "We use ``tools.drop_view_if_exists`` to ensure that we don't create a conflicting view and then execute the SQL query. It is standard to separate the different parts of the query to allow for easier model extension. Exactly how the query is split up across methods is not standardized, but you will often see at minimum ``_select`` and ``_from`` methods [or something similar] and of course all of these methods will return strings. The columns from the SELECT will populate our model's fields so ensure that your column names match your field names or use alias names that match." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:295 +msgid "Create report model." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:297 +msgid "Create a report model with the following fields:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:300 +msgid "Note" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:302 +#: ../../content/developer/reference/addons/static/res.country.state.csv:1 +msgid "id" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:302 +msgid "Corresponds to ``id`` of ``estate.property.offer``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:303 +msgid "offer_state" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:303 +msgid "Equals ``state`` choices of ``estate.property.offer``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:305 +msgid "property_state" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:305 +msgid "Equals ``state`` choices of ``estate.property``" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:306 +msgid "property_type_id" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:309 +msgid "and write the SQL query necessary to populate the fields (hint, you will need 2 JOINs)." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:311 +msgid "You won't be able to check if your model is correct until we create a view for it, but you are welcome to check your query directly in your database to see if the results are as you expect. If you struggle with this exercise, then `here is an example `__ to reference." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:319 +msgid "Now that we have our model, we can make its dashboard view. There is no difference to how its made except that its file is located in the ``report`` folder. Since it is a new model not linked to any other model, we will also have to add a new menuitem to view our dashboard. Typically SQL views are added under a first level menu called ``Reporting` (because it's a report, surprise!). Do you remember how to add a ``menuitem``? If not, revisit :ref:`howto/rdtraining/06_firstui`) again." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:325 +msgid "Create report view." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:327 +msgid "Recreate the dashboard in the **Goal** of this section. Hint: it uses the ``formula`` element, which we did not need for our previous dashboard." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:330 +msgid "Bonus: Create ``list`` and ``form`` views for your new report model so we don't have to see the ugly defaults when you click on your pie charts." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:334 +msgid "Extra Tips" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:335 +msgid "**Tip 1** A common mistake in SQL views is to not take into account the duplication of certain data due to table JOINs. For example, in our **Goal** we have a pie chart of the offers' property types. We may be tempted to add a similar pie chart with a domain to only include canceled properties, so we think we are only counting the number of canceled properties by property type. In reality we are still looking at all the offers per property so any property with more than 1 offer will be counted per offer. This example is easily double checked by clicking on the pie chart to see its list view:" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:347 +msgid "But for cases such as average aggregations or using a subview such as the pivot view, it is easy to miss this mistake. It is also easy to miss this mistake when you have insufficient test data. In order to add a number of properties canceled by property type pie chart to this report, we would either have to do a hack (too advanced for this tutorial) or simply exclude it from this report." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/K_dashboard.rst:353 +msgid "**Tip 2** If you have a field that you do not want as a measure (i.e. in your pivot or graph views), then you can add ``store=False`` to it and it will not show." +msgstr "" + +#: ../../content/developer/howtos/rdtraining/L_cron.rst:7 +msgid "Advanced L: Scheduled & Server Actions" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/M_migration.rst:7 +msgid "Advanced M: Migrations" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/N_security.rst:7 +msgid "Advanced N: Security" +msgstr "" + +#: ../../content/developer/howtos/rdtraining/O_perf.rst:7 +msgid "Advanced O: Performances" +msgstr "" + #: ../../content/developer/howtos/themes.rst:4 msgid "Theme Tutorial" msgstr "" @@ -2251,8 +8189,7 @@ msgid "Add Styles" msgstr "" #: ../../content/developer/howtos/themes.rst:306 -#: ../../content/developer/reference/mobile.rst:9 -#: ../../content/developer/webservices/upgrade.rst:10 +#: ../../content/developer/reference/javascript/mobile.rst:9 msgid "Introduction" msgstr "" @@ -2337,7 +8274,7 @@ msgid "\\(1) Set the values for Odoo-provided SCSS variables" msgstr "" #: ../../content/developer/howtos/themes.rst:397 -msgid "Odoo declares many CSS rules, most being entirely customizable by overridding the related SCSS variables. First, create a new file called primary_variables.scss and add it the same way as the style.scss file. The only difference it that you won't add it in the ``assets_frontend`` template but in the ``_assets_primary_variables`` template." +msgid "Odoo declares many CSS rules, most being entirely customizable by overriding the related SCSS variables. First, create a new file called primary_variables.scss and add it the same way as the style.scss file. The only difference it that you won't add it in the ``assets_frontend`` template but in the ``_assets_primary_variables`` template." msgstr "" #: ../../content/developer/howtos/themes.rst:414 @@ -2517,7 +8454,8 @@ msgid "Xpath expression" msgstr "" #: ../../content/developer/howtos/themes.rst:796 -#: ../../content/developer/reference/data.rst:14 +#: ../../content/developer/reference/addons/data.rst:14 +#: ../../content/developer/reference/addons/testing.rst:547 msgid "Structure" msgstr "" @@ -2706,9 +8644,9 @@ msgid "Event" msgstr "" #: ../../content/developer/howtos/themes.rst:959 -#: ../../content/developer/webservices/extract_api.rst:42 -#: ../../content/developer/webservices/extract_api.rst:152 -#: ../../content/developer/webservices/extract_api.rst:382 +#: ../../content/developer/misc/api/extract_api.rst:42 +#: ../../content/developer/misc/api/extract_api.rst:145 +#: ../../content/developer/misc/api/extract_api.rst:359 msgid "Description" msgstr "" @@ -2952,1362 +8890,1371 @@ msgstr "" msgid "Descriptions, while not important to search engine rankings, are extremely important in gaining user click-through. These are an opportunity to advertise content and to let people searching know exactly whether the given page contains the information they're looking for. It is important that titles and descriptions on each page are unique." msgstr "" -#: ../../content/developer/howtos/web.rst:4 +#: ../../content/developer/howtos/web.rst:5 msgid "Customizing the web client" msgstr "" -#: ../../content/developer/howtos/web.rst:6 -msgid "Note: this section is really really out of date. It will be updated someday, but meanwhile, this tutorial will probably be frustrating to follow, since it was written a long time ago." +#: ../../content/developer/howtos/web.rst:9 +msgid "this section is really really out of date. It will be updated someday, but meanwhile, this tutorial will probably be frustrating to follow, since it was written a long time ago." msgstr "" -#: ../../content/developer/howtos/web.rst:15 +#: ../../content/developer/howtos/web.rst:18 msgid "This guide is about creating modules for Odoo's web client." msgstr "" -#: ../../content/developer/howtos/web.rst:17 +#: ../../content/developer/howtos/web.rst:20 msgid "To create websites with Odoo, see :doc:`website`; to add business capabilities or extend existing business systems of Odoo, see :doc:`backend`." msgstr "" -#: ../../content/developer/howtos/web.rst:22 +#: ../../content/developer/howtos/web.rst:25 msgid "This guide assumes knowledge of:" msgstr "" -#: ../../content/developer/howtos/web.rst:24 +#: ../../content/developer/howtos/web.rst:27 msgid "Javascript basics and good practices" msgstr "" -#: ../../content/developer/howtos/web.rst:25 +#: ../../content/developer/howtos/web.rst:28 msgid "jQuery_" msgstr "" -#: ../../content/developer/howtos/web.rst:26 +#: ../../content/developer/howtos/web.rst:29 msgid "`Underscore.js`_" msgstr "" -#: ../../content/developer/howtos/web.rst:28 +#: ../../content/developer/howtos/web.rst:31 msgid "It also requires :ref:`an installed Odoo `, and Git_." msgstr "" -#: ../../content/developer/howtos/web.rst:32 +#: ../../content/developer/howtos/web.rst:35 msgid "A Simple Module" msgstr "" -#: ../../content/developer/howtos/web.rst:34 +#: ../../content/developer/howtos/web.rst:37 msgid "Let's start with a simple Odoo module holding basic web component configuration and letting us test the web framework." msgstr "" -#: ../../content/developer/howtos/web.rst:37 +#: ../../content/developer/howtos/web.rst:40 msgid "The example module is available online and can be downloaded using the following command:" msgstr "" -#: ../../content/developer/howtos/web.rst:44 +#: ../../content/developer/howtos/web.rst:47 msgid "This will create a ``petstore`` folder wherever you executed the command. You then need to add that folder to Odoo's :option:`addons path `, create a new database and install the ``oepetstore`` module." msgstr "" -#: ../../content/developer/howtos/web.rst:49 +#: ../../content/developer/howtos/web.rst:52 msgid "If you browse the ``petstore`` folder, you should see the following content:" msgstr "" -#: ../../content/developer/howtos/web.rst:75 +#: ../../content/developer/howtos/web.rst:78 msgid "The module already holds various server customizations. We'll come back to these later, for now let's focus on the web-related content, in the ``static`` folder." msgstr "" -#: ../../content/developer/howtos/web.rst:79 +#: ../../content/developer/howtos/web.rst:82 msgid "Files used in the \"web\" side of an Odoo module must be placed in a ``static`` folder so they are available to a web browser, files outside that folder can not be fetched by browsers. The ``src/css``, ``src/js`` and ``src/xml`` sub-folders are conventional and not strictly necessary." msgstr "" -#: ../../content/developer/howtos/web.rst:84 +#: ../../content/developer/howtos/web.rst:87 msgid "``oepetstore/static/css/petstore.css``" msgstr "" -#: ../../content/developer/howtos/web.rst:85 +#: ../../content/developer/howtos/web.rst:88 msgid "Currently empty, will hold the CSS_ for pet store content" msgstr "" -#: ../../content/developer/howtos/web.rst:86 +#: ../../content/developer/howtos/web.rst:89 msgid "``oepetstore/static/xml/petstore.xml``" msgstr "" -#: ../../content/developer/howtos/web.rst:87 +#: ../../content/developer/howtos/web.rst:90 msgid "Mostly empty, will hold :ref:`reference/qweb` templates" msgstr "" -#: ../../content/developer/howtos/web.rst:106 +#: ../../content/developer/howtos/web.rst:109 msgid "``oepetstore/static/js/petstore.js``" msgstr "" -#: ../../content/developer/howtos/web.rst:89 +#: ../../content/developer/howtos/web.rst:92 msgid "The most important (and interesting) part, contains the logic of the application (or at least its web-browser side) as javascript. It should currently look like::" msgstr "" -#: ../../content/developer/howtos/web.rst:108 +#: ../../content/developer/howtos/web.rst:111 msgid "Which only prints a small message in the browser's console." msgstr "" -#: ../../content/developer/howtos/web.rst:110 +#: ../../content/developer/howtos/web.rst:113 msgid "The files in the ``static`` folder, need to be defined within the module in order for them to be loaded correctly. Everything in ``src/xml`` is defined in ``__manifest__.py`` while the contents of ``src/css`` and ``src/js`` are defined in ``petstore.xml``, or a similar file." msgstr "" -#: ../../content/developer/howtos/web.rst:114 +#: ../../content/developer/howtos/web.rst:117 msgid "All JavaScript files are concatenated and :term:`minified` to improve application load time." msgstr "" -#: ../../content/developer/howtos/web.rst:117 +#: ../../content/developer/howtos/web.rst:120 msgid "One of the drawback is debugging becomes more difficult as individual files disappear and the code is made significantly less readable. It is possible to disable this process by enabling the \"developer mode\": log into your Odoo instance (user *admin* password *admin* by default) open the user menu (in the top-right corner of the Odoo screen) and select :guilabel:`About Odoo` then :guilabel:`Activate the developer mode`:" msgstr "" -#: ../../content/developer/howtos/web.rst:131 +#: ../../content/developer/howtos/web.rst:134 msgid "This will reload the web client with optimizations disabled, making development and debugging significantly more comfortable." msgstr "" -#: ../../content/developer/howtos/web.rst:134 +#: ../../content/developer/howtos/web.rst:137 msgid "qweb files hooked via __manifest__.py, but js and CSS use bundles" msgstr "" -#: ../../content/developer/howtos/web.rst:137 +#: ../../content/developer/howtos/web.rst:140 msgid "Odoo JavaScript Module" msgstr "" -#: ../../content/developer/howtos/web.rst:139 +#: ../../content/developer/howtos/web.rst:142 msgid "Javascript doesn't have built-in modules. As a result variables defined in different files are all mashed together and may conflict. This has given rise to various module patterns used to build clean namespaces and limit risks of naming conflicts." msgstr "" -#: ../../content/developer/howtos/web.rst:144 +#: ../../content/developer/howtos/web.rst:147 msgid "The Odoo framework uses one such pattern to define modules within web addons, in order to both namespace code and correctly order its loading." msgstr "" -#: ../../content/developer/howtos/web.rst:147 +#: ../../content/developer/howtos/web.rst:150 msgid "``oepetstore/static/js/petstore.js`` contains a module declaration::" msgstr "" -#: ../../content/developer/howtos/web.rst:153 +#: ../../content/developer/howtos/web.rst:156 msgid "In Odoo web, modules are declared as functions set on the global ``odoo`` variable. The function's name must be the same as the addon (in this case ``oepetstore``) so the framework can find it, and automatically initialize it." msgstr "" -#: ../../content/developer/howtos/web.rst:157 +#: ../../content/developer/howtos/web.rst:160 msgid "When the web client loads your module it will call the root function and provide two parameters:" msgstr "" -#: ../../content/developer/howtos/web.rst:160 +#: ../../content/developer/howtos/web.rst:163 msgid "the first parameter is the current instance of the Odoo web client, it gives access to various capabilities defined by the Odoo (translations, network services) as well as objects defined by the core or by other modules." msgstr "" -#: ../../content/developer/howtos/web.rst:164 +#: ../../content/developer/howtos/web.rst:167 msgid "the second parameter is your own local namespace automatically created by the web client. Objects and variables which should be accessible from outside your module (either because the Odoo web client needs to call them or because others may want to customize them) should be set inside that namespace." msgstr "" -#: ../../content/developer/howtos/web.rst:171 +#: ../../content/developer/howtos/web.rst:174 msgid "Classes" msgstr "" -#: ../../content/developer/howtos/web.rst:173 +#: ../../content/developer/howtos/web.rst:176 msgid "Much as modules, and contrary to most object-oriented languages, javascript does not build in *classes*\\ [#classes]_ although it provides roughly equivalent (if lower-level and more verbose) mechanisms." msgstr "" -#: ../../content/developer/howtos/web.rst:177 +#: ../../content/developer/howtos/web.rst:180 msgid "For simplicity and developer-friendliness Odoo web provides a class system based on John Resig's `Simple JavaScript Inheritance`_." msgstr "" -#: ../../content/developer/howtos/web.rst:180 +#: ../../content/developer/howtos/web.rst:183 msgid "New classes are defined by calling the :func:`~odoo.web.Class.extend` method of :class:`odoo.web.Class`::" msgstr "" -#: ../../content/developer/howtos/web.rst:189 +#: ../../content/developer/howtos/web.rst:192 msgid "The :func:`~odoo.web.Class.extend` method takes a dictionary describing the new class's content (methods and static attributes). In this case, it will only have a ``say_hello`` method which takes no parameters." msgstr "" -#: ../../content/developer/howtos/web.rst:193 +#: ../../content/developer/howtos/web.rst:196 msgid "Classes are instantiated using the ``new`` operator::" msgstr "" -#: ../../content/developer/howtos/web.rst:199 +#: ../../content/developer/howtos/web.rst:202 msgid "And attributes of the instance can be accessed via ``this``::" msgstr "" -#: ../../content/developer/howtos/web.rst:212 +#: ../../content/developer/howtos/web.rst:215 msgid "Classes can provide an initializer to perform the initial setup of the instance, by defining an ``init()`` method. The initializer receives the parameters passed when using the ``new`` operator::" msgstr "" -#: ../../content/developer/howtos/web.rst:229 +#: ../../content/developer/howtos/web.rst:232 msgid "It is also possible to create subclasses from existing (used-defined) classes by calling :func:`~odoo.web.Class.extend` on the parent class, as is done to subclass :class:`~odoo.web.Class`::" msgstr "" -#: ../../content/developer/howtos/web.rst:243 +#: ../../content/developer/howtos/web.rst:246 msgid "When overriding a method using inheritance, you can use ``this._super()`` to call the original method::" msgstr "" -#: ../../content/developer/howtos/web.rst:259 +#: ../../content/developer/howtos/web.rst:262 msgid "``_super`` is not a standard method, it is set on-the-fly to the next method in the current inheritance chain, if any. It is only defined during the *synchronous* part of a method call, for use in asynchronous handlers (after network calls or in ``setTimeout`` callbacks) a reference to its value should be retained, it should not be accessed via ``this``::" msgstr "" -#: ../../content/developer/howtos/web.rst:282 +#: ../../content/developer/howtos/web.rst:285 msgid "Widgets Basics" msgstr "" -#: ../../content/developer/howtos/web.rst:284 +#: ../../content/developer/howtos/web.rst:287 msgid "The Odoo web client bundles jQuery_ for easy DOM manipulation. It is useful and provides a better API than standard `W3C DOM`_\\ [#dombugs]_, but insufficient to structure complex applications leading to difficult maintenance." msgstr "" -#: ../../content/developer/howtos/web.rst:289 +#: ../../content/developer/howtos/web.rst:292 msgid "Much like object-oriented desktop UI toolkits (e.g. Qt_, Cocoa_ or GTK_), Odoo Web makes specific components responsible for sections of a page. In Odoo web, the base for such components is the :class:`~odoo.Widget` class, a component specialized in handling a page section and displaying information for the user." msgstr "" -#: ../../content/developer/howtos/web.rst:296 +#: ../../content/developer/howtos/web.rst:299 msgid "Your First Widget" msgstr "" -#: ../../content/developer/howtos/web.rst:298 +#: ../../content/developer/howtos/web.rst:301 msgid "The initial demonstration module already provides a basic widget::" msgstr "" -#: ../../content/developer/howtos/web.rst:306 +#: ../../content/developer/howtos/web.rst:309 msgid "It extends :class:`~odoo.Widget` and overrides the standard method :func:`~odoo.Widget.start`, which — much like the previous ``MyClass`` — does little for now." msgstr "" -#: ../../content/developer/howtos/web.rst:310 +#: ../../content/developer/howtos/web.rst:313 msgid "This line at the end of the file::" msgstr "" -#: ../../content/developer/howtos/web.rst:315 +#: ../../content/developer/howtos/web.rst:318 msgid "registers our basic widget as a client action. Client actions will be explained later, for now this is just what allows our widget to be called and displayed when we select the :menuselection:`Pet Store --> Pet Store --> Home Page` menu." msgstr "" -#: ../../content/developer/howtos/web.rst:322 +#: ../../content/developer/howtos/web.rst:325 msgid "because the widget will be called from outside our module, the web client needs its \"fully qualified\" name, not the local version." msgstr "" -#: ../../content/developer/howtos/web.rst:326 +#: ../../content/developer/howtos/web.rst:329 msgid "Display Content" msgstr "" -#: ../../content/developer/howtos/web.rst:328 +#: ../../content/developer/howtos/web.rst:331 msgid "Widgets have a number of methods and features, but the basics are simple:" msgstr "" -#: ../../content/developer/howtos/web.rst:330 +#: ../../content/developer/howtos/web.rst:333 msgid "set up a widget" msgstr "" -#: ../../content/developer/howtos/web.rst:331 +#: ../../content/developer/howtos/web.rst:334 msgid "format the widget's data" msgstr "" -#: ../../content/developer/howtos/web.rst:332 +#: ../../content/developer/howtos/web.rst:335 msgid "display the widget" msgstr "" -#: ../../content/developer/howtos/web.rst:334 +#: ../../content/developer/howtos/web.rst:337 msgid "The ``HomePage`` widget already has a :func:`~odoo.Widget.start` method. That method is part of the normal widget lifecycle and automatically called once the widget is inserted in the page. We can use it to display some content." msgstr "" -#: ../../content/developer/howtos/web.rst:339 +#: ../../content/developer/howtos/web.rst:342 msgid "All widgets have a :attr:`~odoo.Widget.$el` which represents the section of page they're in charge of (as a jQuery_ object). Widget content should be inserted there. By default, :attr:`~odoo.Widget.$el` is an empty ``
`` element." msgstr "" -#: ../../content/developer/howtos/web.rst:344 +#: ../../content/developer/howtos/web.rst:347 msgid "A ``
`` element is usually invisible to the user if it has no content (or without specific styles giving it a size) which is why nothing is displayed on the page when ``HomePage`` is launched." msgstr "" -#: ../../content/developer/howtos/web.rst:348 +#: ../../content/developer/howtos/web.rst:351 msgid "Let's add some content to the widget's root element, using jQuery::" msgstr "" -#: ../../content/developer/howtos/web.rst:356 +#: ../../content/developer/howtos/web.rst:359 msgid "That message will now appear when you open :menuselection:`Pet Store --> Pet Store --> Home Page`" msgstr "" -#: ../../content/developer/howtos/web.rst:361 +#: ../../content/developer/howtos/web.rst:364 msgid "to refresh the javascript code loaded in Odoo Web, you will need to reload the page. There is no need to restart the Odoo server." msgstr "" -#: ../../content/developer/howtos/web.rst:364 +#: ../../content/developer/howtos/web.rst:367 msgid "The ``HomePage`` widget is used by Odoo Web and managed automatically. To learn how to use a widget \"from scratch\" let's create a new one::" msgstr "" -#: ../../content/developer/howtos/web.rst:373 +#: ../../content/developer/howtos/web.rst:376 msgid "We can now add our ``GreetingsWidget`` to the ``HomePage`` by using the ``GreetingsWidget``'s :func:`~odoo.Widget.appendTo` method::" msgstr "" -#: ../../content/developer/howtos/web.rst:384 +#: ../../content/developer/howtos/web.rst:387 msgid "``HomePage`` first adds its own content to its DOM root" msgstr "" -#: ../../content/developer/howtos/web.rst:385 +#: ../../content/developer/howtos/web.rst:388 msgid "``HomePage`` then instantiates ``GreetingsWidget``" msgstr "" -#: ../../content/developer/howtos/web.rst:386 +#: ../../content/developer/howtos/web.rst:389 msgid "Finally it tells ``GreetingsWidget`` where to insert itself, delegating part of its :attr:`~odoo.Widget.$el` to the ``GreetingsWidget``." msgstr "" -#: ../../content/developer/howtos/web.rst:389 +#: ../../content/developer/howtos/web.rst:392 msgid "When the :func:`~odoo.Widget.appendTo` method is called, it asks the widget to insert itself at the specified position and to display its content. The :func:`~odoo.Widget.start` method will be called during the call to :func:`~odoo.Widget.appendTo`." msgstr "" -#: ../../content/developer/howtos/web.rst:394 +#: ../../content/developer/howtos/web.rst:397 msgid "To see what happens under the displayed interface, we will use the browser's DOM Explorer. But first let's alter our widgets slightly so we can more easily find where they are, by :attr:`adding a class to their root elements `::" msgstr "" -#: ../../content/developer/howtos/web.rst:408 +#: ../../content/developer/howtos/web.rst:411 msgid "If you can find the relevant section of the DOM (right-click on the text then :guilabel:`Inspect Element`), it should look like this:" msgstr "" -#: ../../content/developer/howtos/web.rst:420 +#: ../../content/developer/howtos/web.rst:423 msgid "Which clearly shows the two ``
`` elements automatically created by :class:`~odoo.Widget`, because we added some classes on them." msgstr "" -#: ../../content/developer/howtos/web.rst:423 +#: ../../content/developer/howtos/web.rst:426 msgid "We can also see the two message-holding divs we added ourselves" msgstr "" -#: ../../content/developer/howtos/web.rst:425 +#: ../../content/developer/howtos/web.rst:428 msgid "Finally, note the ``
`` element which represents the ``GreetingsWidget`` instance is *inside* the ``
`` which represents the ``HomePage`` instance, since we appended" msgstr "" -#: ../../content/developer/howtos/web.rst:431 +#: ../../content/developer/howtos/web.rst:434 msgid "Widget Parents and Children" msgstr "" -#: ../../content/developer/howtos/web.rst:433 +#: ../../content/developer/howtos/web.rst:436 msgid "In the previous part, we instantiated a widget using this syntax::" msgstr "" -#: ../../content/developer/howtos/web.rst:437 +#: ../../content/developer/howtos/web.rst:440 msgid "The first argument is ``this``, which in that case was a ``HomePage`` instance. This tells the widget being created which other widget is its *parent*." msgstr "" -#: ../../content/developer/howtos/web.rst:441 +#: ../../content/developer/howtos/web.rst:444 msgid "As we've seen, widgets are usually inserted in the DOM by another widget and *inside* that other widget's root element. This means most widgets are \"part\" of another widget, and exist on behalf of it. We call the container the *parent*, and the contained widget the *child*." msgstr "" -#: ../../content/developer/howtos/web.rst:446 +#: ../../content/developer/howtos/web.rst:449 msgid "Due to multiple technical and conceptual reasons, it is necessary for a widget to know who is its parent and who are its children." msgstr "" -#: ../../content/developer/howtos/web.rst:457 +#: ../../content/developer/howtos/web.rst:460 msgid ":func:`~odoo.Widget.getParent`" msgstr "" -#: ../../content/developer/howtos/web.rst:450 +#: ../../content/developer/howtos/web.rst:453 msgid "can be used to get the parent of a widget::" msgstr "" -#: ../../content/developer/howtos/web.rst:469 +#: ../../content/developer/howtos/web.rst:472 msgid ":func:`~odoo.Widget.getChildren`" msgstr "" -#: ../../content/developer/howtos/web.rst:460 +#: ../../content/developer/howtos/web.rst:463 msgid "can be used to get a list of its children::" msgstr "" -#: ../../content/developer/howtos/web.rst:471 +#: ../../content/developer/howtos/web.rst:474 msgid "When overriding the :func:`~odoo.Widget.init` method of a widget it is *of the utmost importance* to pass the parent to the ``this._super()`` call, otherwise the relation will not be set up correctly::" msgstr "" -#: ../../content/developer/howtos/web.rst:482 +#: ../../content/developer/howtos/web.rst:485 msgid "Finally, if a widget does not have a parent (e.g. because it's the root widget of the application), ``null`` can be provided as parent::" msgstr "" -#: ../../content/developer/howtos/web.rst:488 +#: ../../content/developer/howtos/web.rst:491 msgid "Destroying Widgets" msgstr "" -#: ../../content/developer/howtos/web.rst:490 +#: ../../content/developer/howtos/web.rst:493 msgid "If you can display content to your users, you should also be able to erase it. This is done via the :func:`~odoo.Widget.destroy` method::" msgstr "" -#: ../../content/developer/howtos/web.rst:495 +#: ../../content/developer/howtos/web.rst:498 msgid "When a widget is destroyed it will first call :func:`~odoo.Widget.destroy` on all its children. Then it erases itself from the DOM. If you have set up permanent structures in :func:`~odoo.Widget.init` or :func:`~odoo.Widget.start` which must be explicitly cleaned up (because the garbage collector will not handle them), you can override :func:`~odoo.Widget.destroy`." msgstr "" -#: ../../content/developer/howtos/web.rst:504 +#: ../../content/developer/howtos/web.rst:507 msgid "when overriding :func:`~odoo.Widget.destroy`, ``_super()`` *must always* be called otherwise the widget and its children are not correctly cleaned up leaving possible memory leaks and \"phantom events\", even if no error is displayed" msgstr "" -#: ../../content/developer/howtos/web.rst:510 +#: ../../content/developer/howtos/web.rst:513 msgid "The QWeb Template Engine" msgstr "" -#: ../../content/developer/howtos/web.rst:512 +#: ../../content/developer/howtos/web.rst:515 msgid "In the previous section we added content to our widgets by directly manipulating (and adding to) their DOM::" msgstr "" -#: ../../content/developer/howtos/web.rst:517 +#: ../../content/developer/howtos/web.rst:520 msgid "This allows generating and displaying any type of content, but gets unwieldy when generating significant amounts of DOM (lots of duplication, quoting issues, ...)" msgstr "" -#: ../../content/developer/howtos/web.rst:521 +#: ../../content/developer/howtos/web.rst:524 msgid "As many other environments, Odoo's solution is to use a `template engine`_. Odoo's template engine is called :ref:`reference/qweb`." msgstr "" -#: ../../content/developer/howtos/web.rst:524 +#: ../../content/developer/howtos/web.rst:527 msgid "QWeb is an XML-based templating language, similar to `Genshi `_, `Thymeleaf `_ or `Facelets `_. It has the following characteristics:" msgstr "" -#: ../../content/developer/howtos/web.rst:530 +#: ../../content/developer/howtos/web.rst:533 msgid "It's implemented fully in JavaScript and rendered in the browser" msgstr "" -#: ../../content/developer/howtos/web.rst:531 +#: ../../content/developer/howtos/web.rst:534 msgid "Each template file (XML files) contains multiple templates" msgstr "" -#: ../../content/developer/howtos/web.rst:532 +#: ../../content/developer/howtos/web.rst:535 msgid "It has special support in Odoo Web's :class:`~odoo.Widget`, though it can be used outside of Odoo's web client (and it's possible to use :class:`~odoo.Widget` without relying on QWeb)" msgstr "" -#: ../../content/developer/howtos/web.rst:538 +#: ../../content/developer/howtos/web.rst:541 msgid "The rationale behind using QWeb instead of existing javascript template engines is the extensibility of pre-existing (third-party) templates, much like Odoo :ref:`views `." msgstr "" -#: ../../content/developer/howtos/web.rst:542 +#: ../../content/developer/howtos/web.rst:545 msgid "Most javascript template engines are text-based which precludes easy structural extensibility where an XML-based templating engine can be generically altered using e.g. XPath or CSS and a tree-alteration DSL (or even just XSLT). This flexibility and extensibility is a core characteristic of Odoo, and losing it was considered unacceptable." msgstr "" -#: ../../content/developer/howtos/web.rst:549 +#: ../../content/developer/howtos/web.rst:552 msgid "Using QWeb" msgstr "" -#: ../../content/developer/howtos/web.rst:551 +#: ../../content/developer/howtos/web.rst:554 msgid "First let's define a simple QWeb template in the almost-empty ``oepetstore/static/src/xml/petstore.xml`` file:" msgstr "" -#: ../../content/developer/howtos/web.rst:563 +#: ../../content/developer/howtos/web.rst:566 msgid "Now we can use this template inside of the ``HomePage`` widget. Using the ``QWeb`` loader variable defined at the top of the page, we can call to the template defined in the XML file::" msgstr "" -#: ../../content/developer/howtos/web.rst:573 +#: ../../content/developer/howtos/web.rst:576 msgid ":func:`QWeb.render` looks for the specified template, renders it to a string and returns the result." msgstr "" -#: ../../content/developer/howtos/web.rst:576 +#: ../../content/developer/howtos/web.rst:579 msgid "However, because :class:`~odoo.Widget` has special integration for QWeb the template can be set directly on the widget via its :attr:`~odoo.Widget.template` attribute::" msgstr "" -#: ../../content/developer/howtos/web.rst:587 +#: ../../content/developer/howtos/web.rst:590 msgid "Although the result looks similar, there are two differences between these usages:" msgstr "" -#: ../../content/developer/howtos/web.rst:590 +#: ../../content/developer/howtos/web.rst:593 msgid "with the second version, the template is rendered right before :func:`~odoo.Widget.start` is called" msgstr "" -#: ../../content/developer/howtos/web.rst:592 +#: ../../content/developer/howtos/web.rst:595 msgid "in the first version the template's content is added to the widget's root element, whereas in the second version the template's root element is directly *set as* the widget's root element. Which is why the \"greetings\" sub-widget also gets a red background" msgstr "" -#: ../../content/developer/howtos/web.rst:599 +#: ../../content/developer/howtos/web.rst:602 msgid "templates should have a single non-``t`` root element, especially if they're set as a widget's :attr:`~odoo.Widget.template`. If there are multiple \"root elements\", results are undefined (usually only the first root element will be used and the others will be ignored)" msgstr "" -#: ../../content/developer/howtos/web.rst:605 +#: ../../content/developer/howtos/web.rst:608 msgid "QWeb Context" msgstr "" -#: ../../content/developer/howtos/web.rst:607 +#: ../../content/developer/howtos/web.rst:610 msgid "QWeb templates can be given data and can contain basic display logic." msgstr "" -#: ../../content/developer/howtos/web.rst:609 +#: ../../content/developer/howtos/web.rst:612 msgid "For explicit calls to :func:`QWeb.render`, the template data is passed as second parameter::" msgstr "" -#: ../../content/developer/howtos/web.rst:614 +#: ../../content/developer/howtos/web.rst:617 msgid "with the template modified to:" msgstr "" -#: ../../content/developer/howtos/web.rst:622 +#: ../../content/developer/howtos/web.rst:625 msgid "will result in:" msgstr "" -#: ../../content/developer/howtos/web.rst:628 +#: ../../content/developer/howtos/web.rst:631 msgid "When using :class:`~odoo.Widget`'s integration it is not possible to provide additional data to the template. The template will be given a single ``widget`` context variable, referencing the widget being rendered right before :func:`~odoo.Widget.start` is called (the widget's state will essentially be that set up by :func:`~odoo.Widget.init`):" msgstr "" -#: ../../content/developer/howtos/web.rst:652 +#: ../../content/developer/howtos/web.rst:655 +#: ../../content/developer/misc/api/odoo.rst:210 +#: ../../content/developer/misc/api/odoo.rst:296 +#: ../../content/developer/misc/api/odoo.rst:338 +#: ../../content/developer/misc/api/odoo.rst:377 +#: ../../content/developer/misc/api/odoo.rst:417 +#: ../../content/developer/misc/api/odoo.rst:481 +#: ../../content/developer/misc/api/odoo.rst:514 +#: ../../content/developer/misc/api/odoo.rst:562 +#: ../../content/developer/misc/api/odoo.rst:645 +#: ../../content/developer/misc/api/odoo.rst:716 +#: ../../content/developer/misc/api/odoo.rst:785 +#: ../../content/developer/misc/api/odoo.rst:834 +#: ../../content/developer/misc/api/odoo.rst:946 +#: ../../content/developer/misc/api/odoo.rst:1111 msgid "Result:" msgstr "" -#: ../../content/developer/howtos/web.rst:659 +#: ../../content/developer/howtos/web.rst:662 msgid "Template Declaration" msgstr "" -#: ../../content/developer/howtos/web.rst:661 +#: ../../content/developer/howtos/web.rst:664 msgid "We've seen how to *render* QWeb templates, let's now see the syntax of the templates themselves." msgstr "" -#: ../../content/developer/howtos/web.rst:664 +#: ../../content/developer/howtos/web.rst:667 msgid "A QWeb template is composed of regular XML mixed with QWeb *directives*. A QWeb directive is declared with XML attributes starting with ``t-``." msgstr "" -#: ../../content/developer/howtos/web.rst:667 +#: ../../content/developer/howtos/web.rst:670 msgid "The most basic directive is ``t-name``, used to declare new templates in a template file:" msgstr "" -#: ../../content/developer/howtos/web.rst:678 +#: ../../content/developer/howtos/web.rst:681 msgid "``t-name`` takes the name of the template being defined, and declares that it can be called using :func:`QWeb.render`. It can only be used at the top-level of a template file." msgstr "" -#: ../../content/developer/howtos/web.rst:683 +#: ../../content/developer/howtos/web.rst:686 msgid "Escaping" msgstr "" -#: ../../content/developer/howtos/web.rst:685 +#: ../../content/developer/howtos/web.rst:688 msgid "The ``t-esc`` directive can be used to output text:" msgstr "" -#: ../../content/developer/howtos/web.rst:691 +#: ../../content/developer/howtos/web.rst:694 msgid "It takes a Javascript expression which is evaluated, the result of the expression is then HTML-escaped and inserted in the document. Since it's an expression it's possible to provide just a variable name as above, or a more complex expression like a computation:" msgstr "" -#: ../../content/developer/howtos/web.rst:700 +#: ../../content/developer/howtos/web.rst:703 msgid "or method calls:" msgstr "" -#: ../../content/developer/howtos/web.rst:707 +#: ../../content/developer/howtos/web.rst:710 msgid "Outputting HTML" msgstr "" -#: ../../content/developer/howtos/web.rst:709 +#: ../../content/developer/howtos/web.rst:712 msgid "To inject HTML in the page being rendered, use ``t-raw``. Like ``t-esc`` it takes an arbitrary Javascript expression as parameter, but it does not perform an HTML-escape step." msgstr "" -#: ../../content/developer/howtos/web.rst:719 +#: ../../content/developer/howtos/web.rst:722 msgid "``t-raw`` *must not* be used on any data which may contain non-escaped user-provided content as this leads to `cross-site scripting`_ vulnerabilities" msgstr "" -#: ../../content/developer/howtos/web.rst:724 -#: ../../content/developer/reference/qweb.rst:66 +#: ../../content/developer/howtos/web.rst:727 +#: ../../content/developer/reference/javascript/qweb.rst:66 msgid "Conditionals" msgstr "" -#: ../../content/developer/howtos/web.rst:726 +#: ../../content/developer/howtos/web.rst:729 msgid "QWeb can have conditional blocks using ``t-if``. The directive takes an arbitrary expression, if the expression is falsy (``false``, ``null``, ``0`` or an empty string) the whole block is suppressed, otherwise it is displayed." msgstr "" -#: ../../content/developer/howtos/web.rst:743 +#: ../../content/developer/howtos/web.rst:746 msgid "QWeb doesn't have an \"else\" structure, use a second ``t-if`` with the original condition inverted. You may want to store the condition in a local variable if it's a complex or expensive expression." msgstr "" -#: ../../content/developer/howtos/web.rst:748 +#: ../../content/developer/howtos/web.rst:751 msgid "Iteration" msgstr "" -#: ../../content/developer/howtos/web.rst:750 +#: ../../content/developer/howtos/web.rst:753 msgid "To iterate on a list, use ``t-foreach`` and ``t-as``. ``t-foreach`` takes an expression returning a list to iterate on ``t-as`` takes a variable name to bind to each item during iteration." msgstr "" -#: ../../content/developer/howtos/web.rst:764 +#: ../../content/developer/howtos/web.rst:767 msgid "``t-foreach`` can also be used with numbers and objects (dictionaries)" msgstr "" -#: ../../content/developer/howtos/web.rst:768 +#: ../../content/developer/howtos/web.rst:771 msgid "Defining attributes" msgstr "" -#: ../../content/developer/howtos/web.rst:770 +#: ../../content/developer/howtos/web.rst:773 msgid "QWeb provides two related directives to define computed attributes: :samp:`t-att-{name}` and :samp:`t-attf-{name}`. In either case, *name* is the name of the attribute to create (e.g. ``t-att-id`` defines the attribute ``id`` after rendering)." msgstr "" -#: ../../content/developer/howtos/web.rst:775 +#: ../../content/developer/howtos/web.rst:778 msgid "``t-att-`` takes a javascript expression whose result is set as the attribute's value, it is most useful if all of the attribute's value is computed:" msgstr "" -#: ../../content/developer/howtos/web.rst:786 +#: ../../content/developer/howtos/web.rst:789 msgid "``t-attf-`` takes a *format string*. A format string is literal text with interpolation blocks inside, an interpolation block is a javascript expression between ``{{`` and ``}}``, which will be replaced by the result of the expression. It is most useful for attributes which are partially literal and partially computed such as a class:" msgstr "" -#: ../../content/developer/howtos/web.rst:799 +#: ../../content/developer/howtos/web.rst:802 msgid "Calling other templates" msgstr "" -#: ../../content/developer/howtos/web.rst:801 +#: ../../content/developer/howtos/web.rst:804 msgid "Templates can be split into sub-templates (for simplicity, maintainability, reusability or to avoid excessive markup nesting)." msgstr "" -#: ../../content/developer/howtos/web.rst:804 +#: ../../content/developer/howtos/web.rst:807 msgid "This is done using the ``t-call`` directive, which takes the name of the template to render:" msgstr "" -#: ../../content/developer/howtos/web.rst:818 +#: ../../content/developer/howtos/web.rst:821 msgid "rendering the ``A`` template will result in:" msgstr "" -#: ../../content/developer/howtos/web.rst:826 +#: ../../content/developer/howtos/web.rst:829 msgid "Sub-templates inherit the rendering context of their caller." msgstr "" -#: ../../content/developer/howtos/web.rst:829 +#: ../../content/developer/howtos/web.rst:832 msgid "To Learn More About QWeb" msgstr "" -#: ../../content/developer/howtos/web.rst:831 +#: ../../content/developer/howtos/web.rst:834 msgid "For a QWeb reference, see :ref:`reference/qweb`." msgstr "" -#: ../../content/developer/howtos/web.rst:834 -#: ../../content/developer/howtos/web.rst:1100 +#: ../../content/developer/howtos/web.rst:837 +#: ../../content/developer/howtos/web.rst:1103 msgid "Exercise" msgstr "" -#: ../../content/developer/howtos/web.rst:836 +#: ../../content/developer/howtos/web.rst:839 msgid "Usage of QWeb in Widgets" msgstr "" -#: ../../content/developer/howtos/web.rst:838 +#: ../../content/developer/howtos/web.rst:841 msgid "Create a widget whose constructor takes two parameters aside from ``parent``: ``product_names`` and ``color``." msgstr "" -#: ../../content/developer/howtos/web.rst:841 +#: ../../content/developer/howtos/web.rst:844 msgid "``product_names`` should an array of strings, each one the name of a product" msgstr "" -#: ../../content/developer/howtos/web.rst:843 +#: ../../content/developer/howtos/web.rst:846 msgid "``color`` is a string containing a color in CSS color format (ie: ``#000000`` for black)." msgstr "" -#: ../../content/developer/howtos/web.rst:846 +#: ../../content/developer/howtos/web.rst:849 msgid "The widget should display the given product names one under the other, each one in a separate box with a background color with the value of ``color`` and a border. You should use QWeb to render the HTML. Any necessary CSS should be in ``oepetstore/static/src/css/petstore.css``." msgstr "" -#: ../../content/developer/howtos/web.rst:851 +#: ../../content/developer/howtos/web.rst:854 msgid "Use the widget in ``HomePage`` with half a dozen products." msgstr "" -#: ../../content/developer/howtos/web.rst:915 +#: ../../content/developer/howtos/web.rst:918 msgid "Widget Helpers" msgstr "" -#: ../../content/developer/howtos/web.rst:918 +#: ../../content/developer/howtos/web.rst:921 msgid "``Widget``'s jQuery Selector" msgstr "" -#: ../../content/developer/howtos/web.rst:920 +#: ../../content/developer/howtos/web.rst:923 msgid "Selecting DOM elements within a widget can be performed by calling the ``find()`` method on the widget's DOM root::" msgstr "" -#: ../../content/developer/howtos/web.rst:925 +#: ../../content/developer/howtos/web.rst:928 msgid "But because it's a common operation, :class:`~odoo.Widget` provides an equivalent shortcut through the :func:`~odoo.Widget.$` method::" msgstr "" -#: ../../content/developer/howtos/web.rst:936 +#: ../../content/developer/howtos/web.rst:939 msgid "The global jQuery function ``$()`` should *never* be used unless it is absolutely necessary: selection on a widget's root are scoped to the widget and local to it, but selections with ``$()`` are global to the page/application and may match parts of other widgets and views, leading to odd or dangerous side-effects. Since a widget should generally act only on the DOM section it owns, there is no cause for global selection." msgstr "" -#: ../../content/developer/howtos/web.rst:944 +#: ../../content/developer/howtos/web.rst:947 msgid "Easier DOM Events Binding" msgstr "" -#: ../../content/developer/howtos/web.rst:946 +#: ../../content/developer/howtos/web.rst:949 msgid "We have previously bound DOM events using normal jQuery event handlers (e.g. ``.click()`` or ``.change()``) on widget elements::" msgstr "" -#: ../../content/developer/howtos/web.rst:961 +#: ../../content/developer/howtos/web.rst:964 msgid "While this works it has a few issues:" msgstr "" -#: ../../content/developer/howtos/web.rst:963 +#: ../../content/developer/howtos/web.rst:966 msgid "it is rather verbose" msgstr "" -#: ../../content/developer/howtos/web.rst:964 +#: ../../content/developer/howtos/web.rst:967 msgid "it does not support replacing the widget's root element at runtime as the binding is only performed when ``start()`` is run (during widget initialization)" msgstr "" -#: ../../content/developer/howtos/web.rst:967 +#: ../../content/developer/howtos/web.rst:970 msgid "it requires dealing with ``this``-binding issues" msgstr "" -#: ../../content/developer/howtos/web.rst:969 +#: ../../content/developer/howtos/web.rst:972 msgid "Widgets thus provide a shortcut to DOM event binding via :attr:`~odoo.Widget.events`::" msgstr "" -#: ../../content/developer/howtos/web.rst:981 +#: ../../content/developer/howtos/web.rst:984 msgid ":attr:`~odoo.Widget.events` is an object (mapping) of an event to the function or method to call when the event is triggered:" msgstr "" -#: ../../content/developer/howtos/web.rst:984 +#: ../../content/developer/howtos/web.rst:987 msgid "the key is an event name, possibly refined with a CSS selector in which case only if the event happens on a selected sub-element will the function or method run: ``click`` will handle all clicks within the widget, but ``click .my_button`` will only handle clicks in elements bearing the ``my_button`` class" msgstr "" -#: ../../content/developer/howtos/web.rst:989 +#: ../../content/developer/howtos/web.rst:992 msgid "the value is the action to perform when the event is triggered" msgstr "" -#: ../../content/developer/howtos/web.rst:991 +#: ../../content/developer/howtos/web.rst:994 msgid "It can be either a function::" msgstr "" -#: ../../content/developer/howtos/web.rst:997 +#: ../../content/developer/howtos/web.rst:1000 msgid "or the name of a method on the object (see example above)." msgstr "" -#: ../../content/developer/howtos/web.rst:999 +#: ../../content/developer/howtos/web.rst:1002 msgid "In either case, the ``this`` is the widget instance and the handler is given a single parameter, the `jQuery event object`_ for the event." msgstr "" -#: ../../content/developer/howtos/web.rst:1003 +#: ../../content/developer/howtos/web.rst:1006 msgid "Widget Events and Properties" msgstr "" -#: ../../content/developer/howtos/web.rst:1006 +#: ../../content/developer/howtos/web.rst:1009 msgid "Events" msgstr "" -#: ../../content/developer/howtos/web.rst:1008 +#: ../../content/developer/howtos/web.rst:1011 msgid "Widgets provide an event system (separate from the DOM/jQuery event system described above): a widget can fire events on itself, and other widgets (or itself) can bind themselves and listen for these events::" msgstr "" -#: ../../content/developer/howtos/web.rst:1028 +#: ../../content/developer/howtos/web.rst:1031 msgid "This widget acts as a facade, transforming user input (through DOM events) into a documentable internal event to which parent widgets can bind themselves." msgstr "" -#: ../../content/developer/howtos/web.rst:1032 +#: ../../content/developer/howtos/web.rst:1035 msgid ":func:`~odoo.Widget.trigger` takes the name of the event to trigger as its first (mandatory) argument, any further arguments are treated as event data and passed directly to listeners." msgstr "" -#: ../../content/developer/howtos/web.rst:1036 +#: ../../content/developer/howtos/web.rst:1039 msgid "We can then set up a parent event instantiating our generic widget and listening to the ``user_chose`` event using :func:`~odoo.Widget.on`::" msgstr "" -#: ../../content/developer/howtos/web.rst:1054 +#: ../../content/developer/howtos/web.rst:1057 msgid ":func:`~odoo.Widget.on` binds a function to be called when the event identified by ``event_name`` is. The ``func`` argument is the function to call and ``object`` is the object to which that function is related if it is a method. The bound function will be called with the additional arguments of :func:`~odoo.Widget.trigger` if it has any. Example::" msgstr "" -#: ../../content/developer/howtos/web.rst:1073 +#: ../../content/developer/howtos/web.rst:1076 msgid "Triggering events on an other widget is generally a bad idea. The main exception to that rule is ``odoo.web.bus`` which exists specifically to broadcasts evens in which any widget could be interested throughout the Odoo web application." msgstr "" -#: ../../content/developer/howtos/web.rst:1079 +#: ../../content/developer/howtos/web.rst:1082 msgid "Properties" msgstr "" -#: ../../content/developer/howtos/web.rst:1081 +#: ../../content/developer/howtos/web.rst:1084 msgid "Properties are very similar to normal object attributes in that they allow storing data on a widget instance, however they have the additional feature that they trigger events when set::" msgstr "" -#: ../../content/developer/howtos/web.rst:1094 +#: ../../content/developer/howtos/web.rst:1097 msgid ":func:`~odoo.Widget.set` sets the value of a property and triggers :samp:`change:{propname}` (where *propname* is the property name passed as first parameter to :func:`~odoo.Widget.set`) and ``change``" msgstr "" -#: ../../content/developer/howtos/web.rst:1097 +#: ../../content/developer/howtos/web.rst:1100 msgid ":func:`~odoo.Widget.get` retrieves the value of a property." msgstr "" -#: ../../content/developer/howtos/web.rst:1102 +#: ../../content/developer/howtos/web.rst:1105 msgid "Widget Properties and Events" msgstr "" -#: ../../content/developer/howtos/web.rst:1104 +#: ../../content/developer/howtos/web.rst:1107 msgid "Create a widget ``ColorInputWidget`` that will display 3 ````. Each of these ```` is dedicated to type a hexadecimal number from 00 to FF. When any of these ```` is modified by the user the widget must query the content of the three ````, concatenate their values to have a complete CSS color code (ie: ``#00FF00``) and put the result in a property named ``color``. Please note the jQuery ``change()`` event that you can bind on any HTML ```` element and the ``val()`` method that can query the current value of that ```` could be useful to you for this exercise." msgstr "" -#: ../../content/developer/howtos/web.rst:1114 +#: ../../content/developer/howtos/web.rst:1117 msgid "Then, modify the ``HomePage`` widget to instantiate ``ColorInputWidget`` and display it. The ``HomePage`` widget should also display an empty rectangle. That rectangle must always, at any moment, have the same background color as the color in the ``color`` property of the ``ColorInputWidget`` instance." msgstr "" -#: ../../content/developer/howtos/web.rst:1120 +#: ../../content/developer/howtos/web.rst:1123 msgid "Use QWeb to generate all HTML." msgstr "" -#: ../../content/developer/howtos/web.rst:1193 +#: ../../content/developer/howtos/web.rst:1196 msgid "Modify existing widgets and classes" msgstr "" -#: ../../content/developer/howtos/web.rst:1195 +#: ../../content/developer/howtos/web.rst:1198 msgid "The class system of the Odoo web framework allows direct modification of existing classes using the :func:`~odoo.web.Class.include` method::" msgstr "" -#: ../../content/developer/howtos/web.rst:1213 +#: ../../content/developer/howtos/web.rst:1216 msgid "This system is similar to the inheritance mechanism, except it will alter the target class in-place instead of creating a new class." msgstr "" -#: ../../content/developer/howtos/web.rst:1216 +#: ../../content/developer/howtos/web.rst:1219 msgid "In that case, ``this._super()`` will call the original implementation of a method being replaced/redefined. If the class already had sub-classes, all calls to ``this._super()`` in sub-classes will call the new implementations defined in the call to :func:`~odoo.web.Class.include`. This will also work if some instances of the class (or of any of its sub-classes) were created prior to the call to :func:`~odoo.Widget.include`." msgstr "" -#: ../../content/developer/howtos/web.rst:1224 -msgid "Translations" -msgstr "" - -#: ../../content/developer/howtos/web.rst:1226 +#: ../../content/developer/howtos/web.rst:1229 msgid "The process to translate text in Python and JavaScript code is very similar. You could have noticed these lines at the beginning of the ``petstore.js`` file::" msgstr "" -#: ../../content/developer/howtos/web.rst:1233 +#: ../../content/developer/howtos/web.rst:1236 msgid "These lines are simply used to import the translation functions in the current JavaScript module. They are used thus::" msgstr "" -#: ../../content/developer/howtos/web.rst:1238 +#: ../../content/developer/howtos/web.rst:1241 msgid "In Odoo, translations files are automatically generated by scanning the source code. All piece of code that calls a certain function are detected and their content is added to a translation file that will then be sent to the translators. In Python, the function is ``_()``. In JavaScript the function is :func:`~odoo.web._t` (and also :func:`~odoo.web._lt`)." msgstr "" -#: ../../content/developer/howtos/web.rst:1244 +#: ../../content/developer/howtos/web.rst:1247 msgid "``_t()`` will return the translation defined for the text it is given. If no translation is defined for that text, it will return the original text as-is." msgstr "" -#: ../../content/developer/howtos/web.rst:1249 +#: ../../content/developer/howtos/web.rst:1252 msgid "To inject user-provided values in translatable strings, it is recommended to use `_.str.sprintf `_ with named arguments *after* the translation::" msgstr "" -#: ../../content/developer/howtos/web.rst:1259 +#: ../../content/developer/howtos/web.rst:1262 msgid "This makes translatable strings more readable to translators, and gives them more flexibility to reorder or ignore parameters." msgstr "" -#: ../../content/developer/howtos/web.rst:1262 +#: ../../content/developer/howtos/web.rst:1265 msgid ":func:`~odoo.web._lt` (\"lazy translate\") is similar but somewhat more complex: instead of translating its parameter immediately, it returns an object which, when converted to a string, will perform the translation." msgstr "" -#: ../../content/developer/howtos/web.rst:1266 +#: ../../content/developer/howtos/web.rst:1269 msgid "It is used to define translatable terms before the translations system is initialized, for class attributes for instance (as modules are loaded before the user's language is configured and translations are downloaded)." msgstr "" -#: ../../content/developer/howtos/web.rst:1271 +#: ../../content/developer/howtos/web.rst:1274 msgid "Communication with the Odoo Server" msgstr "" -#: ../../content/developer/howtos/web.rst:1274 +#: ../../content/developer/howtos/web.rst:1277 msgid "Contacting Models" msgstr "" -#: ../../content/developer/howtos/web.rst:1276 +#: ../../content/developer/howtos/web.rst:1279 msgid "Most operations with Odoo involve communicating with *models* implementing business concern, these models will then (potentially) interact with some storage engine (usually PostgreSQL_)." msgstr "" -#: ../../content/developer/howtos/web.rst:1280 +#: ../../content/developer/howtos/web.rst:1283 msgid "Although jQuery_ provides a `$.ajax`_ function for network interactions, communicating with Odoo requires additional metadata whose setup before every call would be verbose and error-prone. As a result, Odoo web provides higher-level communication primitives." msgstr "" -#: ../../content/developer/howtos/web.rst:1285 +#: ../../content/developer/howtos/web.rst:1288 msgid "To demonstrate this, the file ``petstore.py`` already contains a small model with a sample method:" msgstr "" -#: ../../content/developer/howtos/web.rst:1300 +#: ../../content/developer/howtos/web.rst:1303 msgid "This declares a model with two fields, and a method ``my_method()`` which returns a literal dictionary." msgstr "" -#: ../../content/developer/howtos/web.rst:1303 +#: ../../content/developer/howtos/web.rst:1306 msgid "Here is a sample widget that calls ``my_method()`` and displays the result::" msgstr "" -#: ../../content/developer/howtos/web.rst:1316 +#: ../../content/developer/howtos/web.rst:1319 msgid "The class used to call Odoo models is :class:`odoo.Model`. It is instantiated with the Odoo model's name as first parameter (``oepetstore.message_of_the_day`` here)." msgstr "" -#: ../../content/developer/howtos/web.rst:1320 +#: ../../content/developer/howtos/web.rst:1323 msgid ":func:`~odoo.web.Model.call` can be used to call any (public) method of an Odoo model. It takes the following positional arguments:" msgstr "" -#: ../../content/developer/howtos/web.rst:1323 -#: ../../content/developer/reference/actions.rst:19 -#: ../../content/developer/reference/actions.rst:416 -#: ../../content/developer/reference/data.rst:221 -#: ../../content/developer/reference/views.rst:1456 -#: ../../content/developer/reference/views.rst:1490 -#: ../../content/developer/reference/views.rst:1570 -#: ../../content/developer/reference/views.rst:1680 -#: ../../content/developer/reference/views.rst:1841 -#: ../../content/developer/reference/views.rst:1977 -#: ../../content/developer/webservices/odoo.rst:1014 -#: ../../content/developer/webservices/odoo.rst:1163 +#: ../../content/developer/howtos/web.rst:1326 +#: ../../content/developer/misc/api/odoo.rst:856 +#: ../../content/developer/misc/api/odoo.rst:992 +#: ../../content/developer/reference/addons/actions.rst:19 +#: ../../content/developer/reference/addons/actions.rst:416 +#: ../../content/developer/reference/addons/data.rst:221 +#: ../../content/developer/reference/addons/views.rst:1458 +#: ../../content/developer/reference/addons/views.rst:1492 +#: ../../content/developer/reference/addons/views.rst:1572 +#: ../../content/developer/reference/addons/views.rst:1682 +#: ../../content/developer/reference/addons/views.rst:1843 +#: ../../content/developer/reference/addons/views.rst:1979 msgid "``name``" msgstr "" -#: ../../content/developer/howtos/web.rst:1324 +#: ../../content/developer/howtos/web.rst:1327 msgid "The name of the method to call, ``my_method`` here" msgstr "" -#: ../../content/developer/howtos/web.rst:1340 -#: ../../content/developer/reference/views.rst:1458 +#: ../../content/developer/howtos/web.rst:1343 +#: ../../content/developer/reference/addons/views.rst:1460 msgid "``args``" msgstr "" -#: ../../content/developer/howtos/web.rst:1326 +#: ../../content/developer/howtos/web.rst:1329 msgid "an array of `positional arguments`_ to provide to the method. Because the example has no positional argument to provide, the ``args`` parameter is not provided." msgstr "" -#: ../../content/developer/howtos/web.rst:1330 +#: ../../content/developer/howtos/web.rst:1333 msgid "Here is an other example with positional arguments:" msgstr "" -#: ../../content/developer/howtos/web.rst:1354 +#: ../../content/developer/howtos/web.rst:1357 msgid "``kwargs``" msgstr "" -#: ../../content/developer/howtos/web.rst:1343 +#: ../../content/developer/howtos/web.rst:1346 msgid "a mapping of `keyword arguments`_ to pass. The example provides a single named argument ``context``." msgstr "" -#: ../../content/developer/howtos/web.rst:1356 +#: ../../content/developer/howtos/web.rst:1359 msgid ":func:`~odoo.Widget.call` returns a deferred resolved with the value returned by the model's method as first argument." msgstr "" -#: ../../content/developer/howtos/web.rst:1360 +#: ../../content/developer/howtos/web.rst:1363 msgid "CompoundContext" msgstr "" -#: ../../content/developer/howtos/web.rst:1362 +#: ../../content/developer/howtos/web.rst:1365 msgid "The previous section used a ``context`` argument which was not explained in the method call::" msgstr "" -#: ../../content/developer/howtos/web.rst:1367 +#: ../../content/developer/howtos/web.rst:1370 msgid "The context is like a \"magic\" argument that the web client will always give to the server when calling a method. The context is a dictionary containing multiple keys. One of the most important key is the language of the user, used by the server to translate all the messages of the application. Another one is the time zone of the user, used to compute correctly dates and times if Odoo is used by people in different countries." msgstr "" -#: ../../content/developer/howtos/web.rst:1374 +#: ../../content/developer/howtos/web.rst:1377 msgid "The ``argument`` is necessary in all methods, otherwise bad things could happen (such as the application not being translated correctly). That's why, when you call a model's method, you should always provide that argument. The solution to achieve that is to use :class:`odoo.web.CompoundContext`." msgstr "" -#: ../../content/developer/howtos/web.rst:1379 +#: ../../content/developer/howtos/web.rst:1382 msgid ":class:`~odoo.web.CompoundContext` is a class used to pass the user's context (with language, time zone, etc...) to the server as well as adding new keys to the context (some models' methods use arbitrary keys added to the context). It is created by giving to its constructor any number of dictionaries or other :class:`~odoo.web.CompoundContext` instances. It will merge all those contexts before sending them to the server." msgstr "" -#: ../../content/developer/howtos/web.rst:1397 +#: ../../content/developer/howtos/web.rst:1400 msgid "You can see the dictionary in the argument ``context`` contains some keys that are related to the configuration of the current user in Odoo plus the ``new_key`` key that was added when instantiating :class:`~odoo.web.CompoundContext`." msgstr "" -#: ../../content/developer/howtos/web.rst:1403 +#: ../../content/developer/howtos/web.rst:1406 msgid "Queries" msgstr "" -#: ../../content/developer/howtos/web.rst:1405 +#: ../../content/developer/howtos/web.rst:1408 msgid "While :func:`~odoo.Model.call` is sufficient for any interaction with Odoo models, Odoo Web provides a helper for simpler and clearer querying of models (fetching of records based on various conditions): :func:`~odoo.Model.query` which acts as a shortcut for the common combination of :py:meth:`~odoo.models.Model.search` and ::py:meth:`~odoo.models.Model.read`. It provides a clearer syntax to search and read models::" msgstr "" -#: ../../content/developer/howtos/web.rst:1420 +#: ../../content/developer/howtos/web.rst:1423 msgid "versus::" msgstr "" -#: ../../content/developer/howtos/web.rst:1430 +#: ../../content/developer/howtos/web.rst:1433 msgid ":func:`~odoo.web.Model.query` takes an optional list of fields as parameter (if no field is provided, all fields of the model are fetched). It returns a :class:`odoo.web.Query` which can be further customized before being executed" msgstr "" -#: ../../content/developer/howtos/web.rst:1434 +#: ../../content/developer/howtos/web.rst:1437 msgid ":class:`~odoo.web.Query` represents the query being built. It is immutable, methods to customize the query actually return a modified copy, so it's possible to use the original and the new version side-by-side. See :class:`~odoo.web.Query` for its customization options." msgstr "" -#: ../../content/developer/howtos/web.rst:1439 +#: ../../content/developer/howtos/web.rst:1442 msgid "When the query is set up as desired, simply call :func:`~odoo.web.Query.all` to execute it and return a deferred to its result. The result is the same as :py:meth:`~odoo.models.Model.read`'s, an array of dictionaries where each dictionary is a requested record, with each requested field a dictionary key." msgstr "" -#: ../../content/developer/howtos/web.rst:1446 +#: ../../content/developer/howtos/web.rst:1449 msgid "Exercises" msgstr "" -#: ../../content/developer/howtos/web.rst:1448 +#: ../../content/developer/howtos/web.rst:1451 msgid "Message of the Day" msgstr "" -#: ../../content/developer/howtos/web.rst:1450 +#: ../../content/developer/howtos/web.rst:1453 msgid "Create a ``MessageOfTheDay`` widget displaying the last record of the ``oepetstore.message_of_the_day`` model. The widget should fetch its record as soon as it is displayed." msgstr "" -#: ../../content/developer/howtos/web.rst:1454 +#: ../../content/developer/howtos/web.rst:1457 msgid "Display the widget in the Pet Store home page." msgstr "" -#: ../../content/developer/howtos/web.rst:1514 +#: ../../content/developer/howtos/web.rst:1517 msgid "Pet Toys List" msgstr "" -#: ../../content/developer/howtos/web.rst:1516 +#: ../../content/developer/howtos/web.rst:1519 msgid "Create a ``PetToysList`` widget displaying 5 toys (using their name and their images)." msgstr "" -#: ../../content/developer/howtos/web.rst:1519 +#: ../../content/developer/howtos/web.rst:1522 msgid "The pet toys are not stored in a new model, instead they're stored in ``product.product`` using a special category *Pet Toys*. You can see the pre-generated toys and add new ones by going to :menuselection:`Pet Store --> Pet Store --> Pet Toys`. You will probably need to explore ``product.product`` to create the right domain to select just pet toys." msgstr "" -#: ../../content/developer/howtos/web.rst:1526 +#: ../../content/developer/howtos/web.rst:1529 msgid "In Odoo, images are generally stored in regular fields encoded as base64_, HTML supports displaying images straight from base64 with :samp:``" msgstr "" -#: ../../content/developer/howtos/web.rst:1530 +#: ../../content/developer/howtos/web.rst:1533 msgid "The ``PetToysList`` widget should be displayed on the home page on the right of the ``MessageOfTheDay`` widget. You will need to make some layout with CSS to achieve this." msgstr "" -#: ../../content/developer/howtos/web.rst:1650 +#: ../../content/developer/howtos/web.rst:1653 msgid "Existing web components" msgstr "" -#: ../../content/developer/howtos/web.rst:1653 +#: ../../content/developer/howtos/web.rst:1656 msgid "The Action Manager" msgstr "" -#: ../../content/developer/howtos/web.rst:1655 +#: ../../content/developer/howtos/web.rst:1658 msgid "In Odoo, many operations start from an :ref:`action `: opening a menu item (to a view), printing a report, ..." msgstr "" -#: ../../content/developer/howtos/web.rst:1658 +#: ../../content/developer/howtos/web.rst:1661 msgid "Actions are pieces of data describing how a client should react to the activation of a piece of content. Actions can be stored (and read through a model) or they can be generated on-the fly (locally to the client by javascript code, or remotely by a method of a model)." msgstr "" -#: ../../content/developer/howtos/web.rst:1663 +#: ../../content/developer/howtos/web.rst:1666 msgid "In Odoo Web, the component responsible for handling and reacting to these actions is the *Action Manager*." msgstr "" -#: ../../content/developer/howtos/web.rst:1667 +#: ../../content/developer/howtos/web.rst:1670 msgid "Using the Action Manager" msgstr "" -#: ../../content/developer/howtos/web.rst:1669 +#: ../../content/developer/howtos/web.rst:1672 msgid "The action manager can be invoked explicitly from javascript code by creating a dictionary describing :ref:`an action ` of the right type, and calling an action manager instance with it." msgstr "" -#: ../../content/developer/howtos/web.rst:1673 +#: ../../content/developer/howtos/web.rst:1676 msgid ":func:`~odoo.Widget.do_action` is a shortcut of :class:`~odoo.Widget` looking up the \"current\" action manager and executing the action::" msgstr "" -#: ../../content/developer/howtos/web.rst:1689 +#: ../../content/developer/howtos/web.rst:1692 msgid "The most common action ``type`` is ``ir.actions.act_window`` which provides views to a model (displays a model in various manners), its most common attributes are:" msgstr "" -#: ../../content/developer/howtos/web.rst:1693 -#: ../../content/developer/reference/actions.rst:74 +#: ../../content/developer/howtos/web.rst:1696 +#: ../../content/developer/reference/addons/actions.rst:74 msgid "``res_model``" msgstr "" -#: ../../content/developer/howtos/web.rst:1694 +#: ../../content/developer/howtos/web.rst:1697 msgid "The model to display in views" msgstr "" -#: ../../content/developer/howtos/web.rst:1695 -#: ../../content/developer/reference/actions.rst:86 +#: ../../content/developer/howtos/web.rst:1698 +#: ../../content/developer/reference/addons/actions.rst:86 msgid "``res_id`` (optional)" msgstr "" -#: ../../content/developer/howtos/web.rst:1696 +#: ../../content/developer/howtos/web.rst:1699 msgid "For form views, a preselected record in ``res_model``" msgstr "" -#: ../../content/developer/howtos/web.rst:1701 -#: ../../content/developer/reference/actions.rst:83 +#: ../../content/developer/howtos/web.rst:1704 +#: ../../content/developer/reference/addons/actions.rst:83 msgid "``views``" msgstr "" -#: ../../content/developer/howtos/web.rst:1698 +#: ../../content/developer/howtos/web.rst:1701 msgid "Lists the views available through the action. A list of ``[view_id, view_type]``, ``view_id`` can either be the database identifier of a view of the right type, or ``false`` to use the view by default for the specified type. View types can not be present multiple times. The action will open the first view of the list by default." msgstr "" -#: ../../content/developer/howtos/web.rst:1704 -#: ../../content/developer/reference/actions.rst:197 -#: ../../content/developer/webservices/upgrade.rst:537 +#: ../../content/developer/howtos/web.rst:1707 +#: ../../content/developer/reference/addons/actions.rst:197 msgid "``target``" msgstr "" -#: ../../content/developer/howtos/web.rst:1704 +#: ../../content/developer/howtos/web.rst:1707 msgid "Either ``current`` (the default) which replaces the \"content\" section of the web client by the action, or ``new`` to open the action in a dialog box." msgstr "" -#: ../../content/developer/howtos/web.rst:1707 +#: ../../content/developer/howtos/web.rst:1710 msgid "Additional context data to use within the action." msgstr "" -#: ../../content/developer/howtos/web.rst:1709 +#: ../../content/developer/howtos/web.rst:1712 msgid "Jump to Product" msgstr "" -#: ../../content/developer/howtos/web.rst:1711 +#: ../../content/developer/howtos/web.rst:1714 msgid "Modify the ``PetToysList`` component so clicking on a toy replaces the homepage by the toy's form view." msgstr "" -#: ../../content/developer/howtos/web.rst:1758 +#: ../../content/developer/howtos/web.rst:1761 msgid "Client Actions" msgstr "" -#: ../../content/developer/howtos/web.rst:1760 +#: ../../content/developer/howtos/web.rst:1763 msgid "Throughout this guide, we used a simple ``HomePage`` widget which the web client automatically starts when we select the right menu item. But how did the Odoo web know to start this widget? Because the widget is registered as a *client action*." msgstr "" -#: ../../content/developer/howtos/web.rst:1765 +#: ../../content/developer/howtos/web.rst:1768 msgid "A client action is (as its name implies) an action type defined almost entirely in the client, in javascript for Odoo web. The server simply sends an action tag (an arbitrary name), and optionally adds a few parameters, but beyond that *everything* is handled by custom client code." msgstr "" -#: ../../content/developer/howtos/web.rst:1770 +#: ../../content/developer/howtos/web.rst:1773 msgid "Our widget is registered as the handler for the client action through this::" msgstr "" -#: ../../content/developer/howtos/web.rst:1775 +#: ../../content/developer/howtos/web.rst:1778 msgid "``instance.web.client_actions`` is a :class:`~odoo.web.Registry` in which the action manager looks up client action handlers when it needs to execute one. The first parameter of :class:`~odoo.web.Registry.add` is the name (tag) of the client action, and the second parameter is the path to the widget from the Odoo web client root." msgstr "" -#: ../../content/developer/howtos/web.rst:1781 +#: ../../content/developer/howtos/web.rst:1784 msgid "When a client action must be executed, the action manager looks up its tag in the registry, walks the specified path and displays the widget it finds at the end." msgstr "" -#: ../../content/developer/howtos/web.rst:1785 -msgid "a client action handler can also be a regular function, in whch case it'll be called and its result (if any) will be interpreted as the next action to execute." +#: ../../content/developer/howtos/web.rst:1788 +msgid "a client action handler can also be a regular function, in which case it'll be called and its result (if any) will be interpreted as the next action to execute." msgstr "" -#: ../../content/developer/howtos/web.rst:1789 +#: ../../content/developer/howtos/web.rst:1792 msgid "On the server side, we had simply defined an ``ir.actions.client`` action:" msgstr "" -#: ../../content/developer/howtos/web.rst:1797 +#: ../../content/developer/howtos/web.rst:1800 msgid "and a menu opening the action:" msgstr "" -#: ../../content/developer/howtos/web.rst:1805 +#: ../../content/developer/howtos/web.rst:1808 msgid "Architecture of the Views" msgstr "" -#: ../../content/developer/howtos/web.rst:1807 +#: ../../content/developer/howtos/web.rst:1810 msgid "Much of Odoo web's usefulness (and complexity) resides in views. Each view type is a way of displaying a model in the client." msgstr "" -#: ../../content/developer/howtos/web.rst:1811 +#: ../../content/developer/howtos/web.rst:1814 msgid "The View Manager" msgstr "" -#: ../../content/developer/howtos/web.rst:1813 +#: ../../content/developer/howtos/web.rst:1816 msgid "When an ``ActionManager`` instance receive an action of type ``ir.actions.act_window``, it delegates the synchronization and handling of the views themselves to a *view manager*, which will then set up one or multiple views depending on the original action's requirements:" msgstr "" -#: ../../content/developer/howtos/web.rst:1823 +#: ../../content/developer/howtos/web.rst:1826 msgid "The Views" msgstr "" -#: ../../content/developer/howtos/web.rst:1825 +#: ../../content/developer/howtos/web.rst:1828 msgid "Most :ref:`Odoo views ` are implemented through a subclass of :class:`odoo.web.View` which provides a bit of generic basic structure for handling events and displaying model information." msgstr "" -#: ../../content/developer/howtos/web.rst:1829 +#: ../../content/developer/howtos/web.rst:1832 msgid "The *search view* is considered a view type by the main Odoo framework, but handled separately by the web client (as it's a more permanent fixture and can interact with other views, which regular views don't do)." msgstr "" -#: ../../content/developer/howtos/web.rst:1833 +#: ../../content/developer/howtos/web.rst:1836 msgid "A view is responsible for loading its own description XML (using :py:class:`~odoo.models.Model.fields_view_get`) and any other data source it needs. To that purpose, views are provided with an optional view identifier set as the :attr:`~odoo.web.View.view_id` attribute." msgstr "" -#: ../../content/developer/howtos/web.rst:1838 +#: ../../content/developer/howtos/web.rst:1841 msgid "Views are also provided with a :class:`~odoo.web.DataSet` instance which holds most necessary model information (the model name and possibly various record ids)." msgstr "" -#: ../../content/developer/howtos/web.rst:1842 +#: ../../content/developer/howtos/web.rst:1845 msgid "Views may also want to handle search queries by overriding :func:`~odoo.web.View.do_search`, and updating their :class:`~odoo.web.DataSet` as necessary." msgstr "" -#: ../../content/developer/howtos/web.rst:1847 +#: ../../content/developer/howtos/web.rst:1850 msgid "The Form View Fields" msgstr "" -#: ../../content/developer/howtos/web.rst:1849 +#: ../../content/developer/howtos/web.rst:1852 msgid "A common need is the extension of the web form view to add new ways of displaying fields." msgstr "" -#: ../../content/developer/howtos/web.rst:1852 +#: ../../content/developer/howtos/web.rst:1855 msgid "All built-in fields have a default display implementation, a new form widget may be necessary to correctly interact with a new field type (e.g. a :term:`GIS` field) or to provide new representations and ways to interact with existing field types (e.g. validate :py:class:`~odoo.fields.Char` fields which should contain email addresses and display them as email links)." msgstr "" -#: ../../content/developer/howtos/web.rst:1859 +#: ../../content/developer/howtos/web.rst:1862 msgid "To explicitly specify which form widget should be used to display a field, simply use the ``widget`` attribute in the view's XML description:" msgstr "" -#: ../../content/developer/howtos/web.rst:1868 +#: ../../content/developer/howtos/web.rst:1871 msgid "the same widget is used in both \"view\" (read-only) and \"edit\" modes of a form view, it's not possible to use a widget in one and an other widget in the other" msgstr "" -#: ../../content/developer/howtos/web.rst:1871 +#: ../../content/developer/howtos/web.rst:1874 msgid "and a given field (name) can not be used multiple times in the same form" msgstr "" -#: ../../content/developer/howtos/web.rst:1872 +#: ../../content/developer/howtos/web.rst:1875 msgid "a widget may ignore the current mode of the form view and remain the same in both view and edit modes" msgstr "" -#: ../../content/developer/howtos/web.rst:1875 +#: ../../content/developer/howtos/web.rst:1878 msgid "most of this should probably move to an advanced form view guide" msgstr "" -#: ../../content/developer/howtos/web.rst:1877 +#: ../../content/developer/howtos/web.rst:1880 msgid "Fields are instantiated by the form view after it has read its XML description and constructed the corresponding HTML representing that description. After that, the form view will communicate with the field objects using some methods. These methods are defined by the ``FieldInterface`` interface. Almost all fields inherit the ``AbstractField`` abstract class. That class defines some default mechanisms that need to be implemented by most fields." msgstr "" -#: ../../content/developer/howtos/web.rst:1885 +#: ../../content/developer/howtos/web.rst:1888 msgid "Here are some of the responsibilities of a field class:" msgstr "" -#: ../../content/developer/howtos/web.rst:1887 +#: ../../content/developer/howtos/web.rst:1890 msgid "The field class must display and allow the user to edit the value of the field." msgstr "" -#: ../../content/developer/howtos/web.rst:1888 +#: ../../content/developer/howtos/web.rst:1891 msgid "It must correctly implement the 3 field attributes available in all fields of Odoo. The ``AbstractField`` class already implements an algorithm that dynamically calculates the value of these attributes (they can change at any moment because their value change according to the value of other fields). Their values are stored in *Widget Properties* (the widget properties were explained earlier in this guide). It is the responsibility of each field class to check these widget properties and dynamically adapt depending of their values. Here is a description of each of these attributes:" msgstr "" -#: ../../content/developer/howtos/web.rst:1898 +#: ../../content/developer/howtos/web.rst:1901 msgid "``required``: The field must have a value before saving. If ``required`` is ``true`` and the field doesn't have a value, the method ``is_valid()`` of the field must return ``false``." msgstr "" -#: ../../content/developer/howtos/web.rst:1901 +#: ../../content/developer/howtos/web.rst:1904 msgid "``invisible``: When this is ``true``, the field must be invisible. The ``AbstractField`` class already has a basic implementation of this behavior that fits most fields." msgstr "" -#: ../../content/developer/howtos/web.rst:1904 +#: ../../content/developer/howtos/web.rst:1907 msgid "``readonly``: When ``true``, the field must not be editable by the user. Most fields in Odoo have a completely different behavior depending on the value of ``readonly``. As example, the ``FieldChar`` displays an HTML ```` when it is editable and simply displays the text when it is read-only. This also means it has much more code it would need to implement only one behavior, but this is necessary to ensure a good user experience." msgstr "" -#: ../../content/developer/howtos/web.rst:1912 +#: ../../content/developer/howtos/web.rst:1915 msgid "Fields have two methods, ``set_value()`` and ``get_value()``, which are called by the form view to give it the value to display and get back the new value entered by the user. These methods must be able to handle the value as given by the Odoo server when a ``read()`` is performed on a model and give back a valid value for a ``write()``. Remember that the JavaScript/Python data types used to represent the values given by ``read()`` and given to ``write()`` is not necessarily the same in Odoo. As example, when you read a many2one, it is always a tuple whose first value is the id of the pointed record and the second one is the name get (ie: ``(15, \"Agrolait\")``). But when you write a many2one it must be a single integer, not a tuple anymore. ``AbstractField`` has a default implementation of these methods that works well for simple data type and set a widget property named ``value``." msgstr "" -#: ../../content/developer/howtos/web.rst:1926 +#: ../../content/developer/howtos/web.rst:1929 msgid "Please note that, to better understand how to implement fields, you are strongly encouraged to look at the definition of the ``FieldInterface`` interface and the ``AbstractField`` class directly in the code of the Odoo web client." msgstr "" -#: ../../content/developer/howtos/web.rst:1932 +#: ../../content/developer/howtos/web.rst:1935 msgid "Creating a New Type of Field" msgstr "" -#: ../../content/developer/howtos/web.rst:1934 +#: ../../content/developer/howtos/web.rst:1937 msgid "In this part we will explain how to create a new type of field. The example here will be to re-implement the ``FieldChar`` class and progressively explain each part." msgstr "" -#: ../../content/developer/howtos/web.rst:1939 +#: ../../content/developer/howtos/web.rst:1942 msgid "Simple Read-Only Field" msgstr "" -#: ../../content/developer/howtos/web.rst:1941 +#: ../../content/developer/howtos/web.rst:1944 msgid "Here is a first implementation that will only display text. The user will not be able to modify the content of the field." msgstr "" -#: ../../content/developer/howtos/web.rst:1958 +#: ../../content/developer/howtos/web.rst:1961 msgid "In this example, we declare a class named ``FieldChar2`` inheriting from ``AbstractField``. We also register this class in the registry ``instance.web.form.widgets`` under the key ``char2``. That will allow us to use this new field in any form view by specifying ``widget=\"char2\"`` in the ```` tag in the XML declaration of the view." msgstr "" -#: ../../content/developer/howtos/web.rst:1964 +#: ../../content/developer/howtos/web.rst:1967 msgid "In this example, we define a single method: ``render_value()``. All it does is display the widget property ``value``. Those are two tools defined by the ``AbstractField`` class. As explained before, the form view will call the method ``set_value()`` of the field to set the value to display. This method already has a default implementation in ``AbstractField`` which simply sets the widget property ``value``. ``AbstractField`` also watch the ``change:value`` event on itself and calls the ``render_value()`` when it occurs. So, ``render_value()`` is a convenience method to implement in child classes to perform some operation each time the value of the field changes." msgstr "" -#: ../../content/developer/howtos/web.rst:1974 +#: ../../content/developer/howtos/web.rst:1977 msgid "In the ``init()`` method, we also define the default value of the field if none is specified by the form view (here we assume the default value of a ``char`` field should be an empty string)." msgstr "" -#: ../../content/developer/howtos/web.rst:1979 +#: ../../content/developer/howtos/web.rst:1982 msgid "Read-Write Field" msgstr "" -#: ../../content/developer/howtos/web.rst:1981 +#: ../../content/developer/howtos/web.rst:1984 msgid "Read-only fields, which only display content and don't allow the user to modify it can be useful, but most fields in Odoo also allow editing. This makes the field classes more complicated, mostly because fields are supposed to handle both editable and non-editable mode, those modes are often completely different (for design and usability purpose) and the fields must be able to switch between modes at any moment." msgstr "" -#: ../../content/developer/howtos/web.rst:1988 +#: ../../content/developer/howtos/web.rst:1991 msgid "To know in which mode the current field should be, the ``AbstractField`` class sets a widget property named ``effective_readonly``. The field should watch for changes in that widget property and display the correct mode accordingly. Example::" msgstr "" -#: ../../content/developer/howtos/web.rst:2036 +#: ../../content/developer/howtos/web.rst:2039 msgid "In the ``start()`` method (which is called immediately after a widget has been appended to the DOM), we bind on the event ``change:effective_readonly``. That allows us to redisplay the field each time the widget property ``effective_readonly`` changes. This event handler will call ``display_field()``, which is also called directly in ``start()``. This ``display_field()`` was created specifically for this field, it's not a method defined in ``AbstractField`` or any other class. We can use this method to display the content of the field depending on the current mode." msgstr "" -#: ../../content/developer/howtos/web.rst:2045 +#: ../../content/developer/howtos/web.rst:2048 msgid "From now on the conception of this field is typical, except there is a lot of verifications to know the state of the ``effective_readonly`` property:" msgstr "" -#: ../../content/developer/howtos/web.rst:2048 +#: ../../content/developer/howtos/web.rst:2051 msgid "In the QWeb template used to display the content of the widget, it displays an ```` if we are in read-write mode and nothing in particular in read-only mode." msgstr "" -#: ../../content/developer/howtos/web.rst:2051 +#: ../../content/developer/howtos/web.rst:2054 msgid "In the ``display_field()`` method, we have to bind on the ``change`` event of the ```` to know when the user has changed the value. When it happens, we call the ``internal_set_value()`` method with the new value of the field. This is a convenience method provided by the ``AbstractField`` class. That method will set a new value in the ``value`` property but will not trigger a call to ``render_value()`` (which is not necessary since the ```` already contains the correct value)." msgstr "" -#: ../../content/developer/howtos/web.rst:2059 +#: ../../content/developer/howtos/web.rst:2062 msgid "In ``render_value()``, we use a completely different code to display the value of the field depending if we are in read-only or in read-write mode." msgstr "" -#: ../../content/developer/howtos/web.rst:2062 +#: ../../content/developer/howtos/web.rst:2065 msgid "Create a Color Field" msgstr "" -#: ../../content/developer/howtos/web.rst:2064 +#: ../../content/developer/howtos/web.rst:2067 msgid "Create a ``FieldColor`` class. The value of this field should be a string containing a color code like those used in CSS (example: ``#FF0000`` for red). In read-only mode, this color field should display a little block whose color corresponds to the value of the field. In read-write mode, you should display an ````. That type of ```` is an HTML5 component that doesn't work in all browsers but works well in Google Chrome. So it's OK to use as an exercise." msgstr "" -#: ../../content/developer/howtos/web.rst:2072 +#: ../../content/developer/howtos/web.rst:2075 msgid "You can use that widget in the form view of the ``message_of_the_day`` model for its field named ``color``. As a bonus, you can change the ``MessageOfTheDay`` widget created in the previous part of this guide to display the message of the day with the background color indicated in the ``color`` field." msgstr "" -#: ../../content/developer/howtos/web.rst:2137 +#: ../../content/developer/howtos/web.rst:2140 msgid "The Form View Custom Widgets" msgstr "" -#: ../../content/developer/howtos/web.rst:2139 +#: ../../content/developer/howtos/web.rst:2142 msgid "Form fields are used to edit a single field, and are intrinsically linked to a field. Because this may be limiting, it is also possible to create *form widgets* which are not so restricted and have less ties to a specific lifecycle." msgstr "" -#: ../../content/developer/howtos/web.rst:2144 +#: ../../content/developer/howtos/web.rst:2147 msgid "Custom form widgets can be added to a form view through the ``widget`` tag:" msgstr "" -#: ../../content/developer/howtos/web.rst:2150 +#: ../../content/developer/howtos/web.rst:2153 msgid "This type of widget will simply be created by the form view during the creation of the HTML according to the XML definition. They have properties in common with the fields (like the ``effective_readonly`` property) but they are not assigned a precise field. And so they don't have methods like ``get_value()`` and ``set_value()``. They must inherit from the ``FormWidget`` abstract class." msgstr "" -#: ../../content/developer/howtos/web.rst:2157 +#: ../../content/developer/howtos/web.rst:2160 msgid "Form widgets can interact with form fields by listening for their changes and fetching or altering their values. They can access form fields through their :attr:`~odoo.web.form.FormWidget.field_manager` attribute::" msgstr "" -#: ../../content/developer/howtos/web.rst:2177 +#: ../../content/developer/howtos/web.rst:2180 msgid ":attr:`~odoo.web.form.FormWidget` is generally the :class:`~odoo.web.form.FormView` itself, but features used from it should be limited to those defined by :class:`~odoo.web.form.FieldManagerMixin`, the most useful being:" msgstr "" -#: ../../content/developer/howtos/web.rst:2182 +#: ../../content/developer/howtos/web.rst:2185 msgid ":func:`~odoo.web.form.FieldManagerMixin.get_field_value(field_name)` which returns the value of a field." msgstr "" -#: ../../content/developer/howtos/web.rst:2184 +#: ../../content/developer/howtos/web.rst:2187 msgid ":func:`~odoo.web.form.FieldManagerMixin.set_values(values)` sets multiple field values, takes a mapping of ``{field_name: value_to_set}``" msgstr "" -#: ../../content/developer/howtos/web.rst:2186 +#: ../../content/developer/howtos/web.rst:2189 msgid "An event :samp:`field_changed:{field_name}` is triggered any time the value of the field called ``field_name`` is changed" msgstr "" -#: ../../content/developer/howtos/web.rst:2189 +#: ../../content/developer/howtos/web.rst:2192 msgid "Show Coordinates on Google Map" msgstr "" -#: ../../content/developer/howtos/web.rst:2191 +#: ../../content/developer/howtos/web.rst:2194 msgid "Add two fields to ``product.product`` storing a latitude and a longitude, then create a new form widget to display the latitude and longitude of a product's origin on a map" msgstr "" -#: ../../content/developer/howtos/web.rst:2195 +#: ../../content/developer/howtos/web.rst:2198 msgid "To display the map, use Google Map's embedding:" msgstr "" -#: ../../content/developer/howtos/web.rst:2202 +#: ../../content/developer/howtos/web.rst:2205 msgid "where ``XXX`` should be replaced by the latitude and ``YYY`` by the longitude." msgstr "" -#: ../../content/developer/howtos/web.rst:2205 +#: ../../content/developer/howtos/web.rst:2208 msgid "Display the two position fields and a map widget using them in a new notebook page of the product's form view." msgstr "" -#: ../../content/developer/howtos/web.rst:2237 +#: ../../content/developer/howtos/web.rst:2240 msgid "Get the Current Coordinate" msgstr "" -#: ../../content/developer/howtos/web.rst:2239 +#: ../../content/developer/howtos/web.rst:2242 msgid "Add a button resetting the product's coordinates to the location of the user, you can get these coordinates using the `javascript geolocation API`_." msgstr "" -#: ../../content/developer/howtos/web.rst:2243 +#: ../../content/developer/howtos/web.rst:2246 msgid "Now we would like to display an additional button to automatically set the coordinates to the location of the current user." msgstr "" -#: ../../content/developer/howtos/web.rst:2246 +#: ../../content/developer/howtos/web.rst:2249 msgid "To get the coordinates of the user, an easy way is to use the geolocation JavaScript API. `See the online documentation to know how to use it`_." msgstr "" -#: ../../content/developer/howtos/web.rst:2251 +#: ../../content/developer/howtos/web.rst:2254 msgid "Please also note that the user should not be able to click on that button when the form view is in read-only mode. So, this custom widget should handle correctly the ``effective_readonly`` property just like any field. One way to do this would be to make the button disappear when ``effective_readonly`` is true." msgstr "" -#: ../../content/developer/howtos/web.rst:2302 +#: ../../content/developer/howtos/web.rst:2305 msgid "as a separate concept from instances. In many languages classes are full-fledged objects and themselves instance (of metaclasses) but there remains two fairly separate hierarchies between classes and instances" msgstr "" -#: ../../content/developer/howtos/web.rst:2306 +#: ../../content/developer/howtos/web.rst:2309 msgid "as well as papering over cross-browser differences, although this has become less necessary over time" msgstr "" @@ -4536,10 +10483,6 @@ msgstr "" msgid "In this case we're using demonstration data because an actual user of the system would want to input or import their own teachers list, this list is only useful for testing." msgstr "" -#: ../../content/developer/howtos/website.rst:234 -msgid "Accessing the data" -msgstr "" - #: ../../content/developer/howtos/website.rst:236 msgid "The last step is to alter model and template to use our demonstration data:" msgstr "" @@ -4888,15033 +10831,17060 @@ msgstr "" msgid "With this, the *Product Categories* sidebar will automatically be enabled when the *Academy* module is installed." msgstr "" -#: ../../content/developer/reference.rst:5 -msgid "Reference" +#: ../../content/developer/misc.rst:5 +msgid "Misc" msgstr "" -#: ../../content/developer/reference/actions.rst:6 -#: ../../content/developer/reference/iot.rst:138 -msgid "Actions" -msgstr "" - -#: ../../content/developer/reference/actions.rst:8 -msgid "Actions define the behavior of the system in response to user actions: login, action button, selection of an invoice, ..." -msgstr "" - -#: ../../content/developer/reference/actions.rst:11 -msgid "Actions can be stored in the database or returned directly as dictionaries in e.g. button methods. All actions share two mandatory attributes:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:15 -#: ../../content/developer/reference/data.rst:135 -#: ../../content/developer/reference/views.rst:1120 -#: ../../content/developer/reference/views.rst:1156 -#: ../../content/developer/reference/views.rst:1454 -#: ../../content/developer/reference/views.rst:1742 -msgid "``type``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:15 -msgid "the category of the current action, determines which fields may be used and how the action is interpreted" -msgstr "" - -#: ../../content/developer/reference/actions.rst:18 -msgid "short user-readable description of the action, may be displayed in the client's interface" -msgstr "" - -#: ../../content/developer/reference/actions.rst:21 -msgid "A client can get actions in 4 forms:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:23 -msgid "``False``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:24 -msgid "if any action dialog is currently open, close it" -msgstr "" - -#: ../../content/developer/reference/actions.rst:26 -msgid "A string" -msgstr "" - -#: ../../content/developer/reference/actions.rst:26 -msgid "if a :ref:`client action ` matches, interpret as a client action's tag, otherwise treat as a number" -msgstr "" - -#: ../../content/developer/reference/actions.rst:29 -msgid "A number" -msgstr "" - -#: ../../content/developer/reference/actions.rst:29 -msgid "read the corresponding action record from the database, may be a database identifier or an :term:`external id`" -msgstr "" - -#: ../../content/developer/reference/actions.rst:32 -msgid "A dictionary" -msgstr "" - -#: ../../content/developer/reference/actions.rst:32 -msgid "treat as a client action descriptor and execute" -msgstr "" - -#: ../../content/developer/reference/actions.rst:37 -msgid "Bindings" -msgstr "" - -#: ../../content/developer/reference/actions.rst:39 -msgid "Aside from their two mandatory attributes, all actions also share *optional* attributes used to present an action in an arbitrary model's contextual menu:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:45 -msgid "``binding_model_id``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:43 -msgid "specifies which model the action is bound to" -msgstr "" - -#: ../../content/developer/reference/actions.rst:45 -msgid "For Server Actions, use ``model_id``." -msgstr "" - -#: ../../content/developer/reference/actions.rst:55 -msgid "``binding_type``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:48 -msgid "specifies the type of binding, which is mostly which contextual menu the action will appear under" -msgstr "" - -#: ../../content/developer/reference/actions.rst:52 -msgid "``action`` (default)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:52 -msgid "Specifies that the action will appear in the :menuselection:`Action` contextual menu of the bound model." -msgstr "" - -#: ../../content/developer/reference/actions.rst:55 -msgid "``report``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:55 -msgid "Specifies that the action will appear in the :menuselection:`Print` contextual menu of the bound model." -msgstr "" - -#: ../../content/developer/reference/actions.rst:60 -msgid "``binding_view_types``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:58 -msgid "a comma-separated list of view types for which the action appears in the contextual menu, mostly \"list\" and / or \"form\". Defaults to ``list,form`` (both list and form )" -msgstr "" - -#: ../../content/developer/reference/actions.rst:65 -msgid "Window Actions (``ir.actions.act_window``)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:67 -msgid "The most common action type, used to present visualisations of a model through :ref:`views `: a window action defines a set of view types (and possibly specific views) for a model (and possibly specific record of the model)." -msgstr "" - -#: ../../content/developer/reference/actions.rst:72 -msgid "Its fields are:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:75 -msgid "model to present views for" -msgstr "" - -#: ../../content/developer/reference/actions.rst:77 -msgid "a list of ``(view_id, view_type)`` pairs. The second element of each pair is the category of the view (tree, form, graph, ...) and the first is an optional database id (or ``False``). If no id is provided, the client should fetch the default view of the specified type for the requested model (this is automatically done by :meth:`~odoo.models.Model.fields_view_get`). The first type of the list is the default view type and will be open by default when the action is executed. Each view type should be present at most once in the list" -msgstr "" - -#: ../../content/developer/reference/actions.rst:86 -msgid "if the default view is ``form``, specifies the record to load (otherwise a new record should be created)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:90 -msgid "``search_view_id`` (optional)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:89 -msgid "``(id, name)`` pair, ``id`` is the database identifier of a specific search view to load for the action. Defaults to fetching the default search view for the model" -msgstr "" - -#: ../../content/developer/reference/actions.rst:95 -#: ../../content/developer/reference/actions.rst:393 -msgid "``target`` (optional)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:93 -msgid "whether the views should be open in the main content area (``current``), in full screen mode (``fullscreen``) or in a dialog/popup (``new``). Use ``main`` instead of ``current`` to clear the breadcrumbs. Defaults to ``current``." -msgstr "" - -#: ../../content/developer/reference/actions.rst:97 -#: ../../content/developer/reference/actions.rst:222 -msgid "``context`` (optional)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:98 -msgid "additional context data to pass to the views" -msgstr "" - -#: ../../content/developer/reference/actions.rst:99 -#: ../../content/developer/reference/views.rst:624 -#: ../../content/developer/reference/views.rst:1891 -msgid "``domain`` (optional)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:100 -msgid "filtering domain to implicitly add to all view search queries" -msgstr "" - -#: ../../content/developer/reference/actions.rst:103 -msgid "``limit`` (optional)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:102 -msgid "number of records to display in lists by default. Defaults to 80 in the web client" -msgstr "" - -#: ../../content/developer/reference/actions.rst:105 -msgid "For instance, to open customers (partner with the ``customer`` flag set) with list and form views::" -msgstr "" - -#: ../../content/developer/reference/actions.rst:115 -msgid "Or to open the form view of a specific product (obtained separately) in a new dialog::" -msgstr "" - -#: ../../content/developer/reference/actions.rst:126 -msgid "In-database window actions have a few different fields which should be ignored by clients, mostly to use in composing the ``views`` list:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:130 -msgid "``view_mode`` (default= ``tree,form`` )" -msgstr "" - -#: ../../content/developer/reference/actions.rst:130 -msgid "comma-separated list of view types as a string (/!\\\\ No spaces /!\\\\). All of these types will be present in the generated ``views`` list (with at least a ``False`` view_id)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:148 -#: ../../content/developer/webservices/odoo.rst:1025 -msgid "``view_ids``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:133 -msgid "M2M\\ [#notquitem2m]_ to view objects, defines the initial content of ``views``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:136 -msgid "Act_window views can also be defined cleanly through ``ir.actions.act_window.view``." -msgstr "" - -#: ../../content/developer/reference/actions.rst:138 -msgid "If you plan to allow multiple views for your model, prefer using ir.actions.act_window.view instead of the action ``view_ids``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:153 -msgid "``view_id``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:151 -msgid "specific view added to the ``views`` list in case its type is part of the ``view_mode`` list and not already filled by one of the views in ``view_ids``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:155 -msgid "These are mostly used when defining actions from :ref:`reference/data`:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:166 -msgid "will use the \"my_specific_view\" view even if that's not the default view for the model." -msgstr "" - -#: ../../content/developer/reference/actions.rst:169 -msgid "The server-side composition of the ``views`` sequence is the following:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:171 -msgid "get each ``(id, type)`` from ``view_ids`` (ordered by ``sequence``)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:172 -msgid "if ``view_id`` is defined and its type isn't already filled, append its ``(id, type)``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:174 -msgid "for each unfilled type in ``view_mode``, append ``(False, type)``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:178 -msgid "``usage``?" -msgstr "" - -#: ../../content/developer/reference/actions.rst:179 -msgid "``groups_id``?" -msgstr "" - -#: ../../content/developer/reference/actions.rst:180 -msgid "``filter``?" -msgstr "" - -#: ../../content/developer/reference/actions.rst:182 -msgid "technically not an M2M: adds a sequence field and may be composed of just a view type, without a view id." -msgstr "" - -#: ../../content/developer/reference/actions.rst:188 -msgid "URL Actions (``ir.actions.act_url``)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:190 -msgid "Allow opening a URL (website/web page) via an Odoo action. Can be customized via two fields:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:193 -msgid "``url``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:194 -msgid "the address to open when activating the action" -msgstr "" - -#: ../../content/developer/reference/actions.rst:196 -msgid "opens the address in a new window/page if ``new``, replaces the current content with the page if ``self``. Defaults to ``new``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:207 -msgid "will replace the current content section by the Odoo home page." -msgstr "" - -#: ../../content/developer/reference/actions.rst:212 -msgid "Server Actions (``ir.actions.server``)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:216 -msgid "Allow triggering complex server code from any valid action location. Only two fields are relevant to clients:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:219 -#: ../../content/developer/reference/data.rst:70 -#: ../../content/developer/reference/data.rst:155 -#: ../../content/developer/reference/data.rst:232 -#: ../../content/developer/reference/data.rst:242 -#: ../../content/developer/reference/views.rst:810 -#: ../../content/developer/webservices/extract_api.rst:107 -#: ../../content/developer/webservices/extract_api.rst:192 -#: ../../content/developer/webservices/extract_api.rst:504 -#: ../../content/developer/webservices/upgrade.rst:531 -msgid "``id``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:220 -msgid "the in-database identifier of the server action to run" -msgstr "" - -#: ../../content/developer/reference/actions.rst:222 -msgid "context data to use when running the server action" -msgstr "" - -#: ../../content/developer/reference/actions.rst:224 -msgid "In-database records are significantly richer and can perform a number of specific or generic actions based on their ``state``. Some fields (and corresponding behaviors) are shared between states:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:229 -#: ../../content/developer/reference/actions.rst:433 -#: ../../content/developer/webservices/odoo.rst:1161 -msgid "``model_id``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:229 -msgid "Odoo model linked to the action." -msgstr "" - -#: ../../content/developer/reference/actions.rst:231 -#: ../../content/developer/webservices/odoo.rst:1019 -#: ../../content/developer/webservices/odoo.rst:1170 -#: ../../content/developer/webservices/upgrade.rst:545 -msgid "``state``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:233 -msgid "``code``: Executes python code given through the ``code`` argument." -msgstr "" - -#: ../../content/developer/reference/actions.rst:235 -msgid "``object_create``: Creates a new record of model ``crud_model_id`` following ``fields_lines`` specifications." -msgstr "" - -#: ../../content/developer/reference/actions.rst:237 -msgid "``object_write``: Updates the current record(s) following ``fields_lines`` specifications" -msgstr "" - -#: ../../content/developer/reference/actions.rst:239 -msgid "``multi``: Executes serveral actions given through the ``child_ids`` argument." -msgstr "" - -#: ../../content/developer/reference/actions.rst:242 -msgid "State fields" -msgstr "" - -#: ../../content/developer/reference/actions.rst:244 -msgid "Depending on its state, the behavior is defined through different fields. The concerned state is given after each field." -msgstr "" - -#: ../../content/developer/reference/actions.rst:289 -msgid "``code`` (code)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:248 -msgid "Specify a piece of Python code to execute when the action is called" -msgstr "" - -#: ../../content/developer/reference/actions.rst:263 -msgid "The code segment can define a variable called ``action``, which will be returned to the client as the next action to execute:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:283 -msgid "will ask the client to open a form for the record if it fulfills some condition" -msgstr "" - -#: ../../content/developer/reference/actions.rst:291 -msgid "``crud_model_id`` (create)(required)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:292 -msgid "model in which to create a new record" -msgstr "" - -#: ../../content/developer/reference/actions.rst:295 -msgid "``link_field_id`` (create)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:294 -msgid "many2one to ``ir.model.fields``, specifies the current record's m2o field on which the newly created record should be set (models should match)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:309 -msgid "``fields_lines`` (create/write)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:298 -msgid "fields to override when creating or copying the record. :class:`~odoo.fields.One2many` with the fields:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:302 -msgid "``col1``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:302 -msgid "``ir.model.fields`` to set in the concerned model (``crud_model_id`` for creates, ``model_id`` for updates)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:304 -#: ../../content/developer/reference/orm.rst:827 -msgid "``value``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:305 -msgid "value for the field, interpreted via ``type``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:309 -msgid "``type`` (value|reference|equation)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:307 -msgid "If ``value``, the ``value`` field is interpreted as a literal value (possibly converted), if ``equation`` the ``value`` field is interpreted as a Python expression and evaluated" -msgstr "" - -#: ../../content/developer/reference/actions.rst:314 -msgid "``child_ids`` (multi)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:312 -msgid "Specify the multiple sub-actions (``ir.actions.server``) to enact in state multi. If sub-actions themselves return actions, the last one will be returned to the client as the multi's own next action" -msgstr "" - -#: ../../content/developer/reference/actions.rst:319 -msgid "Evaluation context" -msgstr "" - -#: ../../content/developer/reference/actions.rst:321 -msgid "A number of keys are available in the evaluation context of or surrounding server actions:" -msgstr "" - -#: ../../content/developer/reference/actions.rst:324 -msgid "``model`` model object linked to the action via ``model_id``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:325 -msgid "``record``/``records`` record/recorset on which the action is triggered, can be void." -msgstr "" - -#: ../../content/developer/reference/actions.rst:326 -msgid "``env`` Odoo Environment" -msgstr "" - -#: ../../content/developer/reference/actions.rst:327 -msgid "``datetime``, ``dateutil``, ``time``, ``timezone`` corresponding Python modules" -msgstr "" - -#: ../../content/developer/reference/actions.rst:328 -msgid "``log: log(message, level='info')`` logging function to record debug information in ir.logging table" -msgstr "" - -#: ../../content/developer/reference/actions.rst:329 -msgid "``Warning`` constructor for the ``Warning`` exception" -msgstr "" - -#: ../../content/developer/reference/actions.rst:334 -msgid "Report Actions (``ir.actions.report``)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:336 -msgid "Triggers the printing of a report." -msgstr "" - -#: ../../content/developer/reference/actions.rst:338 -msgid "If you define your report through a `` instead of a `` tag and want the action to show up in the Print menu of the model's views, you will also need to specify ``binding_model_id`` from :ref:`reference/bindings`. It's not necessary to set ``binding_type`` to ``report``, since ``ir.actions.report`` will implicitly default to that." -msgstr "" - -#: ../../content/developer/reference/actions.rst:347 -#: ../../content/developer/reference/reports.rst:195 -#: ../../content/developer/reference/views.rst:616 -#: ../../content/developer/reference/views.rst:719 -#: ../../content/developer/reference/views.rst:807 -msgid "``name`` (mandatory)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:346 -msgid "used as the file name if ``print_report_name`` is not specified. Otherwise, only useful as a mnemonic/description of the report when looking for one in a list of some sort" -msgstr "" - -#: ../../content/developer/reference/actions.rst:349 -msgid "``model`` (mandatory)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:350 -msgid "the model your report will be about" -msgstr "" - -#: ../../content/developer/reference/actions.rst:351 -msgid "``report_type`` (default=qweb-pdf)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:352 -msgid "either ``qweb-pdf`` for PDF reports or ``qweb-html`` for HTML" -msgstr "" - -#: ../../content/developer/reference/actions.rst:353 -msgid "``report_name`` (mandatory)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:354 -msgid "the name (:term:`external id`) of the qweb template used to render the report" -msgstr "" - -#: ../../content/developer/reference/actions.rst:355 -msgid "``print_report_name``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:356 -msgid "python expression defining the name of the report." -msgstr "" - -#: ../../content/developer/reference/actions.rst:358 -msgid "``groups_id``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:358 -msgid ":class:`~odoo.fields.Many2many` field to the groups allowed to view/use the current report" -msgstr "" - -#: ../../content/developer/reference/actions.rst:360 -msgid "``multi``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:361 -msgid "if set to ``True``, the action will not be displayed on a form view." -msgstr "" - -#: ../../content/developer/reference/actions.rst:363 -msgid "``paperformat_id``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:363 -msgid ":class:`~odoo.fields.Many2one` field to the paper format you wish to use for this report (if not specified, the company format will be used)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:370 -msgid "``attachment_use``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:366 -msgid "if set to ``True``, the report is only generated once the first time it is requested, and re-printed from the stored report afterwards instead of being re-generated every time." -msgstr "" - -#: ../../content/developer/reference/actions.rst:370 -msgid "Can be used for reports which must only be generated once (e.g. for legal reasons)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:374 -msgid "``attachment``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:373 -msgid "python expression that defines the name of the report; the record is accessible as the variable ``object``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:379 -msgid "Client Actions (``ir.actions.client``)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:381 -msgid "Triggers an action implemented entirely in the client." -msgstr "" - -#: ../../content/developer/reference/actions.rst:384 -msgid "``tag``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:384 -msgid "the client-side identifier of the action, an arbitrary string which the client should know how to react to" -msgstr "" - -#: ../../content/developer/reference/actions.rst:387 -msgid "``params`` (optional)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:387 -msgid "a Python dictionary of additional data to send to the client, alongside the client action tag" -msgstr "" - -#: ../../content/developer/reference/actions.rst:390 -msgid "whether the client action should be open in the main content area (``current``), in full screen mode (``fullscreen``) or in a dialog/popup (``new``). Use ``main`` instead of ``current`` to clear the breadcrumbs. Defaults to ``current``." -msgstr "" - -#: ../../content/developer/reference/actions.rst:402 -msgid "tells the client to start the Point of Sale interface, the server has no idea how the POS interface works." -msgstr "" - -#: ../../content/developer/reference/actions.rst:406 -msgid ":ref:`Tutorial: Client Actions `" -msgstr "" - -#: ../../content/developer/reference/actions.rst:411 -msgid "Automated Actions (``ir.cron``)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:413 -msgid "Actions triggered automatically on a predefined frequency." -msgstr "" - -#: ../../content/developer/reference/actions.rst:416 -msgid "Name of the automated action (Mainly used in log display)" -msgstr "" - -#: ../../content/developer/reference/actions.rst:419 -msgid "``interval_number``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:419 -msgid "Number of *interval_type* uom between two executions of the action" -msgstr "" - -#: ../../content/developer/reference/actions.rst:422 -msgid "``interval_type``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:422 -msgid "Unit of measure of frequency interval (``minutes``, ``hours``, ``days``, ``weeks``, ``months``," -msgstr "" - -#: ../../content/developer/reference/actions.rst:426 -msgid "``numbercall``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:425 -msgid "Number of times this action has to be run. If the action is expected to run indefinitely, set to ``-1``." -msgstr "" - -#: ../../content/developer/reference/actions.rst:430 -msgid "``doall``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:429 -msgid "Boolean precising whether the missed actions have to be executed in case of server restarts." -msgstr "" - -#: ../../content/developer/reference/actions.rst:433 -msgid "Model on which this action will be called" -msgstr "" - -#: ../../content/developer/reference/actions.rst:441 -msgid "``code``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:436 -msgid "Code content of the action. Can be a simple call to the model's method :" -msgstr "" - -#: ../../content/developer/reference/actions.rst:443 -msgid "``nextcall``" -msgstr "" - -#: ../../content/developer/reference/actions.rst:444 -msgid "Next planned execution date of this action (date/time format)" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:6 -msgid "Command-line interface: odoo-bin" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:11 -msgid "Running the server" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:17 -msgid "database(s) used when installing or updating modules. Providing a comma-separated list restrict access to databases provided in list." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:21 -msgid "For advanced database options, take a look :ref:`below `." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:25 -msgid "comma-separated list of modules to install before running the server (requires :option:`-d`)." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:30 -msgid "comma-separated list of modules to update before running the server (requires :option:`-d`)." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:35 -msgid "comma-separated list of directories in which modules are stored. These directories are scanned for modules." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:42 -msgid "provide an alternate :ref:`configuration file `" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:46 -msgid "saves the server configuration to the current configuration file (:file:`{$HOME}/.odoorc` by default, and can be overridden using :option:`-c`)." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:52 -msgid "disables demo data loading for modules installed comma-separated, use ``all`` for all modules." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:57 -msgid "runs tests after installing modules" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:61 -msgid "select the tests to run by using tags." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:65 -msgid "Specify directory where to write screenshots when an HttpCase.browser_js test fails. It defaults to :file:`/tmp/odoo_tests/{db_name}/screenshots`" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:70 -msgid "Enable screencasts and specify directory where to write screencasts files. The ``ffmpeg`` utility needs to be installed to encode frames into a video file. Otherwise frames will be kept instead of the video file." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:77 -msgid "Database" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:81 -msgid "database username, used to connect to PostgreSQL." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:85 -msgid "database password, if using `password authentication`_." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:89 -msgid "host for the database server" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:91 -msgid "``localhost`` on Windows" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:92 -msgid "UNIX socket otherwise" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:96 -msgid "port the database listens on, defaults to 5432" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:100 -msgid "hides databases that do not match ````. The filter is a `regular expression`_, with the additions that:" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:103 -msgid "``%h`` is replaced by the whole hostname the request is made on." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:104 -msgid "``%d`` is replaced by the subdomain the request is made on, with the exception of ``www`` (so domain ``odoo.com`` and ``www.odoo.com`` both match the database ``odoo``)." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:108 -msgid "These operations are case sensitive. Add option ``(?i)`` to match all databases (so domain ``odoo.com`` using ``(?i)%d`` matches the database ``Odoo``)." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:112 -msgid "Since version 11, it's also possible to restrict access to a given database listen by using the --database parameter and specifying a comma-separated list of databases" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:116 -msgid "When combining the two parameters, db-filter supersedes the comma-separated database list for restricting database list, while the comma-separated list is used for performing requested operations like upgrade of modules." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:124 -msgid "Restrict access to databases whose name starts with 11" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:130 -msgid "Restrict access to only two databases, 11firstdatabase and 11seconddatabase" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:136 -msgid "Restrict access to only two databases, 11firstdatabase and 11seconddatabase, and update base module on one database: 11firstdatabase. If database 11seconddatabase doesn't exist, the database is created and base modules is installed" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:145 -msgid "Restrict access to databases whose name starts with 11, and update base module on one database: 11firstdatabase. If database 11seconddatabase doesn't exist, the database is created and base modules is installed" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:152 -msgid "when creating new databases from the database-management screens, use the specified `template database`_. Defaults to ``template0``." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:157 -msgid "Path to the PostgreSQL binaries that are used by the database manager to dump and restore databases. You have to specify this option only if these binaries are located in a non-standard directory." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:163 -msgid "Suppresses the ability to list databases available on the system" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:167 -msgid "Control the SSL security of the connection between Odoo and PostgreSQL. Value should bve one of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or 'verify-full' Default value is 'prefer'" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:175 -msgid "Emails" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:179 -msgid "Email address used as when Odoo needs to send mails" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:183 -msgid "Address of the SMTP server to connect to in order to send mails" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:189 -msgid "If set, odoo should use SSL/STARTSSL SMTP connections" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:193 -msgid "Username to connect to the SMTP server" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:197 -msgid "Password to connect to the SMTP server" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:202 -msgid "Internationalisation" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:204 -msgid "Use these options to translate Odoo to another language. See i18n section of the user manual. Option '-d' is mandatory. Option '-l' is mandatory in case of importation" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:210 -msgid "specifies the languages (separated by commas) for the translations you want to be loaded" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:215 -msgid "specify the language of the translation file. Use it with --i18n-export or --i18n-import" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:220 -msgid "export all sentences to be translated to a CSV file, a PO file or a TGZ archive and exit." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:225 -msgid "import a CSV or a PO file with translations and exit. The '-l' option is required." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:230 -msgid "overwrites existing translation terms on updating a module or importing a CSV or a PO file." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:235 -msgid "specify modules to export. Use in combination with --i18n-export" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:240 -msgid "Advanced Options" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:245 -msgid "Developer features" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:249 -msgid "``all``: all the features below are activated" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:251 -msgid "``xml``: read template qweb from xml file directly instead of database. Once a template has been modified in database, it will be not be read from the xml file until the next update/init." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:255 -msgid "``reload``: restart server when python file are updated (may not be detected depending on the text editor used)" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:258 -msgid "``qweb``: break in the evaluation of qweb template when a node contains ``t-debug='debugger'``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:260 -msgid "``(i)p(u)db``: start the chosen python debugger in the code when an unexpected error is raised before logging and returning the error." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:267 -msgid "HTTP" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:271 -msgid "do not start the HTTP or long-polling workers (may still start :ref:`cron ` workers)" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:274 -msgid "has no effect if :option:`--test-enable` is set, as tests require an accessible HTTP server" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:279 -msgid "TCP/IP address on which the HTTP server listens, defaults to ``0.0.0.0`` (all addresses)" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:284 -msgid "Port on which the HTTP server listens, defaults to 8069." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:288 -msgid "TCP port for long-polling connections in multiprocessing or gevent mode, defaults to 8072. Not used in default (threaded) mode." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:293 -msgid "enables the use of ``X-Forwarded-*`` headers through `Werkzeug's proxy support`_." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:296 -msgid "proxy mode *must not* be enabled outside of a reverse proxy scenario" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:302 -msgid "Logging" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:304 -msgid "By default, Odoo displays all logging of level_ ``info`` except for workflow logging (``warning`` only), and log output is sent to ``stdout``. Various options are available to redirect logging to other destinations and to customize the amount of logging output." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:311 -msgid "sends logging output to the specified file instead of stdout. On Unix, the file `can be managed by external log rotation programs `_ and will automatically be reopened when replaced" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:318 -msgid "logs to the system's event logger: `syslog on unices `_ and `the Event Log on Windows `_." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:321 -msgid "Neither is configurable" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:325 -msgid "logs to the ``ir.logging`` model (``ir_logging`` table) of the specified database. The database can be the name of a database in the \"current\" PostgreSQL, or `a PostgreSQL URI`_ for e.g. log aggregation." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:331 -msgid ":samp:`{LOGGER}:{LEVEL}`, enables ``LOGGER`` at the provided ``LEVEL`` e.g. ``odoo.models:DEBUG`` will enable all logging messages at or above ``DEBUG`` level in the models." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:335 -msgid "The colon ``:`` is mandatory" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:336 -msgid "The logger can be omitted to configure the root (default) handler" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:337 -msgid "If the level is omitted, the logger is set to ``INFO``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:339 -msgid "The option can be repeated to configure multiple loggers e.g." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:347 -msgid "enable DEBUG logging for RPC requests, equivalent to ``--log-handler=odoo.http.rpc.request:DEBUG``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:352 -msgid "enable DEBUG logging for RPC responses, equivalent to ``--log-handler=odoo.http.rpc.response:DEBUG``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:357 -msgid "enables DEBUG logging of HTTP requests and responses, equivalent to ``--log-handler=odoo.http:DEBUG``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:362 -msgid "enables DEBUG logging of SQL querying, equivalent to ``--log-handler=odoo.sql_db:DEBUG``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:367 -msgid "Shortcut to more easily set predefined levels on specific loggers. \"real\" levels (``critical``, ``error``, ``warn``, ``debug``) are set on the ``odoo`` and ``werkzeug`` loggers (except for ``debug`` which is only set on ``odoo``)." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:372 -msgid "Odoo also provides debugging pseudo-levels which apply to different sets of loggers:" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:377 -msgid "``debug_sql``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:376 -msgid "sets the SQL logger to ``debug``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:378 -msgid "equivalent to ``--log-sql``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:381 -msgid "``debug_rpc``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:380 -msgid "sets the ``odoo`` and HTTP request loggers to ``debug``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:382 -msgid "equivalent to ``--log-level debug --log-request``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:387 -msgid "``debug_rpc_answer``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:384 -msgid "sets the ``odoo`` and HTTP request and response loggers to ``debug``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:387 -msgid "equivalent to ``--log-level debug --log-request --log-response``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:391 -msgid "In case of conflict between :option:`--log-level` and :option:`--log-handler`, the latter is used" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:397 -msgid "Multiprocessing" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:401 -msgid "if ``count`` is not 0 (the default), enables multiprocessing and sets up the specified number of HTTP workers (sub-processes processing HTTP and RPC requests)." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:405 -msgid "multiprocessing mode is only available on Unix-based systems" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:407 -msgid "A number of options allow limiting and recycling workers:" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:411 -msgid "Number of requests a worker will process before being recycled and restarted." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:414 -msgid "Defaults to *8196*." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:418 -msgid "Maximum allowed virtual memory per worker. If the limit is exceeded, the worker is killed and recycled at the end of the current request." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:421 -msgid "Defaults to *2048MiB*." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:425 -msgid "Hard limit on virtual memory, any worker exceeding the limit will be immediately killed without waiting for the end of the current request processing." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:429 -msgid "Defaults to *2560MiB*." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:433 -msgid "Prevents the worker from using more than CPU seconds for each request. If the limit is exceeded, the worker is killed." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:436 -msgid "Defaults to *60*." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:440 -msgid "Prevents the worker from taking longer than seconds to process a request. If the limit is exceeded, the worker is killed." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:443 -msgid "Differs from :option:`--limit-time-cpu` in that this is a \"wall time\" limit including e.g. SQL queries." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:446 -msgid "Defaults to *120*." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:450 -msgid "number of workers dedicated to :ref:`cron ` jobs. Defaults to *2*. The workers are threads in multi-threading mode and processes in multi-processing mode." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:453 -msgid "For multi-processing mode, this is in addition to the HTTP worker processes." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:458 -msgid "Configuration file" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:462 -msgid "Most of the command-line options can also be specified via a configuration file. Most of the time, they use similar names with the prefix ``-`` removed and other ``-`` are replaced by ``_`` e.g. :option:`--db-template` becomes ``db_template``." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:467 -msgid "Some conversions don't match the pattern:" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:469 -msgid ":option:`--db-filter` becomes ``dbfilter``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:470 -msgid ":option:`--no-http` corresponds to the ``http_enable`` boolean" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:471 -msgid "logging presets (all options starting with ``--log-`` except for :option:`--log-handler` and :option:`--log-db`) just add content to ``log_handler``, use that directly in the configuration file" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:474 -msgid ":option:`--smtp` is stored as ``smtp_server``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:475 -msgid ":option:`--database` is stored as ``db_name``" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:476 -msgid ":option:`--i18n-import` and :option:`--i18n-export` aren't available at all from configuration files" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:479 -msgid "The default configuration file is :file:`{$HOME}/.odoorc` which can be overridden using :option:`--config `. Specifying :option:`--save ` will save the current configuration state back to that file. The configuration items relative to the command-line are to be specified in the section ``[options]``." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:485 -msgid "Here is a sample file:" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:509 -msgid "Shell" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:511 -msgid "Odoo command-line also allows to launch odoo as a python console environment. This enables direct interaction with the :ref:`orm ` and its functionalities." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:521 -msgid "Specify a preferred REPL to use in shell mode." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:527 -msgid "Scaffolding" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:531 -msgid "Scaffolding is the automated creation of a skeleton structure to simplify bootstrapping (of new modules, in the case of Odoo). While not necessary it avoids the tedium of setting up basic structures and looking up what all starting requirements are." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:536 -msgid "Scaffolding is available via the :command:`odoo-bin scaffold` subcommand." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:544 -msgid "the name of the module to create, may munged in various manners to generate programmatic names (e.g. module directory name, model names, …)" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:549 -msgid "directory in which to create the new module, defaults to the current directory" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:554 -msgid "a template directory, files are passed through jinja2_ then copied to the ``destination`` directory" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:558 -msgid "This will create module *my_module* in directory */addons/*." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:563 -msgid "Database Population" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:567 -msgid "Odoo CLI supports database population features. If the feature is :ref:`implemented on a given model `, it allows automatic data generation of the model's records to test your modules in databases containing non-trivial amounts of records." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:577 -msgid "list of models for which the database should be filled" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:581 -msgid "population size, the actual records number depends on the model's `_populate_sizes` attribute. The generated records content is specified by the :meth:`~odoo.models._populate_factories` method of a given model (cf. the :file:`populate` folder of modules for further details)." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:587 -msgid ":ref:`reference/testing/populate`" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:591 -msgid "Cloc" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:595 -msgid "Odoo Cloc is a tool to count the number of relevant lines written in Python, Javascript or XML. This can be used as a rough metric for pricing maintenance of extra modules." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:600 -msgid "Command-line options" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:605 -msgid "Process the code of all extra modules installed on the provided database, and of all server actions and computed fields manually created in the provided database." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:607 -msgid "The :option:`--addons-path` option is required to specify the path(s) to the module folder(s)." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:610 -msgid "If combined with :option:`--path`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:617 -msgid ":ref:`reference/cmdline/cloc/database-option`" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:622 -msgid "Process the files in the provided path." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:625 -msgid "If combined with :option:`--database`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:632 -msgid "Multiple paths can be provided by repeating the option." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:639 -msgid ":ref:`reference/cmdline/cloc/path-option`" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:645 -msgid "Comma-separated list of directories in which modules are stored. These directories are scanned for modules." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:646 -msgid "Required if the :option:`--database` option is used." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:651 -msgid "Specify a configuration file to use in place of the :option:`--addons-path` option." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:660 -msgid "Show the details of lines counted for each file." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:664 -msgid "Processed files" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:669 -msgid "With the :option:`--database` option" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:671 -msgid "Odoo Cloc counts the lines in each file of extra installed modules in a given database. In addition, it counts the Python lines of server actions and custom computed fields that have been directly created in the database or imported." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:676 -msgid "Some files are excluded from the count by default:" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:678 -msgid "The manifest (:file:`__manifest__.py` or :file:`__openerp__.py`)" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:679 -msgid "The contents of the folder :file:`static/lib`" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:680 -msgid "The tests defined in the folder :file:`tests` and :file:`static/tests`" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:681 -msgid "The migrations scripts defined in the folder :file:`migrations`" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:682 -msgid "The XML files declared in the ``demo`` or ``demo_xml`` sections of the manifest" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:684 -msgid "For special cases, a list of files that should be ignored by Odoo Cloc can be defined per module. This is specified by the ``cloc_exclude`` entry of the manifest:" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:696 -msgid "The pattern ``**/*`` can be used to ignore an entire module. This can be useful to exclude a module from maintenance service costs." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:698 -msgid "For more information about the pattern syntax, see `glob `_." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:705 -msgid "With the :option:`--path` option" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:707 -msgid "This method works the same as with the :ref:`--database option ` if a manifest file is present in the given folder. Otherwise, it counts all files." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:713 -msgid "Identifying Extra Modules" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:715 -msgid "To distinguish between standard and extra modules, Odoo Cloc uses the following heuristic: modules that are located (real file system path, after following symbolic links) in the same parent directory as the ``base``, ``web`` or ``web_enterprise`` standard modules are considered standard. Other modules are treated as extra modules." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:722 -msgid "Error Handling" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:724 -msgid "Some file cannot be counted by Odoo Cloc. Those file are reported at the end of the output." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:728 -msgid "Max file size exceeded" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:730 -msgid "Odoo Cloc rejects any file larger than 25MB. Usually, source files are smaller than 1 MB. If a file is rejected, it may be:" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:733 -msgid "A generated XML file that contains lots of data. It should be excluded in the manifest." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:734 -msgid "A JavaScript library that should be placed in the :file:`static/lib` folder." -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:737 -msgid "Syntax Error" -msgstr "" - -#: ../../content/developer/reference/cmdline.rst:739 -msgid "Odoo Cloc cannot count the lines of code of a Python file with a syntax problem. If an extra module contains such files, they should be fixed to allow the module to load. If the module works despite the presence of those files, they are probably not loaded and should therefore be removed from the module, or at least excluded in the manifest via ``cloc_exclude``." -msgstr "" - -#: ../../content/developer/reference/data.rst:6 -msgid "Data Files" -msgstr "" - -#: ../../content/developer/reference/data.rst:8 -msgid "Odoo is greatly data-driven, and a big part of modules definition is thus the definition of the various records it manages: UI (menus and views), security (access rights and access rules), reports and plain data are all defined via records." -msgstr "" - -#: ../../content/developer/reference/data.rst:16 -msgid "The main way to define data in Odoo is via XML data files: The broad structure of an XML data file is the following:" -msgstr "" - -#: ../../content/developer/reference/data.rst:19 -msgid "Any number of operation elements within the root element ``odoo``" -msgstr "" - -#: ../../content/developer/reference/data.rst:30 -msgid "Data files are executed sequentially, operations can only refer to the result of operations defined previously" -msgstr "" - -#: ../../content/developer/reference/data.rst:35 -msgid "If the content of the data file is expected to be applied only once, you can specify the odoo flag ``noupdate`` set to 1. If part of the data in the file is expected to be applied once, you can place this part of the file in a domain." -msgstr "" - -#: ../../content/developer/reference/data.rst:53 -msgid "Core operations" -msgstr "" - -#: ../../content/developer/reference/data.rst:58 -#: ../../content/developer/reference/views.rst:387 -#: ../../content/developer/reference/views.rst:1270 -msgid "``record``" -msgstr "" - -#: ../../content/developer/reference/data.rst:60 -msgid "``record`` appropriately defines or updates a database record, it has the following attributes:" -msgstr "" - -#: ../../content/developer/reference/data.rst:63 -#: ../../content/developer/reference/data.rst:153 -msgid "``model`` (required)" -msgstr "" - -#: ../../content/developer/reference/data.rst:64 -msgid "name of the model to create (or update)" -msgstr "" - -#: ../../content/developer/reference/data.rst:66 -msgid "the :term:`external identifier` for this record. It is strongly recommended to provide one" -msgstr "" - -#: ../../content/developer/reference/data.rst:69 -msgid "for record creation, allows subsequent definitions to either modify or refer to this record" -msgstr "" - -#: ../../content/developer/reference/data.rst:71 -msgid "for record modification, the record to modify" -msgstr "" - -#: ../../content/developer/reference/data.rst:73 -msgid "context to use when creating the record" -msgstr "" - -#: ../../content/developer/reference/data.rst:77 -msgid "``forcecreate``" -msgstr "" - -#: ../../content/developer/reference/data.rst:75 -msgid "in update mode whether the record should be created if it doesn't exist" -msgstr "" - -#: ../../content/developer/reference/data.rst:77 -msgid "Requires an :term:`external id`, defaults to ``True``." -msgstr "" - -#: ../../content/developer/reference/data.rst:80 -#: ../../content/developer/reference/views.rst:369 -#: ../../content/developer/reference/views.rst:881 -#: ../../content/developer/reference/views.rst:1232 -#: ../../content/developer/reference/views.rst:1560 -#: ../../content/developer/reference/views.rst:1878 -msgid "``field``" -msgstr "" - -#: ../../content/developer/reference/data.rst:82 -msgid "Each record can be composed of ``field`` tags, defining values to set when creating the record. A ``record`` with no ``field`` will use all default values (creation) or do nothing (update)." -msgstr "" - -#: ../../content/developer/reference/data.rst:86 -msgid "A ``field`` has a mandatory ``name`` attribute, the name of the field to set, and various methods to define the value itself:" -msgstr "" - -#: ../../content/developer/reference/data.rst:91 -msgid "Nothing" -msgstr "" - -#: ../../content/developer/reference/data.rst:90 -msgid "if no value is provided for the field, an implicit ``False`` will be set on the field. Can be used to clear a field, or avoid using a default value for the field." -msgstr "" - -#: ../../content/developer/reference/data.rst:98 -#: ../../content/developer/reference/data.rst:159 -msgid "``search``" -msgstr "" - -#: ../../content/developer/reference/data.rst:94 -msgid "for :ref:`relational fields `, should be a :ref:`domain ` on the field's model." -msgstr "" - -#: ../../content/developer/reference/data.rst:97 -msgid "Will evaluate the domain, search the field's model using it and set the search's result as the field's value. Will only use the first result if the field is a :class:`~odoo.fields.Many2one`" -msgstr "" - -#: ../../content/developer/reference/data.rst:104 -msgid "``ref``" -msgstr "" - -#: ../../content/developer/reference/data.rst:101 -msgid "if a ``ref`` attribute is provided, its value must be a valid :term:`external id`, which will be looked up and set as the field's value." -msgstr "" - -#: ../../content/developer/reference/data.rst:104 -msgid "Mostly for :class:`~odoo.fields.Many2one` and :class:`~odoo.fields.Reference` fields" -msgstr "" - -#: ../../content/developer/reference/data.rst:107 -msgid "if a ``type`` attribute is provided, it is used to interpret and convert the field's content. The field's content can be provided through an external file using the ``file`` attribute, or through the node's body." -msgstr "" - -#: ../../content/developer/reference/data.rst:111 -msgid "Available types are:" -msgstr "" - -#: ../../content/developer/reference/data.rst:115 -msgid "``xml``, ``html``" -msgstr "" - -#: ../../content/developer/reference/data.rst:114 -msgid "extracts the ``field``'s children as a single document, evaluates any :term:`external id` specified with the form ``%(external_id)s``. ``%%`` can be used to output actual *%* signs." -msgstr "" - -#: ../../content/developer/reference/data.rst:118 -msgid "``file``" -msgstr "" - -#: ../../content/developer/reference/data.rst:118 -msgid "ensures that the field content is a valid file path in the current model, saves the pair :samp:`{module},{path}` as the field value" -msgstr "" - -#: ../../content/developer/reference/data.rst:121 -msgid "``char``" -msgstr "" - -#: ../../content/developer/reference/data.rst:121 -msgid "sets the field content directly as the field's value without alterations" -msgstr "" - -#: ../../content/developer/reference/data.rst:124 -msgid "``base64``" -msgstr "" - -#: ../../content/developer/reference/data.rst:124 -msgid "base64_-encodes the field's content, useful combined with the ``file`` *attribute* to load e.g. image data into attachments" -msgstr "" - -#: ../../content/developer/reference/data.rst:127 -msgid "``int``" -msgstr "" - -#: ../../content/developer/reference/data.rst:127 -msgid "converts the field's content to an integer and sets it as the field's value" -msgstr "" - -#: ../../content/developer/reference/data.rst:130 -msgid "``float``" -msgstr "" - -#: ../../content/developer/reference/data.rst:130 -msgid "converts the field's content to a float and sets it as the field's value" -msgstr "" - -#: ../../content/developer/reference/data.rst:135 -msgid "``list``, ``tuple``" -msgstr "" - -#: ../../content/developer/reference/data.rst:133 -msgid "should contain any number of ``value`` elements with the same properties as ``field``, each element resolves to an item of a generated tuple or list, and the generated collection is set as the field's value" -msgstr "" - -#: ../../content/developer/reference/data.rst:145 -msgid "``eval``" -msgstr "" - -#: ../../content/developer/reference/data.rst:138 -msgid "for cases where the previous methods are unsuitable, the ``eval`` attributes simply evaluates whatever Python expression it is provided and sets the result as the field's value." -msgstr "" - -#: ../../content/developer/reference/data.rst:142 -msgid "The evaluation context contains various modules (``time``, ``datetime``, ``timedelta``, ``relativedelta``), a function to resolve :term:`external identifiers` (``ref``) and the model object for the current field if applicable (``obj``)" -msgstr "" - -#: ../../content/developer/reference/data.rst:148 -#: ../../content/developer/reference/views.rst:1314 -msgid "``delete``" -msgstr "" - -#: ../../content/developer/reference/data.rst:150 -msgid "The ``delete`` tag can remove any number of records previously defined. It has the following attributes:" -msgstr "" - -#: ../../content/developer/reference/data.rst:154 -msgid "the model in which a specified record should be deleted" -msgstr "" - -#: ../../content/developer/reference/data.rst:156 -msgid "the :term:`external id` of a record to remove" -msgstr "" - -#: ../../content/developer/reference/data.rst:158 -msgid "a :ref:`domain ` to find records of the model to remove" -msgstr "" - -#: ../../content/developer/reference/data.rst:161 -msgid "``id`` and ``search`` are exclusive" -msgstr "" - -#: ../../content/developer/reference/data.rst:164 -msgid "``function``" -msgstr "" - -#: ../../content/developer/reference/data.rst:166 -msgid "The ``function`` tag calls a method on a model, with provided parameters. It has two mandatory parameters ``model`` and ``name`` specifying respectively the model and the name of the method to call." -msgstr "" - -#: ../../content/developer/reference/data.rst:170 -msgid "Parameters can be provided using ``eval`` (should evaluate to a sequence of parameters to call the method with) or ``value`` elements (see ``list`` values)." -msgstr "" - -#: ../../content/developer/reference/data.rst:200 -msgid "Shortcuts" -msgstr "" - -#: ../../content/developer/reference/data.rst:202 -msgid "Because some important structural models of Odoo are complex and involved, data files provide shorter alternatives to defining them using :ref:`record tags `:" -msgstr "" - -#: ../../content/developer/reference/data.rst:207 -msgid "``menuitem``" -msgstr "" - -#: ../../content/developer/reference/data.rst:209 -msgid "Defines an ``ir.ui.menu`` record with a number of defaults and fallbacks:" -msgstr "" - -#: ../../content/developer/reference/data.rst:218 -msgid "``parent``" -msgstr "" - -#: ../../content/developer/reference/data.rst:212 -msgid "If a ``parent`` attribute is set, it should be the :term:`external id` of an other menu item, used as the new item's parent" -msgstr "" - -#: ../../content/developer/reference/data.rst:214 -msgid "If no ``parent`` is provided, tries to interpret the ``name`` attribute as a ``/``-separated sequence of menu names and find a place in the menu hierarchy. In that interpretation, intermediate menus are automatically created" -msgstr "" - -#: ../../content/developer/reference/data.rst:218 -msgid "Otherwise the menu is defined as a \"top-level\" menu item (*not* a menu with no parent)" -msgstr "" - -#: ../../content/developer/reference/data.rst:221 -msgid "If no ``name`` attribute is specified, tries to get the menu name from a linked action if any. Otherwise uses the record's ``id``" -msgstr "" - -#: ../../content/developer/reference/data.rst:226 -#: ../../content/developer/reference/data.rst:250 -#: ../../content/developer/reference/views.rst:837 -#: ../../content/developer/reference/views.rst:1499 -#: ../../content/developer/reference/views.rst:1873 -#: ../../content/developer/reference/views.rst:1983 -#: ../../content/developer/webservices/odoo.rst:1175 -msgid "``groups``" -msgstr "" - -#: ../../content/developer/reference/data.rst:224 -msgid "A ``groups`` attribute is interpreted as a comma-separated sequence of :term:`external identifiers` for ``res.groups`` models. If an :term:`external identifier` is prefixed with a minus (``-``), the group is *removed* from the menu's groups" -msgstr "" - -#: ../../content/developer/reference/data.rst:229 -#: ../../content/developer/reference/views.rst:1454 -msgid "``action``" -msgstr "" - -#: ../../content/developer/reference/data.rst:229 -msgid "if specified, the ``action`` attribute should be the :term:`external id` of an action to execute when the menu is open" -msgstr "" - -#: ../../content/developer/reference/data.rst:232 -msgid "the menu item's :term:`external id`" -msgstr "" - -#: ../../content/developer/reference/data.rst:237 -msgid "``template``" -msgstr "" - -#: ../../content/developer/reference/data.rst:239 -msgid "Creates a :ref:`QWeb view ` requiring only the ``arch`` section of the view, and allowing a few *optional* attributes:" -msgstr "" - -#: ../../content/developer/reference/data.rst:243 -msgid "the view's :term:`external identifier`" -msgstr "" - -#: ../../content/developer/reference/data.rst:245 -msgid "``name``, ``inherit_id``, ``priority``" -msgstr "" - -#: ../../content/developer/reference/data.rst:245 -msgid "same as the corresponding field on ``ir.ui.view`` (nb: ``inherit_id`` should be an :term:`external identifier`)" -msgstr "" - -#: ../../content/developer/reference/data.rst:248 -msgid "``primary``" -msgstr "" - -#: ../../content/developer/reference/data.rst:248 -msgid "if set to ``True`` and combined with a ``inherit_id``, defines the view as a primary" -msgstr "" - -#: ../../content/developer/reference/data.rst:251 -msgid "comma-separated list of group :term:`external identifiers`" -msgstr "" - -#: ../../content/developer/reference/data.rst:253 -#: ../../content/developer/webservices/extract_api.rst:282 -msgid "``page``" -msgstr "" - -#: ../../content/developer/reference/data.rst:253 -msgid "if set to ``\"True\"``, the template is a website page (linkable to, deletable)" -msgstr "" - -#: ../../content/developer/reference/data.rst:258 -msgid "``optional``" -msgstr "" - -#: ../../content/developer/reference/data.rst:256 -msgid "``enabled`` or ``disabled``, whether the view can be disabled (in the website interface) and its default status. If unset, the view is always enabled." -msgstr "" - -#: ../../content/developer/reference/data.rst:264 -msgid "CSV data files" -msgstr "" - -#: ../../content/developer/reference/data.rst:266 -msgid "XML data files are flexible and self-descriptive, but very verbose when creating a number of simple records of the same model in bulk." -msgstr "" - -#: ../../content/developer/reference/data.rst:269 -msgid "For this case, data files can also use csv_, this is often the case for :ref:`access rights `:" -msgstr "" - -#: ../../content/developer/reference/data.rst:272 -msgid "the file name is :file:`{model_name}.csv`" -msgstr "" - -#: ../../content/developer/reference/data.rst:273 -msgid "the first row lists the fields to write, with the special field ``id`` for :term:`external identifiers` (used for creation or update)" -msgstr "" - -#: ../../content/developer/reference/data.rst:275 -msgid "each row thereafter creates a new record" -msgstr "" - -#: ../../content/developer/reference/data.rst:277 -msgid "Here's the first lines of the data file defining US states ``res.country.state.csv``" -msgstr "" - -#: ../../content/developer/reference/data.rst:283 -msgid "rendered in a more readable format:" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "id" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "country_id:id" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "name" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "code" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_au_1" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "au" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Australian Capital Territory" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "ACT" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_au_2" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "New South Wales" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "NSW" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_au_3" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Northern Territory" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "NT" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_au_4" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Queensland" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "QLD" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_au_5" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "South Australia" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "SA" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_au_6" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Tasmania" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "TAS" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_au_7" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Victoria" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "VIC" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_au_8" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Western Australia" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "WA" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_us_1" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "us" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Alabama" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "AL" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_us_2" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Alaska" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "AK" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_us_3" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Arizona" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "AZ" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_us_4" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Arkansas" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "AR" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_us_5" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "California" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "CA" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "state_us_6" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "Colorado" -msgstr "" - -#: ../../content/developer/reference/static/res.country.state.csv:1 -msgid "CO" -msgstr "" - -#: ../../content/developer/reference/data.rst:290 -msgid "For each row (record):" -msgstr "" - -#: ../../content/developer/reference/data.rst:292 -msgid "the first column is the :term:`external id` of the record to create or update" -msgstr "" - -#: ../../content/developer/reference/data.rst:294 -msgid "the second column is the :term:`external id` of the country object to link to (country objects must have been defined beforehand)" -msgstr "" - -#: ../../content/developer/reference/data.rst:296 -msgid "the third column is the ``name`` field for ``res.country.state``" -msgstr "" - -#: ../../content/developer/reference/data.rst:297 -msgid "the fourth column is the ``code`` field for ``res.country.state``" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:8 -msgid "Odoo Guidelines" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:10 -msgid "This page introduces the Odoo Coding Guidelines. Those aim to improve the quality of Odoo Apps code. Indeed proper code improves readability, eases maintenance, helps debugging, lowers complexity and promotes reliability. These guidelines should be applied to every new module and to all new development." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:17 -msgid "When modifying existing files in **stable version** the original file style strictly supersedes any other style guidelines. In other words please never modify existing files in order to apply these guidelines. It avoids disrupting the revision history of code lines. Diff should be kept minimal. For more details, see our `pull request guide `_." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:25 -msgid "When modifying existing files in **master (development) version** apply those guidelines to existing code only for modified code or if most of the file is under revision. In other words modify existing files structure only if it is going under major changes. In that case first do a **move** commit then apply the changes related to the feature." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:35 -msgid "Directories" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:36 -msgid "A module is organized in important directories. Those contain the business logic; having a look at them should make you understand the purpose of the module." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:39 -msgid "*data/* : demo and data xml" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:40 -msgid "*models/* : models definition" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:41 -msgid "*controllers/* : contains controllers (HTTP routes)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:42 -msgid "*views/* : contains the views and templates" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:43 -msgid "*static/* : contains the web assets, separated into *css/, js/, img/, lib/, ...*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:45 -msgid "Other optional directories compose the module." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:47 -msgid "*wizard/* : regroups the transient models (``models.TransientModel``) and their views" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:48 -msgid "*report/* : contains the printable reports and models based on SQL views. Python objects and XML views are included in this directory" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:49 -msgid "*tests/* : contains the Python tests" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:53 -msgid "File naming" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:55 -msgid "File naming is important to quickly find information through all odoo addons. This section explains how to name files in a standard odoo module. As an example we use a `plant nursery `_ application. It holds two main models *plant.nursery* and *plant.order*." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:60 -msgid "Concerning *models*, split the business logic by sets of models belonging to a same main model. Each set lies in a given file named based on its main model. If there is only one model, its name is the same as the module name. Each inherited model should be in its own file to help understanding of impacted models." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:74 -msgid "Concerning *security* and access rights and rules two main files should be used. First one is the definition of access rights done in a ``ir.model.access.csv`` file. User groups are defined in ``_groups.xml``. Access rules are defined in ``_security.xml``." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:88 -msgid "Concerning *views*, backend views should be split like models and suffixed by ``_views.xml``. Backend views are list, form, kanban, activity, graph, pivot, .. views. To ease split by model in views main menus not linked to specific actions may be extracted into an optional ``_menus.xml`` file. Templates (QWeb pages used notably for portal / website display) and bundles (import of JS and CSS assets) are put in separate files. Those are respectively ``_templates.xml`` and ``assets.xml`` files." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:108 -msgid "Concerning *data*, split them by purpose (demo or data) and main model. Filenames will be the main_model name suffixed by ``_demo.xml`` or ``_data.xml``. For instance for an application having demo and data for its main model as well as subtypes, activities and mail templates all related to mail module:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:121 -msgid "Concerning *controllers*, generally all controllers belong to a single controller contained in a file named ``.py``. An old convention in Odoo is to name this file ``main.py`` but it is considered as outdated. If you need to inherit an existing controller from another module do it in ``.py``. For example adding portal controller in an application is done in ``portal.py``." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:135 -msgid "Concerning *static files*, Javascript files follow globally the same logic as python models. Each component should be in its own file with a meaningful name. For instance, the activity widgets are located in ``activity.js`` of mail module. Subdirectories can also be created to structure the 'package' (see web module for more details). The same logic should be applied for the templates of JS widgets (static XML files) and for their styles (scss files). Don't link data (image, libraries) outside Odoo: do not use an URL to an image but copy it in the codebase instead." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:144 -msgid "Concerning *wizards*, naming convention is the same of for python models: ``.py`` and ``_views.xml``. Both are put in the wizard directory. This naming comes from old odoo applications using the wizard keyword for transient models." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:156 -msgid "Concerning *statistics reports* done with python / SQL views and classic views naming is the following :" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:166 -msgid "Concerning *printable reports* which contain mainly data preparation and Qweb templates naming is the following :" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:176 -msgid "The complete tree of our Odoo module therefore looks like" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:235 -msgid "File names should only contain ``[a-z0-9_]`` (lowercase alphanumerics and ``_``)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:238 -msgid "Use correct file permissions : folder 755 and file 644." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:243 -msgid "XML files" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:246 -msgid "Format" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:247 -msgid "To declare a record in XML, the **record** notation (using **) is recommended:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:249 -msgid "Place ``id`` attribute before ``model``" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:250 -msgid "For field declaration, ``name`` attribute is first. Then place the *value* either in the ``field`` tag, either in the ``eval`` attribute, and finally other attributes (widget, options, ...) ordered by importance." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:255 -msgid "Try to group the record by model. In case of dependencies between action/menu/views, this convention may not be applicable." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:257 -msgid "Use naming convention defined at the next point" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:258 -msgid "The tag ** is only used to set not-updatable data with ``noupdate=1``. If there is only not-updatable data in the file, the ``noupdate=1`` can be set on the ```` tag and do not set a ```` tag." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:276 -msgid "Odoo supports custom tags acting as syntactic sugar:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:278 -msgid "menuitem: use it as a shortcut to declare a ``ir.ui.menu``" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:279 -msgid "template: use it to declare a QWeb View requiring only the ``arch`` section of the view." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:280 -msgid "report: use to declare a :ref:`report action `" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:281 -msgid "act_window: use it if the record notation can't do what you want" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:283 -msgid "The 4 first tags are preferred over the *record* notation." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:287 -msgid "XML IDs and naming" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:290 -msgid "Security, View and Action" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:292 -msgid "Use the following pattern :" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:294 -msgid "For a menu: :samp:`{}_menu`, or :samp:`{}_menu_{do_stuff}` for submenus." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:295 -msgid "For a view: :samp:`{}_view_{}`, where *view_type* is ``kanban``, ``form``, ``tree``, ``search``, ..." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:297 -msgid "For an action: the main action respects :samp:`{}_action`. Others are suffixed with :samp:`_{}`, where *detail* is a lowercase string briefly explaining the action. This is used only if multiple actions are declared for the model." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:301 -msgid "For window actions: suffix the action name by the specific view information like :samp:`{}_action_view_{}`." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:303 -msgid "For a group: :samp:`{}_group_{}` where *group_name* is the name of the group, generally 'user', 'manager', ..." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:305 -msgid "For a rule: :samp:`{}_rule_{}` where *concerned_group* is the short name of the concerned group ('user' for the 'model_name_group_user', 'public' for public user, 'company' for multi-company rules, ...)." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:310 -msgid "Name should be identical to xml id with dots replacing underscores. Actions should have a real naming as it is used as display name." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:364 -msgid "Inheriting XML" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:366 -msgid "Xml Ids of inheriting views should use the same ID as the original record. It helps finding all inheritance at a glance. As final Xml Ids are prefixed by the module that creates them there is no overlap." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:370 -msgid "Naming should contain an ``.inherit.{details}`` suffix to ease understanding the override purpose when looking at its name." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:381 -msgid "New primary views do not require the inherit suffix as those are new records based upon the first one." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:396 -#: ../../content/developer/reference/qweb.rst:332 -#: ../../content/developer/reference/security.rst:355 -#: ../../content/developer/reference/security.rst:357 -msgid "Python" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:400 -msgid "Do not forget to read the :ref:`Security Pitfalls ` section as well to write secure code." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:404 -msgid "PEP8 options" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:406 -msgid "Using a linter can help show syntax and semantic warnings or errors. Odoo source code tries to respect Python standard, but some of them can be ignored." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:409 -msgid "E501: line too long" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:410 -msgid "E301: expected 1 blank line, found 0" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:411 -msgid "E302: expected 2 blank lines, found 1" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:414 -msgid "Imports" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:415 -msgid "The imports are ordered as" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:417 -msgid "External libraries (one per line sorted and split in python stdlib)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:418 -msgid "Imports of ``odoo``" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:419 -msgid "Imports from Odoo modules (rarely, and only if necessary)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:421 -msgid "Inside these 3 groups, the imported lines are alphabetically sorted." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:439 -msgid "Idiomatics of Programming (Python)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:441 -msgid "Each python file should have ``# -*- coding: utf-8 -*-`` as first line." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:442 -msgid "Always favor *readability* over *conciseness* or using the language features or idioms." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:443 -msgid "Don't use ``.clone()``" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:454 -msgid "Python dictionary : creation and update" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:479 -msgid "Use meaningful variable/class/method names" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:480 -msgid "Useless variable : Temporary variables can make the code clearer by giving names to objects, but that doesn't mean you should create temporary variables all the time:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:492 -msgid "Multiple return points are OK, when they're simpler" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:512 -msgid "Know your builtins : You should at least have a basic understanding of all the Python builtins (http://docs.python.org/library/functions.html)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:520 -msgid "Also, ``if 'key' in my_dict`` and ``if my_dict.get('key')`` have very different meaning, be sure that you're using the right one." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:523 -msgid "Learn list comprehensions : Use list comprehension, dict comprehension, and basic manipulation using ``map``, ``filter``, ``sum``, ... They make the code easier to read." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:536 -msgid "Collections are booleans too : In python, many objects have \"boolean-ish\" value when evaluated in a boolean context (such as an if). Among these are collections (lists, dicts, sets, ...) which are \"falsy\" when empty and \"truthy\" when containing items:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:547 -msgid "So, you can write ``if some_collection:`` instead of ``if len(some_collection):``." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:550 -msgid "Iterate on iterables" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:564 -msgid "Use dict.setdefault" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:580 -msgid "As a good developer, document your code (docstring on methods, simple comments for tricky part of code)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:582 -msgid "In additions to these guidelines, you may also find the following link interesting: http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html (a little bit outdated, but quite relevant)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:587 -msgid "Programming in Odoo" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:589 -msgid "Avoid to create generators and decorators: only use the ones provided by the Odoo API." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:591 -msgid "As in python, use ``filtered``, ``mapped``, ``sorted``, ... methods to ease code reading and performance." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:596 -msgid "Make your method work in batch" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:597 -msgid "When adding a function, make sure it can process multiple records by iterating on self to treat each record." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:606 -msgid "For performance issue, when developing a 'stat button' (for instance), do not perform a ``search`` or a ``search_count`` in a loop. It is recommended to use ``read_group`` method, to compute all value in only one request." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:621 -msgid "Propagate the context" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:622 -msgid "The context is a ``frozendict`` that cannot be modified. To call a method with a different context, the ``with_context`` method should be used :" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:631 -msgid "Passing parameter in context can have dangerous side-effects." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:633 -msgid "Since the values are propagated automatically, some unexpected behavior may appear. Calling ``create()`` method of a model with *default_my_field* key in context will set the default value of *my_field* for the concerned model. But if during this creation, other objects (such as sale.order.line, on sale.order creation) having a field name *my_field* are created, their default value will be set too." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:639 -msgid "If you need to create a key context influencing the behavior of some object, choice a good name, and eventually prefix it by the name of the module to isolate its impact. A good example are the keys of ``mail`` module : *mail_create_nosubscribe*, *mail_notrack*, *mail_notify_user_signature*, ..." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:646 -msgid "Think extendable" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:648 -msgid "Functions and methods should not contain too much logic: having a lot of small and simple methods is more advisable than having few large and complex methods. A good rule of thumb is to split a method as soon as it has more than one responsibility (see http://en.wikipedia.org/wiki/Single_responsibility_principle)." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:653 -msgid "Hardcoding a business logic in a method should be avoided as it prevents to be easily extended by a submodule." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:679 -msgid "The above code is over extendable for the sake of example but the readability must be taken into account and a tradeoff must be made." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:682 -msgid "Also, name your functions accordingly: small and properly named functions are the starting point of readable/maintainable code and tighter documentation." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:685 -msgid "This recommendation is also relevant for classes, files, modules and packages. (See also http://en.wikipedia.org/wiki/Cyclomatic_complexity)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:690 -msgid "Never commit the transaction" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:691 -msgid "The Odoo framework is in charge of providing the transactional context for all RPC calls. The principle is that a new database cursor is opened at the beginning of each RPC call, and committed when the call has returned, just before transmitting the answer to the RPC client, approximately like this:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:712 -msgid "If any error occurs during the execution of the RPC call, the transaction is rolled back atomically, preserving the state of the system." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:715 -msgid "Similarly, the system also provides a dedicated transaction during the execution of tests suites, so it can be rolled back or not depending on the server startup options." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:719 -msgid "The consequence is that if you manually call ``cr.commit()`` anywhere there is a very high chance that you will break the system in various ways, because you will cause partial commits, and thus partial and unclean rollbacks, causing among others:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:724 -msgid "inconsistent business data, usually data loss" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:725 -msgid "workflow desynchronization, documents stuck permanently" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:726 -msgid "tests that can't be rolled back cleanly, and will start polluting the database, and triggering error (this is true even if no error occurs during the transaction)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:737 -msgid "Here is the very simple rule:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:731 -msgid "You should **NEVER** call ``cr.commit()`` yourself, **UNLESS** you have created your own database cursor explicitly! And the situations where you need to do that are exceptional!" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:735 -msgid "And by the way if you did create your own cursor, then you need to handle error cases and proper rollback, as well as properly close the cursor when you're done with it." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:739 -msgid "And contrary to popular belief, you do not even need to call ``cr.commit()`` in the following situations: - in the ``_auto_init()`` method of an *models.Model* object: this is taken care of by the addons initialization method, or by the ORM transaction when creating custom models - in reports: the ``commit()`` is handled by the framework too, so you can update the database even from within a report - within *models.Transient* methods: these methods are called exactly like regular *models.Model* ones, within a transaction and with the corresponding ``cr.commit()/rollback()`` at the end - etc. (see general rule above if you have in doubt!)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:751 -msgid "All ``cr.commit()`` calls outside of the server framework from now on must have an **explicit comment** explaining why they are absolutely necessary, why they are indeed correct, and why they do not break the transactions. Otherwise they can and will be removed !" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:758 -msgid "Use translation method correctly" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:760 -msgid "Odoo uses a GetText-like method named \"underscore\" ``_( )`` to indicate that a static string used in the code needs to be translated at runtime using the language of the context. This pseudo-method is accessed within your code by importing as follows:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:769 -msgid "A few very important rules must be followed when using it, in order for it to work and to avoid filling the translations with useless junk." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:772 -msgid "Basically, this method should only be used for static strings written manually in the code, it will not work to translate field values, such as Product names, etc. This must be done instead using the translate flag on the corresponding field." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:777 -msgid "The method accepts optional positional or named parameter The rule is very simple: calls to the underscore method should always be in the form ``_('literal string')`` and nothing else:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:820 -msgid "Also, keep in mind that translators will have to work with the literal values that are passed to the underscore function, so please try to make them easy to understand and keep spurious characters and formatting to a minimum. Translators must be aware that formatting patterns such as ``%s`` or ``%d``, newlines, etc. need to be preserved, but it's important to use these in a sensible and obvious manner:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:840 -msgid "In general in Odoo, when manipulating strings, prefer ``%`` over ``.format()`` (when only one variable to replace in a string), and prefer ``%(varname)`` instead of position (when multiple variables have to be replaced). This makes the translation easier for the community translators." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:847 -msgid "Symbols and Conventions" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:857 -msgid "Model name (using the dot notation, prefix by the module name) :" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:850 -msgid "When defining an Odoo Model : use singular form of the name (*res.partner* and *sale.order* instead of *res.partnerS* and *saleS.orderS*)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:852 -msgid "When defining an Odoo Transient (wizard) : use ``.`` where *related_base_model* is the base model (defined in *models/*) related to the transient, and *action* is the short name of what the transient do. Avoid the *wizard* word. For instance : ``account.invoice.make``, ``project.task.delegate.batch``, ..." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:856 -msgid "When defining *report* model (SQL views e.i.) : use ``.report.``, based on the Transient convention." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:859 -msgid "Odoo Python Class : use camelcase (Object-oriented style)." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:870 -msgid "Variable name :" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:868 -msgid "use camelcase for model variable" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:869 -msgid "use underscore lowercase notation for common variable." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:870 -msgid "suffix your variable name with *_id* or *_ids* if it contains a record id or list of id. Don't use ``partner_id`` to contain a record of res.partner" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:878 -msgid "``One2Many`` and ``Many2Many`` fields should always have *_ids* as suffix (example: sale_order_line_ids)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:879 -msgid "``Many2One`` fields should have *_id* as suffix (example : partner_id, user_id, ...)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:889 -msgid "Method conventions" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:881 -msgid "Compute Field : the compute method pattern is *_compute_*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:882 -msgid "Search method : the search method pattern is *_search_*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:883 -msgid "Default method : the default method pattern is *_default_*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:884 -msgid "Selection method: the selection method pattern is *_selection_*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:885 -msgid "Onchange method : the onchange method pattern is *_onchange_*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:886 -msgid "Constraint method : the constraint method pattern is *_check_*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:887 -msgid "Action method : an object action method is prefix with *action_*. Since it uses only one record, add ``self.ensure_one()`` at the beginning of the method." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:900 -msgid "In a Model attribute order should be" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:892 -msgid "Private attributes (``_name``, ``_description``, ``_inherit``, ...)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:893 -msgid "Default method and ``_default_get``" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:894 -msgid "Field declarations" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:895 -msgid "Compute, inverse and search methods in the same order as field declaration" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:896 -msgid "Selection method (methods used to return computed values for selection fields)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:897 -msgid "Constrains methods (``@api.constrains``) and onchange methods (``@api.onchange``)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:898 -msgid "CRUD methods (ORM overrides)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:899 -msgid "Action methods" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:900 -msgid "And finally, other business methods." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:956 -msgid "Javascript and CSS" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:959 -msgid "Static files organization" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:961 -msgid "Odoo addons have some conventions on how to structure various files. We explain here in more details how web assets are supposed to be organized." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:964 -msgid "The first thing to know is that the Odoo server will serve (statically) all files located in a *static/* folder, but prefixed with the addon name. So, for example, if a file is located in *addons/web/static/src/js/some_file.js*, then it will be statically available at the url *your-odoo-server.com/web/static/src/js/some_file.js*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:969 -msgid "The convention is to organize the code according to the following structure:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:971 -msgid "*static*: all static files in general" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:973 -msgid "*static/lib*: this is the place where js libs should be located, in a sub folder. So, for example, all files from the *jquery* library are in *addons/web/static/lib/jquery*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:975 -msgid "*static/src*: the generic static source code folder" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:977 -msgid "*static/src/css*: all css files" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:978 -msgid "*static/src/fonts*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:979 -msgid "*static/src/img*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:980 -msgid "*static/src/js*" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:982 -msgid "*static/src/js/tours*: end user tour files (tutorials, not tests)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:984 -msgid "*static/src/scss*: scss files" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:985 -msgid "*static/src/xml*: all qweb templates that will be rendered in JS" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:987 -msgid "*static/tests*: this is where we put all test related files." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:989 -msgid "*static/tests/tours*: this is where we put all tour test files (not tutorials)." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:992 -msgid "Javascript coding guidelines" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:994 -msgid "``use strict;`` is recommended for all javascript files" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:995 -msgid "Use a linter (jshint, ...)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:996 -msgid "Never add minified Javascript Libraries" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:997 -msgid "Use camelcase for class declaration" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:999 -msgid "More precise JS guidelines are detailed in the `github wiki `_. You may also have a look at existing API in Javascript by looking Javascript References." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1004 -msgid "CSS coding guidelines" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1006 -msgid "Prefix all your classes with *o_* where *module_name* is the technical name of the module ('sale', 'im_chat', ...) or the main route reserved by the module (for website module mainly, i.e. : 'o_forum' for *website_forum* module). The only exception for this rule is the webclient: it simply uses *o_* prefix." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1011 -msgid "Avoid using *id* tag" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1012 -msgid "Use Bootstrap native classes" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1013 -msgid "Use underscore lowercase notation to name class" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1018 -msgid "Git" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1021 -msgid "Configure your git" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1023 -msgid "Based on ancestral experience and oral tradition, the following things go a long way towards making your commits more helpful:" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1026 -msgid "Be sure to define both the user.email and user.name in your local git config" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1032 -msgid "Be sure to add your full name to your Github profile here. Please feel fancy and add your team, avatar, your favorite quote, and whatnot ;-)" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1036 -msgid "Commit message structure" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1038 -msgid "Commit message has four parts: tag, module, short description and full description. Try to follow the preferred structure for your commit messages" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1061 -msgid "Tag and module name" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1063 -msgid "Tags are used to prefix your commit. They should be one of the following" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1065 -msgid "**[FIX]** for bug fixes: mostly used in stable version but also valid if you are fixing a recent bug in development version;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1067 -msgid "**[REF]** for refactoring: when a feature is heavily rewritten;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1068 -msgid "**[ADD]** for adding new modules;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1069 -msgid "**[REM]** for removing resources: removing dead code, removing views, removing modules, ...;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1071 -msgid "**[REV]** for reverting commits: if a commit causes issues or is not wanted reverting it is done using this tag;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1073 -msgid "**[MOV]** for moving files: use git move and do not change content of moved file otherwise Git may loose track and history of the file; also used when moving code from one file to another;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1076 -msgid "**[REL]** for release commits: new major or minor stable versions;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1077 -msgid "**[IMP]** for improvements: most of the changes done in development version are incremental improvements not related to another tag;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1079 -msgid "**[MERGE]** for merge commits: used in forward port of bug fixes but also as main commit for feature involving several separated commits;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1081 -msgid "**[CLA]** for signing the Odoo Individual Contributor License;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1082 -msgid "**[I18N]** for changes in translation files;" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1084 -msgid "After tag comes the modified module name. Use the technical name as functional name may change with time. If several modules are modified, list them or use various to tell it is cross-modules. Unless really required or easier avoid modifying code across several modules in the same commit. Understanding module history may become difficult." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1091 -msgid "Commit message header" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1093 -msgid "After tag and module name comes a meaningful commit message header. It should be self explanatory and include the reason behind the change. Do not use single words like \"bugfix\" or \"improvements\". Try to limit the header length to about 50 characters for readability." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1098 -msgid "Commit message header should make a valid sentence once concatenated with ``if applied, this commit will
``. For example ``[IMP] base: prevent to archive users linked to active partners`` is correct as it makes a valid sentence ``if applied, this commit will prevent users to archive...``." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1104 -msgid "Commit message full description" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1106 -msgid "In the message description specify the part of the code impacted by your changes (module name, lib, transversal object, ...) and a description of the changes." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1109 -msgid "First explain WHY you are modifying code. What is important if someone goes back to your commit in about 4 decades (or 3 days) is why you did it. It is the purpose of the change." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1113 -msgid "What you did can be found in the commit itself. If there was some technical choices involved it is a good idea to explain it also in the commit message after the why. For Odoo R&D developers \"PO team asked me to do it\" is not a valid why, by the way." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1117 -msgid "Please avoid commits which simultaneously impact multiple modules. Try to split into different commits where impacted modules are different. It will be helpful if we need to revert changes in a given module separately." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1121 -msgid "Don't hesitate to be a bit verbose. Most people will only see your commit message and judge everything you did in your life just based on those few sentences. No pressure at all." -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1125 -msgid "**You spend several hours, days or weeks working on meaningful features. Take some time to calm down and write clear and understandable commit messages.**" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1128 -msgid "If you are an Odoo R&D developer the WHY should be the purpose of the task you are working on. Full specifications make the core of the commit message. **If you are working on a task that lacks purpose and specifications please consider making them clear before continuing.**" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1133 -msgid "Finally here are some examples of correct commit messages :" -msgstr "" - -#: ../../content/developer/reference/guidelines.rst:1156 -msgid "Use the long description to explain the *why* not the *what*, the *what* can be seen in the diff" -msgstr "" - -#: ../../content/developer/reference/http.rst:6 -msgid "Web Controllers" -msgstr "" - -#: ../../content/developer/reference/http.rst:9 -msgid "Controllers" -msgstr "" - -#: ../../content/developer/reference/http.rst:11 -msgid "Controllers need to provide extensibility, much like :class:`~odoo.models.Model`, but can't use the same mechanism as the pre-requisites (a database with loaded modules) may not be available yet (e.g. no database created, or no database selected)." -msgstr "" - -#: ../../content/developer/reference/http.rst:16 -msgid "Controllers thus provide their own extension mechanism, separate from that of models:" -msgstr "" - -#: ../../content/developer/reference/http.rst:19 -msgid "Controllers are created by :ref:`inheriting ` from :class:`~odoo.http.Controller`. Routes are defined through methods decorated with :func:`~odoo.http.route`::" -msgstr "" - -#: ../../content/developer/reference/http.rst:27 -msgid "To *override* a controller, :ref:`inherit ` from its class and override relevant methods, re-exposing them if necessary::" -msgstr "" - -#: ../../content/developer/reference/http.rst:36 -msgid "decorating with :func:`~odoo.http.route` is necessary to keep the method (and route) visible: if the method is redefined without decorating, it will be \"unpublished\"" -msgstr "" - -#: ../../content/developer/reference/http.rst:39 -msgid "the decorators of all methods are combined, if the overriding method's decorator has no argument all previous ones will be kept, any provided argument will override previously defined ones e.g.::" -msgstr "" - -#: ../../content/developer/reference/http.rst:48 -msgid "will change ``/some_url`` from public authentication to user (requiring a log-in)" -msgstr "" - -#: ../../content/developer/reference/http.rst:52 -#: ../../content/developer/reference/orm.rst:48 -#: ../../content/developer/reference/qweb.rst:590 +#: ../../content/developer/misc/api.rst:5 +#: ../../content/developer/reference/addons/http.rst:52 +#: ../../content/developer/reference/addons/orm.rst:48 +#: ../../content/developer/reference/javascript/qweb.rst:592 msgid "API" msgstr "" -#: ../../content/developer/reference/http.rst:57 -msgid "Routing" -msgstr "" - -#: ../../content/developer/reference/http.rst:64 -msgid "Request" -msgstr "" - -#: ../../content/developer/reference/http.rst:66 -msgid "The request object is automatically set on :data:`odoo.http.request` at the start of the request" -msgstr "" - -#: ../../content/developer/reference/http.rst:78 -#: ../../content/developer/webservices/extract_api.rst:103 -#: ../../content/developer/webservices/extract_api.rst:188 -#: ../../content/developer/webservices/extract_api.rst:500 -msgid "Response" -msgstr "" - -#: ../../content/developer/reference/iot.rst:4 -msgid "Internet of Things" -msgstr "" - -#: ../../content/developer/reference/iot.rst:6 -msgid "IoT Drivers allow any Odoo module to communicate in real-time with any device connected to the IoT Box. Communication with the IoT Box goes both ways, so the Odoo client can send commands to and receive information from any of the supported devices." -msgstr "" - -#: ../../content/developer/reference/iot.rst:11 -msgid "To add support for a device, all we need is:" -msgstr "" - -#: ../../content/developer/reference/iot.rst:13 -msgid "an `Interface`, to detect connected devices of a specific type" -msgstr "" - -#: ../../content/developer/reference/iot.rst:14 -msgid "a `Driver`, to communicate with an individual device" -msgstr "" - -#: ../../content/developer/reference/iot.rst:16 -msgid "At each boot, the IoT Box will load all of the Interfaces and Drivers that can be located on the connected Odoo instance. Each module can contain an `iot_handlers` directory that will be copied to the IoT Box. The structure of this directory is the following" -msgstr "" - -#: ../../content/developer/reference/iot.rst:35 -msgid "Detect Devices" -msgstr "" - -#: ../../content/developer/reference/iot.rst:37 -msgid "Devices connected to the IoT Box are detected through `Interfaces`. There is an Interface for each supported connection type (USB, Bluetooth, Video, Printers, Serial, etc.). The interface maintains a list of detected devices and associates them with the right Driver." -msgstr "" - -#: ../../content/developer/reference/iot.rst:42 -msgid "Supported devices will appear both on the IoT Box Homepage that you can access through its IP address and in the IoT module of the connected Odoo instance." -msgstr "" - -#: ../../content/developer/reference/iot.rst:46 -msgid "Interface" -msgstr "" - -#: ../../content/developer/reference/iot.rst:48 -msgid "The role of the Interface is to maintain a list of devices connected through a determined connection type. Creating a new interface requires" -msgstr "" - -#: ../../content/developer/reference/iot.rst:51 -msgid "Extending the `Interface` class" -msgstr "" - -#: ../../content/developer/reference/iot.rst:52 -msgid "Setting the `connection_type` class attribute" -msgstr "" - -#: ../../content/developer/reference/iot.rst:53 -msgid "Implementing the `get_devices` method, that should return a dictionary containing data about each detected device. This data will be given as argument to the constructors and `supported` method of the Drivers." -msgstr "" - -#: ../../content/developer/reference/iot.rst:58 -msgid "Setting the `_loop_delay` attribute will modify the interval between calls to `get_devices`. By default, this interval is set to 3 seconds." -msgstr "" - -#: ../../content/developer/reference/iot.rst:75 -msgid "Driver" -msgstr "" - -#: ../../content/developer/reference/iot.rst:77 -msgid "Once the interface has retrieved the list of detected devices, it will loop through all of the Drivers that have the same `connection_type` attribute and test their respective `supported` method on all detected devices. If the supported method of a Driver returns `True`, an instance of this Driver will be created for the corresponding device." -msgstr "" - -#: ../../content/developer/reference/iot.rst:84 -msgid "`supported` methods of drivers are given a priority order. The `supported` method of a child class will always be tested before the one of its parent. This priority can be adjusted by modifying the `priority` attribute of the Driver." -msgstr "" - -#: ../../content/developer/reference/iot.rst:89 -msgid "Creating a new Driver requires:" -msgstr "" - -#: ../../content/developer/reference/iot.rst:91 -msgid "Extending `Driver`" -msgstr "" - -#: ../../content/developer/reference/iot.rst:92 -msgid "Setting the `connection_type` class attribute." -msgstr "" - -#: ../../content/developer/reference/iot.rst:93 -msgid "Setting the `device_type`, `device_connection` and `device_name` attributes." -msgstr "" - -#: ../../content/developer/reference/iot.rst:94 -msgid "Defining the `supported` method" -msgstr "" - -#: ../../content/developer/reference/iot.rst:114 -msgid "Communicate With Devices" -msgstr "" - -#: ../../content/developer/reference/iot.rst:116 -msgid "Once your new device is detected and appears in the IoT module, the next step is to communicate with it. Since the box only has a local IP address, it can only be reached from the same local network. Communication, therefore, needs to happen on the browser-side, in JavaScript." -msgstr "" - -#: ../../content/developer/reference/iot.rst:121 -msgid "The process depends on the direction of the communication: - From the browser to the box, through `Actions`_ - From the box to the browser, through `Longpolling`_" -msgstr "" - -#: ../../content/developer/reference/iot.rst:125 -msgid "Both channels are accessed from the same JS object, the `DeviceProxy`, which is instantiated using the IP of the IoT Box and the device identifier." -msgstr "" - -#: ../../content/developer/reference/iot.rst:140 -msgid "Actions are used to tell a selected device to execute a specific action, such as taking a picture, printing a receipt, etc." -msgstr "" - -#: ../../content/developer/reference/iot.rst:144 -msgid "It must be noted that no “answer” will be sent by the box on this route, only the request status. The answer to the action, if any, has to be retrieved via the longpolling." -msgstr "" - -#: ../../content/developer/reference/iot.rst:148 -msgid "An action can be performed on the DeviceProxy Object." -msgstr "" - -#: ../../content/developer/reference/iot.rst:154 -msgid "In your driver, define an `action` method that will be executed when called from an Odoo module. It takes the data given during the call as argument." -msgstr "" - -#: ../../content/developer/reference/iot.rst:163 -msgid "Longpolling" -msgstr "" - -#: ../../content/developer/reference/iot.rst:165 -msgid "When any module in Odoo wants to read data from a specific device, it creates a listener identified by the IP/domain of the box and the device identifier and passes it a callback function to be called every time the device status changes. The callback is called with the new data as argument." -msgstr "" - -#: ../../content/developer/reference/iot.rst:178 -msgid "In the Driver, an event is released by calling the `device_changed` function from the `event_manager`. All callbacks set on the listener will then be called with `self.data` as argument." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:6 -msgid "Javascript Cheatsheet" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:8 -msgid "There are many ways to solve a problem in JavaScript, and in Odoo. However, the Odoo framework was designed to be extensible (this is a pretty big constraint), and some common problems have a nice standard solution. The standard solution has probably the advantage of being easy to understand for an odoo developers, and will probably keep working when Odoo is modified." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:14 -msgid "This document tries to explain the way one could solve some of these issues. Note that this is not a reference. This is just a random collection of recipes, or explanations on how to proceed in some cases." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:19 -msgid "First of all, remember that the first rule of customizing odoo with JS is: *try to do it in python*. This may seem strange, but the python framework is quite extensible, and many behaviours can be done simply with a touch of xml or python. This has usually a lower cost of maintenance than working with JS:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:24 -msgid "the JS framework tends to change more, so JS code needs to be more frequently updated" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:26 -msgid "it is often more difficult to implement a customized behaviour if it needs to communicate with the server and properly integrate with the javascript framework. There are many small details taken care by the framework that customized code needs to replicate. For example, responsiveness, or updating the url, or displaying data without flickering." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:33 -msgid "This document does not really explain any concepts. This is more a cookbook. For more details, please consult the javascript reference page (see :doc:`javascript_reference`)" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:38 -msgid "Creating a new field widget" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:40 -msgid "This is probably a really common usecase: we want to display some information in a form view in a really specific (maybe business dependent) way. For example, assume that we want to change the text color depending on some business condition." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:44 -msgid "This can be done in three steps: creating a new widget, registering it in the field registry, then adding the widget to the field in the form view" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:58 -msgid "creating a new widget:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:48 -msgid "This can be done by extending a widget:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:68 -msgid "registering it in the field registry:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:61 -msgid "The web client needs to know the mapping between a widget name and its actual class. This is done by a registry:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:77 -msgid "adding the widget in the form view" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:75 -msgid "Note that only the form, list and kanban views use this field widgets registry. These views are tightly integrated, because the list and kanban views can appear inside a form view)." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:80 -msgid "Modifying an existing field widget" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:82 -msgid "Another use case is that we want to modify an existing field widget. For example, the voip addon in odoo need to modify the FieldPhone widget to add the possibility to easily call the given number on voip. This is done by *including* the FieldPhone widget, so there is no need to change any existing form view." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:87 -msgid "Field Widgets (instances of (subclass of) AbstractField) are like every other widgets, so they can be monkey patched. This looks like this:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:109 -msgid "Note that there is no need to add the widget to the registry, since it is already registered." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:113 -msgid "Modifying a main widget from the interface" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:115 -msgid "Another common usecase is the need to customize some elements from the user interface. For example, adding a message in the home menu. The usual process in this case is again to *include* the widget. This is the only way to do it, since there are no registries for those widgets." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:120 -msgid "This is usually done with code looking like this:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:136 -msgid "Creating a new view (from scratch)" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:138 -msgid "Creating a new view is a more advanced topic. This cheatsheet will only highlight the steps that will probably need to be done (in no particular order):" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:141 -msgid "adding a new view type to the field ``type`` of ``ir.ui.view``::" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:148 -msgid "adding the new view type to the field ``view_mode`` of ``ir.actions.act_window.view``::" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:179 -msgid "creating the four main pieces which makes a view (in JavaScript):" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:157 -msgid "we need a view (a subclass of ``AbstractView``, this is the factory), a renderer (from ``AbstractRenderer``), a controller (from ``AbstractController``) and a model (from ``AbstractModel``). I suggest starting by simply extending the superclasses:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:189 -msgid "adding the view to the registry:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:182 -msgid "As usual, the mapping between a view type and the actual class needs to be updated:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:196 -msgid "implementing the four main classes:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:192 -msgid "The ``View`` class needs to parse the ``arch`` field and setup the other three classes. The ``Renderer`` is in charge of representing the data in the user interface, the ``Model`` is supposed to talk to the server, to load data and process it. And the ``Controller`` is there to coordinate, to talk to the web client, ..." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:210 -msgid "creating some views in the database:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:213 -msgid "Customizing an existing view" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:215 -msgid "Assume we need to create a custom version of a generic view. For example, a kanban view with some extra *ribbon-like* widget on top (to display some specific custom information). In that case, this can be done with 3 steps: extend the kanban view (which also probably mean extending controllers/renderers and/or models), then registering the view in the view registry, and finally, using the view in the kanban arch (a specific example is the helpdesk dashboard)." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:245 -msgid "extending a view:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:223 -msgid "Here is what it could look like:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:254 -msgid "adding it to the view registry:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:248 -msgid "as usual, we need to inform the web client of the mapping between the name of the views and the actual class." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:273 -msgid "using it in an actual view:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:257 -msgid "we now need to inform the web client that a specific ``ir.ui.view`` needs to use our new class. Note that this is a web client specific concern. From the point of view of the server, we still have a kanban view. The proper way to do this is by using a special attribute ``js_class`` (which will be renamed someday into ``widget``, because this is really not a good name) on the root node of the arch:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:277 -msgid "Note: you can change the way the view interprets the arch structure. However, from the server point of view, this is still a view of the same base type, subjected to the same rules (rng validation, for example). So, your views still need to have a valid arch field." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:283 -msgid "Promises and asynchronous code" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:285 -msgid "For a very good and complete introduction to promises, please read this excellent article https://github.com/getify/You-Dont-Know-JS/blob/1st-ed/async%20%26%20performance/ch3.md" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:288 -msgid "Creating new Promises" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:307 -msgid "turn a constant into a promise" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:290 -msgid "There are 2 static functions on Promise that create a resolved or rejected promise based on a constant:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:306 -msgid "Note that even if the promises are created already resolved or rejected, the `then` or `catch` handlers will still be called asynchronously." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:320 -msgid "based on an already asynchronous code" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:310 -msgid "Suppose that in a function you must do a rpc, and when it is completed set the result on this. The `this._rpc` is a function that returns a `Promise`." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:350 -msgid "for callback based function" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:323 -msgid "Suppose that you were using a function `this.close` that takes as parameter a callback that is called when the closing is finished. Now suppose that you are doing that in a method that must send a promise that is resolved when the closing is finished." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:336 -msgid "line 2: we save the `this` into a variable so that in an inner function, we can access the scope of our component" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:338 -msgid "line 3: we create and return a new promise. The constructor of a promise takes a function as parameter. This function itself has 2 parameters that we called here `resolve` and `reject`" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:338 -msgid "`resolve` is a function that, when called, puts the promise in the resolved state." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:339 -msgid "`reject` is a function that, when called, puts the promise in the rejected state. We do not use reject here and it can be omitted." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:340 -msgid "line 4: we are calling the function close on our object. It takes a function as parameter (the callback) and it happens that resolve is already a function, so we can pass it directly. To be clearer, we could have written:" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:366 -msgid "creating a promise generator (calling one promise after the other *in sequence* and waiting for the last one)" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:353 -msgid "Suppose that you need to loop over an array, do an operation *in sequence* and resolve a promise when the last operation is done." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:367 -msgid "This way, the promise you return is effectively the last promise." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:382 -msgid "creating a promise, then resolving it outside the scope of its definition (anti-pattern)" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:369 -msgid "we do not recommend using this, but sometimes it is useful. Think carefully for alternatives first..." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:385 -msgid "Waiting for Promises" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:404 -msgid "waiting for a number of Promises" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:387 -msgid "if you have multiple promises that all need to be waited, you can convert them into a single promise that will be resolved when all the promises are resolved using Promise.all(arrayOfPromises)." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:419 -msgid "waiting for a part of a promise chain, but not another part" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:407 -msgid "If you have an asynchronous process that you want to wait to do something, but you also want to return to the caller before that something is done." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:422 -msgid "Error handling" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:446 -msgid "in general in promises" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:425 -msgid "The general idea is that a promise should not be rejected for control flow, but should only be rejected for errors. When that is the case, you would have multiple resolutions of your promise with, for instance status codes that you would have to check in the `then` handlers and a single `catch` handler at the end of the promise chain." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:486 -msgid "in Odoo specifically" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:449 -msgid "In Odoo, it happens that we use promise rejection for control flow, like in mutexes and other concurrency primitives defined in module `web.concurrency` We also want to execute the catch for *business* reasons, but not when there is a coding error in the definition of the promise or of the handlers. For this, we have introduced the concept of `guardedCatch`. It is called like `catch` but not when the rejected reason is an error" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:489 -msgid "Testing asynchronous code" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:543 -msgid "using promises in tests" -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:492 -msgid "In the tests code, we support the latest version of Javascript, including primitives like `async` and `await`. This makes using and waiting for promises very easy. Most helper methods also return a promise (either by being marked `async` or by returning a promise directly." -msgstr "" - -#: ../../content/developer/reference/javascript_cheatsheet.rst:544 -msgid "as you can see, the nicer form is to use `async/await` as it is clearer and shorter to write." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:8 -msgid "Javascript Reference" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:10 -msgid "This document presents the Odoo Javascript framework. This framework is not a large application in term of lines of code, but it is quite generic, because it is basically a machine to turn a declarative interface description into a live application, able to interact with every model and records in the database. It is even possible to use the web client to modify the interface of the web client." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:18 -#: ../../content/developer/webservices/iap.rst:26 -msgid "Overview" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:20 -msgid "The Javascript framework is designed to work with three main use cases:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:22 -msgid "the *web client*: this is the private web application, where one can view and edit business data. This is a single page application (the page is never reloaded, only the new data is fetched from the server whenever it is needed)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:25 -msgid "the *website*: this is the public part of Odoo. It allows an unidentified user to browse some content, to shop or to perform many actions, as a client. This is a classical website: various routes with controllers and some javascript to make it work." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:29 -msgid "the *point of sale*: this is the interface for the point of sale. It is a specialized single page application." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:32 -msgid "Some javascript code is common to these three use cases, and is bundled together (see below in the assets section). This document will focus mostly on the web client design." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:37 -msgid "Web client" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:40 -msgid "Single Page Application" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:42 -msgid "In short, the *webClient*, instance of *WebClient* is the root component of the whole user interface. Its responsibility is to orchestrate all various subcomponents, and to provide services, such as rpcs, local storage and more." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:46 -msgid "In runtime, the web client is a single page application. It does not need to request a full page from the server each time the user perform an action. Instead, it only requests what it needs, and then replaces/updates the view. Also, it manages the url: it is kept in sync with the web client state." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:51 -msgid "It means that while a user is working on Odoo, the web client class (and the action manager) actually creates and destroys many sub components. The state is highly dynamic, and each widget could be destroyed at any time." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:56 -msgid "Overview of web client JS code" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:58 -msgid "Here, we give a very quick overview on the web client code, in the *web/static/src/js* addon. Note that it is deliberately not exhaustive. We only cover the most important files/folders." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:62 -msgid "*boot.js*: this is the file that defines the module system. It needs to be loaded first." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:64 -msgid "*core/*: this is a collection of lower level building blocks. Notably, it contains the class system, the widget system, concurrency utilities, and many other class/functions." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:67 -msgid "*chrome/*: in this folder, we have most large widgets which make up most of the user interface." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:69 -msgid "*chrome/abstract_web_client.js* and *chrome/web_client.js*: together, these files define the WebClient widget, which is the root widget for the web client." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:71 -msgid "*chrome/action_manager.js*: this is the code that will convert an action into a widget (for example a kanban or a form view)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:73 -msgid "*chrome/search_X.js* all these files define the search view (it is not a view in the point of view of the web client, only from the server point of view)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:75 -msgid "*fields*: all main view field widgets are defined here" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:76 -msgid "*views*: this is where the views are located" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:79 -msgid "Assets Management" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:81 -msgid "Managing assets in Odoo is not as straightforward as it is in some other apps. One of the reason is that we have a variety of situations where some, but not all the assets are required. For example, the needs of the web client, the point of sale, the website or even the mobile application are different. Also, some assets may be large, but are seldom needed. In that case, we sometimes want them to be loaded lazily." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:88 -msgid "The main idea is that we define a set of *bundles* in xml. A bundle is here defined as a collection of files (javascript, css, scss). In Odoo, the most important bundles are defined in the file *addons/web/views/webclient_templates.xml*. It looks like this:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:103 -msgid "The files in a bundle can then be inserted into a template by using the *t-call-assets* directive:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:111 -msgid "Here is what happens when a template is rendered by the server with these directives:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:113 -msgid "all the *scss* files described in the bundle are compiled into css files. A file named *file.scss* will be compiled in a file named *file.scss.css*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:116 -msgid "if we are in *debug=assets* mode" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:118 -msgid "the *t-call-assets* directive with the *t-js* attribute set to false will be replaced by a list of stylesheet tags pointing to the css files" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:121 -msgid "the *t-call-assets* directive with the *t-css* attribute set to false will be replaced by a list of script tags pointing to the js files" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:124 -msgid "if we are not in *debug=assets* mode" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:126 -msgid "the css files will be concatenated and minified, then a stylesheet tag is generated" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:129 -msgid "the js files are concatenated and minified, then a script tag is generated" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:131 -msgid "Note that the assets files are cached, so in theory, a browser should only load them once." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:135 -msgid "Main bundles" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:136 -msgid "When the Odoo server is started, it checks the timestamp of each file in a bundle, and if necessary, will create/recreate the corresponding bundles." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:139 -msgid "Here are some important bundles that most developers will need to know:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:141 -msgid "*web.assets_common*: this bundle contains most assets which are common to the web client, the website, and also the point of sale. This is supposed to contain lower level building blocks for the odoo framework. Note that it contains the *boot.js* file, which defines the odoo module system." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:146 -msgid "*web.assets_backend*: this bundle contains the code specific to the web client (notably the web client/action manager/views)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:149 -msgid "*web.assets_frontend*: this bundle is about all that is specific to the public website: ecommerce, forum, blog, event management, ..." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:154 -msgid "Adding files in an asset bundle" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:156 -msgid "The proper way to add a file located in *addons/web* to a bundle is simple: it is just enough to add a *script* or a *stylesheet* tag to the bundle in the file *webclient_templates.xml*. But when we work in a different addon, we need to add a file from that addon. In that case, it should be done in three steps:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:161 -msgid "add a *assets.xml* file in the *views/* folder" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:162 -msgid "add the string 'views/assets.xml' in the 'data' key in the manifest file" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:163 -msgid "create an inherited view of the desired bundle, and add the file(s) with an xpath expression. For example," -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:178 -msgid "Note that the files in a bundle are all loaded immediately when the user loads the odoo web client. This means that the files are transferred through the network everytime (except when the browser cache is active). In some cases, it may be better to lazyload some assets. For example, if a widget requires a large library, and that widget is not a core part of the experience, then it may be a good idea to only load the library when the widget is actually created. The widget class has actually builtin support just for this use case. (see section :ref:`reference/javascript_reference/qweb`)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:188 -msgid "What to do if a file is not loaded/updated" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:190 -msgid "There are many different reasons why a file may not be properly loaded. Here are a few things you can try to solve the issue:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:193 -msgid "once the server is started, it does not know if an asset file has been modified. So, you can simply restart the server to regenerate the assets." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:195 -msgid "check the console (in the dev tools, usually opened with F12) to make sure there are no obvious errors" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:197 -msgid "try to add a console.log at the beginning of your file (before any module definition), so you can see if a file has been loaded or not" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:199 -msgid "in the user interface, in debug mode (INSERT LINK HERE TO DEBUG MODE), there is an option to force the server to update its assets files." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:201 -msgid "use the *debug=assets* mode. This will actually bypass the asset bundles (note that it does not actually solve the issue. The server still uses outdated bundles)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:203 -msgid "finally, the most convenient way to do it, for a developer, is to start the server with the *--dev=all* option. This activates the file watcher options, which will automatically invalidate assets when necessary. Note that it does not work very well if the OS is Windows." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:207 -msgid "remember to refresh your page!" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:208 -msgid "or maybe to save your code file..." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:211 -msgid "Once an asset file has been recreated, you need to refresh the page, to reload the proper files (if that does not work, the files may be cached)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:216 -msgid "Javascript Module System" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:218 -msgid "Once we are able to load our javascript files into the browser, we need to make sure they are loaded in the correct order. In order to do that, Odoo has defined a small module system (located in the file *addons/web/static/src/js/boot.js*, which needs to be loaded first)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:223 -msgid "The Odoo module system, inspired by AMD, works by defining the function *define* on the global odoo object. We then define each javascript module by calling that function. In the Odoo framework, a module is a piece of code that will be executed as soon as possible. It has a name and potentially some dependencies. When its dependencies are loaded, a module will then be loaded as well. The value of the module is then the return value of the function defining the module." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:231 -msgid "As an example, it may look like this:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:256 -msgid "An alternative way to define a module is to give explicitly a list of dependencies in the second argument." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:271 -msgid "If some dependencies are missing/non ready, then the module will simply not be loaded. There will be a warning in the console after a few seconds." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:274 -msgid "Note that circular dependencies are not supported. It makes sense, but it means that one needs to be careful." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:278 -msgid "Defining a module" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:280 -msgid "The *odoo.define* method is given three arguments:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:282 -msgid "*moduleName*: the name of the javascript module. It should be a unique string. The convention is to have the name of the odoo addon followed by a specific description. For example, 'web.Widget' describes a module defined in the *web* addon, which exports a *Widget* class (because the first letter is capitalized)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:287 -msgid "If the name is not unique, an exception will be thrown and displayed in the console." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:290 -msgid "*dependencies*: the second argument is optional. If given, it should be a list of strings, each corresponding to a javascript module. This describes the dependencies that are required to be loaded before the module is executed. If the dependencies are not explicitly given here, then the module system will extract them from the function by calling toString on it, then using a regexp to find all *require* statements." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:308 -msgid "finally, the last argument is a function which defines the module. Its return value is the value of the module, which may be passed to other modules requiring it. Note that there is a small exception for asynchronous modules, see the next section." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:313 -msgid "If an error happens, it will be logged (in debug mode) in the console:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:315 -msgid "``Missing dependencies``: These modules do not appear in the page. It is possible that the JavaScript file is not in the page or that the module name is wrong" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:318 -msgid "``Failed modules``: A javascript error is detected" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:320 -msgid "``Rejected modules``: The module returns a rejected Promise. It (and its dependent modules) is not loaded." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:323 -msgid "``Rejected linked modules``: Modules who depend on a rejected module" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:325 -msgid "``Non loaded modules``: Modules who depend on a missing or a failed module" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:331 -msgid "Asynchronous modules" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:333 -msgid "It can happen that a module needs to perform some work before it is ready. For example, it could do a rpc to load some data. In that case, the module can simply return a promise. In that case, the module system will simply wait for the promise to complete before registering the module." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:353 -msgid "Best practices" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:355 -msgid "remember the convention for a module name: *addon name* suffixed with *module name*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:357 -msgid "declare all your dependencies at the top of the module. Also, they should be sorted alphabetically by module name. This makes it easier to understand your module." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:359 -msgid "declare all exported values at the end" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:360 -msgid "try to avoid exporting too many things from one module. It is usually better to simply export one thing in one (small/smallish) module." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:362 -msgid "asynchronous modules can be used to simplify some use cases. For example, the *web.dom_ready* module returns a promise which will be resolved when the dom is actually ready. So, another module that needs the DOM could simply have a `require('web.dom_ready')` statement somewhere, and the code will only be executed when the DOM is ready." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:367 -msgid "try to avoid defining more than one module in one file. It may be convenient in the short term, but this is actually harder to maintain." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:372 -msgid "Class System" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:374 -msgid "Odoo was developed before ECMAScript 6 classes were available. In Ecmascript 5, the standard way to define a class is to define a function and to add methods on its prototype object. This is fine, but it is slightly complex when we want to use inheritance, mixins." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:379 -msgid "For these reasons, Odoo decided to use its own class system, inspired by John Resig. The base Class is located in *web.Class*, in the file *class.js*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:383 -msgid "Creating a subclass" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:385 -msgid "Let us discuss how classes are created. The main mechanism is to use the *extend* method (this is more or less the equivalent of *extend* in ES6 classes)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:407 -msgid "In this example, the *init* function is the constructor. It will be called when an instance is created. Making an instance is done by using the *new* keyword." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:413 -msgid "It is convenient to be able to inherit an existing class. This is simply done by using the *extend* method on the superclass. When a method is called, the framework will secretly rebind a special method: *_super* to the currently called method. This allows us to use *this._super* whenever we need to call a parent method." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:438 -msgid "Mixins" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:440 -msgid "The odoo Class system does not support multiple inheritance, but for those cases when we need to share some behaviour, we have a mixin system: the *extend* method can actually take an arbitrary number of arguments, and will combine all of them in the new class." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:460 -msgid "In this example, the *Hamster* class is a subclass of Animal, but it also mix the DanceMixin in." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:465 -msgid "Patching an existing class" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:467 -msgid "It is not common, but we sometimes need to modify another class *in place*. The goal is to have a mechanism to change a class and all future/present instances. This is done by using the *include* method:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:483 -msgid "This is obviously a dangerous operation and should be done with care. But with the way Odoo is structured, it is sometimes necessary in one addon to modify the behavior of a widget/class defined in another addon. Note that it will modify all instances of the class, even if they have already been created." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:490 -msgid "Widgets" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:492 -msgid "The *Widget* class is really an important building block of the user interface. Pretty much everything in the user interface is under the control of a widget. The Widget class is defined in the module *web.Widget*, in *widget.js*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:496 -msgid "In short, the features provided by the Widget class include:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:498 -msgid "parent/child relationships between widgets (*PropertiesMixin*)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:499 -msgid "extensive lifecycle management with safety features (e.g. automatically destroying children widgets during the destruction of a parent)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:501 -msgid "automatic rendering with :ref:`qweb `" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:502 -msgid "various utility functions to help interacting with the outside environment." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:504 -msgid "Here is an example of a basic counter widget:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:525 -msgid "For this example, assume that the template *some.template* (and is properly loaded: the template is in a file, which is properly defined in the *qweb* key in the module manifest) is given by:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:536 -msgid "This example widget can be used in the following manner:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:545 -msgid "This example illustrates a few of the features of the *Widget* class, including the event system, the template system, the constructor with the initial *parent* argument." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:549 -msgid "Widget Lifecycle" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:551 -msgid "Like many component systems, the widget class has a well defined lifecycle. The usual lifecycle is the following: *init* is called, then *willStart*, then the rendering takes place, then *start* and finally *destroy*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:557 -msgid "this is the constructor. The init method is supposed to initialize the base state of the widget. It is synchronous and can be overridden to take more parameters from the widget's creator/parent" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:0 -#: ../../content/developer/reference/javascript_reference.rst:0 -#: ../../content/developer/reference/javascript_reference.rst:0 -#: ../../content/developer/reference/mobile.rst:0 -#: ../../content/developer/reference/mobile.rst:0 -#: ../../content/developer/reference/mobile.rst:0 -#: ../../content/developer/reference/mobile.rst:0 -#: ../../content/developer/reference/mobile.rst:0 -#: ../../content/developer/reference/qweb.rst:0 -msgid "Arguments" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:561 -msgid "the new widget's parent, used to handle automatic destruction and event propagation. Can be ``null`` for the widget to have no parent." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:568 -msgid "this method will be called once by the framework when a widget is created and in the process of being appended to the DOM. The *willStart* method is a hook that should return a promise. The JS framework will wait for this promise to complete before moving on to the rendering step. Note that at this point, the widget does not have a DOM root element. The *willStart* hook is mostly useful to perform some asynchronous work, such as fetching data from the server" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:577 -msgid "This step is automatically done by the framework. What happens is that the framework checks if a template key is defined on the widget. If that is the case, then it will render that template with the *widget* key bound to the widget in the rendering context (see the example above: we use *widget.count* in the QWeb template to read the value from the widget). If no template is defined, we read the *tagName* key and create a corresponding DOM element. When the rendering is done, we set the result as the $el property of the widget. After this, we automatically bind all events in the events and custom_events keys." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:589 -msgid "when the rendering is complete, the framework will automatically call the *start* method. This is useful to perform some specialized post-rendering work. For example, setting up a library." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:593 -msgid "Must return a promise to indicate when its work is done." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:0 -#: ../../content/developer/reference/javascript_reference.rst:0 -#: ../../content/developer/reference/javascript_reference.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mobile.rst:0 -#: ../../content/developer/reference/mobile.rst:0 -#: ../../content/developer/reference/qweb.rst:0 -#: ../../content/developer/webservices/iap.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -msgid "Returns" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:595 -msgid "promise" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:599 -msgid "This is always the final step in the life of a widget. When a widget is destroyed, we basically perform all necessary cleanup operations: removing the widget from the component tree, unbinding all events, ..." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:603 -msgid "Automatically called when the widget's parent is destroyed, must be called explicitly if the widget has no parent or if it is removed but its parent remains." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:607 -msgid "Note that the willStart and start method are not necessarily called. A widget can be created (the *init* method will be called) and then destroyed (*destroy* method) without ever having been appended to the DOM. If that is the case, the willStart and start will not even be called." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:613 -msgid "Widget API" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:617 -msgid "Used if the widget has no template defined. Defaults to ``div``, will be used as the tag name to create the DOM element to set as the widget's DOM root. It is possible to further customize this generated DOM root with the following attributes:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:625 -msgid "Used to generate an ``id`` attribute on the generated DOM root. Note that this is rarely needed, and is probably not a good idea if a widget can be used more than once." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:631 -msgid "Used to generate a ``class`` attribute on the generated DOM root. Note that it can actually contain more than one css class: *'some-class other-class'*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:637 -msgid "Mapping (object literal) of attribute names to attribute values. Each of these k:v pairs will be set as a DOM attribute on the generated DOM root." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:643 -msgid "raw DOM element set as root to the widget (only available after the start lifecycle method)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:648 -msgid "jQuery wrapper around :attr:`~Widget.el`. (only available after the start lifecycle method)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:653 -msgid "Should be set to the name of a :ref:`QWeb template `. If set, the template will be rendered after the widget has been initialized but before it has been started. The root element generated by the template will be set as the DOM root of the widget." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:660 -msgid "List of paths to xml files that need to be loaded before the widget can be rendered. This will not induce loading anything that has already been loaded. This is useful when you want to load your templates lazily, or if you want to share a widget between the website and the web client interface." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:674 -msgid "Events are a mapping of an event selector (an event name and an optional CSS selector separated by a space) to a callback. The callback can be the name of a widget's method or a function object. In either case, the ``this`` will be set to the widget:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:688 -msgid "The selector is used for jQuery's event delegation, the callback will only be triggered for descendants of the DOM root matching the selector. If the selector is left out (only an event name is specified), the event will be set directly on the widget's DOM root." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:694 -msgid "Note: the use of an inline function is discouraged, and will probably be removed sometimes in the future." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:699 -msgid "this is almost the same as the *events* attribute, but the keys are arbitrary strings. They represent business events triggered by some sub widgets. When an event is triggered, it will 'bubble up' the widget tree (see the section on component communication for more details)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:706 -msgid "``true`` if the widget is being or has been destroyed, ``false`` otherwise" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:711 -msgid "Applies the CSS selector specified as parameter to the widget's DOM root:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:718 -msgid "is functionally identical to:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:724 -msgid "CSS selector" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:725 -msgid "jQuery object" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:727 -msgid "this helper method is similar to ``Backbone.View.$``" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:731 -msgid "Re-sets the widget's DOM root to the provided element, also handles re-setting the various aliases of the DOM root as well as unsetting and re-setting delegated events." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:735 -msgid "a DOM element or jQuery object to set as the widget's DOM root" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:740 -msgid "Inserting a widget in the DOM" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:744 -msgid "Renders the widget and inserts it as the last child of the target, uses `.appendTo()`_" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:749 -msgid "Renders the widget and inserts it as the first child of the target, uses `.prependTo()`_" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:754 -msgid "Renders the widget and inserts it as the preceding sibling of the target, uses `.insertAfter()`_" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:759 -msgid "Renders the widget and inserts it as the following sibling of the target, uses `.insertBefore()`_" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:762 -msgid "All of these methods accept whatever the corresponding jQuery method accepts (CSS selectors, DOM nodes or jQuery objects). They all return a promise and are charged with three tasks:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:766 -msgid "rendering the widget's root element via :func:`~Widget.renderElement`" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:767 -msgid "inserting the widget's root element in the DOM using whichever jQuery method they match" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:769 -msgid "starting the widget, and returning the result of starting it" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:772 -msgid "Widget Guidelines" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:774 -msgid "Identifiers (``id`` attribute) should be avoided. In generic applications and modules, ``id`` limits the re-usability of components and tends to make code more brittle. Most of the time, they can be replaced with nothing, classes or keeping a reference to a DOM node or jQuery element." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:779 -msgid "If an ``id`` is absolutely necessary (because a third-party library requires one), the id should be partially generated using ``_.uniqueId()`` e.g.:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:786 -msgid "Avoid predictable/common CSS class names. Class names such as \"content\" or \"navigation\" might match the desired meaning/semantics, but it is likely an other developer will have the same need, creating a naming conflict and unintended behavior. Generic class names should be prefixed with e.g. the name of the component they belong to (creating \"informal\" namespaces, much as in C or Objective-C)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:793 -msgid "Global selectors should be avoided. Because a component may be used several times in a single page (an example in Odoo is dashboards), queries should be restricted to a given component's scope. Unfiltered selections such as ``$(selector)`` or ``document.querySelectorAll(selector)`` will generally lead to unintended or incorrect behavior. Odoo Web's :class:`~Widget` has an attribute providing its DOM root (:attr:`~Widget.$el`), and a shortcut to select nodes directly (:func:`~Widget.$`)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:802 -msgid "More generally, never assume your components own or controls anything beyond its own personal :attr:`~Widget.$el` (so, avoid using a reference to the parent widget)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:806 -msgid "Html templating/rendering should use QWeb unless absolutely trivial." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:808 -msgid "All interactive components (components displaying information to the screen or intercepting DOM events) must inherit from :class:`~Widget` and correctly implement and use its API and life cycle." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:812 -msgid "Make sure to wait for start to be finished before using $el e.g.:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:844 -msgid "QWeb Template Engine" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:846 -msgid "The web client uses the :doc:`qweb` template engine to render widgets (unless they override the *renderElement* method to do something else). The Qweb JS template engine is based on XML, and is mostly compatible with the python implementation." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:851 -msgid "Now, let us explain how the templates are loaded. Whenever the web client starts, a rpc is made to the */web/webclient/qweb* route. The server will then return a list of all templates defined in data files for each installed modules. The correct files are listed in the *qweb* entry in each module manifest." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:856 -msgid "The web client will wait for that list of template to be loaded, before starting its first widget." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:859 -msgid "This mechanism works quite well for our needs, but sometimes, we want to lazy load a template. For example, imagine that we have a widget which is rarely used. In that case, maybe we prefer to not load its template in the main file, in order to make the web client slightly lighter. In that case, we can use the *xmlDependencies* key of the Widget:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:877 -msgid "With this, the *Counter* widget will load the xmlDependencies files in its *willStart* method, so the template will be ready when the rendering is performed." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:882 -msgid "Event system" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:884 -msgid "There are currently two event systems supported by Odoo: a simple system which allows adding listeners and triggering events, and a more complete system that also makes events 'bubble up'." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:888 -msgid "Both of these event systems are implemented in the *EventDispatcherMixin*, in the file *mixins.js*. This mixin is included in the *Widget* class." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:892 -msgid "Base Event system" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:894 -msgid "This event system was historically the first. It implements a simple bus pattern. We have 4 main methods:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:897 -msgid "*on*: this is used to register a listener on an event." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:898 -msgid "*off*: useful to remove events listener." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:899 -msgid "*once*: this is used to register a listener that will only be called once." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:900 -msgid "*trigger*: trigger an event. This will cause each listeners to be called." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:902 -msgid "Here is an example on how this event system could be used:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:927 -msgid "the use of this event system is discouraged, we plan to replace each *trigger* method by the *trigger_up* method from the extended event system" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:931 -msgid "Extended Event System" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:933 -msgid "The custom event widgets is a more advanced system, which mimic the DOM events API. Whenever an event is triggered, it will 'bubble up' the component tree, until it reaches the root widget, or is stopped." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:937 -msgid "*trigger_up*: this is the method that will create a small *OdooEvent* and dispatch it in the component tree. Note that it will start with the component that triggered the event" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:940 -msgid "*custom_events*: this is the equivalent of the *event* dictionary, but for odoo events." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:943 -msgid "The OdooEvent class is very simple. It has three public attributes: *target* (the widget that triggered the event), *name* (the event name) and *data* (the payload). It also has 2 methods: *stopPropagation* and *is_stopped*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:947 -msgid "The previous example can be updated to use the custom event system:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:974 -msgid "Registries" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:976 -msgid "A common need in the Odoo ecosystem is to extend/change the behaviour of the base system from the outside (by installing an application, i.e. a different module). For example, one may need to add a new widget type in some views. In that case, and many others, the usual process is to create the desired component, then add it to a registry (registering step), to make the rest of the web client aware of its existence." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:983 -msgid "There are a few registries available in the system:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:998 -msgid "field registry (exported by :js:data:`web.field_registry`)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:986 -msgid "The field registry contains all field widgets known to the web client. Whenever a view (typically form or list/kanban) needs a field widget, this is where it will look. A typical use case look like this:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:998 -msgid "Note that each value should be a subclass of *AbstractField*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1003 -msgid "view registry" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1001 -msgid "This registry contains all JS views known to the web client (and in particular, the view manager). Each value of this registry should be a subclass of *AbstractView*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1010 -msgid "action registry" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1006 -msgid "We keep track of all client actions in this registry. This is where the action manager looks up whenever it needs to create a client action. In version 11, each value should simply be a subclass of *Widget*. However, in version 12, the values are required to be *AbstractAction*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1013 -msgid "Communication between widgets" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1015 -msgid "There are many ways to communicate between components." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1023 -msgid "From a parent to its child" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1018 -msgid "This is a simple case. The parent widget can simply call a method on its child:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1050 -msgid "From a widget to its parent/some ancestor" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1026 -msgid "In this case, the widget's job is simply to notify its environment that something happened. Since we do not want the widget to have a reference to its parent (this would couple the widget with its parent's implementation), the best way to proceed is usually to trigger an event, which will bubble up the component tree, by using the ``trigger_up`` method:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1036 -msgid "This event will be triggered on the widget, then will bubble up and be eventually caught by some upstream widget:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1081 -msgid "Cross component" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1053 -msgid "Cross component communication can be achieved by using a bus. This is not the preferred form of communication, because it has the disadvantage of making the code harder to maintain. However, it has the advantage of decoupling the components. In that case, this is simply done by triggering and listening to events on a bus. For example:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1084 -msgid "Services" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1086 -msgid "In version 11.0, we introduced the notion of *service*. The main idea is to give to sub components a controlled way to access their environment, in a way that allow the framework enough control, and which is testable." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1090 -msgid "The service system is organized around three ideas: services, service providers and widgets. The way it works is that widgets trigger (with *trigger_up*) events, these events bubble up to a service provider, which will ask a service to perform a task, then maybe return an answer." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1096 -#: ../../content/developer/webservices/iap.rst:354 -msgid "Service" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1098 -msgid "A service is an instance of the *AbstractService* class. It basically only has a name and a few methods. Its job is to perform some work, typically something depending on the environment." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1102 -msgid "For example, we have the *ajax* service (job is to perform a rpc), the *localStorage* (interact with the browser local storage) and many others." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1105 -msgid "Here is a simplified example on how the ajax service is implemented:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1118 -msgid "This service is named 'ajax' and define one method, *rpc*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1121 -msgid "Service Provider" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1123 -msgid "For services to work, it is necessary that we have a service provider ready to dispatch the custom events. In the *backend* (web client), this is done by the main web client instance. Note that the code for the service provider comes from the *ServiceProviderMixin*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1130 -msgid "Widget" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1132 -msgid "The widget is the part that requests a service. In order to do that, it simply triggers an event *call_service* (typically by using the helper function *call*). This event will bubble up and communicate the intent to the rest of the system." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1136 -msgid "In practice, some functions are so frequently called that we have some helpers functions to make them easier to use. For example, the *_rpc* method is a helper that helps making a rpc." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1152 -msgid "If a widget is destroyed, it will be detached from the main component tree and will not have a parent. In that case, the events will not bubble up, which means that the work will not be done. This is usually exactly what we want from a destroyed widget." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1158 -msgid "RPCs" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1160 -msgid "The rpc functionality is supplied by the ajax service. But most people will probably only interact with the *_rpc* helpers." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1163 -msgid "There are typically two usecases when working on Odoo: one may need to call a method on a (python) model (this goes through a controller *call_kw*), or one may need to directly call a controller (available on some route)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1167 -msgid "Calling a method on a python model:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1177 -msgid "Directly calling a controller:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1187 -msgid "Notifications" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1189 -msgid "The Odoo framework has a standard way to communicate various information to the user: notifications, which are displayed on the top right of the user interface." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1192 -msgid "There are two types of notifications:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1194 -msgid "*notification*: useful to display some feedback. For example, whenever a user unsubscribed to a channel." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1197 -msgid "*warning*: useful to display some important/urgent information. Typically most kind of (recoverable) errors in the system." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1200 -msgid "Also, notifications can be used to ask a question to the user without disturbing its workflow. Imagine a phone call received through VOIP: a sticky notification could be displayed with two buttons *Accept* and *Decline*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1205 -msgid "Notification system" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1207 -msgid "The notification system in Odoo is designed with the following components:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1209 -msgid "a *Notification* widget: this is a simple widget that is meant to be created and displayed with the desired information" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1212 -msgid "a *NotificationService*: a service whose responsibility is to create and destroy notifications whenever a request is done (with a custom_event). Note that the web client is a service provider." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1216 -msgid "a client action *display_notification*: this allows to trigger the display of a notification from python (e.g. in the method called when the user clicked on a button of type object)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1220 -msgid "two helper functions in *ServiceMixin*: *do_notify* and *do_warn*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1224 -msgid "Displaying a notification" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1225 -msgid "The most common way to display a notification is by using two methods that come from the *ServiceMixin*:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1241 -msgid "*do_notify(title, message, sticky, className)*:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1229 -msgid "Display a notification of type *notification*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1231 -#: ../../content/developer/reference/javascript_reference.rst:1246 -msgid "*title*: string. This will be displayed on the top as a title" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1233 -#: ../../content/developer/reference/javascript_reference.rst:1248 -msgid "*message*: string, the content of the notification" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1235 -#: ../../content/developer/reference/javascript_reference.rst:1250 -msgid "*sticky*: boolean, optional. If true, the notification will stay until the user dismisses it. Otherwise, the notification will be automatically closed after a short delay." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1239 -#: ../../content/developer/reference/javascript_reference.rst:1254 -msgid "*className*: string, optional. This is a css class name that will be automatically added to the notification. This could be useful for styling purpose, even though its use is discouraged." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1256 -msgid "*do_warn(title, message, sticky, className)*:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1244 -msgid "Display a notification of type *warning*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1258 -msgid "Here are two examples on how to use these methods:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1267 -msgid "Here an example in python:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1284 -msgid "Systray" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1286 -msgid "The Systray is the right part of the menu bar in the interface, where the web client displays a few widgets, such as a messaging menu." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1289 -msgid "When the SystrayMenu is created by the menu, it will look for all registered widgets and add them as a sub widget at the proper place." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1292 -msgid "There is currently no specific API for systray widgets. They are supposed to be simple widgets, and can communicate with their environment just like other widgets with the *trigger_up* method." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1297 -msgid "Adding a new Systray Item" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1299 -msgid "There is no systray registry. The proper way to add a widget is to add it to the class variable SystrayMenu.items." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1314 -msgid "Ordering" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1316 -msgid "Before adding the widget to himself, the Systray Menu will sort the items by a sequence property. If that property is not present on the prototype, it will use 50 instead. So, to position a systray item to be on the right, one can set a very high sequence number (and conversely, a low number to put it on the left)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1328 -msgid "Translation management" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1330 -msgid "Some translations are made on the server side (basically all text strings rendered or processed by the server), but there are strings in the static files that need to be translated. The way it currently works is the following:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1334 -msgid "each translatable string is tagged with the special function *_t* (available in the JS module *web.core*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1336 -msgid "these strings are used by the server to generate the proper PO files" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1337 -msgid "whenever the web client is loaded, it will call the route */web/webclient/translations*, which returns a list of all translatable terms" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1339 -msgid "in runtime, whenever the function *_t* is called, it will look up in this list in order to find a translation, and return it or the original string if none is found." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1343 -msgid "Note that translations are explained in more details, from the server point of view, in the document :doc:`translations`." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1346 -msgid "There are two important functions for the translations in javascript: *_t* and *_lt*. The difference is that *_lt* is lazily evaluated." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1365 -msgid "In this example, the *_lt* is necessary because the translations are not ready when the module is loaded." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1368 -msgid "Note that translation functions need some care. The string given in argument should not be dynamic." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1372 -msgid "Session" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1374 -msgid "There is a specific module provided by the web client which contains some information specific to the user current *session*. Some notable keys are" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1377 -msgid "uid: the current user ID (its ID as a *res.users*)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1378 -msgid "user_name: the user name, as a string" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1379 -msgid "the user context (user ID, language and timezone)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1380 -msgid "partner_id: the ID of the partner associated to the current user" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1381 -msgid "db: the name of the database currently being in use" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1384 -msgid "Adding information to the session" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1386 -msgid "When the /web route is loaded, the server will inject some session information in the template a script tag. The information will be read from the method *session_info* of the model *ir.http*. So, if one wants to add a specific information, it can be done by overriding the session_info method and adding it to the dictionary." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1406 -msgid "Now, the value can be obtained in javascript by reading it in the session:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1414 -msgid "Note that this mechanism is designed to reduce the amount of communication needed by the web client to be ready. It is more appropriate for data which is cheap to compute (a slow session_info call will delay the loading for the web client for everyone), and for data which is required early in the initialization process." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1423 -msgid "The word 'view' has more than one meaning. This section is about the design of the javascript code of the views, not the structure of the *arch* or anything else." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1427 -msgid "In 2017, Odoo replaced the previous view code with a new architecture. The main need was to separate the rendering logic from the model logic." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1431 -msgid "Views (in a generic sense) are now described with 4 pieces: a View, a Controller, a Renderer and a Model. The API of these 4 pieces is described in the AbstractView, AbstractController, AbstractRenderer and AbstractModel classes." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1452 -msgid "the View is the factory. Its job is to get a set of fields, arch, context and some other parameters, then to construct a Controller/Renderer/Model triplet." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1455 -msgid "The view's role is to properly setup each piece of the MVC pattern, with the correct information. Usually, it has to process the arch string and extract the data necessary for each other parts of the view." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1459 -msgid "Note that the view is a class, not a widget. Once its job has been done, it can be discarded." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1462 -msgid "the Renderer has one job: representing the data being viewed in a DOM element. Each view can render the data in a different way. Also, it should listen on appropriate user actions and notify its parent (the Controller) if necessary." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1466 -msgid "The Renderer is the V in the MVC pattern." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1468 -msgid "the Model: its job is to fetch and hold the state of the view. Usually, it represents in some way a set of records in the database. The Model is the owner of the 'business data'. It is the M in the MVC pattern." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1472 -msgid "the Controller: its job is to coordinate the renderer and the model. Also, it is the main entry point for the rest of the web client. For example, when the user changes something in the search view, the *update* method of the controller will be called with the appropriate information." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1477 -msgid "It is the C in the MVC pattern." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1480 -msgid "The JS code for the views has been designed to be usable outside of the context of a view manager/action manager. They could be used in a client action, or, they could be displayed in the public website (with some work on the assets)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1487 -msgid "Field Widgets" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1489 -msgid "A good part of the web client experience is about editing and creating data. Most of that work is done with the help of field widgets, which are aware of the field type and of the specific details on how a value should be displayed and edited." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1494 -msgid "AbstractField" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1496 -msgid "The *AbstractField* class is the base class for all widgets in a view, for all views that support them (currently: Form, List, Kanban)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1499 -msgid "There are many differences between the v11 field widgets and the previous versions. Let us mention the most important ones:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1502 -msgid "the widgets are shared between all views (well, Form/List/Kanban). No need to duplicate the implementation anymore. Note that it is possible to have a specialized version of a widget for a view, by prefixing it with the view name in the view registry: *list.many2one* will be chosen in priority over *many2one*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1506 -msgid "the widgets are no longer the owner of the field value. They only represent the data and communicate with the rest of the view." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1508 -msgid "the widgets do no longer need to be able to switch between edit and readonly mode. Now, when such a change is necessary, the widget will be destroyed and rerendered again. It is not a problem, since they do not own their value anyway" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1512 -msgid "the field widgets can be used outside of a view. Their API is slightly awkward, but they are designed to be standalone." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1516 -msgid "Decorations" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1518 -msgid "Like the list view, field widgets have a simple support for decorations. The goal of decorations is to have a simple way to specify a text color depending on the record current state. For example," -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1526 -msgid "The valid decoration names are:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1528 -msgid "decoration-bf" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1529 -msgid "decoration-it" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1530 -msgid "decoration-danger" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1531 -msgid "decoration-info" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1532 -msgid "decoration-muted" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1533 -msgid "decoration-primary" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1534 -msgid "decoration-success" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1535 -msgid "decoration-warning" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1537 -msgid "Each decoration *decoration-X* will be mapped to a css class *text-X*, which is a standard bootstrap css class (except for *text-it* and *text-bf*, which are handled by odoo and correspond to italic and bold, respectively). Note that the value of the decoration attribute should be a valid python expression, which will be evaluated with the record as evaluation context." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1544 -msgid "Non relational fields" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1546 -msgid "We document here all non relational fields available by default, in no particular order." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1580 -msgid "integer (FieldInteger)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1550 -msgid "This is the default field type for fields of type *integer*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1552 -#: ../../content/developer/reference/javascript_reference.rst:1741 -msgid "Supported field types: *integer*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1554 -#: ../../content/developer/reference/javascript_reference.rst:1595 -#: ../../content/developer/reference/javascript_reference.rst:1667 -#: ../../content/developer/reference/javascript_reference.rst:1680 -#: ../../content/developer/reference/javascript_reference.rst:1693 -#: ../../content/developer/reference/javascript_reference.rst:1720 -#: ../../content/developer/reference/javascript_reference.rst:1805 -#: ../../content/developer/reference/javascript_reference.rst:1823 -#: ../../content/developer/reference/javascript_reference.rst:1888 -#: ../../content/developer/reference/javascript_reference.rst:1932 -#: ../../content/developer/reference/javascript_reference.rst:1951 -#: ../../content/developer/reference/javascript_reference.rst:1983 -#: ../../content/developer/reference/javascript_reference.rst:2004 -#: ../../content/developer/reference/javascript_reference.rst:2076 -#: ../../content/developer/reference/javascript_reference.rst:2106 -#: ../../content/developer/reference/javascript_reference.rst:2180 -#: ../../content/developer/reference/javascript_reference.rst:2195 -#: ../../content/developer/reference/javascript_reference.rst:2205 -#: ../../content/developer/reference/javascript_reference.rst:2253 -msgid "Options:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1556 -#: ../../content/developer/reference/javascript_reference.rst:1597 -msgid "type: setting the input type (*text* by default, can be set on *number*)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1558 -#: ../../content/developer/reference/javascript_reference.rst:1599 -msgid "On edit mode, the field is rendered as an input with the HTML attribute type setted on *number* (so user can benefit the native support, especially on mobile). In this case, the default formatting is disabled to avoid incompability." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1566 -#: ../../content/developer/reference/javascript_reference.rst:1607 -msgid "step: set the step to the value up and down when the user click on buttons (only for input of type number, 1 by default)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1573 -msgid "format: should the number be formatted. (true by default)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1576 -msgid "By default, numbers are formatted according to locale parameters." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1576 -msgid "This option will prevent the field's value from being formatted." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1621 -msgid "float (FieldFloat)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1583 -msgid "This is the default field type for fields of type *float*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1585 -#: ../../content/developer/reference/javascript_reference.rst:1628 -#: ../../content/developer/reference/javascript_reference.rst:1635 -#: ../../content/developer/reference/javascript_reference.rst:1644 -msgid "Supported field types: *float*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1587 -#: ../../content/developer/reference/javascript_reference.rst:2100 -#: ../../content/developer/reference/javascript_reference.rst:2175 -msgid "Attributes:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1589 -msgid "digits: displayed precision" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1628 -msgid "float_time (FieldFloatTime)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1624 -msgid "The goal of this widget is to display properly a float value that represents a time interval (in hours). So, for example, 0.5 should be formatted as 0:30, or 4.75 correspond to 4:45." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1635 -msgid "float_factor (FieldFloatFactor)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1631 -msgid "This widget aims to display properly a float value that converted using a factor given in its options. So, for example, the value saved in database is 0.5 and the factor is 3, the widget value should be formatted as 1.5." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1648 -msgid "float_toggle (FieldFloatToggle)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1638 -msgid "The goal of this widget is to replace the input field by a button containing a range of possible values (given in the options). Each click allows the user to loop in the range. The purpose here is to restrict the field value to a predefined selection. Also, the widget support the factor conversion as the *float_factor* widget (Range values should be the result of the conversion)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1653 -msgid "boolean (FieldBoolean)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1651 -msgid "This is the default field type for fields of type *boolean*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1653 -#: ../../content/developer/reference/javascript_reference.rst:1920 -#: ../../content/developer/reference/javascript_reference.rst:1930 -#: ../../content/developer/reference/javascript_reference.rst:2002 -msgid "Supported field types: *boolean*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1658 -msgid "char (FieldChar)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1656 -msgid "This is the default field type for fields of type *char*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1658 -#: ../../content/developer/reference/javascript_reference.rst:1748 -#: ../../content/developer/reference/javascript_reference.rst:1756 -#: ../../content/developer/reference/javascript_reference.rst:1787 -#: ../../content/developer/reference/javascript_reference.rst:1794 -#: ../../content/developer/reference/javascript_reference.rst:2021 -msgid "Supported field types: *char*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1673 -msgid "date (FieldDate)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1661 -msgid "This is the default field type for fields of type *date*. Note that it also works with datetime fields. It uses the session timezone when formatting dates." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1665 -#: ../../content/developer/reference/javascript_reference.rst:1678 -#: ../../content/developer/reference/javascript_reference.rst:1691 -#: ../../content/developer/reference/javascript_reference.rst:1711 -msgid "Supported field types: *date*, *datetime*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1669 -#: ../../content/developer/reference/javascript_reference.rst:1682 -msgid "datepicker: extra settings for the datepicker_ widget." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1686 -msgid "datetime (FieldDateTime)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1676 -msgid "This is the default field type for fields of type *datetime*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1703 -msgid "daterange (FieldDateRange)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1689 -msgid "This widget allows the user to select start and end date into a single picker." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1695 -msgid "related_start_date: apply on end date field to get start date value which is used to display range in the picker." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1697 -msgid "related_end_date: apply on start date field to get end date value which is used to display range in the picker." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1699 -msgid "picker_options: extra settings for picker." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1711 -msgid "remaining_days (RemainingDays)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1706 -msgid "This widget can be used on date and datetime fields. In readonly, it displays the delta (in days) between the value of the field and today. The widget is intended to be used for informative purpose: therefore the value cannot be modified in edit mode." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1726 -msgid "monetary (FieldMonetary)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1714 -msgid "This is the default field type for fields of type 'monetary'. It is used to display a currency. If there is a currency fields given in option, it will use that, otherwise it will fall back to the default currency (in the session)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1718 -msgid "Supported field types: *monetary*, *float*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1722 -msgid "currency_field: another field name which should be a many2one on currency." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1732 -msgid "text (FieldText)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1729 -msgid "This is the default field type for fields of type *text*." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1731 -msgid "Supported field types: *text*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1742 -msgid "handle (HandleWidget)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1735 -msgid "This field's job is to be displayed as a *handle*, and allows reordering the various records by drag and dropping them." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1738 -msgid "It has to be specified on the field by which records are sorted." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1739 -msgid "Having more than one field with a handle widget on the same list is not supported." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1748 -msgid "email (FieldEmail)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1745 -msgid "This field displays email address. The main reason to use it is that it is rendered as an anchor tag with the proper href, in readonly mode." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1756 -msgid "phone (FieldPhone)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1751 -msgid "This field displays a phone number. The main reason to use it is that it is rendered as an anchor tag with the proper href, in readonly mode, but only in some cases: we only want to make it clickable if the device can call this particular number." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1775 -msgid "url (UrlWidget)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1759 -msgid "This field displays an url (in readonly mode). The main reason to use it is that it is rendered as an anchor tag with the proper css classes and href." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1762 -msgid "Also, the text of the anchor tag can be customized with the *text* attribute (it won't change the href value)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1787 -msgid "domain (FieldDomain)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1778 -msgid "The \"Domain\" field allows the user to construct a technical-prefix domain thanks to a tree-like interface and see the selected records in real time. In debug mode, an input is also there to be able to enter the prefix char domain directly (or to build advanced domains the tree-like interface does not allow to)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1784 -msgid "Note that this is limited to 'static' domain (no dynamic expression, or access to context variable)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1794 -msgid "link_button (LinkButton)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1790 -msgid "The LinkButton widget actually simply displays a span with an icon and the text value as content. The link is clickable and will open a new browser window with its value as url." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1816 -msgid "image (FieldBinaryImage)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1797 -msgid "This widget is used to represent a binary value as an image. In some cases, the server returns a 'bin_size' instead of the real image (a bin_size is a string representing a file size, such as 6.5kb). In that case, the widget will make an image with a source attribute corresponding to an image on the server." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1803 -#: ../../content/developer/reference/javascript_reference.rst:1821 -msgid "Supported field types: *binary*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1807 -msgid "preview_image: if the image is only loaded as a 'bin_size', then this option is useful to inform the web client that the default field name is not the name of the current field, but the name of another field." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1811 -msgid "accepted_file_extensions: the file extension the user can pick from the file input dialog box (default value is `image/\\*`) (cf: ``accept`` attribute on )" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1836 -msgid "binary (FieldBinaryFile)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1819 -msgid "Generic widget to allow saving/downloading a binary file." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1825 -#: ../../content/developer/reference/javascript_reference.rst:2197 -msgid "accepted_file_extensions: the file extension the user can pick from the file input dialog box (cf: ``accept`` attribute on )" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1828 -msgid "Attribute:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1830 -msgid "filename: saving a binary file will lose its file name, since it only saves the binary value. The filename can be saved in another field. To do that, an attribute filename should be set to a field present in the view." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1845 -msgid "priority (PriorityWidget)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1839 -msgid "This widget is rendered as a set of stars, allowing the user to click on it to select a value or not. This is useful for example to mark a task as high priority." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1843 -msgid "Note that this widget also works in 'readonly' mode, which is unusual." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1845 -#: ../../content/developer/reference/javascript_reference.rst:1862 -#: ../../content/developer/reference/javascript_reference.rst:1886 -#: ../../content/developer/reference/javascript_reference.rst:1905 -#: ../../content/developer/reference/javascript_reference.rst:1914 -#: ../../content/developer/reference/javascript_reference.rst:2057 -msgid "Supported field types: *selection*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1857 -msgid "attachment_image (AttachmentImage)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1848 -msgid "Image widget for many2one fields. If the field is set, this widget will be rendered as an image with the proper src url. This widget does not have a different behaviour in edit or readonly mode, it is only useful to view an image." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1853 -#: ../../content/developer/reference/javascript_reference.rst:2098 -#: ../../content/developer/reference/javascript_reference.rst:2130 -#: ../../content/developer/reference/javascript_reference.rst:2141 -#: ../../content/developer/reference/javascript_reference.rst:2150 -#: ../../content/developer/reference/javascript_reference.rst:2168 -msgid "Supported field types: *many2one*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1880 -msgid "image_selection (ImageSelection)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1860 -msgid "Allow the user to select a value by clicking on an image." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1864 -msgid "Options: a dictionary with a mapping from a selection value to an object with the url for an image (*image_link*) and a preview image (*preview_link*)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1867 -msgid "Note that this option is not optional!" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1896 -msgid "label_selection (LabelSelection)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1883 -msgid "This widget renders a simple non-editable label. This is only useful to display some information, not to edit it." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1890 -msgid "classes: a mapping from a selection value to a css class" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1909 -msgid "state_selection (StateSelectionWidget)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1899 -msgid "This is a specialized selection widget. It assumes that the record has some hardcoded fields, present in the view: *stage_id*, *legend_normal*, *legend_blocked*, *legend_done*. This is mostly used to display and change the state of a task in a project, with additional information displayed in the dropdown." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1914 -msgid "kanban_state_selection (StateSelectionWidget)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1912 -msgid "This is exactly the same widget as state_selection" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1920 -msgid "boolean_favorite (FavoriteWidget)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1917 -msgid "This widget is displayed as an empty (or not) star, depending on a boolean value. Note that it also can be edited in readonly mode." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1939 -msgid "boolean_button (FieldBooleanButton)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1923 -msgid "The Boolean Button widget is meant to be used in a stat button in a form view. The goal is to display a nice button with the current state of a boolean field (for example, 'Active'), and allow the user to change that field when clicking on it." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1928 -msgid "Note that it also can be edited in readonly mode." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1934 -msgid "terminology: it can be either 'active', 'archive', 'close' or a customized mapping with the keys *string_true*, *string_false*, *hover_true*, *hover_false*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1943 -msgid "boolean_toggle (BooleanToggle)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1942 -msgid "Displays a toggle switch to represent a boolean. This is a subfield of FieldBoolean, mostly used to have a different look." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1964 -msgid "statinfo (StatInfo)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1946 -msgid "This widget is meant to represent statistical information in a *stat button*. It is basically just a label with a number." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1949 -#: ../../content/developer/reference/javascript_reference.rst:1972 -#: ../../content/developer/reference/javascript_reference.rst:1981 -msgid "Supported field types: *integer, float*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1953 -msgid "label_field: if given, the widget will use the value of the label_field as text." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1976 -msgid "percentpie (FieldPercentPie)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1967 -msgid "This widget is meant to represent statistical information in a *stat button*. This is similar to a statinfo widget, but the information is represented in a *pie* chart (empty to full). Note that the value is interpreted as a percentage (a number between 0 and 100)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1995 -msgid "progressbar (FieldProgressBar)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1979 -msgid "Represent a value as a progress bar (from 0 to some value)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1985 -msgid "editable: boolean if value is editable" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1986 -msgid "current_value: get the current_value from the field that must be present in the view" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1987 -msgid "max_value: get the max_value from the field that must be present in the view" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1988 -msgid "edit_max_value: boolean if the max_value is editable" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1989 -msgid "title: title of the bar, displayed on top of the bar --> not translated, use parameter (not option) \"title\" instead" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2013 -msgid "toggle_button (FieldToggleBoolean)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:1998 -msgid "This widget is intended to be used on boolean fields. It toggles a button switching between a green bullet / gray bullet. It also set up a tooltip, depending on the value and some options." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2006 -msgid "active: the string for the tooltip that should be set when boolean is true" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2007 -msgid "inactive: the tooltip that should be set when boolean is false" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2031 -msgid "dashboard_graph (JournalDashboardGraph)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2016 -msgid "This is a more specialized widget, useful to display a graph representing a set of data. For example, it is used in the accounting dashboard kanban view." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2019 -msgid "It assumes that the field is a JSON serialization of a set of data." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2023 -msgid "Attribute" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2025 -msgid "graph_type: string, can be either 'line' or 'bar'" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2037 -msgid "ace (AceEditor)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2034 -msgid "This widget is intended to be used on Text fields. It provides Ace Editor for editing XML and Python." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2037 -msgid "Supported field types: *char, text*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2050 -msgid "badge (FieldBadge)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2040 -msgid "Displays the value inside a bootstrap badge pill." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2042 -msgid "Supported field types: *char*, *selection*, *many2one*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2044 -msgid "By default, the badge has a lightgrey background, but it can be customized by using the decoration-X mechanism. For instance, to display a red badge under a given condition:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2061 -msgid "a string which is used to display some info when no value is selected" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2083 -msgid "radio (FieldRadio)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2068 -msgid "This is a subfield of FielSelection, but specialized to display all the valid choices as radio buttons." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2071 -msgid "Note that if used on a many2one records, then more rpcs will be done to fetch the name_gets of the related records." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2074 -#: ../../content/developer/reference/javascript_reference.rst:2089 -#: ../../content/developer/reference/javascript_reference.rst:2273 -msgid "Supported field types: *selection, many2one*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2078 -msgid "horizontal: if true, radio buttons will be displayed horizontally." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2093 -msgid "selection_badge (FieldSelectionBadge)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2086 -msgid "This is a subfield of FieldSelection, but specialized to display all the valid choices as rectangular badges." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2121 -msgid "many2one (FieldMany2One)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2096 -msgid "Default widget for many2one fields." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2102 -msgid "can_create: allow the creation of related records (take precedence over no_create option)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2104 -msgid "can_write: allow the editing of related records (default: true)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2108 -msgid "no_create: prevent the creation of related records" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2109 -msgid "quick_create: allow the quick creation of related records (default: true)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2110 -msgid "no_quick_create: prevent the quick creation of related records (don't ask me)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2111 -msgid "no_create_edit: same as no_create, maybe..." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2112 -msgid "create_name_field: when creating a related record, if this option is set, the value of the *create_name_field* will be filled with the value of the input (default: *name*)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2113 -msgid "always_reload: boolean, default to false. If true, the widget will always do an additional name_get to fetch its name value. This is used for the situations where the name_get method is overridden (please do not do that)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2116 -msgid "no_open: boolean, default to false. If set to true, the many2one will not redirect on the record when clicking on it (in readonly mode)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2130 -msgid "list.many2one (ListFieldMany2One)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2124 -msgid "Default widget for many2one fields (in list view)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2126 -msgid "Specialization of many2one field for list views. The main reason is that we need to render many2one fields (in readonly mode) as a text, which does not allow opening the related records." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2141 -msgid "many2one_barcode (FieldMany2OneBarcode)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2133 -msgid "Widget for many2one fields allows to open the camera from a mobile device (Android/iOS) to scan a barcode." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2135 -msgid "Specialization of many2one field where the user is allowed to use the native camera to scan a barcode. Then it uses name_search to search this value." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2138 -msgid "If this widget is set and user is not using the mobile application, it will fallback to regular many2one (FieldMany2One)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2150 -msgid "many2one_avatar (Many2OneAvatar)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2144 -msgid "This widget is only supported on many2one fields pointing to a model which inherits from 'image.mixin'. In readonly, it displays the image of the related record next to its display_name. Note that the display_name isn't a clickable link in this case. In edit, it behaves exactly like the regular many2one." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2157 -msgid "many2one_avatar_user (Many2OneAvatarUser)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2153 -msgid "This widget is a specialization of the Many2OneAvatar. When the avatar is clicked, we open a chat window with the corresponding user. This widget can only be set on many2one fields pointing to the 'res.users' model." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2157 -msgid "Supported field types: *many2one* (pointing to 'res.users')" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2162 -msgid "many2one_avatar_employee (Many2OneAvatarEmployee)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2160 -msgid "Same as Many2OneAvatarUser, but for many2one fields pointing to 'hr.employee'." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2162 -msgid "Supported field types: *many2one* (pointing to 'hr.employee')" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2168 -msgid "kanban.many2one (KanbanFieldMany2One)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2165 -msgid "Default widget for many2one fields (in kanban view). We need to disable all editing in kanban views." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2185 -msgid "many2many (FieldMany2Many)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2171 -msgid "Default widget for many2many fields." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2173 -#: ../../content/developer/reference/javascript_reference.rst:2193 -#: ../../content/developer/reference/javascript_reference.rst:2203 -#: ../../content/developer/reference/javascript_reference.rst:2230 -#: ../../content/developer/reference/javascript_reference.rst:2235 -#: ../../content/developer/reference/javascript_reference.rst:2244 -msgid "Supported field types: *many2many*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2177 -msgid "mode: string, default view to display" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2178 -msgid "domain: restrict the data to a specific domain" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2182 -msgid "create_text: allow the customization of the text displayed when adding a new record" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2184 -msgid "link: domain determining whether or not records can be added to the relation (default: True)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2185 -msgid "unlink: domain determining whether or not records can be removed from the relation (default: True)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2198 -msgid "many2many_binary (FieldMany2ManyBinaryMultiFiles)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2188 -msgid "This widget helps the user to upload or delete one or more files at the same time." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2191 -msgid "Note that this widget is specific to the model 'ir.attachment'." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2224 -msgid "many2many_tags (FieldMany2ManyTags)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2201 -msgid "Display many2many as a list of tags." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2207 -msgid "create: domain determining whether or not new tags can be created (default: True)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2213 -msgid "color_field: the name of a numeric field, which should be present in the view. A color will be chosen depending on its value." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2220 -msgid "no_edit_color: set to True to remove the possibility to change the color of the tags (default: False)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2230 -msgid "form.many2many_tags (FormFieldMany2ManyTags)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2227 -msgid "Specialization of many2many_tags widget for form views. It has some extra code to allow editing the color of a tag." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2235 -msgid "kanban.many2many_tags (KanbanFieldMany2ManyTags)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2233 -msgid "Specialization of many2many_tags widget for kanban views." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2244 -msgid "many2many_checkboxes (FieldMany2ManyCheckBoxes)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2238 -msgid "This field displays a list of checkboxes and allows the user to select a subset of the choices. Note that the number of displayed values is limited to 100. This limit isn't customizable. It simply allows to handle extreme cases where this widget is wrongly set on a field with a huge comodel. In those cases, a list view is more adequate as it allows pagination and filtering." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2267 -msgid "one2many (FieldOne2Many)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2247 -msgid "Default widget for one2many fields." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2249 -msgid "It usually displays data in a sub list view, or a sub kanban view." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2251 -msgid "Supported field types: *one2many*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2255 -msgid "create: domain determining whether or not related records can be created (default: True)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2257 -msgid "delete: domain determining whether or not related records can be deleted (default: True)." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2263 -msgid "create_text: a string that is used to customize the 'Add' label/text." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2273 -msgid "statusbar (FieldStatus)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2270 -msgid "This is a really specialized widget for the form views. It is the bar on top of many forms which represent a flow, and allow selecting a specific state." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2281 -msgid "reference (FieldReference)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2276 -msgid "The FieldReference is a combination of a select (for the model) and a FieldMany2One (for its value). It allows the selection of a record on an arbitrary model." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2280 -msgid "Supported field types: *char, reference*" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2284 -msgid "Client actions" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2286 -msgid "The idea of a client action is a customized widget that is integrated in the web client interface, just like a *act_window_action*. This is useful when you need a component that is not closely linked to an existing view or a specific model. For example, the Discuss application is actually a client action." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2292 -msgid "A client action is a term that has various meanings, depending on the context:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2294 -msgid "from the perspective of the server, it is a record of the model *ir_action*, with a field *tag* of type char" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2296 -msgid "from the perspective of the web client, it is a widget, which inherit from the class AbstractAction, and is supposed to be registered in the action registry under the corresponding key (from the field char)" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2300 -msgid "Whenever a menu item is associated to a client action, opening it will simply fetch the action definition from the server, then lookup into its action registry to get the Widget definition at the appropriate key, and finally, it will instantiate and append the widget to the proper place in the DOM." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2306 -msgid "Adding a client action" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2308 -msgid "A client action is a widget which will control the part of the screen below the menu bar. It can have a control panel, if necessary. Defining a client action can be done in two steps: implementing a new widget, and registering the widget in the action registry." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2323 -msgid "Implementing a new client action." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2314 -msgid "This is done by creating a widget:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2346 -msgid "Registering the client action:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2326 -msgid "As usual, we need to make the web client aware of the mapping between client actions and the actual class:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2336 -msgid "Then, to use the client action in the web client, we need to create a client action record (a record of the model ``ir.actions.client``) with the proper ``tag`` attribute:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2349 -msgid "Using the control panel" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2351 -msgid "By default, the client action does not display a control panel. In order to do that, several steps should be done." -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2354 -msgid "Set the *hasControlPanel* to *true*. In the widget code:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2366 -msgid "when the ``loadControlPanel`` is set to true, the client action will automatically get the content of a search view or a control panel view. In this case, a model name should be specified like this:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2377 -msgid "Call the method *updateControlPanel* whenever we need to update the control panel. For example:" -msgstr "" - -#: ../../content/developer/reference/javascript_reference.rst:2406 -msgid "The ``updateControlPanel`` is the main method to customize the content in controlpanel. For more information, look into the `control_panel_renderer.js `_ file." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:6 -msgid "Mixins and Useful Classes" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:8 -msgid "Odoo implements some useful classes and mixins that make it easy for you to add often-used behaviours on your objects. This guide will details most of them, with examples and use cases." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:15 -msgid "Messaging features" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:20 -msgid "Messaging integration" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:23 -msgid "Basic messaging system" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:25 -msgid "Integrating messaging features to your model is extremely easy. Simply inheriting the ``mail.thread`` model and adding the messaging fields (and their appropriate widgets) to your form view will get you up and running in no time." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:29 -#: ../../content/developer/reference/mixins.rst:203 -#: ../../content/developer/reference/mixins.rst:275 -#: ../../content/developer/reference/mixins.rst:425 -#: ../../content/developer/reference/mixins.rst:612 -#: ../../content/developer/reference/mixins.rst:741 -#: ../../content/developer/reference/orm.rst:177 -#: ../../content/developer/reference/orm.rst:843 -#: ../../content/developer/reference/views.rst:1004 -msgid "Example" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:31 -msgid "Let's create a simplistic model representing a business trip. Since organizing this kind of trip usually involves a lot of people and a lot of discussion, let's add support for message exchange on the model." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:46 -msgid "In the form view:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:66 -msgid "Once you've added chatter support on your model, users can easily add messages or internal notes on any record of your model; every one of those will send a notification (to all followers for messages, to employee (*base.group_user*) users for internal notes). If your mail gateway and catchall address are correctly configured, these notifications will be sent by e-mail and can be replied-to directly from your mail client; the automatic routing system will route the answer to the correct thread." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:74 -msgid "Server-side, some helper functions are there to help you easily send messages and to manage followers on your record:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:78 -msgid "Posting messages" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:81 -msgid "Post a new message in an existing thread, returning the new mail.message ID." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/qweb.rst:0 -#: ../../content/developer/webservices/iap.rst:0 -#: ../../content/developer/webservices/iap.rst:0 -#: ../../content/developer/webservices/iap.rst:0 -#: ../../content/developer/webservices/iap.rst:0 -#: ../../content/developer/webservices/iap.rst:0 -#: ../../content/developer/webservices/iap.rst:0 -#: ../../content/developer/webservices/iap.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -msgid "Parameters" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:84 -msgid "body of the message, usually raw HTML that will be sanitized" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:86 -msgid "see mail_message.message_type field" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:87 -msgid "handle reply to a previous message by adding the parent partners to the message in case of private discussion" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:89 -msgid "list of attachment tuples in the form ``(name,content)``, where content is NOT base64 encoded" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:91 -msgid "extra keyword arguments will be used as default column values for the new mail.message record" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:93 -msgid "ID of newly created mail.message" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/reference/mixins.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -#: ../../content/developer/webservices/upgrade.rst:0 -msgid "Return type" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:98 -msgid "Helper method to send a mail / post a message using a view_id to render using the ir.qweb engine. This method is stand alone, because there is nothing in template and composer that allows to handle views in batch. This method will probably disappear when templates handle ir ui views." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:104 -msgid "external id or record of the view that should be sent" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:109 -msgid "Helper method to send a mail with a template" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:111 -msgid "the id of the template to render to create the body of the message" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:112 -msgid "parameter to create a mail.compose.message wizzard (which inherit from mail.message)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:115 -msgid "Receiving messages" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:116 -msgid "These methods are called when a new e-mail is processed by the mail gateway. These e-mails can either be new thread (if they arrive via an :ref:`alias `) or simply replies from an existing thread. Overriding them allows you to set values on the thread's record depending on some values from the email itself (i.e. update a date or an e-mail address, add CC's addresses as followers, etc.)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:124 -msgid "Called by ``message_process`` when a new message is received for a given thread model, if the message did not belong to an existing thread." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:128 -msgid "The default behavior is to create a new record of the corresponding model (based on some very basic info extracted from the message). Additional behavior may be implemented by overriding this method." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:132 -msgid "a map containing the email details and attachments. See ``message_process`` and ``mail.message.parse`` for details" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:134 -msgid "optional dictionary of additional field values to pass to create() when creating the new thread record; be careful, these values may override any other values coming from the message" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:139 -msgid "the id of the newly created thread object" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:143 -msgid "Called by ``message_process`` when a new message is received for an existing thread. The default behavior is to update the record with ``update_vals`` taken from the incoming email." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:147 -msgid "Additional behavior may be implemented by overriding this method." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:150 -msgid "a map containing the email details and attachments; see ``message_process`` and ``mail.message.parse()`` for details." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:152 -msgid "a dict containing values to update records given their ids; if the dict is None or is void, no write operation is performed." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:154 -#: ../../content/developer/reference/mixins.rst:182 -#: ../../content/developer/reference/mixins.rst:192 -msgid "True" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:157 -msgid "Followers management" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:160 -msgid "Add partners to the records followers." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:162 -#: ../../content/developer/reference/mixins.rst:178 -msgid "IDs of the partners that will be subscribed to the record" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:164 -#: ../../content/developer/reference/mixins.rst:180 -msgid "IDs of the channels that will be subscribed to the record" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:166 -msgid "IDs of the subtypes that the channels/partners will be subscribed to (defaults to the default subtypes if ``None``)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:168 -msgid "if True, delete existing followers before creating new one using the subtypes given in the parameters" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:170 -msgid "Success/Failure" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:176 -msgid "Remove partners from the record's followers." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:188 -msgid "Wrapper on message_subscribe, using users." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:190 -msgid "IDs of the users that will be unsubscribed to the record; if None, unsubscribe the current user instead." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:197 -msgid "Logging changes" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:199 -msgid "The ``mail`` module adds a powerful tracking system on fields, allowing you to log changes to specific fields in the record's chatter. To add tracking to a field, simple set the tracking attribute to True." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:205 -msgid "Let's track changes on the name and responsible of our business trips:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:219 -msgid "From now on, every change to a trip's name or responsible will log a note on the record. The ``name`` field will be displayed in the notification as well to give more context about the notification (even if the name did not change)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:226 -msgid "Subtypes" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:228 -msgid "Subtypes give you more granular control over messages. Subtypes act as a classification system for notifications, allowing subscribers to a document to customize the subtype of notifications they wish to receive." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:232 -msgid "Subtypes are created as data in your module; the model has the following fields:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:235 -msgid "``name`` (mandatory) - :class:`~odoo.fields.Char`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:235 -msgid "name of the subtype, will be displayed in the notification customization popup" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:238 -msgid "``description`` - :class:`~odoo.fields.Char`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:238 -msgid "description that will be added in the message posted for this subtype. If void, the name will be added instead" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:241 -msgid "``internal`` - :class:`~odoo.fields.Boolean`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:241 -msgid "messages with internal subtypes will be visible only by employees, aka members of the ``base.group_user`` group" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:246 -msgid "``parent_id`` - :class:`~odoo.fields.Many2one`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:244 -msgid "link subtypes for automatic subscription; for example project subtypes are linked to task subtypes through this link. When someone is subscribed to a project, he will be subscribed to all tasks of this project with subtypes found using the parent subtype" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:249 -msgid "``relation_field`` - :class:`~odoo.fields.Char`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:249 -msgid "as an example, when linking project and tasks subtypes, the relation field is the project_id field of tasks" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:251 -msgid "``res_model`` - :class:`~odoo.fields.Char`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:252 -msgid "model the subtype applies to; if False, this subtype applies to all models" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:253 -msgid "``default`` - :class:`~odoo.fields.Boolean`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:254 -msgid "wether the subtype is activated by default when subscribing" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:255 -msgid "``sequence`` - :class:`~odoo.fields.Integer`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:256 -msgid "used to order subtypes in the notification customization popup" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:259 -msgid "``hidden`` - :class:`~odoo.fields.Boolean`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:258 -msgid "wether the subtype is hidden in the notification customization popup" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:261 -msgid "Interfacing subtypes with field tracking allows to subscribe to different kind of notifications depending on what might interest users. To do this, you can override the ``_track_subtype()`` function:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:267 -#: ../../content/developer/reference/mixins.rst:349 -msgid "Give the subtype triggered by the changes on the record according to values that have been updated." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:270 -msgid "the original values of the record; only modified fields are present in the dict" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:272 -#: ../../content/developer/reference/mixins.rst:391 -msgid "a subtype's full external id or False if no subtype is triggered" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:277 -msgid "Let's add a ``state`` field on our example class and trigger a notification with a specific subtype when this field change values." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:280 -msgid "First, let's define our subtype:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:292 -msgid "Then, we need to override the ``track_subtype()`` function. This function is called by the tracking system to know which subtype should be used depending on the change currently being applied. In our case, we want to use our shiny new subtype when the ``state`` field changes from *draft* to *confirmed*:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:323 -msgid "Customizing notifications" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:325 -msgid "When sending notifications to followers, it can be quite useful to add buttons in the template to allow quick actions directly from the e-mail. Even a simple button to link directly to the record's form view can be useful; however in most cases you don't want to display these buttons to portal users." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:330 -msgid "The notification system allows customizing notification templates in the following ways:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:333 -msgid "Display *Access Buttons*: these buttons are visible at the top of the notification e-mail and allow the recipient to directly access the form view of the record" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:335 -msgid "Display *Follow Buttons*: these buttons allow the recipient to directly quickly subscribe from the record" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:337 -msgid "Display *Unfollow Buttons*: these buttons allow the recipient to directly quickly unsubscribe from the record" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:339 -msgid "Display *Custom Action Buttons*: these buttons are calls to specific routes and allow you to make some useful actions directly available from the e-mail (i.e. converting a lead to an opportunity, validating an expense sheet for an Expense Manager, etc.)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:344 -msgid "These buttons settings can be applied to different groups that you can define yourself by overriding the function ``_notification_recipients``." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:352 -msgid "``mail.message`` record currently being sent" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:353 -msgid "list of tuple of the form (group_name, group_func,group_data) where: group_name is an identifier used only to be able to override and manipulate groups. Default groups are ``user`` (recipients linked to an employee user), ``portal`` (recipients linked to a portal user) and ``customer`` (recipients not linked to any user). An example of override use would be to add a group linked to a res.groups like Hr Officers to set specific action buttons to them. group_func is a function pointer taking a partner record as parameter. This method will be applied on recipients to know whether they belong to a given group or not. Only first matching group is kept. Evaluation order is the list order. group_data is a dict containing parameters for the notification email with the following possible keys - values: - has_button_access whether to display Access in email. True by default for new groups, False for portal / customer. - button_access dict with url and title of the button - has_button_follow whether to display Follow in email (if recipient is not currently following the thread). True by default for new groups, False for portal / customer. - button_follow dict with url adn title of the button - has_button_unfollow whether to display Unfollow in email (if recipient is currently following the thread). True by default for new groups, False for portal / customer. - button_unfollow dict with url and title of the button - actions list of action buttons to display in the notification email. Each action is a dict containing url and title of the button." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:353 -msgid "list of tuple of the form (group_name, group_func,group_data) where:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:360 -msgid "group_name" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:356 -msgid "is an identifier used only to be able to override and manipulate groups. Default groups are ``user`` (recipients linked to an employee user), ``portal`` (recipients linked to a portal user) and ``customer`` (recipients not linked to any user). An example of override use would be to add a group linked to a res.groups like Hr Officers to set specific action buttons to them." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:365 -msgid "group_func" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:363 -msgid "is a function pointer taking a partner record as parameter. This method will be applied on recipients to know whether they belong to a given group or not. Only first matching group is kept. Evaluation order is the list order." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:389 -msgid "group_data" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:368 -msgid "is a dict containing parameters for the notification email with the following possible keys - values:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:372 -msgid "has_button_access" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:372 -msgid "whether to display Access in email. True by default for new groups, False for portal / customer." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:374 -msgid "button_access" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:375 -#: ../../content/developer/reference/mixins.rst:386 -msgid "dict with url and title of the button" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:378 -msgid "has_button_follow" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:377 -msgid "whether to display Follow in email (if recipient is not currently following the thread). True by default for new groups, False for portal / customer." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:380 -msgid "button_follow" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:381 -msgid "dict with url adn title of the button" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:383 -msgid "has_button_unfollow" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:383 -msgid "whether to display Unfollow in email (if recipient is currently following the thread). True by default for new groups, False for portal / customer." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:385 -msgid "button_unfollow" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:389 -msgid "actions" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:388 -msgid "list of action buttons to display in the notification email. Each action is a dict containing url and title of the button." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:394 -msgid "The urls in the actions list can be generated automatically by calling the ``_notification_link_helper()`` function:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:400 -msgid "Generate a link for the given type on the current record (or on a specific record if the kwargs ``model`` and ``res_id`` are set)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:403 -msgid "link type to be generated; can be any of these values: ``view`` link to form view of the record ``assign`` assign the logged user to the ``user_id`` field of the record (if it exists) ``follow`` self-explanatory ``unfollow`` self-explanatory ``method`` call a method on the record; the method's name should be provided as the kwarg ``method`` ``new`` open an empty form view for a new record; you can specify a specific action by providing its id (database id or fully resolved external id) in the kwarg ``action_id``" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:403 -msgid "link type to be generated; can be any of these values:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:405 -#: ../../content/developer/reference/views.rst:579 -msgid "``view``" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:406 -msgid "link to form view of the record" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:408 -msgid "``assign``" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:408 -msgid "assign the logged user to the ``user_id`` field of the record (if it exists)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:410 -msgid "``follow``" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:411 -#: ../../content/developer/reference/mixins.rst:413 -#: ../../content/developer/reference/views.rst:1276 -#: ../../content/developer/reference/views.rst:1278 -msgid "self-explanatory" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:412 -msgid "``unfollow``" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:415 -msgid "``method``" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:415 -msgid "call a method on the record; the method's name should be provided as the kwarg ``method``" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:420 -msgid "``new``" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:418 -msgid "open an empty form view for a new record; you can specify a specific action by providing its id (database id or fully resolved external id) in the kwarg ``action_id``" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:422 -msgid "link of the type selected for the record" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:427 -msgid "Let's add a custom button to the Business Trip state change notification; this button will reset the state to Draft and will be only visible to a member of the (imaginary) group Travel Manager (``business.group_trip_manager``)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:466 -msgid "Note that that I could have defined my evaluation function outside of this method and define a global function to do it instead of a lambda, but for the sake of being more brief and less verbose in these documentation files that can sometimes be boring, I choose the former instead of the latter." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:472 -msgid "Overriding defaults" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:474 -msgid "There are several ways you can customize the behaviour of ``mail.thread`` models, including (but not limited to):" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:479 -msgid "``_mail_post_access`` - :class:`~odoo.models.Model` attribute" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:478 -msgid "the required access rights to be able to post a message on the model; by default a ``write`` access is needed, can be set to ``read`` as well" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:499 -msgid "Context keys:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:482 -msgid "These context keys can be used to somewhat control ``mail.thread`` features like auto-subscription or field tracking during calls to ``create()`` or ``write()`` (or any other method where it may be useful)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:486 -msgid "``mail_create_nosubscribe``: at create or message_post, do not subscribe the current user to the record thread" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:488 -msgid "``mail_create_nolog``: at create, do not log the automatic ' created' message" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:490 -msgid "``mail_notrack``: at create and write, do not perform the value tracking creating messages" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:492 -msgid "``tracking_disable``: at create and write, perform no MailThread features (auto subscription, tracking, post, ...)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:494 -msgid "``mail_auto_delete``: auto delete mail notifications; True by default" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:495 -msgid "``mail_notify_force_send``: if less than 50 email notifications to send, send them directly instead of using the queue; True by default" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:497 -msgid "``mail_notify_user_signature``: add the current user signature in email notifications; True by default" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:504 -msgid "Mail alias" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:506 -msgid "Aliases are configurable email addresses that are linked to a specific record (which usually inherits the ``mail.alias.mixin`` model) that will create new records when contacted via e-mail. They are an easy way to make your system accessible from the outside, allowing users or customers to quickly create records in your database without needing to connect to Odoo directly." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:513 -msgid "Aliases vs. Incoming Mail Gateway" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:515 -msgid "Some people use the Incoming Mail Gateway for this same purpose. You still need a correctly configured mail gateway to use aliases, however a single catchall domain will be sufficient since all routing will be done inside Odoo. Aliases have several advantages over Mail Gateways:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:523 -msgid "Easier to configure" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:521 -msgid "A single incoming gateway can be used by many aliases; this avoids having to configure multiple emails on your domain name (all configuration is done inside Odoo)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:524 -msgid "No need for System access rights to configure aliases" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:525 -msgid "More coherent" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:526 -msgid "Configurable on the related record, not in a Settings submenu" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:531 -msgid "Easier to override server-side" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:528 -msgid "Mixin model is built to be extended from the start, allowing you to extract useful data from incoming e-mails more easily than with a mail gateway." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:534 -msgid "Alias support integration" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:536 -msgid "Aliases are usually configured on a parent model which will then create specific record when contacted by e-mail. For example, Project have aliases to create tasks or issues, Sales Team have aliases to generate Leads." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:540 -msgid "The model that will be created by the alias **must** inherit the ``mail_thread`` model." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:543 -msgid "Alias support is added by inheriting ``mail.alias.mixin``; this mixin will generate a new ``mail.alias`` record for each record of the parent class that gets created (for example, every ``project.project`` record having its ``mail.alias`` record initialized on creation)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:548 -msgid "Aliases can also be created manually and supported by a simple :class:`~odoo.fields.Many2one` field. This guide assumes you wish a more complete integration with automatic creation of the alias, record-specific default values, etc." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:553 -msgid "Unlike ``mail.thread`` inheritance, the ``mail.alias.mixin`` **requires** some specific overrides to work correctly. These overrides will specify the values of the created alias, like the kind of record it must create and possibly some default values these records may have depending on the parent object:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:560 -msgid "Return the model name for the alias. Incoming emails that are not replies to existing records will cause the creation of a new record of this alias model. The value may depend on ``vals``, the dict of values passed to ``create`` when a record of this model is created." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:565 -msgid "values of the newly created record that will holding the alias" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:567 -msgid "model name" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:572 -msgid "Return values to create an alias, or to write on the alias after its creation. While not completely mandatory, it is usually required to make sure that newly created records will be linked to the alias' parent (i.e. tasks getting created in the right project) by setting a dictionary of default values in the alias' ``alias_defaults`` field." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:578 -msgid "dictionnary of values that will be written to the new alias" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:581 -msgid "The ``_get_alias_values()`` override is particularly interesting as it allows you to modify the behaviour of your aliases easily. Among the fields that can be set on the alias, the following are of particular interest:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:586 -msgid "``alias_name`` - :class:`~odoo.fields.Char`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:586 -msgid "name of the email alias, e.g. 'jobs' if you want to catch emails for " -msgstr "" - -#: ../../content/developer/reference/mixins.rst:591 -msgid "``alias_user_id`` - :class:`~odoo.fields.Many2one` (``res.users``)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:589 -msgid "owner of records created upon receiving emails on this alias; if this field is not set the system will attempt to find the right owner based on the sender (From) address, or will use the Administrator account if no system user is found for that address" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:594 -msgid "``alias_defaults`` - :class:`~odoo.fields.Text`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:594 -msgid "Python dictionary that will be evaluated to provide default values when creating new records for this alias" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:598 -msgid "``alias_force_thread_id`` - :class:`~odoo.fields.Integer`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:597 -msgid "optional ID of a thread (record) to which all incoming messages will be attached, even if they did not reply to it; if set, this will disable the creation of new records completely" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:605 -msgid "``alias_contact`` - :class:`~odoo.fields.Selection`" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:601 -msgid "Policy to post a message on the document using the mailgateway" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:603 -msgid "*everyone*: everyone can post" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:604 -msgid "*partners*: only authenticated partners" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:605 -msgid "*followers*: only followers of the related document or members of following channels" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:607 -msgid "Note that aliases make use of :ref:`delegation inheritance `, which means that while the alias is stored in another table, you have access to all these fields directly from your parent object. This allows you to make your alias easily configurable from the record's form view." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:614 -msgid "Let's add aliases on our business trip class to create expenses on the fly via e-mail." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:662 -msgid "We would like our alias to be easily configurable from the form view of our business trips, so let's add the following to our form view:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:687 -msgid "Now we can change the alias address directly from the form view and change who can send e-mails to the alias." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:690 -msgid "We can then override ``message_new()`` on our expense model to fetch the values from our email when the expense will be created:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:727 -msgid "Activities tracking" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:729 -msgid "Activities are actions users have to take on a document like making a phone call or organizing a meeting. Activities come with the mail module as they are integrated in the Chatter but are *not bundled with mail.thread*. Activities are records of the ``mail.activity`` class, which have a type (``mail.activity.type``), name, description, scheduled time (among others). Pending activities are visible above the message history in the chatter widget." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:736 -msgid "You can integrate activities using the ``mail.activity.mixin`` class on your object and the specific widgets to display them (via the field ``activity_ids``) in the form view and kanban view of your records (``mail_activity`` and ``kanban_activity`` widgets, respectively)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:743 -msgid "Organizing a business trip is a tedious process and tracking needed activities like ordering plane tickets or a cab for the airport could be useful. To do so, we will add the activities mixin on our model and display the next planned activities in the message history of our trip." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:758 -msgid "We modify the form view of our trips to display their next activites:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:777 -#: ../../content/developer/reference/mixins.rst:853 -#: ../../content/developer/reference/mixins.rst:1072 -msgid "You can find concrete examples of integration in the following models:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:779 -#: ../../content/developer/reference/mixins.rst:855 -msgid "``crm.lead`` in the CRM (*crm*) Application" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:780 -msgid "``sale.order`` in the Sales (*sale*) Application" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:781 -msgid "``project.task`` in the Project (*poject*) Application" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:787 -msgid "Website features" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:792 -msgid "Visitor tracking" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:794 -msgid "The ``utm.mixin`` class can be used to track online marketing/communication campaigns through arguments in links to specified resources. The mixin adds 3 fields to your model:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:798 -msgid "``campaign_id``: :class:`~odoo.fields.Many2one` field to a ``utm.campaign`` object (i.e. Christmas_Special, Fall_Collection, etc.)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:800 -msgid "``source_id``: :class:`~odoo.fields.Many2one` field to a ``utm.source`` object (i.e. Search Engine, mailing list, etc.)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:802 -msgid "``medium_id``: :class:`~odoo.fields.Many2one` field to a ``utm.medium`` object (i.e. Snail Mail, e-Mail, social network update, etc.)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:805 -msgid "These models have a single field ``name`` (i.e. they are simply there to distinguish campaigns but don't have any specific behaviour)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:808 -msgid "Once a customer visits your website with these parameters set in the url (i.e. https://www.odoo.com/?campaign_id=mixin_talk&source_id=www.odoo.com&medium_id=website), three cookies are set in the visitor's website for these parameters. Once a object that inherits the utm.mixin is created from the website (i.e. lead form, job application, etc.), the utm.mixin code kicks in and fetches the values from the cookies to set them in the new record. Once this is done, you can then use the campaign/source/medium fields as any other field when defining reports and views (group by, etc.)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:817 -msgid "To extend this behaviour, simply add a relational field to a simple model (the model should support the *quick create* (i.e. call to ``create()`` with a single ``name`` value) and extend the function ``tracking_fields()``:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:846 -msgid "This will tell the system to create a cookie named *odoo_utm_my_field* with the value found in the url parameter ``my_field``; once a new record of this model is created by a call from a website form, the generic override of the ``create()`` method of ``utm.mixin`` will fetch the default values for this field from the cookie (and the ``my_module.my_track`` record will be creatwed on the fly if it does not exist yet)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:856 -msgid "``hr.applicant`` in the Recruitment Process (*hr_recruitment*) Application" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:857 -#: ../../content/developer/reference/mixins.rst:1075 -msgid "``helpdesk.ticket`` in the Helpdesk (*helpdesk* - Odoo Enterprise only) Application" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:862 -msgid "Website visibility" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:864 -msgid "You can quite easily add a website visibility toggle on any of your record. While this mixin is quite easy to implement manually, it is the most often-used after the ``mail.thread`` inheritance; a testament to its usefulness. The typical use case for this mixin is any object that has a frontend-page; being able to control the visibility of the page allows you to take your time while editing the page and only publish it when you're satisfied." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:871 -msgid "To include the functionnality, you only need to inherit ``website.published.mixin``:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:880 -msgid "This mixin adds 2 fields on your model:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:882 -msgid "``website_published``: :class:`~odoo.fields.Boolean` field which represents the status of the publication" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:884 -msgid "``website_url``: :class:`~odoo.fields.Char` field which represents the URL through which the object is accessed" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:887 -msgid "Note that this last field is a computed field and must be implemented for your class:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:895 -msgid "Once the mechanism is in place, you just have to adapt your frontend and backend views to make it accessible. In the backend, adding a button in the button box is usually the way to go:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:906 -msgid "In the frontend, some security checks are needed to avoid showing 'Editing' buttons to website visitors:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:920 -msgid "Note that you must pass your object as the variable ``object`` to the template; in this example, the ``blog.post`` record was passed as the ``blog_post`` variable to the ``qweb`` rendering engine, it is necessary to specify this to the publish management template. The ``publish_edit`` variable allow the frontend button to link to the backend (allowing you to switch from frontend to backend and vice-versa easily); if set, you must specify the full external id of the action you want to call in the backend in the ``action`` variable (note that a Form View must exist for the model)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:929 -msgid "The action ``website_publish_button`` is defined in the mixin and adapts its behaviour to your object: if the class has a valid ``website_url`` compute function, the user is redirected to the frontend when he clicks on the button; the user can then publish the page directly from the frontend. This ensures that no online publication can happen by accident. If there is not compute function, the boolean ``website_published`` is simply triggered." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:939 -msgid "Website metadata" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:941 -msgid "This simple mixin simply allows you to easily inject metadata in your frontend pages." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:951 -msgid "This mixin adds 3 fields on your model:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:953 -msgid "``website_meta_title``: :class:`~odoo.fields.Char` field that allow you to set an additional title to your page" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:955 -msgid "``website_meta_description``: :class:`~odoo.fields.Char` field that contains a short description of the page (sometimes used in search engines results)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:957 -msgid "``website_meta_keywords``: :class:`~odoo.fields.Char` field that contains some keywords to help your page to be classified more precisely by search engines; the \"Promote\" tool will help you select lexically-related keywords easily" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:961 -msgid "These fields are editable in the frontend using the \"Promote\" tool from the Editor toolbar. Setting these fields can help search engines to better index your pages. Note that search engines do not base their results only on these metadata; the best SEO practice should still be to get referenced by reliable sources." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:969 -msgid "Others" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:974 -msgid "Customer Rating" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:976 -msgid "The rating mixin allows sending email to ask for customer rating, automatic transitioning in a kanban processes and aggregating statistics on your ratings." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:980 -msgid "Adding rating on your model" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:982 -msgid "To add rating support, simply inherit the ``rating.mixin`` model:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:993 -msgid "The behaviour of the mixin adapts to your model:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:995 -msgid "The ``rating.rating`` record will be linked to the ``partner_id`` field of your model (if the field is present)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:998 -msgid "this behaviour can be overridden with the function ``rating_get_partner_id()`` if you use another field than ``partner_id``" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:1001 -msgid "The ``rating.rating`` record will be linked to the partner of the ``user_id`` field of your model (if the field is present) (i.e. the partner who is rated)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:1004 -msgid "this behaviour can be overridden with the function ``rating_get_rated_partner_id()`` if you use another field than ``user_id`` (note that the function must return a ``res.partner``, for ``user_id`` the system automatically fetches the partner of the user)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:1009 -msgid "The chatter history will display the rating event (if your model inherits from ``mail.thread``)" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:1013 -msgid "Send rating requests by e-mail" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:1015 -msgid "If you wish to send emails to request a rating, simply generate an e-mail with links to the rating object. A very basic email template could look like this:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:1039 -msgid "Your customer will then receive an e-mail with links to a simple webpage allowing them to provide a feedback on their interaction with your users (including a free-text feedback message)." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:1043 -msgid "You can then quite easily integrate your ratings with your form view by defining an action for the ratings:" -msgstr "" - -#: ../../content/developer/reference/mixins.rst:1069 -msgid "Note that there are default views (kanban,pivot,graph) for ratings which allow you a quick bird's eye view of your customer ratings." -msgstr "" - -#: ../../content/developer/reference/mixins.rst:1074 -msgid "``project.task`` in the Project (*rating_project*) Application" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:6 -msgid "Mobile JavaScript" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:11 -msgid "In Odoo 10.0 we released a mobile app which allows you to access all **Odoo apps** (even your customized modules)." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:14 -msgid "The application is a combination of **Odoo Web** and **Native Mobile components**. In other words it is a Odoo Web instance loaded inside a native, mobile, WebView container." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:17 -msgid "This page documents how you can access mobile native components like Camera, Vibration, Notification and Toast through Odoo Web (via JavaScript). For this, you do not need to be a mobile developer, if you know Odoo JavaScript API you can access all available mobile features." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:22 -msgid "These features work with **Odoo Enterprise 10.0+** only" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:25 -msgid "How does it work?" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:27 -msgid "Internal workings of the mobile application:" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:31 -msgid "Of course, it is a web page that loads on a Mobile Native Web container. But it is integrated in such a way that you can access native resources from your web JavaScript." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:35 -msgid "WebPages (Odoo Web) is on the top of each layer, where the second layer is a Bridge between Odoo Web (JS) and the native mobile components." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:38 -msgid "When any call from JavaScript is triggered it passes through Bridge and Bridge passes it to the native invoker to perform that action." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:41 -msgid "When the native component has done its work, it is passed to the Bridge again and you get the output in JavaScript." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:44 -msgid "Process time taken by the Native component depends on what you are requesting from the Native resources. For example the Camera or GPS Location." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:48 -msgid "How to use it?" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:50 -msgid "Just like the Odoo Web Framework, the Mobile API can be used anywhere by getting the object from **web_mobile.rpc**" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:55 -msgid "The mobile RPC object provides a list of methods that are available (this only works with the mobile app)." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:58 -msgid "Check if the method is available and then execute it." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:61 -msgid "Methods" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:63 -msgid "Each of the methods returns a JQuery Deffered object which returns a data JSON dictionary" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:67 -msgid "Show Toast in device" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:71 -msgid "**message** text to display" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:73 -msgid "A toast provides simple feedback about an operation in a small popup. It only fills the amount of space required for the message and the current activity remains visible and interactive." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:85 -msgid "Vibrating device" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:90 -msgid "Vibrates constantly for the specified period of time (in milliseconds)." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:93 -msgid "Vibrate mobile device with given duration." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:100 -msgid "Show snackbar with action" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:104 -msgid "(*required*) **Message** to show in snackbar and action **button label** in Snackbar (optional)" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:105 -msgid "``True`` if the user clicks on the Action button, ``False`` if SnackBar auto dismissed after some time." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:107 -msgid "Snackbars provide lightweight feedback about an operation. They show a brief message at the bottom of the screen on mobile or in the lower left corner on larger devices. Snackbars appear above all the other elements on the screen and only one can be displayed at a time." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:125 -msgid "Showing notification" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:129 -msgid "**title** (first row) of the notification, **message** (second row) of the notification, in a standard notification." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:131 -msgid "A notification is a message you can display to the user outside of your application's normal UI. When you tell the system to issue a notification, it first appears as an icon in the notification area. To see the details of the notification, the user opens the notification drawer. Both the notification area and the notification drawer are system-controlled areas that the user can view at any time." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:146 -msgid "Create contact in device" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:150 -msgid "Dictionary with contact details. Possible keys (name, mobile, phone, fax, email, website, street, street2, country_id, state_id, city, zip, parent_id, function and image)" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:152 -msgid "Create a new device contact with the given contact details." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:179 -msgid "Scanning barcodes" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:183 -msgid "Scanned ``code`` from any barcode" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:185 -msgid "The barcode API detects barcodes in real-time, on the device, in any orientation." -msgstr "" - -#: ../../content/developer/reference/mobile.rst:187 -msgid "The barcode API can read the following barcode formats:" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:189 -msgid "1D barcodes: EAN-13, EAN-8, UPC-A, UPC-E, Code-39, Code-93, Code-128, ITF, Codabar" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:190 -msgid "2D barcodes: QR Code, Data Matrix, PDF-417, AZTEC" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:201 -msgid "Switching account in device" -msgstr "" - -#: ../../content/developer/reference/mobile.rst:205 -msgid "Use switchAccount to switch from one account to another on the device." -msgstr "" - -#: ../../content/developer/reference/module.rst:4 -msgid "Module Manifests" -msgstr "" - -#: ../../content/developer/reference/module.rst:11 -msgid "Manifest" -msgstr "" - -#: ../../content/developer/reference/module.rst:13 -msgid "The manifest file serves to declare a python package as an Odoo module and to specify module metadata." -msgstr "" - -#: ../../content/developer/reference/module.rst:16 -msgid "It is a file called ``__manifest__.py`` and contains a single Python dictionary, where each key specifies module metadatum." -msgstr "" - -#: ../../content/developer/reference/module.rst:40 -msgid "Available manifest fields are:" -msgstr "" - -#: ../../content/developer/reference/module.rst:42 -msgid "``name`` (``str``, required)" -msgstr "" - -#: ../../content/developer/reference/module.rst:43 -msgid "the human-readable name of the module" -msgstr "" - -#: ../../content/developer/reference/module.rst:44 -msgid "``version`` (``str``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:45 -msgid "this module's version, should follow `semantic versioning`_ rules" -msgstr "" - -#: ../../content/developer/reference/module.rst:46 -msgid "``description`` (``str``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:47 -msgid "extended description for the module, in reStructuredText" -msgstr "" - -#: ../../content/developer/reference/module.rst:48 -msgid "``author`` (``str``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:49 -msgid "name of the module author" -msgstr "" - -#: ../../content/developer/reference/module.rst:50 -msgid "``website`` (``str``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:51 -msgid "website URL for the module author" -msgstr "" - -#: ../../content/developer/reference/module.rst:65 -msgid "``license`` (``str``, defaults: ``LGPL-3``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:53 -msgid "distribution license for the module. Possible values:" -msgstr "" - -#: ../../content/developer/reference/module.rst:56 -msgid "`GPL-2`" -msgstr "" - -#: ../../content/developer/reference/module.rst:57 -msgid "`GPL-2 or any later version`" -msgstr "" - -#: ../../content/developer/reference/module.rst:58 -msgid "`GPL-3`" -msgstr "" - -#: ../../content/developer/reference/module.rst:59 -msgid "`GPL-3 or any later version`" -msgstr "" - -#: ../../content/developer/reference/module.rst:60 -msgid "`AGPL-3`" -msgstr "" - -#: ../../content/developer/reference/module.rst:61 -msgid "`LGPL-3`" -msgstr "" - -#: ../../content/developer/reference/module.rst:62 -msgid "`Other OSI approved licence`" -msgstr "" - -#: ../../content/developer/reference/module.rst:63 -msgid "`OEEL-1` (Odoo Enterprise Edition License v1.0)" -msgstr "" - -#: ../../content/developer/reference/module.rst:64 -msgid "`OPL-1` (Odoo Proprietary License v1.0)" -msgstr "" - -#: ../../content/developer/reference/module.rst:65 -msgid "`Other proprietary`" -msgstr "" - -#: ../../content/developer/reference/module.rst:73 -msgid "``category`` (``str``, default: ``Uncategorized``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:68 -msgid "classification category within Odoo, rough business domain for the module." -msgstr "" - -#: ../../content/developer/reference/module.rst:70 -msgid "Although using `existing categories`_ is recommended, the field is freeform and unknown categories are created on-the-fly. Category hierarchies can be created using the separator ``/`` e.g. ``Foo / Bar`` will create a category ``Foo``, a category ``Bar`` as child category of ``Foo``, and will set ``Bar`` as the module's category." -msgstr "" - -#: ../../content/developer/reference/module.rst:80 -msgid "``depends`` (``list(str)``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:76 -msgid "Odoo modules which must be loaded before this one, either because this module uses features they create or because it alters resources they define." -msgstr "" - -#: ../../content/developer/reference/module.rst:80 -msgid "When a module is installed, all of its dependencies are installed before it. Likewise dependencies are loaded before a module is loaded." -msgstr "" - -#: ../../content/developer/reference/module.rst:83 -msgid "``data`` (``list(str)``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:83 -msgid "List of data files which must always be installed or updated with the module. A list of paths from the module root directory" -msgstr "" - -#: ../../content/developer/reference/module.rst:86 -msgid "``demo`` (``list(str)``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:86 -msgid "List of data files which are only installed or updated in *demonstration mode*" -msgstr "" - -#: ../../content/developer/reference/module.rst:97 -msgid "``auto_install`` (``bool``, default: ``False``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:89 -msgid "If ``True``, this module will automatically be installed if all of its dependencies are installed." -msgstr "" - -#: ../../content/developer/reference/module.rst:92 -msgid "It is generally used for \"link modules\" implementing synergic integration between two otherwise independent modules." -msgstr "" - -#: ../../content/developer/reference/module.rst:95 -msgid "For instance ``sale_crm`` depends on both ``sale`` and ``crm`` and is set to ``auto_install``. When both ``sale`` and ``crm`` are installed, it automatically adds CRM campaigns tracking to sale orders without either ``sale`` or ``crm`` being aware of one another" -msgstr "" - -#: ../../content/developer/reference/module.rst:110 -msgid "``external_dependencies`` (``dict(key=list(str))``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:100 -msgid "A dictionary containing python and/or binary dependencies." -msgstr "" - -#: ../../content/developer/reference/module.rst:102 -msgid "For python dependencies, the ``python`` key must be defined for this dictionary and a list of python modules to be imported should be assigned to it." -msgstr "" - -#: ../../content/developer/reference/module.rst:106 -msgid "For binary dependencies, the ``bin`` key must be defined for this dictionary and a list of binary executable names should be assigned to it." -msgstr "" - -#: ../../content/developer/reference/module.rst:109 -msgid "The module won't be installed if either the python module is not installed in the host machine or the binary executable is not found within the host machine's PATH environment variable." -msgstr "" - -#: ../../content/developer/reference/module.rst:114 -msgid "``application`` (``bool``, default: ``False``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:113 -msgid "Whether the module should be considered as a fully-fledged application (``True``) or is just a technical module (``False``) that provides some extra functionality to an existing application module." -msgstr "" - -#: ../../content/developer/reference/module.rst:117 -msgid "``css`` (``list(str)``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:117 -msgid "Specify css files with custom rules to be imported, these files should be located in ``static/src/css`` inside the module." -msgstr "" - -#: ../../content/developer/reference/module.rst:119 -msgid "``images`` (``list(str)``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:120 -msgid "Specify image files to be used by the module." -msgstr "" - -#: ../../content/developer/reference/module.rst:121 -msgid "``installable`` (``bool`` default: ``True``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:122 -msgid "Whether a user should be able to install the module from the Web UI or not." -msgstr "" - -#: ../../content/developer/reference/module.rst:124 -msgid "``maintainer`` (``str``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:124 -msgid "Person or entity in charge of the maintenance of this module, by default it is assumed that the author is the maintainer." -msgstr "" - -#: ../../content/developer/reference/module.rst:140 -msgid "``{pre_init, post_init, uninstall}_hook`` (``str``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:127 -msgid "Hooks for module installation/uninstallation, their value should be a string representing the name of a function defined inside the module's ``__init__.py``." -msgstr "" - -#: ../../content/developer/reference/module.rst:131 -msgid "``pre_init_hook`` takes a cursor as its only argument, this function is executed prior to the module's installation." -msgstr "" - -#: ../../content/developer/reference/module.rst:134 -msgid "``post_init_hook`` takes a cursor and a registry as its arguments, this function is executed right after the module's installation." -msgstr "" - -#: ../../content/developer/reference/module.rst:137 -msgid "``uninstall_hook`` takes a cursor and a registry as its arguments, this function is executed after the module's uninstallation." -msgstr "" - -#: ../../content/developer/reference/module.rst:140 -msgid "These hooks should only be used when setup/cleanup required for this module is either extremely difficult or impossible through the api." -msgstr "" - -#: ../../content/developer/reference/module.rst:143 -msgid "``active`` (``bool``)" -msgstr "" - -#: ../../content/developer/reference/module.rst:143 -msgid "This indicates whether this module must install automatically or not." -msgstr "" - -#: ../../content/developer/reference/orm.rst:6 -msgid "ORM API" -msgstr "" - -#: ../../content/developer/reference/orm.rst:14 -msgid "Models" -msgstr "" - -#: ../../content/developer/reference/orm.rst:16 -msgid "Model fields are defined as attributes on the model itself::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:24 -msgid "this means you cannot define a field and a method with the same name, the last one will silently overwrite the former ones." -msgstr "" - -#: ../../content/developer/reference/orm.rst:27 -msgid "By default, the field's label (user-visible name) is a capitalized version of the field name, this can be overridden with the ``string`` parameter. ::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:32 -msgid "For the list of field types and parameters, see :ref:`the fields reference `." -msgstr "" - -#: ../../content/developer/reference/orm.rst:35 -msgid "Default values are defined as parameters on fields, either as a value::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:39 -msgid "or as a function called to compute the default value, which should return that value::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:85 -msgid "AbstractModel" -msgstr "" - -#: ../../content/developer/reference/orm.rst:90 -msgid "Model" -msgstr "" - -#: ../../content/developer/reference/orm.rst:99 -msgid "TransientModel" -msgstr "" - -#: ../../content/developer/reference/orm.rst:111 -#: ../../content/developer/reference/views.rst:36 -msgid "Fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:123 -msgid "Basic Fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:136 -msgid "Advanced Fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:153 -msgid "Date(time) Fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:155 -msgid ":class:`Dates ` and :class:`Datetimes ` are very important fields in any kind of business application. Their misuse can create invisible yet painful bugs, this section aims to provide Odoo developers with the knowledge required to avoid misusing these fields." -msgstr "" - -#: ../../content/developer/reference/orm.rst:161 -msgid "When assigning a value to a Date/Datetime field, the following options are valid:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:163 -msgid "A `date` or `datetime` object." -msgstr "" - -#: ../../content/developer/reference/orm.rst:164 -msgid "A string in the proper server format:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:166 -msgid "``YYYY-MM-DD`` for :class:`~odoo.fields.Date` fields," -msgstr "" - -#: ../../content/developer/reference/orm.rst:167 -msgid "``YYYY-MM-DD HH:MM:SS`` for :class:`~odoo.fields.Datetime` fields." -msgstr "" - -#: ../../content/developer/reference/orm.rst:169 -msgid "`False` or `None`." -msgstr "" - -#: ../../content/developer/reference/orm.rst:171 -msgid "The Date and Datetime fields class have helper methods to attempt conversion into a compatible type:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:174 -msgid ":func:`~odoo.fields.Date.to_date` will convert to a :class:`datetime.date`" -msgstr "" - -#: ../../content/developer/reference/orm.rst:175 -msgid ":func:`~odoo.fields.Datetime.to_datetime` will convert to a :class:`datetime.datetime`." -msgstr "" - -#: ../../content/developer/reference/orm.rst:179 -msgid "To parse date/datetimes coming from external sources::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:183 -msgid "Date / Datetime comparison best practices:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:185 -msgid "Date fields can **only** be compared to date objects." -msgstr "" - -#: ../../content/developer/reference/orm.rst:186 -msgid "Datetime fields can **only** be compared to datetime objects." -msgstr "" - -#: ../../content/developer/reference/orm.rst:188 -msgid "Strings representing dates and datetimes can be compared between each other, however the result may not be the expected result, as a datetime string will always be greater than a date string, therefore this practice is **heavily** discouraged." -msgstr "" - -#: ../../content/developer/reference/orm.rst:194 -msgid "Common operations with dates and datetimes such as addition, substraction or fetching the start/end of a period are exposed through both :class:`~odoo.fields.Date` and :class:`~odoo.fields.Datetime`. These helpers are also available by importing `odoo.tools.date_utils`." -msgstr "" - -#: ../../content/developer/reference/orm.rst:199 -msgid "Timezones" -msgstr "" - -#: ../../content/developer/reference/orm.rst:201 -msgid "Datetime fields are stored as `timestamp without timezone` columns in the database and are stored in the UTC timezone. This is by design, as it makes the Odoo database independent from the timezone of the hosting server system. Timezone conversion is managed entirely by the client side." -msgstr "" - -#: ../../content/developer/reference/orm.rst:214 -msgid "Relational Fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:223 -msgid "Pseudo-relational fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:232 -msgid "Computed Fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:234 -msgid "Fields can be computed (instead of read straight from the database) using the ``compute`` parameter. **It must assign the computed value to the field**. If it uses the values of other *fields*, it should specify those fields using :func:`~odoo.api.depends`. ::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:247 -msgid "dependencies can be dotted paths when using sub-fields::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:254 -msgid "computed fields are not stored by default, they are computed and returned when requested. Setting ``store=True`` will store them in the database and automatically enable searching." -msgstr "" - -#: ../../content/developer/reference/orm.rst:257 -msgid "searching on a computed field can also be enabled by setting the ``search`` parameter. The value is a method name returning a :ref:`reference/orm/domains`. ::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:268 -msgid "The search method is invoked when processing domains before doing an actual search on the model. It must return a domain equivalent to the condition: ``field operator value``." -msgstr "" - -#: ../../content/developer/reference/orm.rst:274 -msgid "Computed fields are readonly by default. To allow *setting* values on a computed field, use the ``inverse`` parameter. It is the name of a function reversing the computation and setting the relevant fields::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:290 -msgid "multiple fields can be computed at the same time by the same method, just use the same method on all fields and set all of them::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:306 -msgid "While it is possible to use the same compute method for multiple fields, it is not recommended to do the same for the inverse method." -msgstr "" - -#: ../../content/developer/reference/orm.rst:310 -msgid "During the computation of the inverse, **all** fields that use said inverse are protected, meaning that they can't be computed, even if their value is not in the cache." -msgstr "" - -#: ../../content/developer/reference/orm.rst:314 -msgid "If any of those fields is accessed and its value is not in cache, the ORM will simply return a default value of `False` for these fields. This means that the value of the inverse fields (other than the one triggering the inverse method) may not give their correct value and this will probably break the expected behavior of the inverse method." -msgstr "" - -#: ../../content/developer/reference/orm.rst:323 -msgid "Related fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:325 -msgid "A special case of computed fields are *related* (proxy) fields, which provide the value of a sub-field on the current record. They are defined by setting the ``related`` parameter and like regular computed fields they can be stored::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:332 -msgid "The value of a related field is given by following a sequence of relational fields and reading a field on the reached model. The complete sequence of fields to traverse is specified by the ``related`` attribute." -msgstr "" - -#: ../../content/developer/reference/orm.rst:336 -msgid "Some field attributes are automatically copied from the source field if they are not redefined: ``string``, ``help``, ``readonly``, ``required`` (only if all fields in the sequence are required), ``groups``, ``digits``, ``size``, ``translate``, ``sanitize``, ``selection``, ``comodel_name``, ``domain``, ``context``. All semantic-free attributes are copied from the source field." -msgstr "" - -#: ../../content/developer/reference/orm.rst:343 -msgid "By default, the values of related fields are not stored to the database. Add the attribute ``store=True`` to make it stored, just like computed fields. Related fields are automatically recomputed when their dependencies are modified." -msgstr "" - -#: ../../content/developer/reference/orm.rst:348 -msgid "The related fields are computed in sudo mode." -msgstr "" - -#: ../../content/developer/reference/orm.rst:352 -msgid "You cannot chain :class:`~odoo.fields.Many2many` or :class:`~odoo.fields.One2many` fields in ``related`` fields dependencies." -msgstr "" - -#: ../../content/developer/reference/orm.rst:354 -msgid "``related`` can be used to refer to a :class:`~odoo.fields.One2many` or :class:`~odoo.fields.Many2many` field on another model on the condition that it's done through a ``Many2one`` relation on the current model. ``One2many`` and ``Many2many`` are not supported and the results will not be aggregated correctly::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:375 -msgid "Automatic fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:379 -msgid "Identifier :class:`field `" -msgstr "" - -#: ../../content/developer/reference/orm.rst:381 -msgid "If length of current recordset is 1, return id of unique record in it." -msgstr "" - -#: ../../content/developer/reference/orm.rst:383 -msgid "Raise an Error otherwise." -msgstr "" - -#: ../../content/developer/reference/orm.rst:388 -msgid "Access Log fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:390 -msgid "These fields are automatically set and updated if :attr:`~odoo.models.BaseModel._log_access` is enabled. It can be disabled to avoid creating or updating those fields on tables for which they are not useful." -msgstr "" - -#: ../../content/developer/reference/orm.rst:395 -msgid "By default, :attr:`~odoo.models.BaseModel._log_access` is set to the same value as :attr:`~odoo.models.BaseModel._auto`" -msgstr "" - -#: ../../content/developer/reference/orm.rst:400 -msgid "Stores when the record was created, :class:`~odoo.fields.Datetime`" -msgstr "" - -#: ../../content/developer/reference/orm.rst:404 -msgid "Stores *who* created the record, :class:`~odoo.fields.Many2one` to a ``res.users``." -msgstr "" - -#: ../../content/developer/reference/orm.rst:409 -msgid "Stores when the record was last updated, :class:`~odoo.fields.Datetime`" -msgstr "" - -#: ../../content/developer/reference/orm.rst:413 -msgid "Stores who last updated the record, :class:`~odoo.fields.Many2one` to a ``res.users``." -msgstr "" - -#: ../../content/developer/reference/orm.rst:416 -msgid ":attr:`~odoo.models.BaseModel._log_access` *must* be enabled on :class:`~odoo.models.TransientModel`." -msgstr "" - -#: ../../content/developer/reference/orm.rst:422 -msgid "Reserved Field names" -msgstr "" - -#: ../../content/developer/reference/orm.rst:424 -msgid "A few field names are reserved for pre-defined behaviors beyond that of automated fields. They should be defined on a model when the related behavior is desired:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:430 -msgid "default value for :attr:`~odoo.models.BaseModel._rec_name`, used to display records in context where a representative \"naming\" is necessary." -msgstr "" - -#: ../../content/developer/reference/orm.rst:434 -#: ../../content/developer/reference/orm.rst:472 -msgid ":class:`~odoo.fields.Char`" -msgstr "" - -#: ../../content/developer/reference/orm.rst:438 -msgid "toggles the global visibility of the record, if ``active`` is set to ``False`` the record is invisible in most searches and listing." -msgstr "" - -#: ../../content/developer/reference/orm.rst:441 -msgid ":class:`~odoo.fields.Boolean`" -msgstr "" - -#: ../../content/developer/reference/orm.rst:452 -msgid "lifecycle stages of the object, used by the ``states`` attribute on :class:`fields `." -msgstr "" - -#: ../../content/developer/reference/orm.rst:455 -msgid ":class:`~odoo.fields.Selection`" -msgstr "" - -#: ../../content/developer/reference/orm.rst:459 -msgid "default_value of :attr:`~._parent_name`, used to organize records in a tree structure and enables the ``child_of`` and ``parent_of`` operators in domains." -msgstr "" - -#: ../../content/developer/reference/orm.rst:463 -msgid ":class:`~odoo.fields.Many2one`" -msgstr "" - -#: ../../content/developer/reference/orm.rst:467 -msgid "When :attr:`~._parent_store` is set to True, used to store a value reflecting the tree structure of :attr:`~._parent_name`, and to optimize the operators ``child_of`` and ``parent_of`` in search domains. It must be declared with ``index=True`` for proper operation." -msgstr "" - -#: ../../content/developer/reference/orm.rst:476 -msgid "Main field name used for Odoo multi-company behavior." -msgstr "" - -#: ../../content/developer/reference/orm.rst:478 -msgid "Used by `:meth:~odoo.models._check_company` to check multi company consistency. Defines whether a record is shared between companies (no value) or only accessible by the users of a given company." -msgstr "" - -#: ../../content/developer/reference/orm.rst:482 -msgid ":class:`~odoo.fields.Many2one` :type: :class:`~odoo.addons.base.models.res_company`" -msgstr "" - -#: ../../content/developer/reference/orm.rst:486 -msgid "Recordsets" -msgstr "" - -#: ../../content/developer/reference/orm.rst:488 -msgid "Interactions with models and records are performed through recordsets, an ordered collection of records of the same model." -msgstr "" - -#: ../../content/developer/reference/orm.rst:491 -msgid "Contrary to what the name implies, it is currently possible for recordsets to contain duplicates. This may change in the future." -msgstr "" - -#: ../../content/developer/reference/orm.rst:494 -msgid "Methods defined on a model are executed on a recordset, and their ``self`` is a recordset::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:504 -msgid "Iterating on a recordset will yield new sets of *a single record* (\"singletons\"), much like iterating on a Python string yields strings of a single characters::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:514 -msgid "Field access" -msgstr "" - -#: ../../content/developer/reference/orm.rst:516 -msgid "Recordsets provide an \"Active Record\" interface: model fields can be read and written directly from the record as attributes." -msgstr "" - -#: ../../content/developer/reference/orm.rst:521 -msgid "When accessing non-relational fields on a recordset of potentially multiple records, use :meth:`~odoo.models.BaseModel.mapped`::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:526 -msgid "Field values can also be accessed like dict items, which is more elegant and safer than ``getattr()`` for dynamic field names. Setting a field's value triggers an update to the database::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:541 -msgid "Trying to read a field on multiple records will raise an error for non relational fields." -msgstr "" - -#: ../../content/developer/reference/orm.rst:544 -msgid "Accessing a relational field (:class:`~odoo.fields.Many2one`, :class:`~odoo.fields.One2many`, :class:`~odoo.fields.Many2many`) *always* returns a recordset, empty if the field is not set." -msgstr "" - -#: ../../content/developer/reference/orm.rst:549 -msgid "Record cache and prefetching" -msgstr "" - -#: ../../content/developer/reference/orm.rst:551 -msgid "Odoo maintains a cache for the fields of the records, so that not every field access issues a database request, which would be terrible for performance. The following example queries the database only for the first statement::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:558 -msgid "To avoid reading one field on one record at a time, Odoo *prefetches* records and fields following some heuristics to get good performance. Once a field must be read on a given record, the ORM actually reads that field on a larger recordset, and stores the returned values in cache for later use. The prefetched recordset is usually the recordset from which the record comes by iteration. Moreover, all simple stored fields (boolean, integer, float, char, text, date, datetime, selection, many2one) are fetched altogether; they correspond to the columns of the model's table, and are fetched efficiently in the same query." -msgstr "" - -#: ../../content/developer/reference/orm.rst:567 -msgid "Consider the following example, where ``partners`` is a recordset of 1000 records. Without prefetching, the loop would make 2000 queries to the database. With prefetching, only one query is made::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:576 -msgid "The prefetching also works on *secondary records*: when relational fields are read, their values (which are records) are subscribed for future prefetching. Accessing one of those secondary records prefetches all secondary records from the same model. This makes the following example generate only two queries, one for partners and one for countries::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:591 -msgid "Method decorators" -msgstr "" - -#: ../../content/developer/reference/orm.rst:605 -msgid "With sphinx 2.0 : autodecorator" -msgstr "" - -#: ../../content/developer/reference/orm.rst:607 -msgid "Add in Views reference * It is possible to suppress the trigger from a specific field by adding ``on_change=\"0\"`` in a view::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:613 -msgid "will not trigger any interface update when the field is edited by the user, even if there are function fields or explicit onchange depending on that field." -msgstr "" - -#: ../../content/developer/reference/orm.rst:620 -msgid "Environment" -msgstr "" - -#: ../../content/developer/reference/orm.rst:622 -msgid "The :class:`~odoo.api.Environment` stores various contextual data used by the ORM: the database cursor (for database queries), the current user (for access rights checking) and the current context (storing arbitrary metadata). The environment also stores caches." -msgstr "" - -#: ../../content/developer/reference/orm.rst:627 -msgid "All recordsets have an environment, which is immutable, can be accessed using :attr:`~odoo.models.Model.env` and gives access to:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:630 -msgid "the current user (:attr:`~odoo.api.Environment.user`)" -msgstr "" - -#: ../../content/developer/reference/orm.rst:631 -msgid "the cursor (:attr:`~odoo.api.Environment.cr`)" -msgstr "" - -#: ../../content/developer/reference/orm.rst:632 -msgid "the superuser flag (:attr:`~odoo.api.Environment.su`)" -msgstr "" - -#: ../../content/developer/reference/orm.rst:633 -msgid "or the context (:attr:`~odoo.api.Environment.context`)" -msgstr "" - -#: ../../content/developer/reference/orm.rst:644 -msgid "When creating a recordset from an other recordset, the environment is inherited. The environment can be used to get an empty recordset in an other model, and query that model::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:668 -msgid "Altering the environment" -msgstr "" - -#: ../../content/developer/reference/orm.rst:685 -msgid "SQL Execution" -msgstr "" - -#: ../../content/developer/reference/orm.rst:687 -msgid "The :attr:`~odoo.api.Environment.cr` attribute on environments is the cursor for the current database transaction and allows executing SQL directly, either for queries which are difficult to express using the ORM (e.g. complex joins) or for performance reasons::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:694 -msgid "Because models use the same cursor and the :class:`~odoo.api.Environment` holds various caches, these caches must be invalidated when *altering* the database in raw SQL, or further uses of models may become incoherent. It is necessary to clear caches when using ``CREATE``, ``UPDATE`` or ``DELETE`` in SQL, but not ``SELECT`` (which simply reads the database)." -msgstr "" - -#: ../../content/developer/reference/orm.rst:701 -msgid "Clearing caches can be performed using the :meth:`~odoo.models.Model.invalidate_cache` method." -msgstr "" - -#: ../../content/developer/reference/orm.rst:707 -msgid "Executing raw SQL bypasses the ORM, and by consequent, Odoo security rules. Please make sure your queries are sanitized when using user input and prefer using ORM utilities if you don't really need to use SQL queries." -msgstr "" - -#: ../../content/developer/reference/orm.rst:715 -msgid "Common ORM methods" -msgstr "" - -#: ../../content/developer/reference/orm.rst:720 -msgid "Create/update" -msgstr "" - -#: ../../content/developer/reference/orm.rst:722 -msgid "api.model_create_multi information" -msgstr "" - -#: ../../content/developer/reference/orm.rst:737 -msgid "Search/Read" -msgstr "" - -#: ../../content/developer/reference/orm.rst:752 -msgid "Fields/Views" -msgstr "" - -#: ../../content/developer/reference/orm.rst:761 -msgid "Search domains" -msgstr "" - -#: ../../content/developer/reference/orm.rst:763 -msgid "A domain is a list of criteria, each criterion being a triple (either a ``list`` or a ``tuple``) of ``(field_name, operator, value)`` where:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:769 -msgid "``field_name`` (``str``)" -msgstr "" - -#: ../../content/developer/reference/orm.rst:767 -msgid "a field name of the current model, or a relationship traversal through a :class:`~odoo.fields.Many2one` using dot-notation e.g. ``'street'`` or ``'partner_id.country'``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:823 -msgid "``operator`` (``str``)" -msgstr "" - -#: ../../content/developer/reference/orm.rst:772 -msgid "an operator used to compare the ``field_name`` with the ``value``. Valid operators are:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:775 -msgid "``=``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:776 -msgid "equals to" -msgstr "" - -#: ../../content/developer/reference/orm.rst:777 -msgid "``!=``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:778 -msgid "not equals to" -msgstr "" - -#: ../../content/developer/reference/orm.rst:779 -msgid "``>``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:780 -msgid "greater than" -msgstr "" - -#: ../../content/developer/reference/orm.rst:781 -msgid "``>=``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:782 -msgid "greater than or equal to" -msgstr "" - -#: ../../content/developer/reference/orm.rst:783 -msgid "``<``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:784 -msgid "less than" -msgstr "" - -#: ../../content/developer/reference/orm.rst:785 -msgid "``<=``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:786 -msgid "less than or equal to" -msgstr "" - -#: ../../content/developer/reference/orm.rst:788 -msgid "``=?``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:788 -msgid "unset or equals to (returns true if ``value`` is either ``None`` or ``False``, otherwise behaves like ``=``)" -msgstr "" - -#: ../../content/developer/reference/orm.rst:792 -msgid "``=like``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:791 -msgid "matches ``field_name`` against the ``value`` pattern. An underscore ``_`` in the pattern stands for (matches) any single character; a percent sign ``%`` matches any string of zero or more characters." -msgstr "" - -#: ../../content/developer/reference/orm.rst:795 -msgid "``like``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:795 -msgid "matches ``field_name`` against the ``%value%`` pattern. Similar to ``=like`` but wraps ``value`` with '%' before matching" -msgstr "" - -#: ../../content/developer/reference/orm.rst:797 -msgid "``not like``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:798 -msgid "doesn't match against the ``%value%`` pattern" -msgstr "" - -#: ../../content/developer/reference/orm.rst:799 -msgid "``ilike``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:800 -msgid "case insensitive ``like``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:801 -msgid "``not ilike``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:802 -msgid "case insensitive ``not like``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:803 -msgid "``=ilike``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:804 -msgid "case insensitive ``=like``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:806 -msgid "``in``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:806 -msgid "is equal to any of the items from ``value``, ``value`` should be a list of items" -msgstr "" - -#: ../../content/developer/reference/orm.rst:808 -msgid "``not in``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:809 -msgid "is unequal to all of the items from ``value``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:815 -msgid "``child_of``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:811 -msgid "is a child (descendant) of a ``value`` record (value can be either one item or a list of items)." -msgstr "" - -#: ../../content/developer/reference/orm.rst:814 -#: ../../content/developer/reference/orm.rst:821 -msgid "Takes the semantics of the model into account (i.e following the relationship field named by :attr:`~odoo.models.Model._parent_name`)." -msgstr "" - -#: ../../content/developer/reference/orm.rst:823 -msgid "``parent_of``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:818 -msgid "is a parent (ascendant) of a ``value`` record (value can be either one item or a list of items)." -msgstr "" - -#: ../../content/developer/reference/orm.rst:826 -msgid "variable type, must be comparable (through ``operator``) to the named field." -msgstr "" - -#: ../../content/developer/reference/orm.rst:829 -msgid "Domain criteria can be combined using logical operators in *prefix* form:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:832 -msgid "``'&'``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:832 -msgid "logical *AND*, default operation to combine criteria following one another. Arity 2 (uses the next 2 criteria or combinations)." -msgstr "" - -#: ../../content/developer/reference/orm.rst:834 -msgid "``'|'``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:835 -msgid "logical *OR*, arity 2." -msgstr "" - -#: ../../content/developer/reference/orm.rst:841 -msgid "``'!'``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:837 -msgid "logical *NOT*, arity 1." -msgstr "" - -#: ../../content/developer/reference/orm.rst:839 -msgid "Mostly to negate combinations of criteria Individual criterion generally have a negative form (e.g. ``=`` -> ``!=``, ``<`` -> ``>=``) which is simpler than negating the positive." -msgstr "" - -#: ../../content/developer/reference/orm.rst:845 -msgid "To search for partners named *ABC*, from belgium or germany, whose language is not english::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:853 -msgid "This domain is interpreted as:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:862 -msgid "Unlink" -msgstr "" - -#: ../../content/developer/reference/orm.rst:869 -msgid "Record(set) information" -msgstr "" - -#: ../../content/developer/reference/orm.rst:875 -msgid "Returns the environment of the given recordset." -msgstr "" - -#: ../../content/developer/reference/orm.rst:0 -msgid "type" -msgstr "" - -#: ../../content/developer/reference/orm.rst:877 -msgid ":class:`~odoo.api.Environment`" -msgstr "" - -#: ../../content/developer/reference/orm.rst:879 -msgid "Environment documentation" -msgstr "" - -#: ../../content/developer/reference/orm.rst:892 -msgid "Operations" -msgstr "" - -#: ../../content/developer/reference/orm.rst:894 -msgid "Recordsets are immutable, but sets of the same model can be combined using various set operations, returning new recordsets." -msgstr "" - -#: ../../content/developer/reference/orm.rst:899 -msgid "``record in set`` returns whether ``record`` (which must be a 1-element recordset) is present in ``set``. ``record not in set`` is the inverse operation" -msgstr "" - -#: ../../content/developer/reference/orm.rst:902 -msgid "``set1 <= set2`` and ``set1 < set2`` return whether ``set1`` is a subset of ``set2`` (resp. strict)" -msgstr "" - -#: ../../content/developer/reference/orm.rst:904 -msgid "``set1 >= set2`` and ``set1 > set2`` return whether ``set1`` is a superset of ``set2`` (resp. strict)" -msgstr "" - -#: ../../content/developer/reference/orm.rst:906 -msgid "``set1 | set2`` returns the union of the two recordsets, a new recordset containing all records present in either source" -msgstr "" - -#: ../../content/developer/reference/orm.rst:908 -msgid "``set1 & set2`` returns the intersection of two recordsets, a new recordset containing only records present in both sources" -msgstr "" - -#: ../../content/developer/reference/orm.rst:910 -msgid "``set1 - set2`` returns a new recordset containing only records of ``set1`` which are *not* in ``set2``" -msgstr "" - -#: ../../content/developer/reference/orm.rst:913 -msgid "Recordsets are iterable so the usual Python tools are available for transformation (:func:`python:map`, :func:`python:sorted`, :func:`~python:itertools.ifilter`, ...) however these return either a :class:`python:list` or an :term:`python:iterator`, removing the ability to call methods on their result, or to use set operations." -msgstr "" - -#: ../../content/developer/reference/orm.rst:919 -msgid "Recordsets therefore provide the following operations returning recordsets themselves (when possible):" -msgstr "" - -#: ../../content/developer/reference/orm.rst:923 -msgid "Filter" -msgstr "" - -#: ../../content/developer/reference/orm.rst:930 -#: ../../content/developer/reference/views.rst:1639 -msgid "Map" -msgstr "" - -#: ../../content/developer/reference/orm.rst:936 -msgid "Since V13, multi-relational field access is supported and works like a mapped call:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:945 -msgid "Sort" -msgstr "" - -#: ../../content/developer/reference/orm.rst:952 -msgid "Inheritance and extension" -msgstr "" - -#: ../../content/developer/reference/orm.rst:954 -msgid "Odoo provides three different mechanisms to extend models in a modular way:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:956 -msgid "creating a new model from an existing one, adding new information to the copy but leaving the original module as-is" -msgstr "" - -#: ../../content/developer/reference/orm.rst:958 -msgid "extending models defined in other modules in-place, replacing the previous version" -msgstr "" - -#: ../../content/developer/reference/orm.rst:960 -msgid "delegating some of the model's fields to records it contains" -msgstr "" - -#: ../../content/developer/reference/orm.rst:966 -msgid "Classical inheritance" -msgstr "" - -#: ../../content/developer/reference/orm.rst:968 -msgid "When using the :attr:`~odoo.models.Model._inherit` and :attr:`~odoo.models.Model._name` attributes together, Odoo creates a new model using the existing one (provided via :attr:`~odoo.models.Model._inherit`) as a base. The new model gets all the fields, methods and meta-information (defaults & al) from its base." -msgstr "" - -#: ../../content/developer/reference/orm.rst:996 -msgid "and using them::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1004 -msgid "will yield:" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1006 -msgid "\"This is model 0 record A\" \"This is model 1 record B\"" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1009 -msgid "the second model has inherited from the first model's ``check`` method and its ``name`` field, but overridden the ``call`` method, as when using standard :ref:`Python inheritance `." -msgstr "" - -#: ../../content/developer/reference/orm.rst:1014 -msgid "Extension" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1016 -msgid "When using :attr:`~odoo.models.Model._inherit` but leaving out :attr:`~odoo.models.Model._name`, the new model replaces the existing one, essentially extending it in-place. This is useful to add new fields or methods to existing models (created in other modules), or to customize or reconfigure them (e.g. to change their default sort order)::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1038 -msgid "will yield::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1045 -msgid "It will also yield the various :ref:`automatic fields ` unless they've been disabled" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1049 -msgid "Delegation" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1051 -msgid "The third inheritance mechanism provides more flexibility (it can be altered at runtime) but less power: using the :attr:`~odoo.models.Model._inherits` a model *delegates* the lookup of any field not found on the current model to \"children\" models. The delegation is performed via :class:`~odoo.fields.Reference` fields automatically set up on the parent model." -msgstr "" - -#: ../../content/developer/reference/orm.rst:1058 -msgid "The main difference is in the meaning. When using Delegation, the model **has one** instead of **is one**, turning the relationship in a composition instead of inheritance::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1100 -#: ../../content/developer/reference/qweb.rst:26 -#: ../../content/developer/reference/qweb.rst:36 -#: ../../content/developer/reference/qweb.rst:324 -msgid "will result in::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1105 -msgid "and it's possible to write directly on the delegated field::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1109 -msgid "when using delegation inheritance, methods are *not* inherited, only fields" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1114 -msgid "`_inherits` is more or less implemented, avoid it if you can;" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1115 -msgid "chained `_inherits` is essentially not implemented, we cannot guarantee anything on the final behavior." -msgstr "" - -#: ../../content/developer/reference/orm.rst:1119 -msgid "Fields Incremental Definition" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1121 -msgid "A field is defined as class attribute on a model class. If the model is extended, one can also extend the field definition by redefining a field with the same name and same type on the subclass. In that case, the attributes of the field are taken from the parent class and overridden by the ones given in subclasses." -msgstr "" - -#: ../../content/developer/reference/orm.rst:1127 -msgid "For instance, the second class below only adds a tooltip on the field ``state``::" -msgstr "" - -#: ../../content/developer/reference/orm.rst:1141 -msgid "Error management" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:8 -#: ../../content/developer/reference/views.rst:1774 -msgid "QWeb" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:10 -msgid "QWeb is the primary templating_ engine used by Odoo\\ [#othertemplates]_. It is an XML templating engine\\ [#genshif]_ and used mostly to generate HTML_ fragments and pages." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:14 -msgid "Template directives are specified as XML attributes prefixed with ``t-``, for instance ``t-if`` for :ref:`reference/qweb/conditionals`, with elements and other attributes being rendered directly." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:18 -msgid "To avoid element rendering, a placeholder element ```` is also available, which executes its directive but doesn't generate any output in and of itself::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:30 -msgid "if ``condition`` is true, but::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:45 -msgid "Data output" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:47 -msgid "QWeb has a primary output directive which automatically HTML-escape its content limiting XSS_ risks when displaying user-provided content: ``esc``." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:50 -msgid "``esc`` takes an expression, evaluates it and prints the content::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:54 -msgid "rendered with the value ``value`` set to ``42`` yields::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:58 -msgid "There is one other output directive ``raw`` which behaves the same as respectively ``esc`` but *does not HTML-escape its output*. It can be useful to display separately constructed markup (e.g. from functions) or already sanitized user-provided markup." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:68 -msgid "QWeb has a conditional directive ``if``, which evaluates an expression given as attribute value::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:77 -msgid "The element is rendered if the condition is true::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:83 -msgid "but if the condition is false it is removed from the result::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:88 -msgid "The conditional rendering applies to the bearer of the directive, which does not have to be ````::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:95 -msgid "will give the same results as the previous example." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:97 -msgid "Extra conditional branching directives ``t-elif`` and ``t-else`` are also available::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:110 -msgid "Loops" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:112 -msgid "QWeb has an iteration directive ``foreach`` which take an expression returning the collection to iterate on, and a second parameter ``t-as`` providing the name to use for the \"current item\" of the iteration::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:120 -#: ../../content/developer/reference/qweb.rst:209 -#: ../../content/developer/reference/qweb.rst:223 -#: ../../content/developer/reference/qweb.rst:234 -#: ../../content/developer/reference/qweb.rst:244 -msgid "will be rendered as::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:126 -msgid "Like conditions, ``foreach`` applies to the element bearing the directive's attribute, and" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:135 -msgid "is equivalent to the previous example." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:137 -msgid "``foreach`` can iterate on an array (the current item will be the current value) or a mapping (the current item will be the current key). Iterating on an integer (equivalent to iterating on an array between 0 inclusive and the provided integer exclusive) is still supported but deprecated." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:142 -msgid "In addition to the name passed via ``t-as``, ``foreach`` provides a few other variables for various data points:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:145 -msgid "``$as`` will be replaced by the name passed to ``t-as``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:150 -msgid ":samp:`{$as}_all` (deprecated)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:148 -msgid "the object being iterated over" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:150 -msgid "This variable is only available on JavaScript QWeb, not Python." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:153 -msgid ":samp:`{$as}_value`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:153 -msgid "the current iteration value, identical to ``$as`` for lists and integers, but for mappings it provides the value (where ``$as`` provides the key)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:155 -msgid ":samp:`{$as}_index`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:156 -msgid "the current iteration index (the first item of the iteration has index 0)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:157 -msgid ":samp:`{$as}_size`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:158 -msgid "the size of the collection if it is available" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:160 -msgid ":samp:`{$as}_first`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:160 -msgid "whether the current item is the first of the iteration (equivalent to :samp:`{$as}_index == 0`)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:164 -msgid ":samp:`{$as}_last`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:163 -msgid "whether the current item is the last of the iteration (equivalent to :samp:`{$as}_index + 1 == {$as}_size`), requires the iteratee's size be available" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:166 -msgid ":samp:`{$as}_parity` (deprecated)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:167 -msgid "either ``\"even\"`` or ``\"odd\"``, the parity of the current iteration round" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:169 -msgid ":samp:`{$as}_even` (deprecated)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:169 -msgid "a boolean flag indicating that the current iteration round is on an even index" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:173 -msgid ":samp:`{$as}_odd` (deprecated)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:172 -msgid "a boolean flag indicating that the current iteration round is on an odd index" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:175 -msgid "These extra variables provided and all new variables created into the ``foreach`` are only available in the scope of the``foreach``. If the variable exists outside the context of the ``foreach``, the value is copied at the end of the foreach into the global context." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:197 -msgid "attributes" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:199 -msgid "QWeb can compute attributes on-the-fly and set the result of the computation on the output node. This is done via the ``t-att`` (attribute) directive which exists in 3 different forms:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:210 -msgid ":samp:`t-att-{$name}`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:204 -msgid "an attribute called ``$name`` is created, the attribute value is evaluated and the result is set as the attribute's value::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:226 -msgid ":samp:`t-attf-{$name}`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:213 -msgid "same as previous, but the parameter is a :term:`format string` instead of just an expression, often useful to mix literal and non-literal string (e.g. classes)::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:235 -msgid ":samp:`t-att=mapping`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:229 -msgid "if the parameter is a mapping, each (key, value) pair generates a new attribute and its value::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:246 -msgid ":samp:`t-att=pair`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:238 -msgid "if the parameter is a pair (tuple or array of 2 element), the first item of the pair is the name of the attribute and the second item is the value::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:249 -msgid "setting variables" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:251 -msgid "QWeb allows creating variables from within the template, to memoize a computation (to use it multiple times), give a piece of data a clearer name, ..." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:255 -msgid "This is done via the ``set`` directive, which takes the name of the variable to create. The value to set can be provided in two ways:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:258 -msgid "a ``t-value`` attribute containing an expression, and the result of its evaluation will be set::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:264 -msgid "will print ``3``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:265 -msgid "if there is no ``t-value`` attribute, the node's body is rendered and set as the variable's value::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:273 -msgid "will generate ``<li>ok</li>`` (the content is escaped as we used the ``esc`` directive)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:276 -msgid "using the result of this operation is a significant use-case for the ``raw`` directive." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:280 -msgid "calling sub-templates" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:282 -msgid "QWeb templates can be used for top-level rendering, but they can also be used from within another template (to avoid duplication or give names to parts of templates) using the ``t-call`` directive::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:288 -msgid "This calls the named template with the execution context of the parent, if ``other_template`` is defined as::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:293 -msgid "the call above will be rendered as ``

`` (no content), but::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:298 -msgid "will be rendered as ``

1

``." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:300 -msgid "However this has the problem of being visible from outside the ``t-call``. Alternatively, content set in the body of the ``call`` directive will be evaluated *before* calling the sub-template, and can alter a local context::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:309 -msgid "The body of the ``call`` directive can be arbitrarily complex (not just ``set`` directives), and its rendered form will be available within the called template as a magical ``0`` variable::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:318 -msgid "being called thus::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:335 -#: ../../content/developer/reference/qweb.rst:436 -msgid "Exclusive directives" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:338 -msgid "Asset bundles" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:340 -msgid "have fme write these up because I've no idea how they work" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:343 -msgid "\"smart records\" fields formatting" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:345 -msgid "The ``t-field`` directive can only be used when performing field access (``a.b``) on a \"smart\" record (result of the ``browse`` method). It is able to automatically format based on field type, and is integrated in the website's rich text editing." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:350 -msgid "``t-options`` can be used to customize fields, the most common option is ``widget``, other options are field- or widget-dependent." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:354 -msgid "Debugging" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:362 -#: ../../content/developer/reference/qweb.rst:563 -msgid "``t-debug``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:357 -msgid "invokes a debugger using PDB's ``set_trace`` API. The parameter should be the name of a module, on which a ``set_trace`` method is called::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:362 -msgid "is equivalent to ``importlib.import_module(\"pdb\").set_trace()``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:365 -#: ../../content/developer/reference/qweb.rst:576 -msgid "Helpers" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:368 -msgid "Request-based" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:370 -msgid "Most Python-side uses of QWeb are in controllers (and during HTTP requests), in which case templates stored in the database (as :ref:`views `) can be trivially rendered by calling :meth:`odoo.http.HttpRequest.render`:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:381 -msgid "This automatically creates a :class:`~odoo.http.Response` object which can be returned from the controller (or further customized to suit)." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:385 -msgid "View-based" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:387 -msgid "At a deeper level than the previous helper is the ``render`` method on ``ir.ui.view``:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:392 -msgid "Renders a QWeb view/template by database id or :term:`external id`. Templates are automatically loaded from ``ir.ui.view`` records." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:395 -msgid "Sets up a number of default values in the rendering context:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:397 -#: ../../content/developer/webservices/upgrade.rst:113 -#: ../../content/developer/webservices/upgrade.rst:320 -msgid "``request``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:398 -msgid "the current :class:`~odoo.http.WebRequest` object, if any" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:399 -msgid "``debug``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:400 -msgid "whether the current request (if any) is in ``debug`` mode" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:401 -msgid ":func:`quote_plus `" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:402 -msgid "url-encoding utility function" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:403 -msgid ":mod:`json`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:404 -#: ../../content/developer/reference/qweb.rst:406 -#: ../../content/developer/reference/qweb.rst:408 -msgid "the corresponding standard library module" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:405 -msgid ":mod:`time`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:407 -msgid ":mod:`datetime`" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:409 -msgid "`relativedelta `_" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:410 -msgid "see module" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:412 -msgid "``keep_query``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:412 -msgid "the ``keep_query`` helper function" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:414 -msgid "context values to pass to QWeb for rendering" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:415 -msgid "name of the Odoo model to use for rendering, can be used to expand or customize QWeb locally (by creating a \"new\" qweb based on ``ir.qweb`` with alterations)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:421 -msgid "the members below are no longer relevant, section to rewrite" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:433 -#: ../../content/developer/reference/security.rst:356 -#: ../../content/developer/reference/security.rst:358 -msgid "Javascript" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:439 -msgid "Defining templates" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:441 -msgid "The ``t-name`` directive can only be placed at the top-level of a template file (direct children to the document root)::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:450 -msgid "It takes no other parameter, but can be used with a ```` element or any other. With a ```` element, the ```` should have a single child." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:453 -msgid "The template name is an arbitrary string, although when multiple templates are related (e.g. called sub-templates) it is customary to use dot-separated names to indicate hierarchical relationships." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:458 -msgid "Template inheritance" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:460 -msgid "Template inheritance is used to either:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:461 -msgid "Alter existing templates in-place, e.g. to add information to templates" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:463 -msgid "created by other modules." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:463 -msgid "Create a new template from a given parent template" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:469 -msgid "Template inheritance is performed via the use of two directives:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:466 -msgid "``t-inherit`` which is the name of the template to inherit from," -msgstr "" - -#: ../../content/developer/reference/qweb.rst:467 -msgid "``t-inherit-mode`` which is the behaviour of the inheritance: it can either be set to ``primary`` to create a new child template from the parented one or to ``extension`` to alter the parent template in place." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:471 -msgid "An optional ``t-name`` directive can also be specified. It will be the name of the newly created template if used in primary mode, else it will be added as a comment on the transformed template to help retrace inheritances." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:475 -msgid "For the inheritance itself, the changes are done using xpaths directives. See the XPATH_ documentation for the complete set of available instructions." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:478 -msgid "Primary inheritance (child template)::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:486 -msgid "Extension inheritance (in-place transformation)::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:495 -msgid "Old inheritance mechanism (deprecated)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:497 -msgid "Template inheritance is performed via the ``t-extend`` directive which takes the name of the template to alter as parameter." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:500 -msgid "The directive ``t-extend`` will act as a primary inheritance when combined with ``t-name`` and as an extension one when used alone." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:503 -msgid "In both cases the alteration is then performed with any number of ``t-jquery`` sub-directives::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:512 -msgid "The ``t-jquery`` directives takes a `CSS selector`_. This selector is used on the extended template to select *context nodes* to which the specified ``t-operation`` is applied:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:517 -msgid "``append``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:517 -msgid "the node's body is appended at the end of the context node (after the context node's last child)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:520 -msgid "``prepend``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:520 -msgid "the node's body is prepended to the context node (inserted before the context node's first child)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:523 -msgid "the node's body is inserted right before the context node" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:525 -msgid "the node's body is inserted right after the context node" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:526 -msgid "``inner``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:527 -msgid "the node's body replaces the context node's children" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:529 -msgid "the node's body is used to replace the context node itself" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:531 -msgid "the nodes's body should be any number of ``attribute`` elements, each with a ``name`` attribute and some textual content, the named attribute of the context node will be set to the specified value (either replaced if it already existed or added if not)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:541 -msgid "No operation" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:536 -msgid "if no ``t-operation`` is specified, the template body is interpreted as javascript code and executed with the context node as ``this``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:539 -msgid "while much more powerful than other operations, this mode is also much harder to debug and maintain, it is recommended to avoid it" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:544 -msgid "debugging" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:546 -msgid "The javascript QWeb implementation provides a few debugging hooks:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:554 -msgid "``t-log``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:549 -msgid "takes an expression parameter, evaluates the expression during rendering and logs its result with ``console.log``::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:555 -msgid "will print ``42`` to the console" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:557 -msgid "triggers a debugger breakpoint during template rendering::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:563 -msgid "will stop execution if debugging is active (exact condition depend on the browser and its development tools)" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:573 -msgid "``t-js``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:566 -msgid "the node's body is javascript code executed during template rendering. Takes a ``context`` parameter, which is the name under which the rendering context will be available in the ``t-js``'s body::" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:580 -msgid "(core is the ``web.core`` module) An instance of :js:class:`QWeb2.Engine` with all module-defined template files loaded, and references to standard helper objects ``_`` (underscore), ``_t`` (translation function) and JSON_." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:584 -msgid ":js:func:`core.qweb.render ` can be used to easily render basic module templates" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:594 -msgid "The QWeb \"renderer\", handles most of QWeb's logic (loading, parsing, compiling and rendering templates)." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:597 -msgid "Odoo Web instantiates one for the user in the core module, and exports it to ``core.qweb``. It also loads all the template files of the various modules into that QWeb instance." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:601 -msgid "A :js:class:`QWeb2.Engine` also serves as a \"template namespace\"." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:605 -msgid "Renders a previously loaded template to a String, using ``context`` (if provided) to find the variables accessed during template rendering (e.g. strings to display)." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:609 -msgid "the name of the template to render" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:610 -msgid "the basic namespace to use for template rendering" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:612 -msgid "String" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:614 -msgid "The engine exposes an other method which may be useful in some cases (e.g. if you need a separate template namespace with, in Odoo Web, Kanban views get their own :js:class:`QWeb2.Engine` instance so their templates don't collide with more general \"module\" templates):" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:622 -msgid "Loads a template file (a collection of templates) in the QWeb instance. The templates can be specified as:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:627 -msgid "An XML string" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:626 -msgid "QWeb will attempt to parse it to an XML document then load it." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:631 -msgid "A URL" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:630 -msgid "QWeb will attempt to download the URL content, then load the resulting XML string." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:636 -msgid "A ``Document`` or ``Node``" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:634 -msgid "QWeb will traverse the first level of the document (the child nodes of the provided root) and load any named template or template override." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:640 -msgid "A :js:class:`QWeb2.Engine` also exposes various attributes for behavior customization:" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:645 -msgid "Prefix used to recognize directives during parsing. A string. By default, ``t``." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:650 -msgid "Boolean flag putting the engine in \"debug mode\". Normally, QWeb intercepts any error raised during template execution. In debug mode, it leaves all exceptions go through without intercepting them." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:657 -msgid "The jQuery instance used during template inheritance processing. Defaults to ``window.jQuery``." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:662 -msgid "A ``Function``. If present, called before compiling each DOM node to template code. In Odoo Web, this is used to automatically translate text content and some attributes in templates. Defaults to ``null``." -msgstr "" - -#: ../../content/developer/reference/qweb.rst:667 -msgid "it is similar in that to Genshi_, although it does not use (and has no support for) `XML namespaces`_" -msgstr "" - -#: ../../content/developer/reference/qweb.rst:670 -msgid "although it uses a few others, either for historical reasons or because they remain better fits for the use case. Odoo 9.0 still depends on Jinja_ and Mako_." -msgstr "" - -#: ../../content/developer/reference/reports.rst:10 -msgid "QWeb Reports" -msgstr "" - -#: ../../content/developer/reference/reports.rst:12 -msgid "Reports are written in HTML/QWeb, like website views in Odoo. You can use the usual :ref:`QWeb control flow tools `. The PDF rendering itself is performed by wkhtmltopdf_." -msgstr "" - -#: ../../content/developer/reference/reports.rst:16 -msgid "Reports are declared using a :ref:`report action `, and a :ref:`reference/reports/templates` for the action to use." -msgstr "" - -#: ../../content/developer/reference/reports.rst:19 -msgid "If useful or necessary, it is possible to specify a :ref:`reference/reports/paper_formats` for the report report." -msgstr "" - -#: ../../content/developer/reference/reports.rst:25 -msgid "Report template" -msgstr "" - -#: ../../content/developer/reference/reports.rst:27 -msgid "Report templates will always provide the following variables:" -msgstr "" - -#: ../../content/developer/reference/reports.rst:29 -msgid "``time``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:30 -msgid "a reference to :mod:`python:time` from the Python standard library" -msgstr "" - -#: ../../content/developer/reference/reports.rst:32 -msgid "``res.user`` record for the user printing the report" -msgstr "" - -#: ../../content/developer/reference/reports.rst:33 -msgid "``res_company``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:34 -msgid "record for the current ``user``'s company" -msgstr "" - -#: ../../content/developer/reference/reports.rst:35 -msgid "``website``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:36 -msgid "the current website object, if any (this item can be present but ``None``)" -msgstr "" - -#: ../../content/developer/reference/reports.rst:37 -msgid "``web_base_url``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:38 -msgid "the base url for the webserver" -msgstr "" - -#: ../../content/developer/reference/reports.rst:41 -msgid "``context_timestamp``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:40 -msgid "a function taking :class:`python:datetime.datetime` in UTC\\ [#unzoned]_ and converting it to the timezone of the user printing the report" -msgstr "" - -#: ../../content/developer/reference/reports.rst:44 -msgid "Minimal viable template" -msgstr "" - -#: ../../content/developer/reference/reports.rst:46 -msgid "A minimal template would look like::" -msgstr "" - -#: ../../content/developer/reference/reports.rst:61 -msgid "Calling ``external_layout`` will add the default header and footer on your report. The PDF body will be the content inside the ``
``. The template's ``id`` must be the name specified in the report declaration; for example ``account.report_invoice`` for the above report. Since this is a QWeb template, you can access all the fields of the ``docs`` objects received by the template." -msgstr "" - -#: ../../content/developer/reference/reports.rst:68 -msgid "By default, the rendering context will also expose the following items:" -msgstr "" - -#: ../../content/developer/reference/reports.rst:71 -msgid "records for the current report" -msgstr "" - -#: ../../content/developer/reference/reports.rst:72 -msgid "``doc_ids``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:73 -msgid "list of ids for the ``docs`` records" -msgstr "" - -#: ../../content/developer/reference/reports.rst:75 -msgid "``doc_model``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:75 -msgid "model for the ``docs`` records" -msgstr "" - -#: ../../content/developer/reference/reports.rst:77 -msgid "If you wish to access other records/models in the template, you will need :ref:`a custom report `, however in that case you will have to provide the items above if you need them." -msgstr "" - -#: ../../content/developer/reference/reports.rst:82 -msgid "Translatable Templates" -msgstr "" - -#: ../../content/developer/reference/reports.rst:84 -msgid "If you wish to translate reports (to the language of a partner, for example), you need to define two templates:" -msgstr "" - -#: ../../content/developer/reference/reports.rst:87 -msgid "The main report template" -msgstr "" - -#: ../../content/developer/reference/reports.rst:88 -msgid "The translatable document" -msgstr "" - -#: ../../content/developer/reference/reports.rst:90 -msgid "You can then call the translatable document from your main template with the attribute ``t-lang`` set to a language code (for example ``fr`` or ``en_US``) or to a record field. You will also need to re-browse the related records with the proper context if you use fields that are translatable (like country names, sales conditions, etc.)" -msgstr "" - -#: ../../content/developer/reference/reports.rst:97 -msgid "If your report template does not use translatable record fields, re-browsing the record in another language is *not* necessary and will impact performances." -msgstr "" - -#: ../../content/developer/reference/reports.rst:100 -msgid "For example, let's look at the Sale Order report from the Sale module::" -msgstr "" - -#: ../../content/developer/reference/reports.rst:130 -msgid "The main template calls the translatable template with ``doc.partner_id.lang`` as a ``t-lang`` parameter, so it will be rendered in the language of the partner. This way, each Sale Order will be printed in the language of the corresponding customer. If you wish to translate only the body of the document, but keep the header and footer in a default language, you could call the report's external layout this way::" -msgstr "" - -#: ../../content/developer/reference/reports.rst:140 -msgid "Please take note that this works only when calling external templates, you will not be able to translate part of a document by setting a ``t-lang`` attribute on an xml node other than ``t-call``. If you wish to translate part of a template, you can create an external template with this partial template and call it from the main one with the ``t-lang`` attribute." -msgstr "" - -#: ../../content/developer/reference/reports.rst:148 -msgid "Barcodes" -msgstr "" - -#: ../../content/developer/reference/reports.rst:150 -msgid "Barcodes are images returned by a controller and can easily be embedded in reports thanks to the QWeb syntax (e.g. see :ref:`reference/qweb/attributes`):" -msgstr "" - -#: ../../content/developer/reference/reports.rst:157 -msgid "More parameters can be passed as a query string" -msgstr "" - -#: ../../content/developer/reference/reports.rst:166 -msgid "Useful Remarks" -msgstr "" - -#: ../../content/developer/reference/reports.rst:167 -msgid "Twitter Bootstrap and FontAwesome classes can be used in your report template" -msgstr "" - -#: ../../content/developer/reference/reports.rst:169 -msgid "Local CSS can be put directly in the template" -msgstr "" - -#: ../../content/developer/reference/reports.rst:170 -msgid "Global CSS can be inserted in the main report layout by inheriting its template and inserting your CSS::" -msgstr "" - -#: ../../content/developer/reference/reports.rst:183 -msgid "If it appears that your PDF report is missing the styles, please check :ref:`these instructions `." -msgstr "" - -#: ../../content/developer/reference/reports.rst:189 -msgid "Paper Format" -msgstr "" - -#: ../../content/developer/reference/reports.rst:191 -msgid "Paper formats are records of ``report.paperformat`` and can contain the following attributes:" -msgstr "" - -#: ../../content/developer/reference/reports.rst:195 -msgid "only useful as a mnemonic/description of the report when looking for one in a list of some sort" -msgstr "" - -#: ../../content/developer/reference/reports.rst:197 -#: ../../content/developer/webservices/iap.rst:441 -msgid "``description``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:198 -msgid "a small description of your format" -msgstr "" - -#: ../../content/developer/reference/reports.rst:201 -msgid "``format``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:200 -msgid "either a predefined format (A0 to A9, B0 to B10, Legal, Letter, Tabloid,...) or ``custom``; A4 by default. You cannot use a non-custom format if you define the page dimensions." -msgstr "" - -#: ../../content/developer/reference/reports.rst:203 -msgid "``dpi``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:204 -msgid "output DPI; 90 by default" -msgstr "" - -#: ../../content/developer/reference/reports.rst:205 -msgid "``margin_top``, ``margin_bottom``, ``margin_left``, ``margin_right``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:206 -msgid "margin sizes in mm" -msgstr "" - -#: ../../content/developer/reference/reports.rst:207 -msgid "``page_height``, ``page_width``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:208 -msgid "page dimensions in mm" -msgstr "" - -#: ../../content/developer/reference/reports.rst:209 -msgid "``orientation``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:210 -msgid "Landscape or Portrait" -msgstr "" - -#: ../../content/developer/reference/reports.rst:211 -msgid "``header_line``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:212 -msgid "boolean to display a header line" -msgstr "" - -#: ../../content/developer/reference/reports.rst:214 -msgid "``header_spacing``" -msgstr "" - -#: ../../content/developer/reference/reports.rst:214 -msgid "header spacing in mm" -msgstr "" - -#: ../../content/developer/reference/reports.rst:216 -#: ../../content/developer/reference/reports.rst:283 -#: ../../content/developer/reference/reports.rst:293 -msgid "Example::" -msgstr "" - -#: ../../content/developer/reference/reports.rst:237 -msgid "Custom Reports" -msgstr "" - -#: ../../content/developer/reference/reports.rst:239 -msgid "By default, the reporting system builds rendering values based on the target model specified through the ``model`` field." -msgstr "" - -#: ../../content/developer/reference/reports.rst:242 -msgid "However, it will first look for a model named :samp:`report.{module.report_name}` and call that model's ``_get_report_values(doc_ids, data)`` in order to prepare the rendering data for the template." -msgstr "" - -#: ../../content/developer/reference/reports.rst:247 -msgid "This can be used to include arbitrary items to use or display while rendering the template, such as data from additional models:" -msgstr "" - -#: ../../content/developer/reference/reports.rst:269 -msgid "When using a custom report, the \"default\" document-related items (``doc_ids``, ``doc_model`` and ``docs``) will *not* be included. If you want them, you will need to include them yourself." -msgstr "" - -#: ../../content/developer/reference/reports.rst:273 -msgid "In the example above, the rendering context will contain the \"global\" values as well as the ``lines`` we put in there but nothing else." -msgstr "" - -#: ../../content/developer/reference/reports.rst:279 -msgid "Custom fonts" -msgstr "" - -#: ../../content/developer/reference/reports.rst:280 -msgid "If you want to use custom fonts you will need to add your custom font and the related less/CSS to the ``web.reports_assets_common`` assets bundle. Adding your custom font(s) to ``web.assets_common`` or ``web.assets_backend`` will not make your font available in QWeb reports." -msgstr "" - -#: ../../content/developer/reference/reports.rst:291 -msgid "You will need to define your ``@font-face`` within this less file, even if you've used in another assets bundle (other than ``web.reports_assets_common``)." -msgstr "" - -#: ../../content/developer/reference/reports.rst:306 -msgid "After you've added the less into your assets bundle you can use the classes - in this example ``h1-title-big`` - in your custom QWeb report." -msgstr "" - -#: ../../content/developer/reference/reports.rst:309 -msgid "Reports are web pages" -msgstr "" - -#: ../../content/developer/reference/reports.rst:311 -msgid "Reports are dynamically generated by the report module and can be accessed directly via URL:" -msgstr "" - -#: ../../content/developer/reference/reports.rst:314 -msgid "For example, you can access a Sale Order report in html mode by going to \\http:///report/html/sale.report_saleorder/38" -msgstr "" - -#: ../../content/developer/reference/reports.rst:317 -msgid "Or you can access the pdf version at \\http:///report/pdf/sale.report_saleorder/38" -msgstr "" - -#: ../../content/developer/reference/reports.rst:320 -msgid "it does not matter what timezone the :class:`python:datetime` object is actually in (including no timezone), its timezone will unconditionally be *set* to UTC before being adjusted to the user's" -msgstr "" - -#: ../../content/developer/reference/security.rst:6 -msgid "Security in Odoo" -msgstr "" - -#: ../../content/developer/reference/security.rst:8 -msgid "Aside from manually managing access using custom code, Odoo provides two main data-driven mechanisms to manage or restrict access to data." -msgstr "" - -#: ../../content/developer/reference/security.rst:11 -msgid "Both mechanisms are linked to specific users through *groups*: a user belongs to any number of groups, and security mechanisms are associated to groups, thus applying security mechamisms to users." -msgstr "" - -#: ../../content/developer/reference/security.rst:18 -msgid "Access Control" -msgstr "" - -#: ../../content/developer/reference/security.rst:20 -msgid "Managed by the ``ir.model.access`` records, defines access to a whole model." -msgstr "" - -#: ../../content/developer/reference/security.rst:22 -msgid "Each access control has a model to which it grants permissions, the permissions it grants and optionally a group." -msgstr "" - -#: ../../content/developer/reference/security.rst:25 -msgid "Access controls are additive, for a given model a user has access all permissions granted to any of its groups: if the user belongs to one group which allows writing and another which allows deleting, they can both write and delete." -msgstr "" - -#: ../../content/developer/reference/security.rst:30 -msgid "If no group is specified, the access control applies to all users, otherwise it only applies to the members of the given group." -msgstr "" - -#: ../../content/developer/reference/security.rst:33 -msgid "Available permissions are creation (``perm_create``), searching and reading (``perm_read``), updating existing records (``perm_write``) and deleting existing records (``perm_unlink``)" -msgstr "" - -#: ../../content/developer/reference/security.rst:40 -msgid "Record Rules" -msgstr "" - -#: ../../content/developer/reference/security.rst:42 -msgid "Record rules are conditions that records must satisfy for an operation (create, read, update or delete) to be allowed. It is applied record-by-record after access control has been applied." -msgstr "" - -#: ../../content/developer/reference/security.rst:46 -msgid "A record rule has:" -msgstr "" - -#: ../../content/developer/reference/security.rst:48 -msgid "a model on which it applies" -msgstr "" - -#: ../../content/developer/reference/security.rst:49 -msgid "a set of permissions to which it applies (e.g. if ``perm_read`` is set, the rule will only be checked when reading a record)" -msgstr "" - -#: ../../content/developer/reference/security.rst:51 -msgid "a set of user groups to which the rule applies, if no group is specified the rule is *global*" -msgstr "" - -#: ../../content/developer/reference/security.rst:53 -msgid "a :ref:`domain ` used to check whether a given record matches the rule (and is accessible) or does not (and is not accessible). The domain is evaluated with two variables in context: ``user`` is the current user's record and ``time`` is the `time module`_" -msgstr "" - -#: ../../content/developer/reference/security.rst:58 -msgid "Global rules and group rules (rules restricted to specific groups versus groups applying to all users) are used quite differently:" -msgstr "" - -#: ../../content/developer/reference/security.rst:61 -msgid "Global rules are subtractive, they *must all* be matched for a record to be accessible" -msgstr "" - -#: ../../content/developer/reference/security.rst:63 -msgid "Group rules are additive, if *any* of them matches (and all global rules match) then the record is accessible" -msgstr "" - -#: ../../content/developer/reference/security.rst:66 -msgid "This means the first *group rule* restricts access, but any further *group rule* expands it, while *global rules* can only ever restrict access (or have no effect)." -msgstr "" - -#: ../../content/developer/reference/security.rst:70 -msgid "record rules do not apply to the Superuser account" -msgstr "" - -#: ../../content/developer/reference/security.rst:76 -msgid "Field Access" -msgstr "" - -#: ../../content/developer/reference/security.rst:78 -msgid "An ORM :class:`~odoo.fields.Field` can have a ``groups`` attribute providing a list of groups (as a comma-separated string of :term:`external identifiers`)." -msgstr "" - -#: ../../content/developer/reference/security.rst:82 -msgid "If the current user is not in one of the listed groups, he will not have access to the field:" -msgstr "" - -#: ../../content/developer/reference/security.rst:85 -msgid "restricted fields are automatically removed from requested views" -msgstr "" - -#: ../../content/developer/reference/security.rst:86 -msgid "restricted fields are removed from :meth:`~odoo.models.Model.fields_get` responses" -msgstr "" - -#: ../../content/developer/reference/security.rst:88 -msgid "attempts to (explicitly) read from or write to restricted fields results in an access error" -msgstr "" - -#: ../../content/developer/reference/security.rst:93 -msgid "field access groups apply to the Superuser in fields_get but not in read/write..." -msgstr "" - -#: ../../content/developer/reference/security.rst:102 -msgid "Security Pitfalls" -msgstr "" - -#: ../../content/developer/reference/security.rst:104 -msgid "As a developer, it is important to understand the security mechanisms and avoid common mistakes leading to insecure code." -msgstr "" - -#: ../../content/developer/reference/security.rst:108 -msgid "Unsafe Public Methods" -msgstr "" - -#: ../../content/developer/reference/security.rst:110 -msgid "Any public method can be executed via a :ref:`RPC call ` with the chosen parameters. The methods starting with a ``_`` are not callable from an action button or external API." -msgstr "" - -#: ../../content/developer/reference/security.rst:114 -msgid "On public methods, the record on which a method is executed and the parameters can not be trusted, ACL being only verified during CRUD operations." -msgstr "" - -#: ../../content/developer/reference/security.rst:128 -msgid "Making a method private is obviously not enough and care must be taken to use it properly." -msgstr "" - -#: ../../content/developer/reference/security.rst:132 -msgid "Bypassing the ORM" -msgstr "" - -#: ../../content/developer/reference/security.rst:133 -msgid "You should never use the database cursor directly when the ORM can do the same thing! By doing so you are bypassing all the ORM features, possibly the automated behaviours like translations, invalidation of fields, ``active``, access rights and so on." -msgstr "" - -#: ../../content/developer/reference/security.rst:138 -msgid "And chances are that you are also making the code harder to read and probably less secure." -msgstr "" - -#: ../../content/developer/reference/security.rst:157 -msgid "SQL injections" -msgstr "" - -#: ../../content/developer/reference/security.rst:158 -msgid "Care must be taken not to introduce SQL injections vulnerabilities when using manual SQL queries. The vulnerability is present when user input is either incorrectly filtered or badly quoted, allowing an attacker to introduce undesirable clauses to a SQL query (such as circumventing filters or executing ``UPDATE`` or ``DELETE`` commands)." -msgstr "" - -#: ../../content/developer/reference/security.rst:164 -msgid "The best way to be safe is to never, NEVER use Python string concatenation (+) or string parameters interpolation (%) to pass variables to a SQL query string." -msgstr "" - -#: ../../content/developer/reference/security.rst:167 -msgid "The second reason, which is almost as important, is that it is the job of the database abstraction layer (psycopg2) to decide how to format query parameters, not your job! For example psycopg2 knows that when you pass a list of values it needs to format them as a comma-separated list, enclosed in parentheses !" -msgstr "" - -#: ../../content/developer/reference/security.rst:187 -msgid "This is very important, so please be careful also when refactoring, and most importantly do not copy these patterns!" -msgstr "" - -#: ../../content/developer/reference/security.rst:190 -msgid "Here is a memorable example to help you remember what the issue is about (but do not copy the code there). Before continuing, please be sure to read the online documentation of pyscopg2 to learn of to use it properly:" -msgstr "" - -#: ../../content/developer/reference/security.rst:194 -msgid "`The problem with query parameters `_" -msgstr "" - -#: ../../content/developer/reference/security.rst:195 -msgid "`How to pass parameters with psycopg2 `_" -msgstr "" - -#: ../../content/developer/reference/security.rst:196 -msgid "`Advanced parameter types `_" -msgstr "" - -#: ../../content/developer/reference/security.rst:197 -msgid "`Psycopg documentation `_" -msgstr "" - -#: ../../content/developer/reference/security.rst:200 -msgid "Unescaped field content" -msgstr "" - -#: ../../content/developer/reference/security.rst:202 -msgid "When rendering content using JavaScript and XML, one may be tempted to use a ``t-raw`` to display rich-text content. This should be avoided as a frequent `XSS `_ vector." -msgstr "" - -#: ../../content/developer/reference/security.rst:206 -msgid "It is very hard to control the integrity of the data from the computation until the final integration in the browser DOM. A ``t-raw`` that is correctly escaped at the time of introduction may no longer be safe at the next bugfix or refactoring." -msgstr "" - -#: ../../content/developer/reference/security.rst:223 -msgid "The above code may feel safe as the message content is controlled but is a bad practice that may lead to unexpected security vulnerabilities once this code evolves in the future." -msgstr "" - -#: ../../content/developer/reference/security.rst:235 -msgid "While formatting the template differently would prevent such vulnerabilities." -msgstr "" - -#: ../../content/developer/reference/security.rst:260 -msgid "Escaping vs Sanitizing" -msgstr "" - -#: ../../content/developer/reference/security.rst:264 -msgid "Escaping is always 100% mandatory when you mix data and code, no matter how safe the data" -msgstr "" - -#: ../../content/developer/reference/security.rst:267 -msgid "**Escaping** converts *TEXT* to *CODE*. It is absolutely mandatory to do it every time you mix *DATA/TEXT* with *CODE* (e.g. generating HTML or python code to be evaluated inside a `safe_eval`), because *CODE* always requires *TEXT* to be encoded. It is critical for security, but it's also a question of correctness. Even when there is no security risk (because the text is 100% guarantee to be safe or trusted), it is still required (e.g. to avoid breaking the layout in generated HTML)." -msgstr "" - -#: ../../content/developer/reference/security.rst:275 -msgid "Escaping will never break any feature, as long as the developer identifies which variable contains *TEXT* and which contains *CODE*." -msgstr "" - -#: ../../content/developer/reference/security.rst:291 -msgid "**Sanitizing** converts *CODE* to *SAFER CODE* (but not necessary *safe* code). It does not work on *TEXT*. Sanitizing is only necessary when *CODE* is untrusted, because it comes in full or in part from some user-provided data. If the user-provided data is in the form of *TEXT* (e.g. the content from a form filled by a user), and if that data was correctly escaped before putting it in *CODE*, then sanitizing is useless (but can still be done). If however, the user-provided data was **not escaped**, then sanitizing will **not** work as expected." -msgstr "" - -#: ../../content/developer/reference/security.rst:310 -msgid "Sanitizing can break features, depending on whether the *CODE* is expected to contain patterns that are not safe. That's why `fields.Html` and `tools.html_sanitize()` have options to fine-tune the level of sanitization for styles, etc. Those options have to be carefully considered depending on where the data comes from, and the desired features. The sanitization safety is balanced against sanitization breakages: the safer the sanitisation the more likely it is to break things." -msgstr "" - -#: ../../content/developer/reference/security.rst:327 -msgid "Evaluating content" -msgstr "" - -#: ../../content/developer/reference/security.rst:328 -msgid "Some may want to ``eval`` to parse user provided content. Using ``eval`` should be avoided at all cost. A safer, sandboxed, method :class:`~odoo.tools.safe_eval` can be used instead but still gives tremendous capabilities to the user running it and must be reserved for trusted privileged users only as it breaks the barrier between code and data." -msgstr "" - -#: ../../content/developer/reference/security.rst:350 -msgid "Parsing content does not need ``eval``" -msgstr "" - -#: ../../content/developer/reference/security.rst:353 -msgid "Language" -msgstr "" - -#: ../../content/developer/reference/security.rst:353 -msgid "Data type" -msgstr "" - -#: ../../content/developer/reference/security.rst:353 -msgid "Suitable parser" -msgstr "" - -#: ../../content/developer/reference/security.rst:355 -#: ../../content/developer/reference/security.rst:356 -msgid "int, float, etc." -msgstr "" - -#: ../../content/developer/reference/security.rst:355 -msgid "int(), float()" -msgstr "" - -#: ../../content/developer/reference/security.rst:356 -msgid "parseInt(), parseFloat()" -msgstr "" - -#: ../../content/developer/reference/security.rst:357 -msgid "dict" -msgstr "" - -#: ../../content/developer/reference/security.rst:357 -msgid "json.loads(), ast.literal_eval()" -msgstr "" - -#: ../../content/developer/reference/security.rst:358 -msgid "object, list, etc." -msgstr "" - -#: ../../content/developer/reference/security.rst:358 -msgid "JSON.parse()" -msgstr "" - -#: ../../content/developer/reference/security.rst:362 -msgid "Accessing object attributes" -msgstr "" - -#: ../../content/developer/reference/security.rst:364 -msgid "If the values of a record needs to be retrieved or modified dynamically, one may want to use the ``getattr`` and ``setattr`` methods." -msgstr "" - -#: ../../content/developer/reference/security.rst:374 -msgid "This code is however not safe as it allows to access any property of the record, including private attributes or methods." -msgstr "" - -#: ../../content/developer/reference/security.rst:377 -msgid "The ``__getitem__`` of a recordset has been defined and accessing a dynamic field value can be easily achieved safely:" -msgstr "" - -#: ../../content/developer/reference/security.rst:387 -msgid "The above method is obviously still too optimistic and additional verifications on the record id and field value must be done." -msgstr "" - -#: ../../content/developer/reference/testing.rst:7 -msgid "Testing Odoo" -msgstr "" - -#: ../../content/developer/reference/testing.rst:9 -msgid "There are many ways to test an application. In Odoo, we have three kinds of tests" -msgstr "" - -#: ../../content/developer/reference/testing.rst:12 -msgid "Python unit tests (see `Testing Python code`_): useful for testing model business logic" -msgstr "" - -#: ../../content/developer/reference/testing.rst:13 -msgid "JS unit tests (see `Testing JS code`_): useful to test the javascript code in isolation" -msgstr "" - -#: ../../content/developer/reference/testing.rst:14 -msgid "Tours (see `Integration Testing`_): tours simulate a real situation. They ensures that the python and the javascript parts properly talk to each other." -msgstr "" - -#: ../../content/developer/reference/testing.rst:18 -msgid "Testing Python code" -msgstr "" - -#: ../../content/developer/reference/testing.rst:20 -msgid "Odoo provides support for testing modules using unittest." -msgstr "" - -#: ../../content/developer/reference/testing.rst:22 -msgid "To write tests, simply define a ``tests`` sub-package in your module, it will be automatically inspected for test modules. Test modules should have a name starting with ``test_`` and should be imported from ``tests/__init__.py``, e.g." -msgstr "" - -#: ../../content/developer/reference/testing.rst:36 -msgid "and ``__init__.py`` contains::" -msgstr "" - -#: ../../content/developer/reference/testing.rst:42 -msgid "test modules which are not imported from ``tests/__init__.py`` will not be run" -msgstr "" - -#: ../../content/developer/reference/testing.rst:45 -msgid "The test runner will simply run any test case, as described in the official `unittest documentation`_, but Odoo provides a number of utilities and helpers related to testing Odoo content (modules, mainly):" -msgstr "" - -#: ../../content/developer/reference/testing.rst:62 -msgid "By default, tests are run once right after the corresponding module has been installed. Test cases can also be configured to run after all modules have been installed, and not run right after the module installation::" -msgstr "" - -#: ../../content/developer/reference/testing.rst:75 -msgid "The most common situation is to use :class:`~odoo.tests.common.TransactionCase` and test a property of a model in each method::" -msgstr "" - -#: ../../content/developer/reference/testing.rst:91 -msgid "Test methods must start with ``test_``" -msgstr "" - -#: ../../content/developer/reference/testing.rst:103 -msgid "Running tests" -msgstr "" - -#: ../../content/developer/reference/testing.rst:105 -msgid "Tests are automatically run when installing or updating modules if :option:`--test-enable ` was enabled when starting the Odoo server." -msgstr "" - -#: ../../content/developer/reference/testing.rst:114 -msgid "Test selection" -msgstr "" - -#: ../../content/developer/reference/testing.rst:116 -msgid "In Odoo, Python tests can be tagged to facilitate the test selection when running tests." -msgstr "" - -#: ../../content/developer/reference/testing.rst:119 -msgid "Subclasses of :class:`odoo.tests.common.BaseCase` (usually through :class:`~odoo.tests.common.TransactionCase`, :class:`~odoo.tests.common.SavepointCase` or :class:`~odoo.tests.common.HttpCase`) are automatically tagged with ``standard``, ``at_install`` and their source module's name by default." -msgstr "" - -#: ../../content/developer/reference/testing.rst:126 -msgid "Invocation" -msgstr "" - -#: ../../content/developer/reference/testing.rst:128 -msgid ":option:`--test-tags ` can be used to select/filter tests to run on the command-line." -msgstr "" - -#: ../../content/developer/reference/testing.rst:131 -msgid "This option defaults to ``+standard`` meaning tests tagged ``standard`` (explicitly or implicitly) will be run by default when starting Odoo with :option:`--test-enable `." -msgstr "" - -#: ../../content/developer/reference/testing.rst:135 -msgid "When writing tests, the :func:`~odoo.tests.common.tagged` decorator can be used on **test classes** to add or remove tags." -msgstr "" - -#: ../../content/developer/reference/testing.rst:138 -msgid "The decorator's arguments are tag names, as strings." -msgstr "" - -#: ../../content/developer/reference/testing.rst:140 -msgid ":func:`~odoo.tests.common.tagged` is a class decorator, it has no effect on functions or methods" -msgstr "" - -#: ../../content/developer/reference/testing.rst:143 -msgid "Tags can be prefixed with the minus (``-``) sign, to *remove* them instead of add or select them e.g. if you don't want your test to be executed by default you can remove the ``standard`` tag:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:155 -msgid "This test will not be selected by default, to run it the relevant tag will have to be selected explicitely:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:162 -msgid "Note that only the tests tagged ``nice`` are going to be executed. To run *both* ``nice`` and ``standard`` tests, provide multiple values to :option:`--test-tags `: on the command-line, values are *additive* (you're selecting all tests with *any* of the specified tags)" -msgstr "" - -#: ../../content/developer/reference/testing.rst:171 -msgid "The config switch parameter also accepts the ``+`` and ``-`` prefixes. The ``+`` prefix is implied and therefore, totaly optional. The ``-`` (minus) prefix is made to deselect tests tagged with the prefixed tags, even if they are selected by other specified tags e.g. if there are ``standard`` tests which are also tagged as ``slow`` you can run all standard tests *except* the slow ones:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:182 -msgid "When you write a test that does not inherit from the :class:`~odoo.tests.common.BaseCase`, this test will not have the default tags, you have to add them explicitely to have the test included in the default test suite. This is a common issue when using a simple ``unittest.TestCase`` as they're not going to get run:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:198 -msgid "Special tags" -msgstr "" - -#: ../../content/developer/reference/testing.rst:200 -msgid "``standard``: All Odoo tests that inherit from :class:`~odoo.tests.common.BaseCase` are implicitely tagged standard. :option:`--test-tags ` also defaults to ``standard``." -msgstr "" - -#: ../../content/developer/reference/testing.rst:204 -msgid "That means untagged test will be executed by default when tests are enabled." -msgstr "" - -#: ../../content/developer/reference/testing.rst:205 -msgid "``at_install``: Means that the test will be executed right after the module installation and before other modules are installed. This is a default implicit tag." -msgstr "" - -#: ../../content/developer/reference/testing.rst:208 -msgid "``post_install``: Means that the test will be executed after all the modules are installed. This is what you want for HttpCase tests most of the time." -msgstr "" - -#: ../../content/developer/reference/testing.rst:211 -msgid "Note that this is *not exclusive* with ``at_install``, however since you will generally not want both ``post_install`` is usually paired with ``-at_install`` when tagging a test class." -msgstr "" - -#: ../../content/developer/reference/testing.rst:214 -msgid "*module_name*: Odoo tests classes extending :class:`~odoo.tests.common.BaseCase` are implicitely tagged with the technical name of their module. This allows easily selecting or excluding specific modules when testing e.g. if you want to only run tests from ``stock_account``:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:225 -msgid "Examples" -msgstr "" - -#: ../../content/developer/reference/testing.rst:229 -msgid "Tests will be executed only in the installed or updated modules. So modules have to be selected with the :option:`-u ` or :option:`-i ` switches. For simplicity, those switches are not specified in the examples below." -msgstr "" - -#: ../../content/developer/reference/testing.rst:234 -msgid "Run only the tests from the sale module:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:240 -msgid "Run the tests from the sale module but not the ones tagged as slow:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:246 -msgid "Run only the tests from stock or tagged as slow:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:252 -msgid "``-standard`` is implicit (not required), and present for clarity" -msgstr "" - -#: ../../content/developer/reference/testing.rst:255 -msgid "Testing JS code" -msgstr "" - -#: ../../content/developer/reference/testing.rst:257 -msgid "Testing a complex system is an important safeguard to prevent regressions and to guarantee that some basic functionality still works. Since Odoo has a non trivial codebase in Javascript, it is necessary to test it. In this section, we will discuss the practice of testing JS code in isolation: these tests stay in the browser, and are not supposed to reach the server." -msgstr "" - -#: ../../content/developer/reference/testing.rst:264 -msgid "Qunit test suite" -msgstr "" - -#: ../../content/developer/reference/testing.rst:266 -msgid "The Odoo framework uses the QUnit_ library testing framework as a test runner. QUnit defines the concepts of *tests* and *modules* (a set of related tests), and gives us a web based interface to execute the tests." -msgstr "" - -#: ../../content/developer/reference/testing.rst:270 -msgid "For example, here is what a pyUtils test could look like:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:285 -msgid "The main way to run the test suite is to have a running Odoo server, then navigate a web browser to ``/web/tests``. The test suite will then be executed by the web browser Javascript engine." -msgstr "" - -#: ../../content/developer/reference/testing.rst:292 -msgid "The web UI has many useful features: it can run only some submodules, or filter tests that match a string. It can show every assertions, failed or passed, rerun specific tests, ..." -msgstr "" - -#: ../../content/developer/reference/testing.rst:298 -msgid "While the test suite is running, make sure that:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:300 -msgid "your browser window is focused," -msgstr "" - -#: ../../content/developer/reference/testing.rst:301 -msgid "it is not zoomed in/out. It needs to have exactly 100% zoom level." -msgstr "" - -#: ../../content/developer/reference/testing.rst:303 -msgid "If this is not the case, some tests will fail, without a proper explanation." -msgstr "" - -#: ../../content/developer/reference/testing.rst:306 -msgid "Testing Infrastructure" -msgstr "" - -#: ../../content/developer/reference/testing.rst:308 -msgid "Here is a high level overview of the most important parts of the testing infrastructure:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:311 -msgid "there is an asset bundle named `web.qunit_suite`_. This bundle contains the main code (assets common + assets backend), some libraries, the QUnit test runner and the test bundles listed below." -msgstr "" - -#: ../../content/developer/reference/testing.rst:315 -msgid "a bundle named `web.tests_assets`_ includes most of the assets and utils required by the test suite: custom QUnit asserts, test helpers, lazy loaded assets, etc." -msgstr "" - -#: ../../content/developer/reference/testing.rst:318 -msgid "another asset bundle, `web.qunit_suite_tests`_, contains all the test scripts. This is typically where the test files are added to the suite." -msgstr "" - -#: ../../content/developer/reference/testing.rst:321 -msgid "there is a `controller`_ in web, mapped to the route */web/tests*. This controller simply renders the *web.qunit_suite* template." -msgstr "" - -#: ../../content/developer/reference/testing.rst:324 -msgid "to execute the tests, one can simply point its browser to the route */web/tests*. In that case, the browser will download all assets, and QUnit will take over." -msgstr "" - -#: ../../content/developer/reference/testing.rst:327 -msgid "there is some code in `qunit_config.js`_ which logs in the console some information when a test passes or fails." -msgstr "" - -#: ../../content/developer/reference/testing.rst:330 -msgid "we want the runbot to also run these tests, so there is a test (in `test_js.py`_) which simply spawns a browser and points it to the *web/tests* url. Note that the browser_js method spawns a Chrome headless instance." -msgstr "" - -#: ../../content/developer/reference/testing.rst:336 -msgid "Modularity and testing" -msgstr "" - -#: ../../content/developer/reference/testing.rst:338 -msgid "With the way Odoo is designed, any addon can modify the behaviour of other parts of the system. For example, the *voip* addon can modify the *FieldPhone* widget to use extra features. This is not really good from the perspective of the testing system, since this means that a test in the addon web will fail whenever the voip addon is installed (note that the runbot runs the tests with all addons installed)." -msgstr "" - -#: ../../content/developer/reference/testing.rst:345 -msgid "At the same time, our testing sytem is good, because it can detect whenever another module breaks some core functionality. There is no complete solution to this issue. For now, we solve this on a case by case basis." -msgstr "" - -#: ../../content/developer/reference/testing.rst:349 -msgid "Usually, it is not a good idea to modify some other behaviour. For our voip example, it is certainly cleaner to add a new *FieldVOIPPhone* widget and modify the few views that needs it. This way, the *FieldPhone* widget is not impacted, and both can be tested." -msgstr "" - -#: ../../content/developer/reference/testing.rst:355 -msgid "Adding a new test case" -msgstr "" - -#: ../../content/developer/reference/testing.rst:357 -msgid "Let us assume that we are maintaining an addon *my_addon*, and that we want to add a test for some javascript code (for example, some utility function myFunction, located in *my_addon.utils*). The process to add a new test case is the following:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:362 -msgid "create a new file *my_addon/static/tests/utils_tests.js*. This file contains the basic code to add a QUnit module *my_addon > utils*." -msgstr "" - -#: ../../content/developer/reference/testing.rst:380 -msgid "In *my_addon/assets.xml*, add the file to the main test assets:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:393 -msgid "Restart the server and update *my_addon*, or do it from the interface (to make sure the new test file is loaded)" -msgstr "" - -#: ../../content/developer/reference/testing.rst:396 -msgid "Add a test case after the definition of the *utils* sub test suite:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:407 -msgid "Visit */web/tests/* to make sure the test is executed" -msgstr "" - -#: ../../content/developer/reference/testing.rst:410 -msgid "Helper functions and specialized assertions" -msgstr "" - -#: ../../content/developer/reference/testing.rst:412 -msgid "Without help, it is quite difficult to test some parts of Odoo. In particular, views are tricky, because they communicate with the server and may perform many rpcs, which needs to be mocked. This is why we developed some specialized helper functions, located in `test_utils.js`_." -msgstr "" - -#: ../../content/developer/reference/testing.rst:417 -msgid "Mock test functions: these functions help setting up a test environment. The most important use case is mocking the answers given by the Odoo server. These functions use a `mock server`_. This is a javascript class that simulates answers to the most common model methods: read, search_read, nameget, ..." -msgstr "" - -#: ../../content/developer/reference/testing.rst:422 -msgid "DOM helpers: useful to simulate events/actions on some specific target. For example, testUtils.dom.click performs a click on a target. Note that it is safer than doing it manually, because it also checks that the target exists, and is visible." -msgstr "" - -#: ../../content/developer/reference/testing.rst:427 -msgid "create helpers: they are probably the most important functions exported by `test_utils.js`_. These helpers are useful to create a widget, with a mock environment, and a lot of small detail to simulate as much as possible the real conditions. The most important is certainly `createView`_." -msgstr "" - -#: ../../content/developer/reference/testing.rst:432 -msgid "`qunit assertions`_: QUnit can be extended with specialized assertions. For Odoo, we frequently test some DOM properties. This is why we made some assertions to help with that. For example, the *containsOnce* assertion takes a widget/jQuery/HtmlElement and a selector, then checks if the target contains exactly one match for the css selector." -msgstr "" - -#: ../../content/developer/reference/testing.rst:438 -msgid "For example, with these helpers, here is what a simple form test could look like:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:462 -msgid "Notice the use of the testUtils.createView helper and of the containsOnce assertion. Also, the form controller was properly destroyed at the end of the test." -msgstr "" - -#: ../../content/developer/reference/testing.rst:467 -msgid "Best Practices" -msgstr "" - -#: ../../content/developer/reference/testing.rst:469 -msgid "In no particular order:" -msgstr "" - -#: ../../content/developer/reference/testing.rst:471 -msgid "all test files should be added in *some_addon/static/tests/*" -msgstr "" - -#: ../../content/developer/reference/testing.rst:472 -msgid "for bug fixes, make sure that the test fails without the bug fix, and passes with it. This ensures that it actually works." -msgstr "" - -#: ../../content/developer/reference/testing.rst:474 -msgid "try to have the minimal amount of code necessary for the test to work." -msgstr "" - -#: ../../content/developer/reference/testing.rst:475 -msgid "usually, two small tests are better than one large test. A smaller test is easier to understand and to fix." -msgstr "" - -#: ../../content/developer/reference/testing.rst:477 -msgid "always cleanup after a test. For example, if your test instantiates a widget, it should destroy it at the end." -msgstr "" - -#: ../../content/developer/reference/testing.rst:479 -msgid "no need to have full and complete code coverage. But adding a few tests helps a lot: it makes sure that your code is not completely broken, and whenever a bug is fixed, it is really much easier to add a test to an existing test suite." -msgstr "" - -#: ../../content/developer/reference/testing.rst:482 -msgid "if you want to check some negative assertion (for example, that a HtmlElement does not have a specific css class), then try to add the positive assertion in the same test (for example, by doing an action that changes the state). This will help avoid the test to become dead in the future (for example, if the css class is changed)." -msgstr "" - -#: ../../content/developer/reference/testing.rst:489 -msgid "Tips" -msgstr "" - -#: ../../content/developer/reference/testing.rst:491 -msgid "running only one test: you can (temporarily!) change the *QUnit.test(...)* definition into *QUnit.only(...)*. This is useful to make sure that QUnit only runs this specific test." -msgstr "" - -#: ../../content/developer/reference/testing.rst:494 -msgid "debug flag: most create utility functions have a debug mode (activated by the debug: true parameter). In that case, the target widget will be put in the DOM instead of the hidden qunit specific fixture, and more information will be logged. For example, all mocked network communications will be available in the console." -msgstr "" - -#: ../../content/developer/reference/testing.rst:499 -msgid "when working on a failing test, it is common to add the debug flag, then comment the end of the test (in particular, the destroy call). With this, it is possible to see the state of the widget directly, and even better, to manipulate the widget by clicking/interacting with it." -msgstr "" - -#: ../../content/developer/reference/testing.rst:506 -#: ../../content/developer/webservices/extract_api.rst:538 -msgid "Integration Testing" -msgstr "" - -#: ../../content/developer/reference/testing.rst:508 -msgid "Testing Python code and JS code separately is very useful, but it does not prove that the web client and the server work together. In order to do that, we can write another kind of test: tours. A tour is a mini scenario of some interesting business flow. It explains a sequence of steps that should be followed. The test runner will then create a Chrome headless browser, point it to the proper url and simulate the click and inputs, according to the scenario." -msgstr "" - -#: ../../content/developer/reference/testing.rst:516 -msgid "Screenshots and screencasts during browser_js tests" -msgstr "" - -#: ../../content/developer/reference/testing.rst:518 -msgid "When running tests that use HttpCase.browser_js from the command line, the Chrome browser is used in headless mode. By default, if a test fails, a PNG screenshot is taken at the moment of the failure and written in" -msgstr "" - -#: ../../content/developer/reference/testing.rst:526 -msgid "Two new command line arguments were added since Odoo 13.0 to control this behavior: :option:`--screenshots ` and :option:`--screencasts `" -msgstr "" - -#: ../../content/developer/reference/testing.rst:531 -msgid "Performance Testing" -msgstr "" - -#: ../../content/developer/reference/testing.rst:534 -msgid "Query counts" -msgstr "" - -#: ../../content/developer/reference/testing.rst:536 -msgid "One of the ways to test performance is to measure database queries. Manually, this can be tested with the `--log-sql` CLI parameter. If you want to establish the maximum number of queries for an operation, you can use the :meth:`~odoo.tests.common.BaseCase.assertQueryCount` method, integrated in Odoo test classes." -msgstr "" - -#: ../../content/developer/reference/testing.rst:548 -msgid "Database population" -msgstr "" - -#: ../../content/developer/reference/testing.rst:550 -msgid "Odoo CLI offers a :ref:`database population` feature." -msgstr "" - -#: ../../content/developer/reference/testing.rst:556 -msgid "Instead of the tedious manual, or programmatic, specification of test data, one can use this feature to fill a database on demand with the desired number of test data. This can be used to detect diverse bugs or performance issues in tested flows." -msgstr "" - -#: ../../content/developer/reference/testing.rst:562 -msgid "To specify this feature for a given model, the following methods and attributes can be defined." -msgstr "" - -#: ../../content/developer/reference/testing.rst:573 -msgid "You have to define at least :meth:`~odoo.models.Model._populate` or :meth:`~odoo.models.Model._populate_factories` on the model to enable database population." -msgstr "" - -#: ../../content/developer/reference/testing.rst:577 -msgid "Example model" -msgstr "" - -#: ../../content/developer/reference/testing.rst:621 -msgid "Population tools" -msgstr "" - -#: ../../content/developer/reference/testing.rst:623 -msgid "Multiple population tools are available to easily create the needed data generators." -msgstr "" - -#: ../../content/developer/reference/translations.rst:7 -msgid "Translating Modules" -msgstr "" - -#: ../../content/developer/reference/translations.rst:9 -msgid "This section explains how to provide translation abilities to your module." -msgstr "" - -#: ../../content/developer/reference/translations.rst:11 -msgid "If you want to contribute to the translation of Odoo itself, please refer to the `Odoo Wiki page `_." -msgstr "" - -#: ../../content/developer/reference/translations.rst:15 -msgid "Exporting translatable term" -msgstr "" - -#: ../../content/developer/reference/translations.rst:17 -msgid "A number of terms in your modules are \"implicitly translatable\" as a result, even if you haven't done any specific work towards translation you can export your module's translatable terms and may find content to work with." -msgstr "" - -#: ../../content/developer/reference/translations.rst:21 -msgid "needs technical features" -msgstr "" - -#: ../../content/developer/reference/translations.rst:23 -msgid "Translations export is performed via the administration interface by logging into the backend interface and opening :menuselection:`Settings --> Translations --> Import / Export --> Export Translations`" -msgstr "" - -#: ../../content/developer/reference/translations.rst:27 -msgid "leave the language to the default (new language/empty template)" -msgstr "" - -#: ../../content/developer/reference/translations.rst:28 -msgid "select the `PO File`_ format" -msgstr "" - -#: ../../content/developer/reference/translations.rst:29 -msgid "select your module" -msgstr "" - -#: ../../content/developer/reference/translations.rst:30 -msgid "click :guilabel:`Export` and download the file" -msgstr "" - -#: ../../content/developer/reference/translations.rst:36 -msgid "This gives you a file called :file:`{yourmodule}.pot` which should be moved to the :file:`{yourmodule}/i18n/` directory. The file is a *PO Template* which simply lists translatable strings and from which actual translations (PO files) can be created. PO files can be created using msginit_, with a dedicated translation tool like POEdit_ or by simply copying the template to a new file called :file:`{language}.po`. Translation files should be put in :file:`{yourmodule}/i18n/`, next to :file:`{yourmodule}.pot`, and will be automatically loaded by Odoo when the corresponding language is installed (via :menuselection:`Settings --> Translations --> Languages`)" -msgstr "" - -#: ../../content/developer/reference/translations.rst:46 -msgid "translations for all loaded languages are also installed or updated when installing or updating a module" -msgstr "" - -#: ../../content/developer/reference/translations.rst:50 -msgid "Implicit exports" -msgstr "" - -#: ../../content/developer/reference/translations.rst:52 -msgid "Odoo automatically exports translatable strings from \"data\"-type content:" -msgstr "" - -#: ../../content/developer/reference/translations.rst:54 -msgid "in non-QWeb views, all text nodes are exported as well as the content of the ``string``, ``help``, ``sum``, ``confirm`` and ``placeholder`` attributes" -msgstr "" - -#: ../../content/developer/reference/translations.rst:57 -msgid "QWeb templates (both server-side and client-side), all text nodes are exported except inside ``t-translation=\"off\"`` blocks, the content of the ``title``, ``alt``, ``label`` and ``placeholder`` attributes are also exported" -msgstr "" - -#: ../../content/developer/reference/translations.rst:61 -msgid "for :class:`~odoo.fields.Field`, unless their model is marked with ``_translate = False``:" -msgstr "" - -#: ../../content/developer/reference/translations.rst:64 -msgid "their ``string`` and ``help`` attributes are exported" -msgstr "" - -#: ../../content/developer/reference/translations.rst:65 -msgid "if ``selection`` is present and a list (or tuple), it's exported" -msgstr "" - -#: ../../content/developer/reference/translations.rst:66 -msgid "if their ``translate`` attribute is set to ``True``, all of their existing values (across all records) are exported" -msgstr "" - -#: ../../content/developer/reference/translations.rst:68 -msgid "help/error messages of :attr:`~odoo.models.Model._constraints` and :attr:`~odoo.models.Model._sql_constraints` are exported" -msgstr "" - -#: ../../content/developer/reference/translations.rst:72 -msgid "Explicit exports" -msgstr "" - -#: ../../content/developer/reference/translations.rst:74 -msgid "When it comes to more \"imperative\" situations in Python code or Javascript code, Odoo cannot automatically export translatable terms so they must be marked explicitly for export. This is done by wrapping a literal string in a function call." -msgstr "" - -#: ../../content/developer/reference/translations.rst:79 -msgid "In Python, the wrapping function is :func:`odoo._`::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:83 -msgid "In JavaScript, the wrapping function is generally :js:func:`odoo.web._t`:" -msgstr "" - -#: ../../content/developer/reference/translations.rst:91 -msgid "Only literal strings can be marked for exports, not expressions or variables. For situations where strings are formatted, this means the format string must be marked, not the formatted string" -msgstr "" - -#: ../../content/developer/reference/translations.rst:95 -msgid "The lazy version of `_` and `_t` is :func:`odoo._lt` in python and :js:func:`odoo.web._lt` in javascript. The translation lookup is executed only at rendering and can be used to declare translatable properties in class methods of global variables." -msgstr "" - -#: ../../content/developer/reference/translations.rst:101 -msgid "Variables" -msgstr "" - -#: ../../content/developer/reference/translations.rst:102 -msgid "**Don't** the extract may work but it will not translate the text correctly::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:106 -msgid "**Do** set the dynamic variables as a parameter of the translation lookup (this will fallback on source in case of missing placeholder in the translation)::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:113 -msgid "Blocks" -msgstr "" - -#: ../../content/developer/reference/translations.rst:114 -msgid "**Don't** split your translation in several blocks or multiples lines::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:124 -msgid "**Do** keep in one block, giving the full context to translators::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:135 -msgid "Plural" -msgstr "" - -#: ../../content/developer/reference/translations.rst:136 -msgid "**Don't** pluralize terms the English-way::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:142 -msgid "**Do** keep in mind every language has different plural forms::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:150 -msgid "Read vs Run Time" -msgstr "" - -#: ../../content/developer/reference/translations.rst:152 -msgid "**Don't** invoke translation lookup at server launch::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:165 -msgid "**Don't** invoke translation lookup when the javascript file is read::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:176 -msgid "**Do** use lazy translation lookup method::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:190 -msgid "or **do** evaluate dynamically the translatable content::" -msgstr "" - -#: ../../content/developer/reference/translations.rst:199 -msgid "**Do** in the case where the translation lookup is done when the JS file is *read*, use `_lt` instead of `_t` to translate the term when it is *used*::" -msgstr "" - -#: ../../content/developer/reference/views.rst:8 -msgid "Views are what define how records should be displayed to end-users. They are specified in XML which means that they can be edited independently from the models that they represent. They are flexible and allow a high level of customization of the screens that they control. There exist various types of views. Each of them represents a mode of visualization: *form*, *list*, *kanban*, etc." -msgstr "" - -#: ../../content/developer/reference/views.rst:13 -msgid "Build doc of ir_ui_view.py ?" -msgstr "" - -#: ../../content/developer/reference/views.rst:18 -#: ../../content/developer/reference/views.rst:906 -msgid "Generic structure" -msgstr "" - -#: ../../content/developer/reference/views.rst:20 -msgid "Basic views generally share the common structure defined below. Placeholders are denoted in all caps." -msgstr "" - -#: ../../content/developer/reference/views.rst:38 -msgid "View objects expose a number of fields. They are optional unless specified otherwise." -msgstr "" - -#: ../../content/developer/reference/views.rst:40 -msgid "``name`` (mandatory) :class:`~odoo.fields.Char`" -msgstr "" - -#: ../../content/developer/reference/views.rst:42 -msgid "Only useful as a mnemonic/description of the view when looking for one in a list of some sort." -msgstr "" - -#: ../../content/developer/reference/views.rst:44 -msgid "``model`` :class:`~odoo.fields.Char`" -msgstr "" - -#: ../../content/developer/reference/views.rst:46 -msgid "The model linked to the view, if applicable." -msgstr "" - -#: ../../content/developer/reference/views.rst:48 -msgid "``priority`` :class:`~odoo.fields.Integer`" -msgstr "" - -#: ../../content/developer/reference/views.rst:50 -msgid "When a view is requested by ``(model, type)``, the view matching the model and the type, with the lowest priority will be returned (it is the default view)." -msgstr "" - -#: ../../content/developer/reference/views.rst:53 -msgid "It also defines the order of views application during :ref:`view inheritance `." -msgstr "" - -#: ../../content/developer/reference/views.rst:56 -msgid "``groups_id`` :class:`~odoo.fields.Many2many` -> :class:`odoo.addons.base.models.res_users.Groups`" -msgstr "" - -#: ../../content/developer/reference/views.rst:58 -msgid "The groups allowed to use/access the current view." -msgstr "" - -#: ../../content/developer/reference/views.rst:60 -msgid "If the view extends an existing view, the extension will only be applied for a given user if the user has access to the provided ``groups_id``." -msgstr "" - -#: ../../content/developer/reference/views.rst:63 -msgid "``arch`` :class:`~odoo.fields.Text`" -msgstr "" - -#: ../../content/developer/reference/views.rst:65 -msgid "The description of the view layout." -msgstr "" - -#: ../../content/developer/reference/views.rst:68 -msgid "Attributes" -msgstr "" - -#: ../../content/developer/reference/views.rst:72 -msgid "view attributes & view element attributes attrs & states attributes are missing generic information" -msgstr "" - -#: ../../content/developer/reference/views.rst:75 -msgid "The different view types have a wide variety of attributes allowing customizations of the generic behaviors. Some main attributes will be explained here. They do not all have an impact on all view types." -msgstr "" - -#: ../../content/developer/reference/views.rst:79 -msgid "The current context and user access rights may also impact the view abilities." -msgstr "" - -#: ../../content/developer/reference/views.rst:81 -msgid "info on create/... in the context ?" -msgstr "" - -#: ../../content/developer/reference/views.rst:83 -#: ../../content/developer/reference/views.rst:1606 -msgid "``create``" -msgstr "" - -#: ../../content/developer/reference/views.rst:85 -msgid "Disable/enable record creation on the view." -msgstr "" - -#: ../../content/developer/reference/views.rst:87 -msgid "``edit`` (``form`` & ``list`` & ``gantt``)" -msgstr "" - -#: ../../content/developer/reference/views.rst:89 -msgid "Disable/enable record editing on the view." -msgstr "" - -#: ../../content/developer/reference/views.rst:91 -msgid "``delete`` (``form`` & ``list``)" -msgstr "" - -#: ../../content/developer/reference/views.rst:93 -msgid "Disable/enable record deletion on the view through the **Action** dropdown." -msgstr "" - -#: ../../content/developer/reference/views.rst:95 -msgid "``duplicate`` (``form`` & ``list``)" -msgstr "" - -#: ../../content/developer/reference/views.rst:97 -msgid "Disable/enable record duplication on the view through the **Action** dropdown." -msgstr "" - -#: ../../content/developer/reference/views.rst:99 -msgid "``decoration-{$name}`` (``list`` & ``gantt``)" -msgstr "" - -#: ../../content/developer/reference/views.rst:101 -msgid "Define a conditional display of a record in the style of a row's text based on the corresponding record's attributes." -msgstr "" - -#: ../../content/developer/reference/views.rst:123 -msgid "Supported values differ for the two view types. The Gantt view only supports ``success``, ``info``, ``warning``, ``danger`` and ``secondary`` displays. The list view supports ``bf``, ``it``, ``success``, ``info``, ``warning``, ``danger``, ``muted`` and ``primary`` displays." -msgstr "" - -#: ../../content/developer/reference/views.rst:127 -msgid "``sample`` (``kanban`` & ``list`` & ``gantt`` & ``graph`` & ``pivot`` & ``cohort`` & ``dashboard``)" -msgstr "" - -#: ../../content/developer/reference/views.rst:129 -msgid "Populate the view with a set of sample records if none are found for the current model. This attribute is false by default." -msgstr "" - -#: ../../content/developer/reference/views.rst:132 -msgid "These fake records will have heuristics for certain field names/models. For example, a field 'display_name' on the model 'res.users' will be populated with sample people names while an 'email' field will be in the form 'firstname.lastname@sample.demo'." -msgstr "" - -#: ../../content/developer/reference/views.rst:136 -msgid "The user will not be able to interact with these data and they will be discarded as soon as an action is performed (record created, column added, etc.)" -msgstr "" - -#: ../../content/developer/reference/views.rst:139 -msgid "``banner_route`` a route address to be fetched and prepended to the view." -msgstr "" - -#: ../../content/developer/reference/views.rst:142 -msgid "If this attribute is set, the :ref:`controller route url` will be fetched and displayed above the view. The json response from the controller should contain an \"html\" key." -msgstr "" - -#: ../../content/developer/reference/views.rst:147 -msgid "If the html contains a stylesheet tag, it will be removed and appended to ." -msgstr "" - -#: ../../content/developer/reference/views.rst:150 -msgid "To interact with the backend you can use tags. Please take a look at the documentation of the _onActionClicked method of AbstractController (*addons/web/static/src/js/views/abstract_controller.js*) for more details." -msgstr "" - -#: ../../content/developer/reference/views.rst:155 -msgid "Only views extending AbstractView and AbstractController can use this attribute, like :ref:`reference/views/form`, :ref:`reference/views/kanban`, :ref:`reference/views/list`, ..." -msgstr "" - -#: ../../content/developer/reference/views.rst:159 -#: ../../content/developer/reference/views.rst:1901 -#: ../../content/developer/reference/views.rst:1938 -#: ../../content/developer/reference/views.rst:1964 -msgid "Example:" -msgstr "" - -#: ../../content/developer/reference/views.rst:179 -msgid "Views main content section, with field, group & separator ?" -msgstr "" - -#: ../../content/developer/reference/views.rst:187 -msgid "Inheritance fields" -msgstr "" - -#: ../../content/developer/reference/views.rst:189 -msgid "The two following :class:`~odoo.addons.base.ir_ui_view.View` fields are used to specify inherited views." -msgstr "" - -#: ../../content/developer/reference/views.rst:192 -msgid "``inherit_id`` :class:`~odoo.fields.Many2one`" -msgstr "" - -#: ../../content/developer/reference/views.rst:194 -msgid "the current view's parent view, unset by default. Specify the parent using the `ref` attribute:" -msgstr "" - -#: ../../content/developer/reference/views.rst:201 -msgid "``mode`` :class:`~odoo.fields.Selection`: `extension / primary`" -msgstr "" - -#: ../../content/developer/reference/views.rst:203 -msgid "inheritance mode, ``extension`` by default if ``inherit_id`` is set, ``primary`` otherwise." -msgstr "" - -#: ../../content/developer/reference/views.rst:206 -msgid "An example of where you would want to override ``mode`` while using ``inherit_id`` is delegation inheritance. In that case your derived model will be separate from its parent and views matching with one won't match with the other. Suppose you inherit from a view associated with the parent model and want to customize the derived view to show data from the derived model. The ``mode`` of the derived view needs to be set to ``primary``, because it's the base (and maybe only) view for that derived model. Otherwise the :ref:`view matching ` rules won't apply." -msgstr "" - -#: ../../content/developer/reference/views.rst:219 -msgid "View matching" -msgstr "" - -#: ../../content/developer/reference/views.rst:221 -msgid "if a view is requested by ``(model, type)``, the view with the right model and type, ``mode=primary`` and the lowest priority is matched." -msgstr "" - -#: ../../content/developer/reference/views.rst:223 -msgid "when a view is requested by ``id``, if its mode is not ``primary`` its *closest* parent with mode ``primary`` is matched." -msgstr "" - -#: ../../content/developer/reference/views.rst:227 -msgid "View resolution" -msgstr "" - -#: ../../content/developer/reference/views.rst:229 -msgid "Resolution generates the final ``arch`` for a requested/matched ``primary`` view:" -msgstr "" - -#: ../../content/developer/reference/views.rst:232 -msgid "if the view has a parent, the parent is fully resolved then the current view's inheritance specs are applied" -msgstr "" - -#: ../../content/developer/reference/views.rst:234 -msgid "if the view has no parent, its ``arch`` is used as-is" -msgstr "" - -#: ../../content/developer/reference/views.rst:235 -msgid "the current view's children with mode ``extension`` are looked up and their inheritance specs are applied depth-first (a child view is applied, then its children, then its siblings)" -msgstr "" - -#: ../../content/developer/reference/views.rst:239 -msgid "The result of applying children views yields the final ``arch``" -msgstr "" - -#: ../../content/developer/reference/views.rst:241 -msgid "NOTE on fields_view_get and link to ORM ?" -msgstr "" - -#: ../../content/developer/reference/views.rst:244 -msgid "Inheritance specs" -msgstr "" - -#: ../../content/developer/reference/views.rst:246 -msgid "Inheritance specs are comprised of an element locator, to match the inherited element in the parent view, and children element that will be used to modify the inherited element." -msgstr "" - -#: ../../content/developer/reference/views.rst:250 -msgid "There are three types of element locators for matching a target element:" -msgstr "" - -#: ../../content/developer/reference/views.rst:252 -msgid "An ``xpath`` element with an ``expr`` attribute. ``expr`` is an XPath_ expression\\ [#hasclass]_ applied to the current ``arch``, the first node it finds is the match" -msgstr "" - -#: ../../content/developer/reference/views.rst:255 -msgid "a ``field`` element with a ``name`` attribute, matches the first ``field`` with the same ``name``. All other attributes are ignored during matching" -msgstr "" - -#: ../../content/developer/reference/views.rst:257 -msgid "any other element: the first element with the same name and identical attributes (ignoring ``position`` and ``version`` attributes) is matched" -msgstr "" - -#: ../../content/developer/reference/views.rst:274 -msgid "The inheritance spec may have an optional ``position`` attribute specifying how the matched node should be altered:" -msgstr "" - -#: ../../content/developer/reference/views.rst:277 -msgid "``inside`` (default)" -msgstr "" - -#: ../../content/developer/reference/views.rst:278 -msgid "the content of the inheritance spec is appended to the matched node" -msgstr "" - -#: ../../content/developer/reference/views.rst:280 -msgid "the content of the inheritance spec replaces the matched node. Any text node containing only ``$0`` within the contents of the spec will be replaced by a complete copy of the matched node, effectively wrapping the matched node." -msgstr "" - -#: ../../content/developer/reference/views.rst:285 -msgid "the content of the inheritance spec is added to the matched node's parent, after the matched node" -msgstr "" - -#: ../../content/developer/reference/views.rst:288 -msgid "the content of the inheritance spec is added to the matched node's parent, before the matched node" -msgstr "" - -#: ../../content/developer/reference/views.rst:291 -msgid "the content of the inheritance spec should be ``attribute`` elements with a ``name`` attribute and an optional body:" -msgstr "" - -#: ../../content/developer/reference/views.rst:294 -msgid "if the ``attribute`` element has a body, a new attributed named after its ``name`` is created on the matched node with the ``attribute`` element's text as value" -msgstr "" - -#: ../../content/developer/reference/views.rst:297 -msgid "if the ``attribute`` element has no body, the attribute named after its ``name`` is removed from the matched node. If no such attribute exists, an error is raised" -msgstr "" - -#: ../../content/developer/reference/views.rst:324 -msgid "``move``" -msgstr "" - -#: ../../content/developer/reference/views.rst:311 -msgid "can be used as a direct child of a inheritance spec with a ``inside``, ``replace``, ``after`` or ``before`` ``position`` attribute to move a node." -msgstr "" - -#: ../../content/developer/reference/views.rst:326 -msgid "A view's specs are applied sequentially." -msgstr "" - -#: ../../content/developer/reference/views.rst:328 -msgid "an extension function is added for simpler matching in QWeb views: ``hasclass(*classes)`` matches if the context node has all the specified classes" -msgstr "" - -#: ../../content/developer/reference/views.rst:335 -msgid "View types" -msgstr "" - -#: ../../content/developer/reference/views.rst:340 -msgid "Activity" -msgstr "" - -#: ../../content/developer/reference/views.rst:342 -msgid "The Activity view is used to display the activities linked to the records. The data are displayed in a chart with the records forming the rows and the activity types the columns. The first cell of each row displays a (customizable, see ``templates``, quite similarly to :ref:`reference/views/kanban`) card representing the corresponding record. When clicking on others cells, a detailed description of all activities of the same type for the record is displayed." -msgstr "" - -#: ../../content/developer/reference/views.rst:351 -msgid "The Activity view is only available when the ``mail`` module is installed, and for the models that inherit from the ``mail.activity.mixin``." -msgstr "" - -#: ../../content/developer/reference/views.rst:354 -msgid "The root element of the Activity view is ````, it accepts the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:358 -#: ../../content/developer/reference/views.rst:487 -msgid "``string`` (mandatory)" -msgstr "" - -#: ../../content/developer/reference/views.rst:358 -#: ../../content/developer/reference/views.rst:487 -msgid "A title, which should describe the view" -msgstr "" - -#: ../../content/developer/reference/views.rst:360 -#: ../../content/developer/reference/views.rst:1223 -msgid "Possible children of the view element are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:363 -msgid "declares fields to use in activity *logic*. If the field is simply displayed in the activity view, it does not need to be pre-declared." -msgstr "" - -#: ../../content/developer/reference/views.rst:366 -#: ../../content/developer/reference/views.rst:1229 -#: ../../content/developer/reference/views.rst:1237 -msgid "Possible attributes are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:369 -#: ../../content/developer/reference/views.rst:520 -#: ../../content/developer/reference/views.rst:1137 -#: ../../content/developer/reference/views.rst:1232 -#: ../../content/developer/reference/views.rst:1723 -msgid "``name`` (required)" -msgstr "" - -#: ../../content/developer/reference/views.rst:369 -#: ../../content/developer/reference/views.rst:1232 -msgid "the name of the field to fetch" -msgstr "" - -#: ../../content/developer/reference/views.rst:387 -#: ../../content/developer/reference/views.rst:1081 -#: ../../content/developer/reference/views.rst:1319 -msgid "``templates``" -msgstr "" - -#: ../../content/developer/reference/views.rst:372 -msgid "defines the :ref:`reference/qweb` templates. Cards definition may be split into multiple templates for clarity, but activity views *must* define at least one root template ``activity-box``, which will be rendered once for each record." -msgstr "" - -#: ../../content/developer/reference/views.rst:377 -msgid "The activity view uses mostly-standard :ref:`javascript qweb ` and provides the following context variables (see :ref:`reference/views/kanban` for more details):" -msgstr "" - -#: ../../content/developer/reference/views.rst:383 -#: ../../content/developer/reference/views.rst:723 -#: ../../content/developer/reference/views.rst:820 -#: ../../content/developer/reference/views.rst:1077 -#: ../../content/developer/reference/views.rst:1263 -#: ../../content/developer/reference/views.rst:1509 -msgid "``widget``" -msgstr "" - -#: ../../content/developer/reference/views.rst:382 -msgid "the current :js:class:`ActivityRecord`, can be used to fetch some meta-information. These methods are also available directly in the template context and don't need to be accessed via ``widget``" -msgstr "" - -#: ../../content/developer/reference/views.rst:386 -msgid "an object with all the requested fields as its attributes. Each field has two attributes ``value`` and ``raw_value``" -msgstr "" - -#: ../../content/developer/reference/views.rst:392 -#: ../../content/developer/reference/views.rst:1324 -msgid "Calendar" -msgstr "" - -#: ../../content/developer/reference/views.rst:394 -msgid "Calendar views display records as events in a daily, weekly, monthly or yearly calendar. Their root element is ````. Available attributes on the calendar view are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:398 -#: ../../content/developer/reference/views.rst:957 -#: ../../content/developer/reference/views.rst:1330 -msgid "``date_start`` (required)" -msgstr "" - -#: ../../content/developer/reference/views.rst:399 -#: ../../content/developer/reference/views.rst:1331 -msgid "name of the record's field holding the start date for the event" -msgstr "" - -#: ../../content/developer/reference/views.rst:402 -#: ../../content/developer/reference/views.rst:1334 -msgid "``date_stop``" -msgstr "" - -#: ../../content/developer/reference/views.rst:401 -#: ../../content/developer/reference/views.rst:1333 -msgid "name of the record's field holding the end date for the event, if ``date_stop`` is provided records become movable (via drag and drop) directly in the calendar" -msgstr "" - -#: ../../content/developer/reference/views.rst:405 -#: ../../content/developer/reference/views.rst:1337 -msgid "``date_delay``" -msgstr "" - -#: ../../content/developer/reference/views.rst:405 -#: ../../content/developer/reference/views.rst:1337 -msgid "alternative to ``date_stop``, provides the duration of the event instead of its end date (unit: day)" -msgstr "" - -#: ../../content/developer/reference/views.rst:408 -#: ../../content/developer/reference/views.rst:1340 -msgid "name of a record field to use for *color segmentation*. Records in the same color segment are allocated the same highlight color in the calendar, colors are allocated semi-randomly. Displayed the display_name/avatar of the visible record in the sidebar" -msgstr "" - -#: ../../content/developer/reference/views.rst:414 -#: ../../content/developer/reference/views.rst:1086 -#: ../../content/developer/reference/views.rst:1346 -msgid "``form_view_id``" -msgstr "" - -#: ../../content/developer/reference/views.rst:413 -#: ../../content/developer/reference/views.rst:1345 -msgid "view to open when the user create or edit an event. Note that if this attribute is not set, the calendar view will fall back to the id of the form view in the current action, if any." -msgstr "" - -#: ../../content/developer/reference/views.rst:418 -#: ../../content/developer/reference/views.rst:1350 -msgid "``event_open_popup``" -msgstr "" - -#: ../../content/developer/reference/views.rst:417 -#: ../../content/developer/reference/views.rst:1349 -msgid "If the option 'event_open_popup' is set to true, then the calendar view will open events (or records) in a FormViewDialog. Otherwise, it will open events in a new form view (with a do_action)" -msgstr "" - -#: ../../content/developer/reference/views.rst:422 -#: ../../content/developer/reference/views.rst:1354 -msgid "``quick_add``" -msgstr "" - -#: ../../content/developer/reference/views.rst:421 -#: ../../content/developer/reference/views.rst:1353 -msgid "enables quick-event creation on click: only asks the user for a ``name`` and tries to create a new event with just that and the clicked event time. Falls back to a full form dialog if the quick creation fails" -msgstr "" - -#: ../../content/developer/reference/views.rst:425 -#: ../../content/developer/reference/views.rst:1357 -msgid "``all_day``" -msgstr "" - -#: ../../content/developer/reference/views.rst:425 -#: ../../content/developer/reference/views.rst:1357 -msgid "name of a boolean field on the record indicating whether the corresponding event is flagged as day-long (and duration is irrelevant)" -msgstr "" - -#: ../../content/developer/reference/views.rst:428 -#: ../../content/developer/reference/views.rst:869 -#: ../../content/developer/reference/views.rst:1360 -msgid "``mode``" -msgstr "" - -#: ../../content/developer/reference/views.rst:428 -msgid "Default display mode when loading the calendar. Possible attributes are: ``day``, ``week``, ``month``, ``year``" -msgstr "" - -#: ../../content/developer/reference/views.rst:432 -#: ../../content/developer/reference/views.rst:1065 -msgid "``scales``" -msgstr "" - -#: ../../content/developer/reference/views.rst:431 -msgid "Comma-separated list of scales to provide. By default, all scales are available. See mode for possible scale values." -msgstr "" - -#: ../../content/developer/reference/views.rst:452 -#: ../../content/developer/reference/views.rst:1367 -msgid "````" -msgstr "" - -#: ../../content/developer/reference/views.rst:435 -#: ../../content/developer/reference/views.rst:1366 -msgid "declares fields to aggregate or to use in kanban *logic*. If the field is simply displayed in the calendar cards." -msgstr "" - -#: ../../content/developer/reference/views.rst:438 -msgid "Fields can have additional attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:440 -msgid "``invisible`` use \"True\" to hide the value in the cards" -msgstr "" - -#: ../../content/developer/reference/views.rst:442 -msgid "``avatar_field`` only for x2many field, to display the avatar instead of the display_name in the cards" -msgstr "" - -#: ../../content/developer/reference/views.rst:445 -msgid "``write_model`` and ``write_field``" -msgstr "" - -#: ../../content/developer/reference/views.rst:447 -msgid "you can add a filter and save the result in the defined model, the filter is added in the sidebar" -msgstr "" - -#: ../../content/developer/reference/views.rst:449 -msgid "``filter`` and ``color``" -msgstr "" - -#: ../../content/developer/reference/views.rst:451 -msgid "use \"True\" to add this field in filter in the sidebar. You can specify a ``color`` field used to colorize the checkbox." -msgstr "" - -#: ../../content/developer/reference/views.rst:457 -msgid "Cohort" -msgstr "" - -#: ../../content/developer/reference/views.rst:463 -msgid "The cohort view is used to display and understand the way some data changes over a period of time. For example, imagine that for a given business, clients can subscribe to some service. The cohort view can then display the total number of subscriptions each month, and study the rate at which client leave the service (churn). When clicking on a cell, the cohort view will redirect you to a new action in which you will only see the records contained in the cell's time interval; this action contains a list view and a form view." -msgstr "" - -#: ../../content/developer/reference/views.rst:471 -msgid "By default the cohort view will use the same list and form views as those defined on the action. You can pass a list view and a form view to the context of the action in order to set/override the views that will be used (the context keys to use being `form_view_id` and `list_view_id`)" -msgstr "" - -#: ../../content/developer/reference/views.rst:476 -msgid "For example, here is a very simple cohort view:" -msgstr "" - -#: ../../content/developer/reference/views.rst:482 -msgid "The root element of the Cohort view is , it accepts the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:491 -msgid "``date_start`` (mandatory)" -msgstr "" - -#: ../../content/developer/reference/views.rst:490 -msgid "A valid date or datetime field. This field is understood by the view as the beginning date of a record" -msgstr "" - -#: ../../content/developer/reference/views.rst:495 -msgid "``date_stop`` (mandatory)" -msgstr "" - -#: ../../content/developer/reference/views.rst:494 -msgid "A valid date or datetime field. This field is understood by the view as the end date of a record. This is the field that will determine the churn." -msgstr "" - -#: ../../content/developer/reference/views.rst:500 -msgid "``mode`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:498 -msgid "A string to describe the mode. It should be either 'churn' or 'retention' (default). Churn mode will start at 0% and accumulate over time whereas retention will start at 100% and decrease over time." -msgstr "" - -#: ../../content/developer/reference/views.rst:506 -msgid "``timeline`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:503 -msgid "A string to describe the timeline. It should be either 'backward' or 'forward' (default). Forward timeline will display data from date_start to date_stop, whereas backward timeline will display data from date_stop to date_start (when the date_start is in future / greater than date_stop)." -msgstr "" - -#: ../../content/developer/reference/views.rst:510 -msgid "``interval`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:509 -msgid "A string to describe a time interval. It should be 'day', 'week', 'month'' (default) or 'year'." -msgstr "" - -#: ../../content/developer/reference/views.rst:514 -#: ../../content/developer/reference/views.rst:663 -msgid "``measure`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:513 -msgid "A field that can be aggregated. This field will be used to compute the values for each cell. If not set, the cohort view will count the number of occurrences." -msgstr "" - -#: ../../content/developer/reference/views.rst:518 -msgid "```` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:517 -msgid "allows to specify a particular field in order to manage it from the available measures, it's main use is for hiding a field from the selectable measures:" -msgstr "" - -#: ../../content/developer/reference/views.rst:521 -msgid "the name of the field to use in the view." -msgstr "" - -#: ../../content/developer/reference/views.rst:523 -#: ../../content/developer/reference/views.rst:588 -#: ../../content/developer/reference/views.rst:620 -#: ../../content/developer/reference/views.rst:693 -msgid "``string`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:523 -msgid "the name that would be used to display the field in the cohort view, overrides the default python String attribute of the field." -msgstr "" - -#: ../../content/developer/reference/views.rst:528 -#: ../../content/developer/reference/views.rst:1144 -msgid "``invisible`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:526 -#: ../../content/developer/reference/views.rst:1745 -msgid "if true, the field will not appear either in the active measures nor in the selectable measures (useful for fields that do not make sense aggregated, such as fields in different units, e.g. € and $)." -msgstr "" - -#: ../../content/developer/reference/views.rst:533 -msgid "Dashboard" -msgstr "" - -#: ../../content/developer/reference/views.rst:539 -msgid "Like pivot and graph view, The dashboard view is used to display aggregate data. However, the dashboard can embed sub views, which makes it possible to have a more complete and interesting look on a given dataset." -msgstr "" - -#: ../../content/developer/reference/views.rst:543 -msgid "The dashboard view can display sub views, aggregates for some fields (over a domain), or even *formulas* (expressions which involves one or more aggregates). For example, here is a very simple dashboard:" -msgstr "" - -#: ../../content/developer/reference/views.rst:560 -msgid "The root element of the Dashboard view is , it does not accept any attributes." -msgstr "" - -#: ../../content/developer/reference/views.rst:563 -msgid "There are 5 possible type of tags in a dashboard view:" -msgstr "" - -#: ../../content/developer/reference/views.rst:566 -msgid "declares a sub view." -msgstr "" - -#: ../../content/developer/reference/views.rst:568 -#: ../../content/developer/reference/views.rst:585 -#: ../../content/developer/reference/views.rst:605 -#: ../../content/developer/reference/views.rst:681 -#: ../../content/developer/reference/views.rst:715 -msgid "Admissible attributes are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:571 -msgid "``type`` (mandatory)" -msgstr "" - -#: ../../content/developer/reference/views.rst:571 -msgid "The type of the sub view. For example, *graph* or *pivot*." -msgstr "" - -#: ../../content/developer/reference/views.rst:575 -msgid "``ref`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:574 -msgid "An xml id for a view. If not given, the default view for the model will be used." -msgstr "" - -#: ../../content/developer/reference/views.rst:579 -#: ../../content/developer/reference/views.rst:690 -#: ../../content/developer/webservices/extract_api.rst:308 -msgid "``name`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:578 -msgid "A string which identifies this element. It is mostly useful to be used as a target for an xpath." -msgstr "" - -#: ../../content/developer/reference/views.rst:596 -#: ../../content/developer/reference/views.rst:766 -#: ../../content/developer/reference/views.rst:2015 -msgid "``group``" -msgstr "" - -#: ../../content/developer/reference/views.rst:582 -msgid "defines a column layout. This is actually very similar to the group element in a form view." -msgstr "" - -#: ../../content/developer/reference/views.rst:588 -msgid "A description which will be displayed as a group title." -msgstr "" - -#: ../../content/developer/reference/views.rst:591 -msgid "``colspan`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:591 -msgid "The number of subcolumns in this group tag. By default, 6." -msgstr "" - -#: ../../content/developer/reference/views.rst:596 -#: ../../content/developer/reference/views.rst:647 -#: ../../content/developer/reference/views.rst:697 -#: ../../content/developer/reference/views.rst:723 -msgid "``col`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:594 -msgid "The number of columns spanned by this group tag (only makes sense inside another group). By default, 6." -msgstr "" - -#: ../../content/developer/reference/views.rst:673 -msgid "``aggregate``" -msgstr "" - -#: ../../content/developer/reference/views.rst:599 -msgid "declares an aggregate. This is the value of an aggregate for a given field over the current domain." -msgstr "" - -#: ../../content/developer/reference/views.rst:602 -msgid "Note that aggregates are supposed to be used inside a group tag (otherwise the style will not be properly applied)." -msgstr "" - -#: ../../content/developer/reference/views.rst:613 -msgid "``field`` (mandatory)" -msgstr "" - -#: ../../content/developer/reference/views.rst:608 -msgid "The field name to use for computing the aggregate. Possible field types are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:611 -msgid "``integer`` (default group operator is sum)" -msgstr "" - -#: ../../content/developer/reference/views.rst:612 -msgid "``float`` (default group operator is sum)" -msgstr "" - -#: ../../content/developer/reference/views.rst:613 -msgid "``many2one`` (default group operator is count distinct)" -msgstr "" - -#: ../../content/developer/reference/views.rst:616 -msgid "A string to identify this aggregate (useful for formulas)" -msgstr "" - -#: ../../content/developer/reference/views.rst:619 -msgid "A short description that will be displayed above the value. If not given, it will fall back to the field string." -msgstr "" - -#: ../../content/developer/reference/views.rst:623 -msgid "An additional restriction on the set of records that we want to aggregate. This domain will be combined with the current domain." -msgstr "" - -#: ../../content/developer/reference/views.rst:629 -msgid "``domain_label`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:627 -msgid "When the user clicks on an aggregate with a domain, it will be added to the search view as a facet. The string displayed for this facet can be customized with this attribute." -msgstr "" - -#: ../../content/developer/reference/views.rst:643 -msgid "``group_operator`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:632 -msgid "A valid postgreSQL aggregate function identifier to use when aggregating values (see https://www.postgresql.org/docs/9.5/static/functions-aggregate.html). If not provided, By default, the group_operator from the field definition is used. Note that no aggregation of field values is achieved if the group_operator value is \"\"." -msgstr "" - -#: ../../content/developer/reference/views.rst:637 -msgid "The special aggregate function ``count_distinct`` (defined in odoo) can also be used here" -msgstr "" - -#: ../../content/developer/reference/views.rst:646 -#: ../../content/developer/reference/views.rst:696 -#: ../../content/developer/reference/views.rst:722 -msgid "The number of columns spanned by this tag (only makes sense inside a group). By default, 1." -msgstr "" - -#: ../../content/developer/reference/views.rst:651 -#: ../../content/developer/reference/views.rst:701 -msgid "``widget`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:650 -msgid "A widget to format the value (like the widget attribute for fields). For example, monetary." -msgstr "" - -#: ../../content/developer/reference/views.rst:654 -#: ../../content/developer/reference/views.rst:704 -msgid "``help`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:654 -#: ../../content/developer/reference/views.rst:704 -msgid "A help message to dipslay in a tooltip (equivalent of help for a field in python)" -msgstr "" - -#: ../../content/developer/reference/views.rst:657 -msgid "This attribute is the name of a field describing the measure that has to be used in the graph and pivot views when clicking on the aggregate. The special value __count__ can be used to use the count measure." -msgstr "" - -#: ../../content/developer/reference/views.rst:668 -msgid "``clickable`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:666 -msgid "A boolean indicating if this aggregate should be clickable or not (default to true). Clicking on a clickable aggregate will change the measures used by the subviews and add the value of the domain attribute (if any) to the search view." -msgstr "" - -#: ../../content/developer/reference/views.rst:673 -#: ../../content/developer/reference/views.rst:709 -msgid "``value_label`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:671 -msgid "A string put on the right of the aggregate value. For example, it can be useful to indicate the unit of measure of the aggregate value." -msgstr "" - -#: ../../content/developer/reference/views.rst:709 -msgid "``formula``" -msgstr "" - -#: ../../content/developer/reference/views.rst:676 -msgid "declares a derived value. Formulas are values computed from aggregates." -msgstr "" - -#: ../../content/developer/reference/views.rst:678 -msgid "Note that like aggregates, formulas are supposed to be used inside a group tag (otherwise the style will not be properly applied)." -msgstr "" - -#: ../../content/developer/reference/views.rst:687 -msgid "``value`` (mandatory)" -msgstr "" - -#: ../../content/developer/reference/views.rst:684 -msgid "A string expression that will be evaluated, with the builtin python evaluator (in the web client). Every aggregate can be used in the context, in the ``record`` variable. For example, ``record.price_total / record.order_id``." -msgstr "" - -#: ../../content/developer/reference/views.rst:690 -msgid "A string to identify this formula" -msgstr "" - -#: ../../content/developer/reference/views.rst:693 -msgid "A short description that will be displayed above the formula." -msgstr "" - -#: ../../content/developer/reference/views.rst:700 -msgid "A widget to format the value (like the widget attribute for fields). For example, monetary. By default, it is 'float'." -msgstr "" - -#: ../../content/developer/reference/views.rst:707 -msgid "A string put on the right of the formula value. For example, it can be useful to indicate the unit of measure of the formula value." -msgstr "" - -#: ../../content/developer/reference/views.rst:712 -msgid "Declares a specialized widget to be used to display the information. This is a mechanism similar to the widgets in the form view." -msgstr "" - -#: ../../content/developer/reference/views.rst:718 -msgid "A string to identify which widget should be instantiated. The view will look into the ``widget_registry`` to get the proper class." -msgstr "" - -#: ../../content/developer/reference/views.rst:728 -msgid "Form" -msgstr "" - -#: ../../content/developer/reference/views.rst:730 -msgid "Form views are used to display the data from a single record. Their root element is ````. They are composed of regular HTML_ with additional structural and semantic components." -msgstr "" - -#: ../../content/developer/reference/views.rst:735 -#: ../../content/developer/reference/views.rst:1663 -msgid "Structural components" -msgstr "" - -#: ../../content/developer/reference/views.rst:737 -msgid "Structural components provide structure or \"visual\" features with little logic. They are used as elements or sets of elements in form views." -msgstr "" - -#: ../../content/developer/reference/views.rst:751 -msgid "``notebook``" -msgstr "" - -#: ../../content/developer/reference/views.rst:741 -msgid "defines a tabbed section. Each tab is defined through a ``page`` child element. Pages can have the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:744 -msgid "``string`` (required) the title of the tab" -msgstr "" - -#: ../../content/developer/reference/views.rst:746 -msgid "``accesskey`` an HTML accesskey_" -msgstr "" - -#: ../../content/developer/reference/views.rst:748 -msgid "``attrs`` standard dynamic attributes based on record values" -msgstr "" - -#: ../../content/developer/reference/views.rst:751 -msgid "Note that ``notebook`` should not be placed within ``group``" -msgstr "" - -#: ../../content/developer/reference/views.rst:754 -msgid "used to define column layouts in forms. By default, groups define 2 columns and most direct children of groups take a single column. ``field`` direct children of groups display a label by default, and the label and the field itself have a colspan of 1 each." -msgstr "" - -#: ../../content/developer/reference/views.rst:759 -msgid "The number of columns in a ``group`` can be customized using the ``col`` attribute, the number of columns taken by an element can be customized using ``colspan``." -msgstr "" - -#: ../../content/developer/reference/views.rst:763 -msgid "Children are laid out horizontally (tries to fill the next column before changing row)." -msgstr "" - -#: ../../content/developer/reference/views.rst:766 -msgid "Groups can have a ``string`` attribute, which is displayed as the group's title" -msgstr "" - -#: ../../content/developer/reference/views.rst:770 -msgid "``newline``" -msgstr "" - -#: ../../content/developer/reference/views.rst:769 -msgid "only useful within ``group`` elements, ends the current row early and immediately switches to a new row (without filling any remaining column beforehand)" -msgstr "" - -#: ../../content/developer/reference/views.rst:773 -#: ../../content/developer/reference/views.rst:2011 -msgid "``separator``" -msgstr "" - -#: ../../content/developer/reference/views.rst:773 -msgid "small horizontal spacing, with a ``string`` attribute behaves as a section title" -msgstr "" - -#: ../../content/developer/reference/views.rst:776 -msgid "``sheet``" -msgstr "" - -#: ../../content/developer/reference/views.rst:776 -msgid "can be used as a direct child to ``form`` for a narrower and more responsive form layout" -msgstr "" - -#: ../../content/developer/reference/views.rst:780 -msgid "``header``" -msgstr "" - -#: ../../content/developer/reference/views.rst:779 -msgid "combined with ``sheet``, provides a full-width location above the sheet itself, generally used to display workflow buttons and status widgets" -msgstr "" - -#: ../../content/developer/reference/views.rst:783 -msgid "Semantic components" -msgstr "" - -#: ../../content/developer/reference/views.rst:785 -msgid "Semantic components tie into and allow interaction with the Odoo system. Available semantic components are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:798 -#: ../../content/developer/reference/views.rst:1483 -msgid "``button``" -msgstr "" - -#: ../../content/developer/reference/views.rst:789 -msgid "call into the Odoo system, similar to :ref:`list view buttons `. In addition, the following attribute can be specified:" -msgstr "" - -#: ../../content/developer/reference/views.rst:794 -msgid "``special``" -msgstr "" - -#: ../../content/developer/reference/views.rst:794 -msgid "for form views opened in dialogs: ``save`` to save the record and close the dialog, ``cancel`` to close the dialog without saving." -msgstr "" - -#: ../../content/developer/reference/views.rst:798 -msgid "``confirm``" -msgstr "" - -#: ../../content/developer/reference/views.rst:797 -msgid "confirmation message to display (and for the user to accept) before performing the button's Odoo call (also works in Kanban views)." -msgstr "" - -#: ../../content/developer/reference/views.rst:801 -msgid "renders (and allow editing of, possibly) a single field of the current record. Using several times a field in a form view is supported and the fields can receive different values for modifiers 'invisible' and 'readonly'. However, the behavior is not guaranteed when several fields exist with different values for modifier 'required'. Possible attributes of the field node are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:808 -msgid "the name of the field to render" -msgstr "" - -#: ../../content/developer/reference/views.rst:810 -msgid "the node id. Useful when there are several occurrences of the same field in the view (see ``label`` component below). Default is the field name." -msgstr "" - -#: ../../content/developer/reference/views.rst:813 -msgid "fields have a default rendering based on their type (e.g. :class:`~odoo.fields.Char`, :class:`~odoo.fields.Many2one`). The ``widget`` attributes allows using a different rendering method and context." -msgstr "" - -#: ../../content/developer/reference/views.rst:818 -msgid "list of widgets" -msgstr "" - -#: ../../content/developer/reference/views.rst:820 -msgid "& options & specific attributes (e.g. widget=statusbar statusbar_visible clickable)" -msgstr "" - -#: ../../content/developer/reference/views.rst:823 -msgid "``options``" -msgstr "" - -#: ../../content/developer/reference/views.rst:823 -msgid "JSON object specifying configuration option for the field's widget (including default widgets)" -msgstr "" - -#: ../../content/developer/reference/views.rst:835 -#: ../../content/developer/reference/views.rst:899 -#: ../../content/developer/reference/views.rst:1197 -msgid "``class``" -msgstr "" - -#: ../../content/developer/reference/views.rst:826 -msgid "HTML class to set on the generated element, common field classes are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:828 -msgid "``oe_inline``" -msgstr "" - -#: ../../content/developer/reference/views.rst:829 -msgid "prevent the usual line break following fields" -msgstr "" - -#: ../../content/developer/reference/views.rst:830 -msgid "``oe_left``, ``oe_right``" -msgstr "" - -#: ../../content/developer/reference/views.rst:831 -msgid "floats_ the field to the corresponding direction" -msgstr "" - -#: ../../content/developer/reference/views.rst:832 -msgid "``oe_read_only``, ``oe_edit_only``" -msgstr "" - -#: ../../content/developer/reference/views.rst:833 -msgid "only displays the field in the corresponding form mode" -msgstr "" - -#: ../../content/developer/reference/views.rst:835 -msgid "``oe_avatar``" -msgstr "" - -#: ../../content/developer/reference/views.rst:835 -msgid "for image fields, displays images as \"avatar\" (square, 90x90 maximum size, some image decorations)" -msgstr "" - -#: ../../content/developer/reference/views.rst:838 -msgid "only displays the field for specific users" -msgstr "" - -#: ../../content/developer/reference/views.rst:845 -msgid "``on_change``" -msgstr "" - -#: ../../content/developer/reference/views.rst:840 -msgid "calls the specified method when this field's value is edited, can generate update other fields or display warnings for the user" -msgstr "" - -#: ../../content/developer/reference/views.rst:845 -msgid "Use :func:`odoo.api.onchange` on the model" -msgstr "" - -#: ../../content/developer/reference/views.rst:847 -#: ../../content/developer/reference/views.rst:903 -#: ../../content/developer/reference/views.rst:1466 -#: ../../content/developer/reference/views.rst:1518 -msgid "``attrs``" -msgstr "" - -#: ../../content/developer/reference/views.rst:848 -msgid "dynamic meta-parameters based on record values" -msgstr "" - -#: ../../content/developer/reference/views.rst:850 -msgid "for relational fields only, filters to apply when displaying existing records for selection" -msgstr "" - -#: ../../content/developer/reference/views.rst:853 -msgid "for relational fields only, context to pass when fetching possible values" -msgstr "" - -#: ../../content/developer/reference/views.rst:855 -msgid "``readonly``" -msgstr "" - -#: ../../content/developer/reference/views.rst:855 -msgid "display the field in both readonly and edit mode, but never make it editable" -msgstr "" - -#: ../../content/developer/reference/views.rst:858 -msgid "``required``" -msgstr "" - -#: ../../content/developer/reference/views.rst:858 -msgid "generates an error and prevents saving the record if the field doesn't have a value" -msgstr "" - -#: ../../content/developer/reference/views.rst:861 -#: ../../content/developer/reference/views.rst:1536 -msgid "``nolabel``" -msgstr "" - -#: ../../content/developer/reference/views.rst:861 -msgid "don't automatically display the field's label, only makes sense if the field is a direct child of a ``group`` element" -msgstr "" - -#: ../../content/developer/reference/views.rst:865 -msgid "``placeholder``" -msgstr "" - -#: ../../content/developer/reference/views.rst:864 -msgid "help message to display in *empty* fields. Can replace field labels in complex forms. *Should not* be an example of data as users are liable to confuse placeholder text with filled fields" -msgstr "" - -#: ../../content/developer/reference/views.rst:868 -msgid "for :class:`~odoo.fields.One2many`, display mode (view type) to use for the field's linked records. One of ``tree``, ``form``, ``kanban`` or ``graph``. The default is ``tree`` (a list display)" -msgstr "" - -#: ../../content/developer/reference/views.rst:871 -#: ../../content/developer/reference/views.rst:1980 -msgid "``help``" -msgstr "" - -#: ../../content/developer/reference/views.rst:872 -msgid "tooltip displayed for users when hovering the field or its label" -msgstr "" - -#: ../../content/developer/reference/views.rst:874 -#: ../../content/developer/webservices/upgrade.rst:541 -msgid "``filename``" -msgstr "" - -#: ../../content/developer/reference/views.rst:874 -msgid "for binary fields, name of the related field providing the name of the file" -msgstr "" - -#: ../../content/developer/reference/views.rst:877 -msgid "``password``" -msgstr "" - -#: ../../content/developer/reference/views.rst:877 -msgid "indicates that a :class:`~odoo.fields.Char` field stores a password and that its data shouldn't be displayed" -msgstr "" - -#: ../../content/developer/reference/views.rst:881 -msgid "``kanban_view_ref``" -msgstr "" - -#: ../../content/developer/reference/views.rst:880 -msgid "for opening specific kanban view when selecting records from m2o/m2m in mobile environment" -msgstr "" - -#: ../../content/developer/reference/views.rst:903 -msgid "``label``" -msgstr "" - -#: ../../content/developer/reference/views.rst:884 -msgid "when a ``field`` component isn't placed directly inside a ``group``, or when its ``nolabel`` attribute is set, the field's label isn't automatically displayed alongside its value. The ``label`` component is the manual alternative of displaying the label of a field. Possible attributes are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:894 -msgid "``for`` (mandatory)" -msgstr "" - -#: ../../content/developer/reference/views.rst:890 -msgid "the reference to the field associated with the label. Can be either the name of a field, or its id (``id`` attribute set on the ``field``). When there are several occurrences of the same field in the view, and there are several ``label`` components associated with these ``field`` nodes, those labels must have unique ``for`` attributes (in this case referencing the ``id`` attribute of the corresponding ``field`` nodes)." -msgstr "" - -#: ../../content/developer/reference/views.rst:897 -msgid "the label to display. Display the field's label (coming from the field definition in the model) by default." -msgstr "" - -#: ../../content/developer/reference/views.rst:900 -#: ../../content/developer/reference/views.rst:902 -msgid "same as for ``field`` component." -msgstr "" - -#: ../../content/developer/reference/views.rst:938 -msgid "classes for forms" -msgstr "" - -#: ../../content/developer/reference/views.rst:940 -msgid "widgets?" -msgstr "" - -#: ../../content/developer/reference/views.rst:951 -msgid "Gantt views appropriately display Gantt charts (for scheduling)." -msgstr "" - -#: ../../content/developer/reference/views.rst:953 -msgid "The root element of gantt views is ````, it has no children but can take the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:957 -msgid "name of the field providing the start datetime of the event for each record." -msgstr "" - -#: ../../content/developer/reference/views.rst:960 -msgid "``date_stop`` (required)" -msgstr "" - -#: ../../content/developer/reference/views.rst:960 -msgid "name of the field providing the end duration of the event for each record." -msgstr "" - -#: ../../content/developer/reference/views.rst:963 -msgid "name of the field used to color the pills according to its value" -msgstr "" - -#: ../../content/developer/reference/views.rst:978 -msgid "``{$name}`` can be one of the following `bootstrap contextual color`_ (``danger``, ``info``, ``secondary``, ``success`` or ``warning``)." -msgstr "" - -#: ../../content/developer/reference/views.rst:980 -#: ../../content/developer/reference/views.rst:1192 -msgid "``default_group_by``" -msgstr "" - -#: ../../content/developer/reference/views.rst:981 -msgid "name of a field to group tasks by" -msgstr "" - -#: ../../content/developer/reference/views.rst:982 -msgid "``consolidation``" -msgstr "" - -#: ../../content/developer/reference/views.rst:983 -msgid "field name to display consolidation value in record cell" -msgstr "" - -#: ../../content/developer/reference/views.rst:986 -msgid "``consolidation_max``" -msgstr "" - -#: ../../content/developer/reference/views.rst:985 -msgid "dictionnary with the \"group by\" field as key and the maximum consolidation value that can be reached before displaying the cell in red (e.g. ``{\"user_id\": 100}``)" -msgstr "" - -#: ../../content/developer/reference/views.rst:990 -msgid "``consolidation_exclude``" -msgstr "" - -#: ../../content/developer/reference/views.rst:989 -msgid "name of the field that describes if the task has to be excluded from the consolidation if set to true it displays a striped zone in the consolidation line" -msgstr "" - -#: ../../content/developer/reference/views.rst:1007 -msgid "``create``, ``cell_create``, ``edit``, ``delete``, ``plan``" -msgstr "" - -#: ../../content/developer/reference/views.rst:993 -msgid "allows *dis*\\ abling the corresponding action in the view by setting the corresponding attribute to ``false`` (default: ``true``)." -msgstr "" - -#: ../../content/developer/reference/views.rst:996 -msgid "``create``: If enabled, an ``Add`` button will be available in the control panel to create records." -msgstr "" - -#: ../../content/developer/reference/views.rst:998 -msgid "``cell_create``: If enabled and ``create`` enabled, a \"**+**\" button will be displayed while hovering on a time slot cell to create a new record on that slot." -msgstr "" - -#: ../../content/developer/reference/views.rst:1000 -msgid "``edit``: If enabled, the opened records will be in edit mode (thus editable)." -msgstr "" - -#: ../../content/developer/reference/views.rst:1001 -msgid "``plan``: If enabled and ``edit`` enabled, a \"magnifying glass\" button will be displayed on time slots to plan unassigned records into that time slot." -msgstr "" - -#: ../../content/developer/reference/views.rst:1006 -msgid "When you do not want to create records on the gantt view and the beginning and end dates are required on the model, the planning feature should be disabled because no record will ever be found." -msgstr "" - -#: ../../content/developer/reference/views.rst:1012 -msgid "``offset``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1010 -msgid "Depending on the scale, the number of units to add to today to compute the default period. Examples: An offset of +1 in default_scale week will open the gantt view for next week, and an offset of -2 in default_scale month will open the gantt view of 2 months ago." -msgstr "" - -#: ../../content/developer/reference/views.rst:1015 -msgid "``progress``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1015 -msgid "name of a field providing the completion percentage for the record's event, between 0 and 100" -msgstr "" - -#: ../../content/developer/reference/views.rst:1018 -msgid "title of the gantt view" -msgstr "" - -#: ../../content/developer/reference/views.rst:1043 -msgid "``precision``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1020 -msgid "JSON object specifying snapping precisions for the pills in each scale." -msgstr "" - -#: ../../content/developer/reference/views.rst:1022 -msgid "Possible values for scale ``day`` are (default: ``hour``):" -msgstr "" - -#: ../../content/developer/reference/views.rst:1024 -msgid "``hour``: records times snap to full hours (ex: 7:12 becomes 8:00)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1026 -msgid "``hour:half``: records times snap to half hours (ex: 7:12 becomes 7:30)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1028 -msgid "``hour:quarter``: records times snap to half hours (ex: 7:12 becomes 7:15)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1030 -msgid "Possible values for scale ``week`` are (default: ``day:half``):" -msgstr "" - -#: ../../content/developer/reference/views.rst:1032 -#: ../../content/developer/reference/views.rst:1038 -msgid "``day``: records times snap to full days (ex: 7:28 AM becomes 11:59:59 PM of the previous day, 10:32 PM becomes 12:00 PM of the current day)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1034 -#: ../../content/developer/reference/views.rst:1040 -msgid "``day:half``: records times snap to half hours (ex: 7:28 AM becomes 12:00 PM)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1036 -msgid "Possible values for scale ``month`` are (default: ``day:half``):" -msgstr "" - -#: ../../content/developer/reference/views.rst:1042 -msgid "Scale ``year`` always snap to full day." -msgstr "" - -#: ../../content/developer/reference/views.rst:1044 -msgid "Example of precision attribute: ``{\"day\": \"hour:quarter\", \"week\": \"day:half\", \"month\": \"day\"}``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1046 -msgid "``total_row``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1046 -msgid "boolean to control whether the row containing the total count of records should be displayed. (default: ``false``)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1049 -msgid "``collapse_first_level``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1049 -msgid "boolean to control whether it is possible to collapse each row if grouped by one field. (default: ``false``, the collapse starts when grouping by two fields)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1053 -msgid "``display_unavailability``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1052 -msgid "boolean to mark the dates returned by the ``gantt_unavailability`` function of the model as available inside the gantt view. Records can still be scheduled in them, but their unavailability is visually displayed. (default: ``false``)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1061 -msgid "``default_scale``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1056 -msgid "default scale when rendering the view. Possible values are (default: ``month``):" -msgstr "" - -#: ../../content/developer/reference/views.rst:1058 -msgid "``day``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1059 -msgid "``week``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1060 -msgid "``month``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1061 -msgid "``year``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1064 -msgid "comma-separated list of allowed scales for this view. By default, all scales are allowed. For possible scale values to use in this list, see ``default_scale``." -msgstr "" - -#: ../../content/developer/reference/views.rst:1068 -msgid "defines the :ref:`reference/qweb` template ``gantt-popover`` which is used when the user hovers over one of the records in the gantt view." -msgstr "" - -#: ../../content/developer/reference/views.rst:1071 -msgid "The gantt view uses mostly-standard :ref:`javascript qweb ` and provides the following context variables:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1075 -msgid "the current :js:class:`GanttRow`, can be used to fetch some meta-information. The ``getColor`` method to convert in a color integer is also available directly in the template context without using ``widget``." -msgstr "" - -#: ../../content/developer/reference/views.rst:1079 -msgid "``on_create`` If specified when clicking the add button on the view, instead of opening a generic dialog, launch a client action. this should hold the xmlid of the action (eg: ``on_create=\"%(my_module.my_wizard)d\"``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1084 -msgid "view to open when the user create or edit a record. Note that if this attribute is not set, the gantt view will fall back to the id of the form view in the current action, if any." -msgstr "" - -#: ../../content/developer/reference/views.rst:1090 -msgid "``dynamic_range``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1089 -msgid "if set to true, the gantt view will start at the first record, instead of starting at the beginning of the year/month/day." -msgstr "" - -#: ../../content/developer/reference/views.rst:1109 -msgid "``thumbnails``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1093 -msgid "This allows to display a thumbnail next to groups name if the group is a relationnal field. This expects a python dict which keys are the name of the field on the active model. Values are the names of the field holding the thumbnail on the related model." -msgstr "" - -#: ../../content/developer/reference/views.rst:1097 -msgid "Example: tasks have a field user_id that reference res.users. The res.users model has a field image that holds the avatar, then:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1109 -msgid "will display the users avatars next to their names when grouped by user_id." -msgstr "" - -#: ../../content/developer/reference/views.rst:1114 -msgid "Graph" -msgstr "" - -#: ../../content/developer/reference/views.rst:1116 -msgid "The graph view is used to visualize aggregations over a number of records or record groups. Its root element is ```` which can take the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1121 -msgid "one of ``bar`` (default), ``pie`` and ``line``, the type of graph to use" -msgstr "" - -#: ../../content/developer/reference/views.rst:1123 -msgid "``stacked``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1123 -msgid "only used for ``bar`` charts. If present and set to ``True``, stacks bars within a group" -msgstr "" - -#: ../../content/developer/reference/views.rst:1125 -#: ../../content/developer/reference/views.rst:1704 -msgid "``disable_linking``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1126 -msgid "set to ``True`` to prevent from redirecting clicks on graph to list view" -msgstr "" - -#: ../../content/developer/reference/views.rst:1130 -msgid "``order``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1128 -msgid "if set, x-axis values will be sorted by default according their measure with respect to the given order (``asc`` or ``desc``). Only used for ``bar`` and ``pie`` charts." -msgstr "" - -#: ../../content/developer/reference/views.rst:1132 -msgid "The only allowed element within a graph view is ``field`` which can have the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1136 -#: ../../content/developer/reference/views.rst:1722 -msgid "the name of a field to use in the view. If used for grouping (rather than aggregating)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1140 -msgid "``title`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1140 -msgid "string displayed on the top of the graph." -msgstr "" - -#: ../../content/developer/reference/views.rst:1143 -msgid "if true, the field will not appear either in the active measures nor in the selectable measures." -msgstr "" - -#: ../../content/developer/reference/views.rst:1147 -#: ../../content/developer/reference/views.rst:1730 -msgid "indicates whether the field should be used as a grouping criteria or as an aggregated value within a group. Possible values are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1151 -msgid "groups by the specified field. All graph types support at least one level of grouping, some may support more." -msgstr "" - -#: ../../content/developer/reference/views.rst:1153 -#: ../../content/developer/reference/views.rst:1735 -msgid "``col``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1154 -msgid "authorized in graph views but only used by pivot tables" -msgstr "" - -#: ../../content/developer/reference/views.rst:1156 -#: ../../content/developer/reference/views.rst:1738 -msgid "field to aggregate within a group" -msgstr "" - -#: ../../content/developer/reference/views.rst:1161 -#: ../../content/developer/reference/views.rst:1742 -msgid "``interval``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1159 -#: ../../content/developer/reference/views.rst:1740 -msgid "on date and datetime fields, groups by the specified interval (``day``, ``week``, ``month``, ``quarter`` or ``year``) instead of grouping on the specific datetime (fixed second resolution) or date (fixed day resolution)." -msgstr "" - -#: ../../content/developer/reference/views.rst:1163 -#: ../../content/developer/reference/views.rst:1749 -msgid "The measures are automatically generated from the model fields; only the aggregatable fields are used. Those measures are also alphabetically sorted on the string of the field." -msgstr "" - -#: ../../content/developer/reference/views.rst:1169 -msgid "graph view aggregations are performed on database content, non-stored function fields can not be used in graph views" -msgstr "" - -#: ../../content/developer/reference/views.rst:1177 -msgid "The kanban view is a `kanban board`_ visualisation: it displays records as \"cards\", halfway between a :ref:`list view ` and a non-editable :ref:`form view `. Records may be grouped in columns for use in workflow visualisation or manipulation (e.g. tasks or work-progress management), or ungrouped (used simply to visualize records)." -msgstr "" - -#: ../../content/developer/reference/views.rst:1183 -msgid "The kanban view will load and display a maximum of ten columns. Any column after that will be closed (but can still be opened by the user)." -msgstr "" - -#: ../../content/developer/reference/views.rst:1187 -msgid "The root element of the Kanban view is ````, it can use the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1191 -msgid "whether the kanban view should be grouped if no grouping is specified via the action or the current search. Should be the name of the field to group by when no grouping is otherwise specified" -msgstr "" - -#: ../../content/developer/reference/views.rst:1195 -#: ../../content/developer/reference/views.rst:1404 -#: ../../content/developer/reference/views.rst:1669 -#: ../../content/developer/reference/views.rst:1716 -msgid "``default_order``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1195 -msgid "cards sorting order used if the user has not already sorted the records (via the list view)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1198 -msgid "adds HTML classes to the root HTML element of the Kanban view" -msgstr "" - -#: ../../content/developer/reference/views.rst:1199 -msgid "``examples``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1200 -msgid "if set to a key in the `KanbanExamplesRegistry`_, examples on column setups will be available in the grouped kanban view. `Here `_ is an example of how to define those setups." -msgstr "" - -#: ../../content/developer/reference/views.rst:1201 -msgid "``group_create``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1202 -msgid "whether the \"Add a new column\" bar is visible or not. Default: true." -msgstr "" - -#: ../../content/developer/reference/views.rst:1203 -msgid "``group_delete``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1204 -msgid "whether groups can be deleted via the context menu. Default: true." -msgstr "" - -#: ../../content/developer/reference/views.rst:1205 -msgid "``group_edit``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1206 -msgid "whether groups can be edited via the context menu. Default: true." -msgstr "" - -#: ../../content/developer/reference/views.rst:1208 -msgid "``archivable``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1208 -msgid "whether records belonging to a column can be archived / restored if an ``active`` field is defined on the model. Default: true." -msgstr "" - -#: ../../content/developer/reference/views.rst:1212 -msgid "``quick_create``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1211 -msgid "whether it should be possible to create records without switching to the form view. By default, ``quick_create`` is enabled when the Kanban view is grouped by many2one, selection, char or boolean fields, and disabled when not." -msgstr "" - -#: ../../content/developer/reference/views.rst:1214 -msgid "``quick_create_view``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1215 -msgid "``form`` view reference, specifying the view used for records quick creation." -msgstr "" - -#: ../../content/developer/reference/views.rst:1219 -msgid "``records_draggable``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1217 -msgid "whether it should be possible to drag records when kanban is grouped. Default: true." -msgstr "" - -#: ../../content/developer/reference/views.rst:1219 -msgid "Set to ``true`` to always enable it, and to ``false`` to always disable it." -msgstr "" - -#: ../../content/developer/reference/views.rst:1221 -msgid "VFE missing information on on_create attribute of kanban views." -msgstr "" - -#: ../../content/developer/reference/views.rst:1226 -msgid "declares fields to use in kanban *logic*. If the field is simply displayed in the kanban view, it does not need to be pre-declared." -msgstr "" - -#: ../../content/developer/reference/views.rst:1250 -#: ../../content/developer/reference/views.rst:1505 -msgid "``progressbar``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1235 -msgid "declares a progressbar element to put on top of kanban columns." -msgstr "" - -#: ../../content/developer/reference/views.rst:1241 -msgid "``field`` (required)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1240 -msgid "the name of the field whose values are used to subgroup column's records in the progressbar" -msgstr "" - -#: ../../content/developer/reference/views.rst:1245 -msgid "``colors`` (required)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1244 -msgid "JSON mapping the above field values to either \"danger\", \"warning\", \"success\" or \"muted\" colors" -msgstr "" - -#: ../../content/developer/reference/views.rst:1250 -msgid "``sum_field`` (optional)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1248 -msgid "the name of the field whose column's records' values will be summed and displayed next to the progressbar (if omitted, displays the total number of records)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1253 -msgid "defines a list of :ref:`reference/qweb` templates. Cards definition may be split into multiple templates for clarity, but kanban views *must* define at least one root template ``kanban-box``, which will be rendered once for each record." -msgstr "" - -#: ../../content/developer/reference/views.rst:1258 -msgid "The kanban view uses mostly-standard :ref:`javascript qweb ` and provides the following context variables:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1262 -msgid "the current :js:class:`KanbanRecord`, can be used to fetch some meta-information. These methods are also available directly in the template context and don't need to be accessed via ``widget``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1266 -msgid "an object with all the requested fields as its attributes. Each field has two attributes ``value`` and ``raw_value``, the former is formatted according to current user parameters, the latter is the direct value from a :meth:`~odoo.models.Model.read` (except for date and datetime fields that are `formatted according to user's locale `_)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1273 -msgid "the current context, coming from the action, and the one2many or many2many field in the case of a Kanban view embedded in a Form view" -msgstr "" - -#: ../../content/developer/reference/views.rst:1275 -msgid "``user_context``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1277 -msgid "``read_only_mode``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1319 -msgid "``selection_mode``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1280 -msgid "set to true when kanban view is opened in mobile environment from m2o/m2m field for selecting records." -msgstr "" - -#: ../../content/developer/reference/views.rst:1283 -msgid "clicking on m2o/m2m field in mobile environment opens kanban view" -msgstr "" - -#: ../../content/developer/reference/views.rst:0 -msgid "buttons and fields" -msgstr "" - -#: ../../content/developer/reference/views.rst:1288 -msgid "While most of the Kanban templates are standard :ref:`reference/qweb`, the Kanban view processes ``field``, ``button`` and ``a`` elements specially:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1291 -msgid "by default fields are replaced by their formatted value, unless the ``widget`` attribute is specified, in which case their rendering and behavior depends on the corresponding widget. Possible values are (among others):" -msgstr "" - -#: ../../content/developer/reference/views.rst:1298 -#: ../../content/developer/reference/views.rst:1509 -msgid "``handle``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1297 -msgid "for ``sequence`` (or ``integer``) fields by which records are sorted, allows to drag&drop records to reorder them." -msgstr "" - -#: ../../content/developer/reference/views.rst:1300 -msgid "list widgets?" -msgstr "" - -#: ../../content/developer/reference/views.rst:1302 -msgid "buttons and links with a ``type`` attribute become perform Odoo-related operations rather than their standard HTML function. Possible types are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1307 -msgid "``action``, ``object``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1306 -msgid "standard behavior for :ref:`Odoo buttons `, most attributes relevant to standard Odoo buttons can be used." -msgstr "" - -#: ../../content/developer/reference/views.rst:1309 -msgid "``open``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1310 -msgid "opens the card's record in the form view in read-only mode" -msgstr "" - -#: ../../content/developer/reference/views.rst:1311 -msgid "``edit``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1312 -msgid "opens the card's record in the form view in editable mode" -msgstr "" - -#: ../../content/developer/reference/views.rst:1314 -msgid "deletes the card's record and removes the card" -msgstr "" - -#: ../../content/developer/reference/views.rst:1318 -msgid "kanban-specific CSS" -msgstr "" - -#: ../../content/developer/reference/views.rst:1319 -msgid "kanban structures/widgets (vignette, details, ...)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1321 -msgid "If you need to extend the Kanban view, see :js:class::`the JS API `." -msgstr "" - -#: ../../content/developer/reference/views.rst:1326 -msgid "Calendar views display records as events in a daily, weekly or monthly calendar. Their root element is ````. Available attributes on the calendar view are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1360 -msgid "Default display mode when loading the calendar. Possible attributes are: ``day``, ``week``, ``month``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1363 -msgid "``create``, ``delete``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1363 -#: ../../content/developer/reference/views.rst:1414 -msgid "allows *dis*\\ abling the corresponding action in the view by setting the corresponding attribute to ``false``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1372 -msgid "List" -msgstr "" - -#: ../../content/developer/reference/views.rst:1374 -msgid "The root element of list views is ````\\ [#treehistory]_. The list view's root can have the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1378 -msgid "by default, selecting a list view's row opens the corresponding :ref:`form view `. The ``editable`` attributes makes the list view itself editable in-place." -msgstr "" - -#: ../../content/developer/reference/views.rst:1382 -msgid "Valid values are ``top`` and ``bottom``, making *new* records appear respectively at the top or bottom of the list." -msgstr "" - -#: ../../content/developer/reference/views.rst:1385 -msgid "The architecture for the inline :ref:`form view ` is derived from the list view. Most attributes valid on a :ref:`form view `'s fields and buttons are thus accepted by list views although they may not have any meaning if the list view is non-editable" -msgstr "" - -#: ../../content/developer/reference/views.rst:1391 -msgid "if the ``edit`` attribute is set to ``false``, the ``editable`` option will be ignored." -msgstr "" - -#: ../../content/developer/reference/views.rst:1395 -msgid "``multi_edit``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1394 -msgid "editable or not editable list can activate the multi-editing feature by defining the `multi_edit=1`" -msgstr "" - -#: ../../content/developer/reference/views.rst:1398 -msgid "overrides the ordering of the view, replacing the model's order (:attr:`~odoo.models.BaseModel._order` model attribute). The value is a comma-separated list of fields, postfixed by ``desc`` to sort in reverse order:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1410 -#: ../../content/developer/reference/views.rst:1531 -msgid "``{$name}`` can be ``bf`` (``font-weight: bold``), ``it`` (``font-style: italic``), or any `bootstrap contextual color`_ (``danger``, ``info``, ``muted``, ``primary``, ``success`` or ``warning``)." -msgstr "" - -#: ../../content/developer/reference/views.rst:1414 -msgid "``create``, ``edit``, ``delete``, ``duplicate``, ``import``, ``export_xlsx``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1416 -#: ../../content/developer/reference/views.rst:1685 -msgid "``limit``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1417 -msgid "the default size of a page. It must be a positive integer" -msgstr "" - -#: ../../content/developer/reference/views.rst:1419 -msgid "``groups_limit``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1419 -msgid "when the list view is grouped, the default number of groups of a page. It must be a position integer" -msgstr "" - -#: ../../content/developer/reference/views.rst:1423 -msgid "``expand``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1422 -msgid "when the list view is grouped, automatically open the first level of groups if set to true (default: false)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1425 -msgid "Possible children elements of the list view are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1430 -msgid "displays a button in a list cell" -msgstr "" - -#: ../../content/developer/reference/views.rst:1432 -msgid "``icon``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1433 -msgid "icon to use to display the button" -msgstr "" - -#: ../../content/developer/reference/views.rst:1435 -msgid "if there is no ``icon``, the button's text" -msgstr "" - -#: ../../content/developer/reference/views.rst:1436 -msgid "if there is an ``icon``, ``alt`` text for the icon" -msgstr "" - -#: ../../content/developer/reference/views.rst:1438 -msgid "type of button, indicates how it clicking it affects Odoo:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1447 -msgid "``object``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1441 -msgid "call a method on the list's model. The button's ``name`` is the method, which is called with the current row's record id and the current context." -msgstr "" - -#: ../../content/developer/reference/views.rst:1450 -msgid "load an execute an ``ir.actions``, the button's ``name`` is the database id of the action. The context is expanded with the list's model (as ``active_model``), the current row's record (``active_id``) and all the records currently loaded in the list (``active_ids``, may be just a subset of the database records matching the current search)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1457 -#: ../../content/developer/reference/views.rst:1459 -msgid "see ``type``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1461 -msgid "dynamic attributes based on record values." -msgstr "" - -#: ../../content/developer/reference/views.rst:1463 -msgid "A mapping of attributes to domains, domains are evaluated in the context of the current row's record, if ``True`` the corresponding attribute is set on the cell." -msgstr "" - -#: ../../content/developer/reference/views.rst:1467 -msgid "Possible attribute is ``invisible`` (hides the button)." -msgstr "" - -#: ../../content/developer/reference/views.rst:1478 -msgid "``states``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1469 -msgid "shorthand for ``invisible`` ``attrs``: a list of states, comma separated, requires that the model has a ``state`` field and that it is used in the view." -msgstr "" - -#: ../../content/developer/reference/views.rst:1473 -msgid "Makes the button ``invisible`` if the record is *not* in one of the listed states" -msgstr "" - -#: ../../content/developer/reference/views.rst:1478 -msgid "Using ``states`` in combination with ``attrs`` may lead to unexpected results as domains are combined with a logical AND." -msgstr "" - -#: ../../content/developer/reference/views.rst:1481 -msgid "merged into the view's context when performing the button's Odoo call" -msgstr "" - -#: ../../content/developer/reference/views.rst:1483 -msgid "declared but unused: help" -msgstr "" - -#: ../../content/developer/reference/views.rst:1486 -msgid "defines a column where the corresponding field should be displayed for each record. Can use the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1490 -msgid "the name of the field to display in the current model. A given name can only be used once per view" -msgstr "" - -#: ../../content/developer/reference/views.rst:1493 -msgid "the title of the field's column (by default, uses the ``string`` of the model's field)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1497 -#: ../../content/developer/reference/views.rst:1747 -msgid "``invisible``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1496 -msgid "fetches and stores the field, but doesn't display the column in the table. Necessary for fields which shouldn't be displayed but are used by e.g. ``@colors``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1500 -msgid "lists the groups which should be able to see the field" -msgstr "" - -#: ../../content/developer/reference/views.rst:1502 -msgid "alternate representations for a field's display. Possible list view values are (among others):" -msgstr "" - -#: ../../content/developer/reference/views.rst:1506 -msgid "displays ``float`` fields as a progress bar." -msgstr "" - -#: ../../content/developer/reference/views.rst:1508 -msgid "for ``sequence`` (or ``integer``) fields by which records are sorted, instead of displaying the field's value just displays a drag&drop icon to reorder records." -msgstr "" - -#: ../../content/developer/reference/views.rst:1514 -msgid "``sum``, ``avg``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1512 -msgid "displays the corresponding aggregate at the bottom of the column. The aggregation is only computed on *currently displayed* records. The aggregation operation must match the corresponding field's ``group_operator``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1517 -msgid "dynamic attributes based on record values. Only effects the current field, so e.g. ``invisible`` will hide the field but leave the same field of other records visible, it will not hide the column itself" -msgstr "" - -#: ../../content/developer/reference/views.rst:1525 -msgid "``width`` (for ``editable``)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1521 -msgid "when there is no data in the list, the width of a column can be forced by setting this attribute. The value can be an absolute width (e.g. '100px'), or a relative weight (e.g. '3', meaning that this column will be 3 times larger than the others). Note that when there are records in the list, we let the browser automatically adapt the column's widths according to their content, and this attribute is thus ignored." -msgstr "" - -#: ../../content/developer/reference/views.rst:1528 -msgid "allow changing the style of a cell's text based on the corresponding record's attributes." -msgstr "" - -#: ../../content/developer/reference/views.rst:1535 -msgid "if set to \"1\", the column header will remain empty. Also, the column won't be sortable." -msgstr "" - -#: ../../content/developer/reference/views.rst:1540 -msgid "if the list view is ``editable``, any field attribute from the :ref:`form view ` is also valid and will be used when setting up the inline form view." -msgstr "" - -#: ../../content/developer/reference/views.rst:1546 -msgid "In case of list sub-views (One2many/Many2many display in a form view), The attribute ``column_invisible`` can be useful to hide a column depending on the parent object." -msgstr "" - -#: ../../content/developer/reference/views.rst:1554 -msgid "When a list view is grouped, numeric fields are aggregated and displayed for each group. Also, if there are too many records in a group, a pager will appear on the right of the group row. For this reason, it is not a good practice to have a numeric field in the last column, when the list view is in a situation where it can be grouped (it is however fine for x2manys field in a form view: they cannot be grouped)." -msgstr "" - -#: ../../content/developer/reference/views.rst:1581 -msgid "``groupby``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1563 -msgid "defines custom headers (with buttons) for the current view when grouping records on many2one fields. It is also possible to add `field`, inside the `groupby` which can be used for modifiers. These fields thus belong on the many2one comodel. These extra fields will be fetched in batch." -msgstr "" - -#: ../../content/developer/reference/views.rst:1569 -msgid "the name of a many2one field (on the current model). Custom header will be displayed when grouping the view on this field name." -msgstr "" - -#: ../../content/developer/reference/views.rst:1581 -msgid "A special button (`type=\"edit\"`) can be defined to open the many2one form view." -msgstr "" - -#: ../../content/developer/reference/views.rst:1631 -msgid "``control``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1584 -msgid "defines custom controls for the current view." -msgstr "" - -#: ../../content/developer/reference/views.rst:1586 -msgid "This makes sense if the parent ``tree`` view is inside a One2many field." -msgstr "" - -#: ../../content/developer/reference/views.rst:1588 -msgid "Does not support any attribute, but can have children:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1591 -msgid "adds a button to create a new element on the current list." -msgstr "" - -#: ../../content/developer/reference/views.rst:1593 -msgid "If any ``create`` is defined, it will overwrite the default \"add a line\" button." -msgstr "" - -#: ../../content/developer/reference/views.rst:1596 -msgid "The following attributes are supported:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1599 -#: ../../content/developer/reference/views.rst:1888 -msgid "``string`` (required)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1599 -msgid "The text displayed on the button." -msgstr "" - -#: ../../content/developer/reference/views.rst:1602 -msgid "This context will be merged into the existing context when retrieving the default value of the new record." -msgstr "" - -#: ../../content/developer/reference/views.rst:1605 -msgid "For example it can be used to override default values." -msgstr "" - -#: ../../content/developer/reference/views.rst:1608 -msgid "The following example will override the default \"add a line\" button by replacing it with 3 new buttons: \"Add a product\", \"Add a section\" and \"Add a note\"." -msgstr "" - -#: ../../content/developer/reference/views.rst:1612 -msgid "\"Add a product\" will set the field 'display_type' to its default value." -msgstr "" - -#: ../../content/developer/reference/views.rst:1614 -msgid "The two other buttons will set the field 'display_type' to be respectively 'line_section' and 'line_note'." -msgstr "" - -#: ../../content/developer/reference/views.rst:1633 -msgid "for historical reasons, it has its origin in tree-type views later repurposed to a more table/list-type display" -msgstr "" - -#: ../../content/developer/reference/views.rst:1645 -msgid "This view is able to display records on a map and the routes between them. The record are represented by pins. It also allows the visualization of fields from the model in a popup tied to the record's pin." -msgstr "" - -#: ../../content/developer/reference/views.rst:1649 -msgid "The model on which the view is applied should contains a res.partner many2one since the view relies on the res.partner's address and coordinates fields to localize the records." -msgstr "" - -#: ../../content/developer/reference/views.rst:1654 -msgid "Api" -msgstr "" - -#: ../../content/developer/reference/views.rst:1656 -msgid "The view uses location data platforms' api to fetch the tiles (the map's background), do the geoforwarding (converting addresses to a set of coordinates) and fetch the routes. The view implements two api, the default one, openstreet map is able to fetch `tiles`_ and do `geoforwarding`_. This api does not require a token. As soon as a valid `MapBox`_ token is provided in the general settings the view switches to the Mapbox api. This api is faster and allows the computation of routes. The token are available by `signing up`_ to MapBox" -msgstr "" - -#: ../../content/developer/reference/views.rst:1665 -msgid "The view's root element is ```` multiple attributes are allowed" -msgstr "" - -#: ../../content/developer/reference/views.rst:1667 -msgid "``res_partner``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1668 -msgid "Contains the res.partner many2one. If not provided the view will resort to create an empty map." -msgstr "" - -#: ../../content/developer/reference/views.rst:1670 -msgid "If a field is provided the view will override the model's default order. The field must be part of the model on which the view is applied not from res.partner" -msgstr "" - -#: ../../content/developer/reference/views.rst:1671 -msgid "``routing``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1672 -msgid "if ``true`` the routes between the records will be shown. The view still needs a valid MapBox token and at least two located records. (i.e the records has a res.partner many2one and the partner has a address or valid coordinates)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1673 -msgid "``hide_name``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1674 -msgid "if ``true`` hide a name from the marker's popup (default: false)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1676 -msgid "``hide_address``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1676 -msgid "if ``true`` hide a address from the marker's popup (default: false)" -msgstr "" - -#: ../../content/developer/reference/views.rst:1678 -msgid "The ```` element can contain multiple ```` elements. Each ```` element will be interpreted as a line in the marker's popup. The field's attributes are the following:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1681 -msgid "The field to display." -msgstr "" - -#: ../../content/developer/reference/views.rst:1683 -msgid "This string will be displayed before the field's content. It Can be used as a description." -msgstr "" - -#: ../../content/developer/reference/views.rst:1685 -msgid "The size of a page (default: 80). It must be a positive integer." -msgstr "" - -#: ../../content/developer/reference/views.rst:1687 -msgid "No attribute or element is mandatory but as stated above if no res.partner many2one is provided the view won't be able to locate records." -msgstr "" - -#: ../../content/developer/reference/views.rst:1694 -msgid "For example here is a map:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1699 -msgid "Pivot" -msgstr "" - -#: ../../content/developer/reference/views.rst:1701 -msgid "The pivot view is used to visualize aggregations as a `pivot table`_. Its root element is ```` which can take the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1705 -msgid "Set to ``True`` to remove table cell's links to list view." -msgstr "" - -#: ../../content/developer/reference/views.rst:1706 -msgid "``display_quantity``" -msgstr "" - -#: ../../content/developer/reference/views.rst:1707 -msgid "Set to ``true`` to display the Quantity column by default." -msgstr "" - -#: ../../content/developer/reference/views.rst:1709 -msgid "The name of the measure and the order (asc or desc) to use as default order in the view." -msgstr "" - -#: ../../content/developer/reference/views.rst:1718 -msgid "The only allowed element within a pivot view is ``field`` which can have the following attributes:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1726 -msgid "the name that will be used to display the field in the pivot view, overrides the default python String attribute of the field." -msgstr "" - -#: ../../content/developer/reference/views.rst:1734 -msgid "groups by the specified field, each group gets its own row." -msgstr "" - -#: ../../content/developer/reference/views.rst:1736 -msgid "creates column-wise groups" -msgstr "" - -#: ../../content/developer/reference/views.rst:1755 -msgid "like the graph view, the pivot aggregates data on database content which means that non-stored function fields can not be used in pivot views" -msgstr "" - -#: ../../content/developer/reference/views.rst:1759 -msgid "In Pivot view a ``field`` can have a ``widget`` attribute to dictate its format. The widget should be a field formatter, of which the most interesting are ``date``, ``datetime``, ``float_time``, and ``monetary``." -msgstr "" - -#: ../../content/developer/reference/views.rst:1763 -msgid "For instance a timesheet pivot view could be defined as::" -msgstr "" - -#: ../../content/developer/reference/views.rst:1776 -msgid "QWeb views are standard :ref:`reference/qweb` templates inside a view's ``arch``. They don't have a specific root element. Because QWeb views don't have a specific root element, their type must be specified explicitly (it can not be inferred from the root element of the ``arch`` field)." -msgstr "" - -#: ../../content/developer/reference/views.rst:1781 -msgid "QWeb views have two use cases:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1783 -msgid "they can be used as frontend templates, in which case :ref:`reference/data/template` should be used as a shortcut." -msgstr "" - -#: ../../content/developer/reference/views.rst:1785 -msgid "they can be used as actual qweb views (opened inside an action), in which case they should be defined as regular view with an explicit ``type`` (it can not be inferred) and a model." -msgstr "" - -#: ../../content/developer/reference/views.rst:1789 -msgid "The main additions of qweb-as-view to the basic qweb-as-template are:" -msgstr "" - -#: ../../content/developer/reference/views.rst:1791 -msgid "qweb-as-view has a special case for a ``