[I18N] *: export saas-16.1 translations
closes odoo/documentation#7075
X-original-commit: a4f0e6b9b8
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-11-30 14:44+0000\n"
|
||||
"POT-Creation-Date: 2023-12-21 13:43+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@@ -548,260 +548,276 @@ msgstr ""
|
||||
msgid "Odoo static files are located in each module's :file:`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:443
|
||||
msgid "Say Odoo has been installed via the **debian packages** for Community and Enterprise and the :option:`--addons-path <odoo-bin --addons-path>` is ``'/usr/lib/python3/dist-packages/odoo/addons'``."
|
||||
#: ../../content/administration/install/deploy.rst:442
|
||||
msgid "It is recommended to set the ``Content-Security-Policy: default-src 'none'`` header on all images delivered by the web server. It is not strictly necessary as users cannot modify/inject content inside of modules' :file:`static/` folder and existing images are final (they do not fetch new resources by themselves). However, it is good practice."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:446
|
||||
#: ../../content/administration/install/deploy.rst:468
|
||||
msgid "Using the above NGINX (https) configuration, the following location block should be added to serve static files via NGINX."
|
||||
#: ../../content/administration/install/deploy.rst:447
|
||||
msgid "Using the above NGINX (https) configuration, the following ``map`` and ``location`` blocks should be added to serve static files via NGINX."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:463
|
||||
msgid "Say Odoo has been installed via the **source**. The two git repositories for Community and Enterprise have been cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise` respectively and the :option:`--addons-path <odoo-bin --addons-path>` is ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``."
|
||||
#: ../../content/administration/install/deploy.rst:474
|
||||
msgid "The actual ``root`` and ``try_files`` directives are dependant on your installation, specifically on your :option:`--addons-path <odoo-bin --addons-path>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:485
|
||||
msgid "The actual NGINX configuration you need is highly dependent on your own installation. The two above snippets only highlight two possible configurations and may not be used as-is."
|
||||
#: ../../content/administration/install/deploy.rst:481
|
||||
msgid "Debian package"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:489
|
||||
msgid "Serving attachments"
|
||||
#: ../../content/administration/install/deploy.rst:483
|
||||
msgid "Say Odoo has been installed via the **debian packages** for Community and Enterprise, and that the :option:`--addons-path <odoo-bin --addons-path>` is ``'/usr/lib/python3/dist-packages/odoo/addons'``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:491
|
||||
msgid "Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be directly accessed via a static web server as accessing them requires multiple lookups in the database to determine where the files are stored and whether the current user can access them or not."
|
||||
#: ../../content/administration/install/deploy.rst:487
|
||||
#: ../../content/administration/install/deploy.rst:501
|
||||
msgid "The ``root`` and ``try_files`` should be:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:494
|
||||
msgid "Git sources"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:496
|
||||
msgid "Say Odoo has been installed via the **sources**, that both the Community and Enterprise git repositories were cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-path <odoo-bin --addons-path>` is ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:509
|
||||
msgid "Serving attachments"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:511
|
||||
msgid "Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be directly accessed via a static web server as accessing them requires multiple lookups in the database to determine where the files are stored and whether the current user can access them or not."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:516
|
||||
msgid "Nevertheless, once the file has been located and the access rights verified by Odoo, it is a good idea to serve the file using the static web server instead of Odoo. For Odoo to delegate serving files to the static web server, the `X-Sendfile <https://tn123.org/mod_xsendfile/>`_ (apache) or `X-Accel <https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/>`_ (nginx) extensions must be enabled and configured on the static web server. Once it is set up, start Odoo with the :option:`--x-sendfile <odoo-bin --x-sendfile>` CLI flag (this unique flag is used for both X-Sendfile and X-Accel)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:506
|
||||
#: ../../content/administration/install/deploy.rst:526
|
||||
msgid "The X-Sendfile extension for apache (and compatible web servers) does not require any supplementary configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:508
|
||||
#: ../../content/administration/install/deploy.rst:528
|
||||
msgid "The X-Accel extension for NGINX **does** require the following additionnal configuration:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:517
|
||||
#: ../../content/administration/install/deploy.rst:537
|
||||
msgid "In case you don't know what is the path to your filestore, start Odoo with the :option:`--x-sendfile <odoo-bin --x-sendfile>` option and navigate to the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via NGINX). This logs a warnings, the message contains the configuration you need."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:526
|
||||
#: ../../content/administration/install/deploy.rst:546
|
||||
msgid "Security"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:528
|
||||
#: ../../content/administration/install/deploy.rst:548
|
||||
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:532
|
||||
#: ../../content/administration/install/deploy.rst:552
|
||||
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:538
|
||||
#: ../../content/administration/install/deploy.rst:558
|
||||
msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:541
|
||||
#: ../../content/administration/install/deploy.rst:561
|
||||
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:544
|
||||
#: ../../content/administration/install/deploy.rst:564
|
||||
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:549
|
||||
#: ../../content/administration/install/deploy.rst:569
|
||||
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:553
|
||||
#: ../../content/administration/install/deploy.rst:573
|
||||
msgid "Use appropriate database filters ( :option:`--db-filter <odoo-bin --db-filter>`) to restrict the visibility of your databases according to the hostname. See :ref:`db_filter`. You may also use :option:`-d <odoo-bin -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:560
|
||||
#: ../../content/administration/install/deploy.rst:580
|
||||
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 <odoo-bin --no-database-list>` command-line option)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:566
|
||||
#: ../../content/administration/install/deploy.rst:586
|
||||
msgid "Make sure the PostgreSQL user (:option:`--db_user <odoo-bin --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:571
|
||||
#: ../../content/administration/install/deploy.rst:591
|
||||
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:575
|
||||
#: ../../content/administration/install/deploy.rst:595
|
||||
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:578
|
||||
#: ../../content/administration/install/deploy.rst:598
|
||||
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 <odoo-bin --proxy-mode>` option. See also :ref:`https_proxy`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:585
|
||||
#: ../../content/administration/install/deploy.rst:605
|
||||
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:591
|
||||
#: ../../content/administration/install/deploy.rst:611
|
||||
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:595
|
||||
#: ../../content/administration/install/deploy.rst:615
|
||||
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:599
|
||||
#: ../../content/administration/install/deploy.rst:619
|
||||
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:603
|
||||
#: ../../content/administration/install/deploy.rst:623
|
||||
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 <http://0pointer.net/blog/ip-accounting-and-access-lists-with-systemd.html>`_ may also be useful to implement per-process network access control."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:614
|
||||
#: ../../content/administration/install/deploy.rst:634
|
||||
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:625
|
||||
#: ../../content/administration/install/deploy.rst:645
|
||||
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:628
|
||||
#: ../../content/administration/install/deploy.rst:648
|
||||
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:631
|
||||
#: ../../content/administration/install/deploy.rst:651
|
||||
msgid "Deploying Odoo on Linux is strongly recommended over Windows. Should you choose nevertheless to deploy on a Windows platform, a thorough security hardening review of the server should be conducted and is outside of the scope of this guide."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:639
|
||||
#: ../../content/administration/install/deploy.rst:659
|
||||
msgid "Blocking Brute Force Attacks"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:641
|
||||
#: ../../content/administration/install/deploy.rst:661
|
||||
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:645
|
||||
#: ../../content/administration/install/deploy.rst:665
|
||||
msgid "The log entries will have the following form."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:647
|
||||
#: ../../content/administration/install/deploy.rst:667
|
||||
msgid "Failed login::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:651
|
||||
#: ../../content/administration/install/deploy.rst:671
|
||||
msgid "Successful login::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:656
|
||||
#: ../../content/administration/install/deploy.rst:676
|
||||
msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:658
|
||||
#: ../../content/administration/install/deploy.rst:678
|
||||
msgid "For example, the following fail2ban filter definition should match a failed login::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:665
|
||||
#: ../../content/administration/install/deploy.rst:685
|
||||
msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:667
|
||||
#: ../../content/administration/install/deploy.rst:687
|
||||
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:681
|
||||
#: ../../content/administration/install/deploy.rst:701
|
||||
msgid "Database Manager Security"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:683
|
||||
#: ../../content/administration/install/deploy.rst:703
|
||||
msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:685
|
||||
#: ../../content/administration/install/deploy.rst:705
|
||||
msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:688
|
||||
#: ../../content/administration/install/deploy.rst:708
|
||||
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:694
|
||||
#: ../../content/administration/install/deploy.rst:714
|
||||
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:700
|
||||
#: ../../content/administration/install/deploy.rst:720
|
||||
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:703
|
||||
#: ../../content/administration/install/deploy.rst:723
|
||||
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:708
|
||||
#: ../../content/administration/install/deploy.rst:728
|
||||
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:712
|
||||
#: ../../content/administration/install/deploy.rst:732
|
||||
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:716
|
||||
#: ../../content/administration/install/deploy.rst:736
|
||||
msgid "It should be stored securely, and should be generated randomly e.g."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:722
|
||||
#: ../../content/administration/install/deploy.rst:742
|
||||
msgid "which will generate a 32 characters pseudorandom printable string."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:725
|
||||
#: ../../content/administration/install/deploy.rst:745
|
||||
msgid "Supported Browsers"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:727
|
||||
#: ../../content/administration/install/deploy.rst:747
|
||||
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:730
|
||||
#: ../../content/administration/install/deploy.rst:750
|
||||
msgid "Here are the supported browsers:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:732
|
||||
#: ../../content/administration/install/deploy.rst:752
|
||||
msgid "Google Chrome"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:733
|
||||
#: ../../content/administration/install/deploy.rst:753
|
||||
msgid "Mozilla Firefox"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:734
|
||||
#: ../../content/administration/install/deploy.rst:754
|
||||
msgid "Microsoft Edge"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:735
|
||||
#: ../../content/administration/install/deploy.rst:755
|
||||
msgid "Apple Safari"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:737
|
||||
#: ../../content/administration/install/deploy.rst:757
|
||||
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:742
|
||||
#: ../../content/administration/install/deploy.rst:762
|
||||
msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:745
|
||||
#: ../../content/administration/install/deploy.rst:765
|
||||
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:748
|
||||
#: ../../content/administration/install/deploy.rst:768
|
||||
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:752
|
||||
#: ../../content/administration/install/deploy.rst:772
|
||||
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 ""
|
||||
|
||||
@@ -976,7 +992,7 @@ msgstr ""
|
||||
|
||||
#: ../../content/administration/install/packages.rst:57
|
||||
#: ../../content/administration/install/source.rst:416
|
||||
msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.5 <https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.5>`_ for it to support headers and footers. Check out the `wkhtmltopdf wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more details on the various versions."
|
||||
msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.6 <https://github.com/wkhtmltopdf/packaging/releases/tag/0.12.6.1-3>`_ for it to support headers and footers. Check out the `wkhtmltopdf wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more details on the various versions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/packages.rst:63
|
||||
@@ -3136,11 +3152,11 @@ msgid "To remove users, select them and click :guilabel:`Remove`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:132
|
||||
msgid ":doc:`../../applications/general/users/manage_users`"
|
||||
msgid ":doc:`/applications/general/users/manage_users`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:133
|
||||
msgid ":doc:`../../applications/general/users/delete_account`"
|
||||
msgid ":doc:`/applications/general/users/odoo_account`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/on_premise.rst:3
|
||||
|
||||
Reference in New Issue
Block a user