[I18N] *: export 16.0 source terms
closes odoo/documentation#3830 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux
parent
fe7aa39bc1
commit
a85211745b
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 16.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-03-03 17:52+0000\n"
|
||||
"POT-Creation-Date: 2023-03-16 11:06+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"
|
||||
@ -33,71 +33,115 @@ msgid "Install"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:3
|
||||
msgid "Setting up a Content Delivery Network (CDN)"
|
||||
msgid "Set up a content delivery network (CDN)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:8
|
||||
msgid "Deploying with KeyCDN_"
|
||||
msgid "Deploying with KeyCDN"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:12
|
||||
msgid "This document will guide you through the setup of a KeyCDN_ account with your Odoo powered website."
|
||||
#: ../../content/administration/install/cdn.rst:10
|
||||
msgid "A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, is a geographically distributed network of servers that provides high speed internet content. The :abbr:`CDN (Content Delivery Network)` provides quick, high-quality content delivery for content-heavy websites."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:16
|
||||
msgid "Step 1: Create a pull zone in the KeyCDN dashboard"
|
||||
#: ../../content/administration/install/cdn.rst:14
|
||||
msgid "This document will guide you through the setup of a KeyCDN_ account with an Odoo powered website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:21
|
||||
msgid "When creating the zone, enable the CORS option in the :guilabel:`advanced features` submenu. (more on that later)"
|
||||
#: ../../content/administration/install/cdn.rst:17
|
||||
msgid "Create a pull zone in the KeyCDN dashboard"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:27
|
||||
msgid "Once done, you'll have to wait a bit while KeyCDN_ is crawling your website."
|
||||
#: ../../content/administration/install/cdn.rst:19
|
||||
msgid "On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` menu item on the left. On the form, give a value to the :guilabel:`Zone Name`, which will appear as part of the :abbr:`CDN (Content Delivery Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the :guilabel:`Zone Status` to :guilabel:`active` to engage the zone. For the :guilabel:`Zone Type` set the value to :guilabel:`Pull`, and then, finally, under the :guilabel:`Pull Settings`, enter the :guilabel:`Origin URL`— this address should be the full Odoo database :abbr:`URL (Uniform Resource Locator)`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:32
|
||||
msgid "a new URL has been generated for your Zone, in this case it is ``http://pulltest-b49.kxcdn.com``"
|
||||
#: ../../content/administration/install/cdn.rst:28
|
||||
msgid "Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* subdomain prefix with the actual name of the database. A custom :abbr:`URL (Uniform Resource Locator)` can be used, as well, in place of the Odoo subdomain that was provided to the database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:None
|
||||
msgid "KeyCDN's Zone configuration page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:36
|
||||
msgid "Step 2: Configure the odoo instance with your zone"
|
||||
msgid "Under the :guilabel:`General Settings` heading below the zone form, click the :guilabel:`Show all settings` button to expand the zone options. This should be the last option on the page. After expanding the :guilabel:`General Settings` ensure that the :guilabel:`CORS` option is :guilabel:`enabled`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:38
|
||||
msgid "In the Odoo back end, go to the :guilabel:`Website Settings`: menu, then activate the CDN support and copy/paste your zone URL in the :guilabel:`CDN Base URL` field. This field is only visible and configurable if you have developer mode activated."
|
||||
#: ../../content/administration/install/cdn.rst:41
|
||||
msgid "Next, scroll to the bottom of the zone configuration page and :guilabel:`Save` the changes. KeyCDN will indicate that the new zone will be deployed. This can take about 10 minutes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:46
|
||||
msgid "Now your website is using the CDN for the resources matching the :guilabel:`CDN filters` regular expressions."
|
||||
#: ../../content/administration/install/cdn.rst:None
|
||||
msgid "KeyCDN deploying the new Zone."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:49
|
||||
msgid "You can have a look to the HTML of your website in order to check if the CDN integration is properly working."
|
||||
msgid "A new :guilabel:`Zone URL` has been generated for your Zone, in this example it is ``pulltest-xxxxx.kxcdn.com``. This value will differ for each database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:52
|
||||
msgid "Copy this :guilabel:`Zone URL` to a text editor for later, as it will be used in the next steps."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:55
|
||||
msgid "Configure the Odoo instance with the new zone"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:57
|
||||
msgid "Why should I activate CORS?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:59
|
||||
msgid "A security restriction in some browsers (Firefox and Chrome at time of writing) prevents a remotely linked CSS file to fetch relative resources on this same external server."
|
||||
msgid "In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and then activate the :guilabel:`Content Delivery Network (CDN)` setting and copy/paste the :guilabel:`Zone URL` value from the earlier step into the :guilabel:`CDN Base URL` field. This field is only visible and configurable when :doc:`Developer Mode <../../applications/general/developer_mode>` is activated."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:63
|
||||
msgid "If you don't activate the CORS option in the CDN zone, the more obvious resulting problem on a default Odoo website will be the lack of font-awesome icons because the font file declared in the font-awesome CSS won't be loaded on the remote server."
|
||||
msgid "Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN Base URL` and one forward slash (`/`) after the :guilabel:`CDN Base URL`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:68
|
||||
msgid "Here's what you would see on your homepage in such a case:"
|
||||
#: ../../content/administration/install/cdn.rst:66
|
||||
msgid ":guilabel:`Save` the settings when complete."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:73
|
||||
msgid "A security error message will also appear in the browser's console:"
|
||||
#: ../../content/administration/install/cdn.rst:None
|
||||
msgid "Activate the CDN setting in Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:78
|
||||
msgid "Enabling the CORS option in the CDN fixes this issue."
|
||||
#: ../../content/administration/install/cdn.rst:72
|
||||
msgid "Now the website is using the CDN for the resources matching the :guilabel:`CDN filters` regular expressions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:75
|
||||
msgid "In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` integration is evidenced as working properly by checking the :abbr:`URL (Uniform Resource Locators)` of images. The *CDN Base URL* value can be seen by using your web browser's :guilabel:`Inspect` feature on the Odoo website. Look for it's record by searching within the :guilabel:`Network` tab inside of devtools."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:None
|
||||
msgid "The CDN Base URL can be seen using the inspect function on the Odoo website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:85
|
||||
msgid "Prevent security issues by activating cross-origin resource sharing (CORS)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:87
|
||||
msgid "A security restriction in some browsers (such as Mozilla Firefox and Google Chrome) prevents a remotely linked CSS file to fetch relative resources on this same external server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:90
|
||||
msgid "If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in the :guilabel:`CDN Zone`, the more obvious resulting problem on a standard Odoo website will be the lack of *Font Awesome* icons because the font file declared in the *Font Awesome* CSS won't be loaded from the remote server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:95
|
||||
msgid "When these cross-origin resource issues occur, a security error message similar to the output below will appear in the web browser's developer console:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:98
|
||||
msgid "``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from loading /shop:1 by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://yourdatabase.odoo.com' is therefore not allowed access.``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:None
|
||||
msgid "Error message populated in the browser console."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/cdn.rst:106
|
||||
msgid "Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the :abbr:`CDN (Content Delivery Network)` settings fixes this issue."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:3
|
||||
@ -477,251 +521,251 @@ msgid "Say Odoo has been installed via the **debian packages** for Community and
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:420
|
||||
#: ../../content/administration/install/deploy.rst:447
|
||||
#: ../../content/administration/install/deploy.rst:442
|
||||
msgid "Using the above NGINX (https) configuration, the following location block should be added to serve static files via NGINX."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:442
|
||||
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/community/addons,/opt/odoo/enterprise'``."
|
||||
#: ../../content/administration/install/deploy.rst:437
|
||||
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'``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:464
|
||||
#: ../../content/administration/install/deploy.rst:459
|
||||
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."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:468
|
||||
#: ../../content/administration/install/deploy.rst:463
|
||||
msgid "Serving attachments"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:470
|
||||
#: ../../content/administration/install/deploy.rst:465
|
||||
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:475
|
||||
#: ../../content/administration/install/deploy.rst:470
|
||||
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:485
|
||||
#: ../../content/administration/install/deploy.rst:480
|
||||
msgid "The X-Sendfile extension for apache (and compatible web servers) does not require any supplementary configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:487
|
||||
#: ../../content/administration/install/deploy.rst:482
|
||||
msgid "The X-Accel extension for NGINX **does** require the following additionnal configuration:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:496
|
||||
#: ../../content/administration/install/deploy.rst:491
|
||||
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:505
|
||||
#: ../../content/administration/install/deploy.rst:500
|
||||
msgid "Security"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:507
|
||||
#: ../../content/administration/install/deploy.rst:502
|
||||
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:511
|
||||
#: ../../content/administration/install/deploy.rst:506
|
||||
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:517
|
||||
#: ../../content/administration/install/deploy.rst:512
|
||||
msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:520
|
||||
#: ../../content/administration/install/deploy.rst:515
|
||||
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:523
|
||||
#: ../../content/administration/install/deploy.rst:518
|
||||
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:528
|
||||
#: ../../content/administration/install/deploy.rst:523
|
||||
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:532
|
||||
#: ../../content/administration/install/deploy.rst:527
|
||||
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:539
|
||||
#: ../../content/administration/install/deploy.rst:534
|
||||
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:545
|
||||
#: ../../content/administration/install/deploy.rst:540
|
||||
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:550
|
||||
#: ../../content/administration/install/deploy.rst:545
|
||||
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:554
|
||||
#: ../../content/administration/install/deploy.rst:549
|
||||
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:557
|
||||
#: ../../content/administration/install/deploy.rst:552
|
||||
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:564
|
||||
#: ../../content/administration/install/deploy.rst:559
|
||||
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:570
|
||||
#: ../../content/administration/install/deploy.rst:565
|
||||
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:574
|
||||
#: ../../content/administration/install/deploy.rst:569
|
||||
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:578
|
||||
#: ../../content/administration/install/deploy.rst:573
|
||||
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:582
|
||||
#: ../../content/administration/install/deploy.rst:577
|
||||
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:593
|
||||
#: ../../content/administration/install/deploy.rst:588
|
||||
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:604
|
||||
#: ../../content/administration/install/deploy.rst:599
|
||||
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:607
|
||||
#: ../../content/administration/install/deploy.rst:602
|
||||
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:614
|
||||
#: ../../content/administration/install/deploy.rst:609
|
||||
msgid "Blocking Brute Force Attacks"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:616
|
||||
#: ../../content/administration/install/deploy.rst:611
|
||||
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:620
|
||||
#: ../../content/administration/install/deploy.rst:615
|
||||
msgid "The log entries will have the following form."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:622
|
||||
#: ../../content/administration/install/deploy.rst:617
|
||||
msgid "Failed login::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:626
|
||||
#: ../../content/administration/install/deploy.rst:621
|
||||
msgid "Successful login::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:631
|
||||
#: ../../content/administration/install/deploy.rst:626
|
||||
msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:633
|
||||
#: ../../content/administration/install/deploy.rst:628
|
||||
msgid "For example, the following fail2ban filter definition should match a failed login::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:640
|
||||
#: ../../content/administration/install/deploy.rst:635
|
||||
msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:642
|
||||
#: ../../content/administration/install/deploy.rst:637
|
||||
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:656
|
||||
#: ../../content/administration/install/deploy.rst:651
|
||||
msgid "Database Manager Security"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:658
|
||||
#: ../../content/administration/install/deploy.rst:653
|
||||
msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:660
|
||||
#: ../../content/administration/install/deploy.rst:655
|
||||
msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:663
|
||||
#: ../../content/administration/install/deploy.rst:658
|
||||
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:669
|
||||
#: ../../content/administration/install/deploy.rst:664
|
||||
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:675
|
||||
#: ../../content/administration/install/deploy.rst:670
|
||||
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:678
|
||||
#: ../../content/administration/install/deploy.rst:673
|
||||
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:683
|
||||
#: ../../content/administration/install/deploy.rst:678
|
||||
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:687
|
||||
#: ../../content/administration/install/deploy.rst:682
|
||||
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:691
|
||||
#: ../../content/administration/install/deploy.rst:686
|
||||
msgid "It should be stored securely, and should be generated randomly e.g."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:697
|
||||
#: ../../content/administration/install/deploy.rst:692
|
||||
msgid "which will generate a 32 characters pseudorandom printable string."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:700
|
||||
#: ../../content/administration/install/deploy.rst:695
|
||||
msgid "Supported Browsers"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:702
|
||||
#: ../../content/administration/install/deploy.rst:697
|
||||
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:705
|
||||
#: ../../content/administration/install/deploy.rst:700
|
||||
msgid "Here are the supported browsers:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:707
|
||||
#: ../../content/administration/install/deploy.rst:702
|
||||
msgid "Google Chrome"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:708
|
||||
#: ../../content/administration/install/deploy.rst:703
|
||||
msgid "Mozilla Firefox"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:709
|
||||
#: ../../content/administration/install/deploy.rst:704
|
||||
msgid "Microsoft Edge"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:710
|
||||
#: ../../content/administration/install/deploy.rst:705
|
||||
msgid "Apple Safari"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:712
|
||||
#: ../../content/administration/install/deploy.rst:707
|
||||
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:717
|
||||
#: ../../content/administration/install/deploy.rst:712
|
||||
msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/deploy.rst:720
|
||||
#: ../../content/administration/install/deploy.rst:715
|
||||
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:723
|
||||
#: ../../content/administration/install/deploy.rst:718
|
||||
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:727
|
||||
#: ../../content/administration/install/deploy.rst:722
|
||||
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 ""
|
||||
|
||||
@ -1600,11 +1644,11 @@ msgid "Then, create a new email server and check the box for :guilabel:`Outlook`
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/azure_oauth.rst:163
|
||||
msgid "If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address <email_communication/default_from>`."
|
||||
msgid "If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address <email_communication/default>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/azure_oauth.rst:166
|
||||
msgid "Then, cick on :guilabel:`Connect your Outlook account`."
|
||||
msgid "Then, click on :guilabel:`Connect your Outlook account`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/azure_oauth.rst:168
|
||||
@ -2790,7 +2834,7 @@ msgid "In order for the notifications feature to work using Mailjet, there are t
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/mailjet_api.rst:201
|
||||
msgid "The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended to set it as a domain and not a full email address. It should match the domain in the two proceeding steps. More information can be referenced :ref:`here <email_servers/outgoing-email-server>`."
|
||||
msgid "The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended to set it as a domain and not a full email address. It should match the domain in the two proceeding steps. More information can be referenced :ref:`here <email_communication/from_filter>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/mailjet_api.rst:205
|
||||
@ -2814,224 +2858,224 @@ msgid "Odoo Online database management"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:5
|
||||
msgid "To manage a database, sign in to https://www.odoo.com and access the `database management page <https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on *My Databases*."
|
||||
msgid "To manage a database, sign in to https://www.odoo.com and access the `database management page <https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on :guilabel:`My Databases`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:None
|
||||
msgid "Clicking on the user icon opens a drop-down menu. \"My databases\" button is highlighted."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:13
|
||||
msgid "Make sure you are connected as the administrator of the database you want to manage."
|
||||
#: ../../content/administration/maintain/odoo_online.rst:14
|
||||
msgid "Make sure to connect as the administrator of the database that changes will be made on."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:None
|
||||
msgid "Clicking on the gear icon opens the drop-down menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_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/odoo_online.rst:21
|
||||
msgid "Several actions are available:"
|
||||
#: ../../content/administration/maintain/odoo_online.rst:20
|
||||
msgid "Open the drop-down menu next to the database that changes will be made on by clicking on the gear icon."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:23
|
||||
msgid ":ref:`odoo_online/upgrade`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:24
|
||||
msgid ":ref:`odoo_online/duplicate`"
|
||||
msgid "Several actions are available:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:25
|
||||
msgid ":ref:`odoo_online/rename`"
|
||||
msgid ":ref:`odoo_online/upgrade`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:26
|
||||
msgid ":ref:`odoo_online/download`"
|
||||
msgid ":ref:`odoo_online/duplicate`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:27
|
||||
msgid ":ref:`odoo_online/domains`"
|
||||
msgid ":ref:`odoo_online/rename`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:28
|
||||
msgid ":ref:`odoo_online/tags`"
|
||||
msgid ":ref:`odoo_online/download`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:29
|
||||
msgid ":ref:`odoo_online/delete`"
|
||||
msgid ":ref:`odoo_online/domains`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:30
|
||||
msgid ":ref:`odoo_online/contact-support`"
|
||||
msgid ":ref:`odoo_online/tags`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:31
|
||||
msgid ":ref:`odoo_online/delete`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:32
|
||||
msgid ":ref:`odoo_online/contact-support`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:33
|
||||
msgid ":ref:`odoo_online/users`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:36
|
||||
#: ../../content/administration/maintain/odoo_online.rst:38
|
||||
#: ../../content/administration/odoo_sh/getting_started/branches.rst:293
|
||||
#: ../../content/administration/upgrade.rst:10
|
||||
msgid "Upgrade"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:38
|
||||
msgid "If you are *not* on the latest **Online version**, you should receive an invitation to :doc:`upgrade <../upgrade>` 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)."
|
||||
#: ../../content/administration/maintain/odoo_online.rst:40
|
||||
msgid "If the database is *not* on the latest **Online version**, the administrator should receive an invitation to :doc:`upgrade <../upgrade>` the database. A :guilabel:`Rolling Release`` button on the database's main screen proposes an upgrade to the latest version (e.g., 14.0 to 16.1)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:0
|
||||
msgid "**If your Odoo database's version is lower than the latest major release:**"
|
||||
msgid "**If the Odoo database's version is lower than the latest major release:**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:0
|
||||
msgid "You must upgrade your database within two months. After these two months, an automatic upgrade is initiated."
|
||||
msgid "The database must be upgraded within two months. After these two months, an automatic upgrade is initiated."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:0
|
||||
msgid "**If your Odoo database's version is equal to or higher than the latest major release:**"
|
||||
msgid "**If the Odoo database's version is equal to or higher than the latest major release:**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:0
|
||||
msgid "You can disregard the invitation to upgrade as you probably wouldn't benefit from new features every two months."
|
||||
msgid "Disregard the invitation to upgrade as the database probably wouldn't benefit from new features every two months."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_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."
|
||||
#: ../../content/administration/maintain/odoo_online.rst:53
|
||||
msgid "Versions that are not supported anymore become deprecated and need to be updated to avoid security issues. Odoo recommends that the company initiate the upgrade, as this method allows for the company to request a test upgrade of the database to check for any discrepancies."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:56
|
||||
#: ../../content/administration/maintain/odoo_online.rst:58
|
||||
msgid ":doc:`../upgrade`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:57
|
||||
#: ../../content/administration/maintain/odoo_online.rst:59
|
||||
msgid ":doc:`supported_versions`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:62
|
||||
#: ../../content/administration/maintain/odoo_online.rst:64
|
||||
msgid "Duplicate"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_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/odoo_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."
|
||||
#: ../../content/administration/maintain/odoo_online.rst:66
|
||||
msgid "This allows to make an exact copy of the database to be able to perform testing without compromising the daily operations."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:70
|
||||
msgid "By checking :guilabel:`For testing purposes`, all external communication (emails, payments, delivery orders, etc.) are disabled by default on the duplicated database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:72
|
||||
msgid "Duplicate databases expire automatically after 15 days."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:75
|
||||
#: ../../content/administration/maintain/odoo_online.rst:77
|
||||
msgid "Rename"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:77
|
||||
#: ../../content/administration/maintain/odoo_online.rst:79
|
||||
msgid "Rename the database and its URL."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:82
|
||||
#: ../../content/administration/maintain/odoo_online.rst:84
|
||||
msgid "Download"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:84
|
||||
msgid "Download instantly a ZIP file with a backup of the database."
|
||||
#: ../../content/administration/maintain/odoo_online.rst:86
|
||||
msgid "Instantly download a ZIP file with a backup of the database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:87
|
||||
#: ../../content/administration/maintain/odoo_online.rst:89
|
||||
msgid "Databases are backed up daily according to the `Odoo Cloud SLA <https://www.odoo.com/cloud-sla>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:93
|
||||
#: ../../content/administration/maintain/odoo_online.rst:95
|
||||
msgid "Domains"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:95
|
||||
#: ../../content/administration/maintain/odoo_online.rst:97
|
||||
msgid "Configure custom domains to access the database via another URL."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:98
|
||||
#: ../../content/administration/maintain/odoo_online.rst:100
|
||||
msgid ":doc:`domain_names`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:103
|
||||
#: ../../content/administration/maintain/odoo_online.rst:105
|
||||
msgid "Tags"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:105
|
||||
#: ../../content/administration/maintain/odoo_online.rst:107
|
||||
msgid "Add tags to sort your databases out. You can search the tags in the search bar."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:110
|
||||
#: ../../content/administration/maintain/odoo_online.rst:112
|
||||
#: ../../content/administration/odoo_sh/getting_started/branches.rst:550
|
||||
msgid "Delete"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:112
|
||||
#: ../../content/administration/maintain/odoo_online.rst:114
|
||||
msgid "Delete a database instantly."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:115
|
||||
#: ../../content/administration/maintain/odoo_online.rst:117
|
||||
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/odoo_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:"
|
||||
#: ../../content/administration/maintain/odoo_online.rst:120
|
||||
msgid "Carefully read the warning message that pops up and proceed only if the implications of deleting a database are fully understood:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:None
|
||||
msgid "A warning message is prompted before deleting a database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:126
|
||||
#: ../../content/administration/maintain/odoo_online.rst:128
|
||||
msgid "Only an administrator can delete a database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:127
|
||||
#: ../../content/administration/maintain/odoo_online.rst:129
|
||||
msgid "The database name is immediately available for a new database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:128
|
||||
#: ../../content/administration/maintain/odoo_online.rst:130
|
||||
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 <https://www.odoo.com/help>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:130
|
||||
msgid "To delete your account, please get in touch with `Odoo Support <https://www.odoo.com/help>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:135
|
||||
#: ../../content/administration/maintain/odoo_online.rst:136
|
||||
msgid "Contact Support"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:137
|
||||
#: ../../content/administration/maintain/odoo_online.rst:138
|
||||
msgid "Access the Odoo `support page <https://www.odoo.com/help>`_ with your database's details already pre-filled."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:143
|
||||
#: ../../content/administration/maintain/odoo_online.rst:144
|
||||
msgid "Invite / Remove Users"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_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*."
|
||||
#: ../../content/administration/maintain/odoo_online.rst:146
|
||||
msgid "To invite users, fill out the email address of the new user and click on :guilabel:`Invite`. To add multiple users, click on :guilabel:`Add more users`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:None
|
||||
msgid "Clicking on \"Add more users\" adds additional email fields."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:152
|
||||
msgid "To remove users, select the users to remove and click on *Remove*."
|
||||
#: ../../content/administration/maintain/odoo_online.rst:153
|
||||
msgid "To remove users, select the users to remove and click on :guilabel:`Remove`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:155
|
||||
#: ../../content/administration/maintain/odoo_online.rst:156
|
||||
msgid ":doc:`/applications/general/users/manage_users`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/odoo_online.rst:157
|
||||
msgid ":doc:`/applications/general/users/delete_account`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/maintain/on_premise.rst:3
|
||||
msgid "On-premise database management"
|
||||
msgstr ""
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 16.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-03-03 17:52+0000\n"
|
||||
"POT-Creation-Date: 2023-03-16 11:06+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"
|
||||
@ -1111,121 +1111,113 @@ msgid "Email Communication"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:3
|
||||
msgid "Send an email with Odoo"
|
||||
msgid "Configure DNS records to send emails in Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:6
|
||||
msgid "Use an email domain in Odoo"
|
||||
msgid "SPAM labels overview"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:8
|
||||
msgid "Documents in Odoo (such as a CRM opportunity, a sales order, an invoice, etc.) have a discussion thread, called *chatter*."
|
||||
msgid "Sometimes, emails from Odoo are misclassified by the different email providers and end up in spam folders. At the moment, some settings are out of Odoo's control, notably the way the different email providers classify Odoo's emails according to their own restriction policy and/or limitations."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:11
|
||||
msgid "When a database user posts a message in the chatter, this message is sent by email to the followers of the document. If a follower replies to the message, the reply updates the chatter, and Odoo relays the reply to the followers as a notification."
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:12
|
||||
msgid "It is standard in Odoo that emails are received from ``\"name of the author\" <notifications@mycompany.odoo.com>``. In other words this can be translated to: ``\"name of the author\" <{ICP.mail.from.filter}@{mail.catchall.domain}>``. In this case ICP stands for `ir.config.parameters`, which are the System Parameters. Deliverability is greatly improved with the :ref:`notifications configuration <email_servers/notifications>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:15
|
||||
msgid "Messages sent in the chatter from internal database users to external users (such as partners, customers, or vendors) are relayed on behalf of the database users. Messages sent back to the chatter from external users will appear in the chatter from their respective email addresses, or as they are listed in their Contacts record."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:20
|
||||
msgid "If the Odoo database is hosted on the cloud (Odoo Online or Odoo.sh), it is not necessary to add an outgoing email server to send emails from a custom domain."
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:18
|
||||
msgid "In order for servers to accept emails from Odoo on a more regular basis, one of the solutions is for customers to create rules within their own mailbox. A filter can be added to the email inbox so that when email is received from Odoo (`notifications@mycompany.odoo.com`) it is moved to the inbox. It is also possible to add the Odoo database domain onto a safe senders list or whitelist on the receiving domain."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:24
|
||||
msgid "The Odoo server is subject to a daily email limit to prevent abuse. The default limit is 200 emails sent per day for databases with an **Enterprise** subscription. This limit can be increased under certain conditions. See the :doc:`FAQ <faq>` or contact support for more information."
|
||||
msgid "If an Odoo email server appears on a blacklist, notify Odoo via a `new help ticket <https://www.odoo.com/help>`_ and the support team will work to get the servers removed from the blacklist."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:29
|
||||
msgid "To ensure that emails sent to and from the chatter reach their intended contacts, instead of being considered spam, Odoo recommends configuring the domain name."
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:28
|
||||
msgid "Should the Odoo database be using a custom domain for sending emails from Odoo there are three records that should be implemented on the custom domain's DNS to ensure deliverability of email. This includes setting records for :abbr:`SPF (Sender Policy Framework)`, :abbr:`DKIM (DomainKeys Identified Mail)` and :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)`. Ultimately though, it is up to the discretion of the final receiving mailbox."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:32
|
||||
msgid "For the same reason, Odoo also recommends giving each database user an email address from the configured domain, rather than a generic email address domain (such as gmail.com, outlook.com, etc.)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:39
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:38
|
||||
msgid "Be SPF compliant"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:41
|
||||
msgid "The Sender Policy Framework (SPF) protocol allows the owner of a domain name to specify which servers are allowed to send emails from that domain. When a server receives an incoming email, it checks if the IP address of the sending server is on the list of allowed IPs according to the sender's :abbr:`SPF (Sender Policy Framework)` record."
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:40
|
||||
msgid "The Sender Policy Framework (SPF) protocol allows the owner of a domain name to specify which servers are allowed to send emails from that domain. When a server receives an incoming email, it checks whether the IP address of the sending server is on the list of allowed IPs according to the sender's :abbr:`SPF (Sender Policy Framework)` record."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:47
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:46
|
||||
msgid "The :abbr:`SPF (Sender Policy Framework)` verification is performed on the domain mentioned in the `Return-Path` field of the email. In the case of an email sent by Odoo, this domain corresponds to the value of the `mail.catchall.domain` key in the database system parameters."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:51
|
||||
msgid "See the :ref:`documentation on incoming emails <email_communication/inbound_messages>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:53
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:50
|
||||
msgid "The :abbr:`SPF (Sender Policy Framework)` policy of a domain is set using a TXT record. The way to create or modify a TXT record depends on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. In order for the verification to work properly, each domain can only have one :abbr:`SPF (Sender Policy Framework)` record."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:58
|
||||
msgid "If the domain name does not yet have an :abbr:`SPF (Sender Policy Framework)` record, the content of the record to create it is as follows:"
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:55
|
||||
msgid "If the domain name does not yet have a :abbr:`SPF (Sender Policy Framework)` record, create one using the following input: `v=spf1 include:_spf.odoo.com ~all`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:61
|
||||
msgid "`v=spf1 include:_spf.odoo.com ~all`"
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:58
|
||||
msgid "If the domain name already has a :abbr:`SPF (Sender Policy Framework)` record, the record must be updated (and do not create a new one)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:63
|
||||
msgid "If the domain name already has an :abbr:`SPF (Sender Policy Framework)` record, the record must be updated (and do not create a new one)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:68
|
||||
msgid "If the TXT record is `v=spf1 include:_spf.google.com ~all`, edit it to add `include:_spf.odoo.com`: `v=spf1 include:_spf.odoo.com include:_spf.google.com ~all`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:71
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:66
|
||||
msgid "Check if the :abbr:`SPF (Sender Policy Framework)` record is valid with a free tool like `MXToolbox SPF <https://mxtoolbox.com/spf.aspx>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:77
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:72
|
||||
msgid "Enable DKIM"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:79
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:74
|
||||
msgid "The DomainKeys Identified Mail (DKIM) allows a user to authenticate emails with a digital signature."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:82
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:77
|
||||
msgid "When sending an email, the Odoo server includes a unique :abbr:`DKIM (DomainKeys Identified Mail)` signature in the headers. The recipient's server decrypts this signature using the :abbr:`DKIM (DomainKeys Identified Mail)` record in the database's domain name. If the signature and the key contained in the record match, this guarantees that the message is authentic and has not been altered during transport."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:88
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:83
|
||||
msgid "To enable :abbr:`DKIM (DomainKeys Identified Mail)`, add a :abbr:`CNAME (Canonical Name)` record to the :abbr:`DNS (Domain Name System)` zone of the domain name:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:91
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:86
|
||||
msgid "`odoo._domainkey IN CNAME odoo._domainkey.odoo.com.`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:94
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:89
|
||||
msgid "If the domain name is `mycompany.com`, make sure to create a subdomain `odoo._domainkey.mycompany.com` whose canonical name is `odoo._domainkey.odoo.com.`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:97
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:92
|
||||
msgid "The way to create or modify a :abbr:`CNAME (Canonical Name)` record depends on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. The most common providers are :ref:`listed below <email_communication/SPFDKIM_common_providers>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:101
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:96
|
||||
msgid "Check if the :abbr:`DKIM (DomainKeys Identified Mail)` record is valid with a free tool like `DKIM Core <https://dkimcore.org/tools/>`_. If a selector is asked, enter `odoo`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:105
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:100
|
||||
msgid "Check the DMARC policy"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:107
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:102
|
||||
msgid "The Domain-based Message Authentication, Reporting, & Conformance (DMARC) record is a protocol that unifies :abbr:`SPF (Sender Policy Framework)` and :abbr:`DKIM (DomainKeys Identified Mail)`. The instructions contained in the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record of a domain name tell the destination server what to do with an incoming email that fails the :abbr:`SPF (Sender Policy Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:110
|
||||
msgid "DMARC: TXT record"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:112
|
||||
msgid "`v=DMARC1; p=none;`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:114
|
||||
msgid "There are three :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policies:"
|
||||
msgstr ""
|
||||
@ -1235,6 +1227,7 @@ msgid "`p=none`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:118
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:171
|
||||
msgid "`p=quarantine`"
|
||||
msgstr ""
|
||||
|
||||
@ -1259,91 +1252,171 @@ msgid "`p=none` is used for the domain owner to receive reports about entities u
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:139
|
||||
msgid "Check the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record of a domain name with a tool like `MXToolbox DMARC <https://mxtoolbox.com/DMARC.aspx>`_."
|
||||
msgid ":abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` records are comprised of tags in the form of :abbr:`DNS (Domain Name System)` records. These tags/parameters allow for reporting, such as :abbr:`RUA (Reporting URI of aggregate reports)` and :abbr:`RUF (Reporting URI for forensic reports)`, along with more precise specification like :abbr:`PCT (Percentage of messages subjected to filtering)`, :abbr:`P (Policy for organizational domain)`, :abbr:`SP (Policy for subdomains of the OD)` :abbr:`ADKIM (Alignment mode for DKIM)` & :abbr:`ASPF (Alignment mode for SPF)`. For best practice, the the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policy should not start out being too restrictive."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:142
|
||||
msgid "If a partner, customer, or vendor, uses :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` and has defined one of these policies, the Odoo server cannot relay emails from this partner to the database users."
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:148
|
||||
msgid "The following chart displays available tags:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:146
|
||||
msgid "To solve this issue, :ref:`handle user notifications in Odoo <discuss_app/notification_preferences>`, or replace the email address of the partner with a default email address."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:153
|
||||
msgid "SPF, DKIM & DMARC documentation of common providers"
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:154
|
||||
msgid "Tag Name"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:155
|
||||
msgid "`OVH DNS <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/>`_"
|
||||
msgid "Purpose"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:156
|
||||
msgid "`OVH SPF <https://docs.ovh.com/us/en/domains/web_hosting_the_spf_record/>`_"
|
||||
msgid "Example"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:157
|
||||
msgid "`GoDaddy TXT record <https://www.godaddy.com/help/add-a-txt-record-19232>`_"
|
||||
msgid "v"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:158
|
||||
msgid "`GoDaddy SPF <https://www.godaddy.com/help/add-an-spf-record-19218>`_"
|
||||
msgid "Protocol version"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:159
|
||||
msgid "`GoDaddy DKIM <https://www.godaddy.com/help/add-a-cname-record-19236>`_"
|
||||
msgid "`v=DMARC1`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:160
|
||||
msgid "`NameCheap <https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-do-i-add- txtspfdkimdmarc-records-for-my-domain/>`_"
|
||||
msgid "pct"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:161
|
||||
msgid "Percentage of messages subjected to filtering"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:162
|
||||
msgid "`CloudFlare DNS <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_"
|
||||
msgid "`pct=20`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:163
|
||||
msgid "`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_"
|
||||
msgid "ruf"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:164
|
||||
msgid "`Azure DNS <https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal>`_"
|
||||
msgid "Reporting URI for forensic reports"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:165
|
||||
msgid "`ruf=mailto:authfail@example.com`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:166
|
||||
msgid "To fully test the configuration, use the `Mail-Tester <https://www.mail-tester.com/>`_ tool, which gives a full overview of the content and configuration in one sent email. Mail-Tester can also be used for other, lesser-known providers."
|
||||
msgid "rua"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:167
|
||||
msgid "Reporting URI of aggregate reports"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:168
|
||||
msgid "`rua=mailto:aggrep@example.com`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:169
|
||||
msgid "p"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:170
|
||||
msgid "Policy for organizational domain"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:172
|
||||
msgid "sp"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:173
|
||||
msgid "Use a default email address"
|
||||
msgid "Policy for subdomains of the OD"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:174
|
||||
msgid "`sp=reject`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:175
|
||||
msgid "Access the :guilabel:`System Parameters` by activating :ref:`developer mode <developer-mode>` and going to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
|
||||
msgid "adkim"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:176
|
||||
msgid "Alignment mode for DKIM"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:177
|
||||
msgid "`adkim=s`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:178
|
||||
msgid "To force the email address from which emails are sent, a combination of the following keys needs to be set in the system parameters of the database:"
|
||||
msgid "aspf"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:181
|
||||
msgid "`mail.default.from`: accepts the local part or a complete email address as value"
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:179
|
||||
msgid "Alignment mode for SPF"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:180
|
||||
msgid "`aspf=r`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:182
|
||||
msgid "`mail.default.from_filter`: accepts a domain name or a full email address as value"
|
||||
msgid "Check the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record of a domain name with a tool like `MXToolbox DMARC <https://mxtoolbox.com/DMARC.aspx>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:185
|
||||
msgid "The `mail.default.from_filter` works only for `odoo-bin` configurations, otherwise this parameter can be set using the `from_filter` field on `ir.mail_server`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:188
|
||||
msgid "If the email address of the author does not match `mail.default.from_filter`, the email address is replaced by `mail.default.from` (if it contains a full email address) or a combination of `mail.default.from` and `mail.catchall.domain`."
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:186
|
||||
msgid "`DMARC.org is another great resource to learn about DMARC records. <https://dmarc.org/overview/>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:192
|
||||
msgid "If the `from_filter` contains a full email address, and if the `mail.default.from` is the same as this address, then all of the email addresses that are different from `mail.default.from` will be encapsulated in `mail.default.from`."
|
||||
msgid "SPF, DKIM & DMARC documentation of common providers"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:194
|
||||
msgid "`OVH DNS <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:195
|
||||
msgid "`OVH SPF <https://docs.ovh.com/us/en/domains/web_hosting_the_spf_record/>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:196
|
||||
msgid "`GoDaddy TXT record <https://www.godaddy.com/help/add-a-txt-record-19232>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:197
|
||||
msgid "`GoDaddy SPF <https://www.godaddy.com/help/add-an-spf-record-19218>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:198
|
||||
msgid "`GoDaddy DKIM <https://www.godaddy.com/help/add-a-cname-record-19236>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:199
|
||||
msgid "`NameCheap <https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-do-i-add- txtspfdkimdmarc-records-for-my-domain/>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:201
|
||||
msgid "`CloudFlare DNS <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:202
|
||||
msgid "`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:203
|
||||
msgid "`Azure DNS <https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:205
|
||||
msgid "To fully test the configuration, use the `Mail-Tester <https://www.mail-tester.com/>`_ tool, which gives a full overview of the content and configuration in one sent email. Mail-Tester can also be used to configure records for other, lesser-known providers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_domain.rst:210
|
||||
msgid "`Using Mail-Tester to set SPF Records for specific carriers <https://www.mail-tester.com/spf/>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:3
|
||||
@ -1355,279 +1428,267 @@ msgid "Odoo Online or Odoo.sh users"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:8
|
||||
msgid "Since **Odoo sets up its own mail servers for the database**, outgoing and incoming emails already work out-of-the-box. So for **Odoo Online** and **Odoo.sh** customers, nothing needs to be done!"
|
||||
msgid "Since **Odoo sets up its own mail servers for the database**, outgoing and incoming emails already work out-of-the-box. So for **Odoo Online** and **Odoo.sh** customers, nothing needs to be configured!"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:11
|
||||
msgid "Unless an external mail server is required to send large batches of mass mailing, simply use the standard online Odoo database normally since it has already been preconfigured for email."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:12
|
||||
msgid "Unless an external mail server is required to send large batches of mass emails, simply use the standard online Odoo database normally since it has already been pre-configured to send email."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:15
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:16
|
||||
msgid "The Odoo server is subject to a daily email limit to prevent abuse. The default limit is 200 emails sent per day for databases with an **Enterprise** subscription. This limit can be increased under certain conditions. See the :doc:`FAQ <faq>` or contact support for more information."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:22
|
||||
msgid "Scope of this documentation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:17
|
||||
msgid "This document is **mainly dedicated to Odoo on-premise users** who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online <https://www.odoo. com/trial>`_ and `Odoo.sh <https://www.odoo.sh>`_."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:24
|
||||
msgid "This document is **mainly dedicated to Odoo on-premise databases** who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online <https://www.odoo. com/trial>`_ and `Odoo.sh <https://www.odoo.sh>`_. Incoming and outgoing servers must be configured for on-premise databases."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:21
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:29
|
||||
msgid "The following sections below contain information on how to integrate an external email server with Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:25
|
||||
msgid "If no one in the company is used to managing email servers, Odoo Online and Odoo.sh are strongly recommended. Those Odoo hosting types' email systems work instantly and are monitored by professionals. Nevertheless, a company can use their own email server if they want to manage the email server's reputation themselves."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:33
|
||||
msgid "If no one in the company is employed to manage email servers, Odoo Online and Odoo.sh are strongly recommended. In these Odoo hosting types email sending and receiving works instantly and is monitored by professionals. Nevertheless, a company can use their own email server if they want to manage the email server's reputation themselves. For more information see :doc:`Configure DNS records to send emails in Odoo <email_domain>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:31
|
||||
msgid "Office 365 email servers don't easily allow the sending of external emails from hosts like Odoo. Refer to `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a- multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18- c805d654b4c4>`_ to make it work."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:42
|
||||
msgid "Default notifications system"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:37
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:44
|
||||
msgid "Documents in Odoo (such as a CRM opportunity, a sales order, an invoice, etc.) have a discussion thread, called *chatter*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:47
|
||||
msgid "When a database user posts a message in the chatter, this message is sent by email to the followers of the document as a notification (except to the sender). If a follower replies to the message, the reply updates the chatter, and Odoo relays another reply to the followers as a notification. Messages sent back to the chatter from users or external users will appear in the chatter from their respective email, or as the name listed in their *Contacts* record."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:53
|
||||
msgid "These notifications are sent using a default from address. For more information see :ref:`Use a default email address <email_communication/default>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:57
|
||||
msgid "Manage outbound messages"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:39
|
||||
msgid "As a system admin, go to :menuselection:`Settings --> General Settings --> Discuss` in Odoo, and enable the :guilabel:`External Email Servers` option. Then, click :guilabel:`Save`. Next, click :guilabel:`Outgoing Email Servers` and click :guilabel:`Create` to create a new outgoing mail server record in Odoo. Reference the SMTP data of the external email server. Once all the information has been filled out, click :guilabel:`Test Connection`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:45
|
||||
msgid "Here is a typical configuration for a G Suite server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:None
|
||||
msgid "The typical G Suite configuration on Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:51
|
||||
msgid "Then, go back to :menuselection:`Settings --> General Settings --> Discuss` and set the email domain name in the :guilabel:`Alias Domain` name. Finally, click :guilabel:`Save` to finish setting up the email server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:56
|
||||
msgid "If an `[AUTHENTICATION FAILED] Invalid credentials (Failure)` warning appears when :guilabel:`Test Connection` is clicked for a Gmail address, activate the :guilabel:`Less secure app access` option. A direct link can be `accessed here <https://myaccount.google.com/ lesssecureapps?pli=1>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:61
|
||||
msgid "In addition to that, enable the :guilabel:`IMAP setting` on the Gmail account."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:64
|
||||
msgid "Use an Office 365 server"
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:59
|
||||
msgid "As a system admin, go to :menuselection:`Settings --> General Settings --> Discuss` in Odoo, and enable the :guilabel:`Custom Email Servers` option. Then, click :guilabel:`Save`. Next, click :guilabel:`Outgoing Email Servers` and click :guilabel:`Create` to create a new outgoing mail server record in Odoo. Reference the SMTP data of the external email server. Once all the information has been filled out, click :guilabel:`Test Connection`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:66
|
||||
msgid "An Office 365 server can be used if the database's hosting type is **Odoo on-premise**. Office 365 SMTP relays are not compatible with Odoo Online or Odoo.sh unless Odoo is configured to :ref:`force the outgoing \"From\" address <email_communication/default_from>`."
|
||||
msgid ":doc:`/administration/maintain/google_oauth`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:67
|
||||
msgid ":doc:`/administration/maintain/azure_oauth`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:70
|
||||
msgid "Please refer to `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up- a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18- c805d654b4c4>`_ to configure an SMTP relay for the Odoo database's IP address."
|
||||
msgid "Ensuring the outgoing domain has :abbr:`SPF (Sender Policy Framework)`, :abbr:`DKIM (DomainKeys Identified Mail)` and :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` set up on the :abbr:`DNS (Domain Name System)` will improve deliverability. For more information see :doc:`email_domain`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:75
|
||||
msgid "Use a G Suite server"
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:78
|
||||
msgid "Port restriction"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:77
|
||||
msgid "A G Suite server can be used for any Odoo hosting type. To do so, set up the SMTP relay service. The configuration steps are explained in `Google documentation <https://support.google.com /a/answer/2956491?hl=en>`__."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:84
|
||||
msgid "Restriction"
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:80
|
||||
msgid "Note that port 25 is blocked for security reasons on the Odoo Online and Odoo.sh platforms. Try using ports 465, 587, or 2525 instead."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:86
|
||||
msgid "Please note that port 25 is blocked for security reasons on Odoo Online and Odoo.sh platforms. Try using ports 465, 587, or 2525 instead."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:92
|
||||
msgid "Use a default \"From\" email address"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:94
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:88
|
||||
msgid "Sometimes, an email's \"From\" (outgoing) address can belong to a different domain, and that can be a problem."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:97
|
||||
msgid "For example, if a customer with the email address *mary\\@customer.example.com* responds to a message, Odoo will try to redistribute that same email to the other subscribers in the thread. However, if the domain *customer.example.com* forbids that kind of usage for security, the email that Odoo is trying to redistribute would get rejected by some recipients' email servers."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:91
|
||||
msgid "For example, if a customer with the email address `mary\\@customer.example.com` responds to a message, Odoo will try to redistribute that same email to the other subscribers in the thread. However, if the domain `customer.example.com` forbids that kind of usage for security, the email that Odoo is trying to redistribute would get rejected by some recipients' email servers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:96
|
||||
msgid "To avoid that problem, Odoo sends all emails using a \"From\" address from the same authorized domain."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:99
|
||||
msgid "Access the :guilabel:`System Parameters` by activating :ref:`developer mode <developer-mode>` and going to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:102
|
||||
msgid "To avoid that problem, make sure all emails use a \"From\" address from the same authorized domain."
|
||||
msgid "To force the email address from which emails are sent, a combination of the following keys needs to be set in the system parameters of the database:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:104
|
||||
msgid "If the MTA supports `SRS (Sender Rewriting Scheme) <https://en.wikipedia.org/wiki/Sender_Rewriting _Scheme>`_, SRS can be enabled to handle these situations. However, that is more complex and requires more technical knowledge that is not meant to be covered by this documentation."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:105
|
||||
msgid "`mail.default.from`: accepts the local part or a complete email address as value"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:108
|
||||
msgid "Instead, Odoo can be configured to do something similar by itself:"
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:106
|
||||
msgid "`mail.default.from_filter`: accepts a domain name or a full email address as value"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:110
|
||||
msgid "Set the :guilabel:`Alias Domain` name in the :menuselection:`Settings --> General Settings --> Discuss`."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:109
|
||||
msgid "The `mail.default.from_filter` works only for `odoo-bin` configurations or the default Odoo email server, otherwise this parameter can be set using the `from_filter` field on `ir.mail_server`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:0
|
||||
msgid "Setting the domain alias configuration on Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:116
|
||||
msgid "Turn on :doc:`developer mode </applications/general/developer_mode>`."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:112
|
||||
msgid "The field can be a domain name or an entire email address, or it can remain empty. If the sender's email address does not match this set filter, then the email will be encapsulated using a combination of the two system parameters: `mail.default.from` and `mail.catchall.domain`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:117
|
||||
msgid "Go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:118
|
||||
msgid "Add one system parameter from the following list:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:120
|
||||
msgid "To use the same \"From\" address for *all* outgoing messages, use the key `mail.force.smtp.from` and set that address as value (such as `outgoing@mycompany.example.com`)."
|
||||
msgid "In the following example, the from email address is replaced with the combination of the the two system parameters (`mail.default.from` and `mail.catchall.domain`). This is the default\\ notifications configuration in Odoo: ``“Admin” <admin@example.com>`` => ``“Admin” <notifications@mycompany.com>``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:122
|
||||
msgid "To keep the original \"From\" address for emails that use the same domain, but change it for emails that use a different domain, use the key `mail.dynamic.smtp.from` and set the value as the email address that should be used in those cases (such as `outgoing@mycompany.example.com` )."
|
||||
msgid "In other words if the email address of the author does not match `mail.default.from_filter`, the email address is replaced by `mail.default.from` (if it contains a full email address) or a combination of `mail.default.from` and `mail.catchall.domain`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:130
|
||||
msgid "Manage inbound messages"
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:126
|
||||
msgid "If the `from_filter` contains a full email address, and if the `mail.default.from` is the same as this address, then all of the email addresses that are different from `mail.default.from` will be encapsulated in `mail.default.from`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:132
|
||||
msgid "Odoo relies on generic email aliases to fetch incoming messages."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:133
|
||||
msgid "Utilizing the \"From\" filter on an outgoing email server"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:134
|
||||
msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the catchall alias (**catchall@**)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:136
|
||||
msgid "**Bounced messages** are routed to **bounce@** in order to track them in Odoo. This is especially used in `Odoo Email Marketing <https://www.odoo.com/page/email-marketing>`__ to opt-out invalid recipients."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:139
|
||||
msgid "**Original messages**: Several business objects have their own alias to create new records in Odoo from incoming emails:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:142
|
||||
msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM <https://www.odoo.com/page/ crm>`__),"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:144
|
||||
msgid "Support Channel (to create Tickets in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`__),"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:145
|
||||
msgid "Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page /project-management>`__),"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:147
|
||||
msgid "Job Positions (to create Applicants in `Odoo Recruitment <https://www.odoo.com/page /recruitment>`__),"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:149
|
||||
msgid "etc."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:151
|
||||
msgid "Depending on the mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in the mail server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:154
|
||||
msgid "Create the corresponding email addresses in the mail server (catchall@, bounce@, sales@, etc.)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:155
|
||||
msgid "Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> General Settings --> Discuss`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:157
|
||||
msgid "If the database's hosting type is Odoo on-premise, create an :guilabel:`Incoming Mail Server` in Odoo for each alias. This can be done from the General Settings as well. Fill out the form according to the email provider's settings. Leave the :guilabel:`Actions to Perform on Incoming Mails` field blank. Once all the information has been filled out, click on :guilabel:`TEST & CONFIRM`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:0
|
||||
msgid "Incoming mail server configuration on Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:167
|
||||
msgid "If the database's hosting type is Odoo Online or Odoo.sh, redirecting incoming messages to Odoo's domain name instead of the external email server is recommended. That way, incoming messages can be received without delay. Odoo Online only fetches incoming messages of external servers once every hour. Redirections for all email addresses should be set to Odoo's domain name in the email server (e.g. *catchall\\@mydomain.ext* to *catchall\\@mycompany.odoo.com*)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:173
|
||||
msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their respective configuration view."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:177
|
||||
msgid "To edit catchall and bounce aliases, first activate the :ref:`developer mode <developer-mode>`. Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & *mail.bounce.alias*)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:0
|
||||
msgid "System parameters with catchall configuration in Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:185
|
||||
msgid "By default, inbound messages are fetched every 5 minutes in Odoo on-premise."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:188
|
||||
msgid "This value can be changed in :ref:`developer mode <developer-mode>`. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for :guilabel:`Mail: Fetchmail Service`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:195
|
||||
msgid "Utilizing the From Filter on an outgoing email server"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:197
|
||||
msgid "The :guilabel:`FROM Filtering` field allows for the use of a specific outgoing email server depending on the :guilabel:`From` email address or domain that Odoo is sending on behalf of. This setting can be used to improve the deliverability or sending success rate of emails sent from the database. Setting the :guilabel:`FROM Filtering` field can also be used to send from different domains in a multi-company environment. Access this field in Odoo by navigating to :menuselection:`Settings --> Custom Mail Servers --> Outgoing Mail Servers --> New`."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:135
|
||||
msgid "The :guilabel:`FROM Filtering` field allows for the use of a specific outgoing email server depending on the :guilabel:`From` email address or domain that Odoo is sending on behalf of. This setting can be used to improve the deliverability or sending success rate of emails sent from the database. Setting the :guilabel:`FROM Filtering` field can also be used to send from different domains in a multi-company environment. Access this field in Odoo by navigating to :menuselection:`Settings --> Discuss --> Custom Mail Servers --> Outgoing Mail Servers --> New`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:None
|
||||
msgid "Outgoing email server settings and the FROM filter settings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:208
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:146
|
||||
msgid "When an email is sent from Odoo while the :guilabel:`FROM Filtering` field is set, an email server is chosen in the following sequence:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:211
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:149
|
||||
msgid "First, Odoo searches for an email server that has the same :guilabel:`FROM Filtering` value as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` value (email address) is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `test\\@example.com` are returned."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:215
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:153
|
||||
msgid "However, if no email servers are found that use the :guilabel:`From` value, then Odoo searches for an email server that has the same *domain* as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` email address is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `example.com` are returned."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:221
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:159
|
||||
msgid "If no email servers are found after checking for the domain, then Odoo returns all email servers that do not have any :guilabel:`FROM Filtering` value(s) set."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:224
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:162
|
||||
msgid "Should this query return no results, then Odoo performs a search for an email server using the system parameter: `mail.default.from`. First, the email address listed attempts to match an email server, and then the domain attempts to find a match. If no email server is found, Odoo returns the first outgoing email server (sorted by priority)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:230
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:168
|
||||
msgid "If several email servers are found, then Odoo uses the first one according to its priority. For example, if there are two email servers, one with a priority of `10` and the other with a priority of `20`, then the email server with a priority of `10` is used first."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:235
|
||||
msgid "Set up different dedicated servers for transactional and mass mails"
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:175
|
||||
msgid "Set up different dedicated servers for transactional and mass emails"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:237
|
||||
msgid "In Odoo a separate Mail Transfer Agent (MTA) server can be used for transactional emails and mass mailings. Example: Use Postmark or SendinBlue for transactional emails, and Amazon SES, Mailgun or Sendgrid for mass mailings."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:177
|
||||
msgid "In Odoo a separate email server can be used for transactional emails and mass mailings. Example: Use Postmark or SendinBlue for transactional emails, and Amazon SES, Mailgun, Sendgrid or :doc:`Mailjet </administration/maintain/mailjet_api>` for mass mailings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:242
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:182
|
||||
msgid "A default outgoing email server is already configured. Do not create an alternative one unless a specific external outgoing email server is needed for technical reasons."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:245
|
||||
msgid "To do this, first activate the :ref:`developer mode <developer-mode>`, and then go to :menuselection:`Settings --> Technical --> Outgoing` email servers. There, create two email MTA server settings; one for the transactional emails and one for the mass mailing server. Make sure to give priority to the transactional server over the mass mailing server by providing a lower priority number for the transactional MTA server."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:185
|
||||
msgid "To do this, first activate the :ref:`developer mode <developer-mode>`, and then go to :menuselection:`Settings --> Technical --> Outgoing` email servers. There, create two outgoing email server settings; one for the transactional emails and one for the mass mailing server. Make sure to give priority to the transactional server over the mass mailing server by providing a lower priority number for the transactional email server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:251
|
||||
msgid "Now, go to :menuselection:`Email Marketing --> Settings` and enable :guilabel:`Dedicated Server`. With these settings, Odoo uses the server with the lower priority for transactional emails, and the server here selected for mass mails. Note that in this case, the domain's Sender Policy Framework (SPF) records must be set to include both transactional and mass mail servers."
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:191
|
||||
msgid "Now, go to :menuselection:`Email Marketing --> Settings` and enable :guilabel:`Dedicated Server`. Choose the appropriate email server. With these settings, Odoo uses the server with the lower priority for transactional emails, and the server here selected for mass mails. Note that in this case, the domain's Sender Policy Framework (SPF) records must be set to include both transactional and mass mail servers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:198
|
||||
msgid ":doc:`email_domain`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:203
|
||||
msgid "Manage inbound messages"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:205
|
||||
msgid "Odoo relies on generic email aliases to fetch incoming messages."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:207
|
||||
msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the alias of the model if there is any or by the catchall alias (**catchall@**). Replies to messages of models that don't have a custom alias will use the catchall alias (`catchall@mycompany.odoo.com`). The catchall address, however, does not have another action attached to it like other aliases might, it is only used to collect replies."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:212
|
||||
msgid "**Bounced messages** are used as a Return-Path. One example this is especially useful for is in `Odoo Email Marketing <https://www.odoo.com/page/email-marketing>`__. In this case bounces are opt-out based on if the email bounced too many times (5) in the last month and the bounces are separated by one week. This is done to avoid blacklisting someone because of a mail server error. If these circumstances are met then the email is considered invalid and is blacklisted. A log note is added on the contact under :guilabel:`Blacklisted Email Addresses` on the :guilabel:`Email Marketing Configuration Menu`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:220
|
||||
msgid "Messages that bounce in the chatter (outside of Email Marketing) will populate a red envelope indicating the failed delivery. This can be helpful to know that a Sales Order or an Invoice did not reach its final destination."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:223
|
||||
msgid "**Original messages**: several business objects have their own alias to create new records in Odoo from incoming emails:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:226
|
||||
msgid "Sales channel (to create *Leads* or *Opportunities* in `Odoo CRM <https://www.odoo.com/page/ crm>`_)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:228
|
||||
msgid "Support channel (to create *Tickets* in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`_)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:229
|
||||
msgid "Projects (to create new *Tasks* in `Odoo Project <https://www.odoo.com/page /project-management>`_)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:231
|
||||
msgid "Job positions (to create *Applicants* in `Odoo Recruitment <https://www.odoo.com/page /recruitment>`_)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:234
|
||||
msgid "Depending on the mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in the mail server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:237
|
||||
msgid "Create the corresponding email addresses in the mail server (**catchall@**, **bounce@**, **sales@**, etc.)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:239
|
||||
msgid "Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> General Settings --> Discuss`. Changing the :guilabel:`Alias Domain` will change the catchall's domain for the database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:242
|
||||
msgid "If the database's hosting type is Odoo on-premise, create an :guilabel:`Incoming Mail Server` in Odoo for each alias. To create a new incoming server go to: :menuselection:`Settings --> Discuss --> Custom Mail Servers --> Incoming Mail Servers --> New` Fill out the form according to the email provider's settings. Leave the :guilabel:`Actions to Perform on Incoming Mails` field blank. Once all the information has been filled out, click on :guilabel:`TEST & CONFIRM`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:0
|
||||
msgid "Incoming mail server configuration on Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:252
|
||||
msgid "If the database's hosting type is Odoo Online or Odoo.sh, redirecting or forwarding incoming messages to Odoo's domain name instead of the external email server is recommended. That way, incoming messages can be received without delay. Redirections for all email addresses should be set to Odoo's domain name in the email server (e.g. `catchall\\@mydomain.ext` to `catchall\\@mycompany.odoo.com`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:258
|
||||
msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their respective configuration view by navigating to :menuselection:`Settings --> Technical Menu --> Email --> Aliases`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:262
|
||||
msgid "To edit catchall and bounce aliases, first activate the :ref:`developer mode <developer-mode>`. Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (`mail.catchall.alias` & `mail.bounce.alias`). These types of changes should be completed prior to the database going live. If a customer replies after a change is made then the system will not recognize the old alias and the reply won't be received."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:268
|
||||
msgid "By default, inbound messages are fetched every 5 minutes for on-premise databases."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_servers.rst:271
|
||||
msgid "This value can be changed in :ref:`developer mode <developer-mode>`. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for :guilabel:`Mail: Fetchmail Service`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:3
|
||||
@ -2775,11 +2836,11 @@ msgstr ""
|
||||
msgid "You can use several groups at the same time. The first group you select is the main cluster, the next one you add further divides the main group's categories, and so on."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/users.rst:7
|
||||
msgid "Users & Companies"
|
||||
#: ../../content/applications/general/users.rst:5
|
||||
msgid "Users and companies"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/users.rst:9
|
||||
#: ../../content/applications/general/users.rst:7
|
||||
msgid "Odoo defines a *user* as someone who has access to a database to perform daily tasks. You can add as many users as you need and, in order to restrict the type of information each user can access, rules can be applied. Users and access rights can be added and changed at any point."
|
||||
msgstr ""
|
||||
|
||||
@ -3048,6 +3109,30 @@ msgstr ""
|
||||
msgid ":doc:`../../finance/accounting/others/multi_currency`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/users/delete_account.rst:3
|
||||
msgid "Deleting an Odoo.com Account"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/users/delete_account.rst:5
|
||||
msgid "To delete your Odoo.com account, access the delete option by clicking on the user icon. The delete option can be accessed by going to :menuselection:`My Account --> Edit Security Settings --> Delete Account`. It can also be accessed by going to https://www.odoo.com/my/home."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/users/delete_account.rst:10
|
||||
msgid "Deleting an Odoo account is irreversible. Take caution when performing this action as the Odoo.com account will not be retrievable."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/users/delete_account.rst:13
|
||||
msgid "Upon clicking the :guilabel:`Delete Account` button, a pop-up window will appear, asking you to confirm the account deletion."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/users/delete_account.rst:None
|
||||
msgid "Clicking on the Delete Account button will populate a window verifying the change."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/users/delete_account.rst:20
|
||||
msgid "Confirm the deletion by entering the :guilabel:`password` and the :guilabel:`login` for the account being deleted. Click the :guilabel:`Delete Account` button to confirm the deletion."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/users/language.rst:3
|
||||
msgid "Change language"
|
||||
msgstr ""
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 16.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-03-03 17:52+0000\n"
|
||||
"POT-Creation-Date: 2023-03-16 11:06+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"
|
||||
@ -64,8 +64,8 @@ msgstr ""
|
||||
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:12
|
||||
#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:13
|
||||
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:12
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:14
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:10
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:20
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:11
|
||||
#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10
|
||||
#: ../../content/applications/sales/point_of_sale/shop/cash_rounding.rst:17
|
||||
@ -1281,107 +1281,6 @@ msgstr ""
|
||||
msgid ":doc:`../../sales/products_prices/prices/pricing`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm.rst:5
|
||||
msgid "Fiscal Data Modules"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:3
|
||||
msgid "Setting up the Fiscal Data Module with the Odoo POS"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:6
|
||||
msgid "Introduction"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:8
|
||||
msgid "The Belgian government requires certain businesses to use a government-certified device called a **Fiscal Data Module** (also known as a **blackbox**). This device works together with the POS application and logs certain transactions. On top of that, the used POS application must also be certified by the government and must adhere to strict standards specified by them. `Odoo 9 (Enterprise Edition) is a certified application <http://www.systemedecaisseenregistreuse.be/systemes-certifies>`_. More information concerning the Fiscal Data Module can be found on `the official website <http://www.systemedecaisseenregistreuse.be/>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:20
|
||||
msgid "Required hardware"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:22
|
||||
msgid "A government certified `Fiscal Data Module <http://www.systemedecaisseenregistreuse.be/systemes-certifies#FDM%20certifiés>`_ per POS, all of them should work, but the Cleancash SC-B is recommended, you will also need:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:27
|
||||
msgid "Serial null modem cable per FDM (`example <http://www.startech.com/Cables/Serial-Parallel-PS-2/DB9-DB25/10-ft-Cross-Wired-Serial-Null-Modem-Cable-DB9-FM~SCNM9FM>`__)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:29
|
||||
msgid "Serial-to-USB adapter per FDM (`example <http://trendnet.com/products/proddetail.asp?prod=265_TU-S9>`__)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:32
|
||||
msgid "A registered IoT Box per POS configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:35
|
||||
msgid "Setup"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:38
|
||||
msgid "IoT Box"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:40
|
||||
msgid "In order to use a Fiscal Data Module, you will need a registered IoT Box. These IoT Boxes are similar to the regular IoT Boxes we sell, but they are registered with the Belgian government. This is required by law. Attempting to use a Fiscal Data Module on a non-registered IoT Box will not work. You can verify that the Fiscal Data Module is recognized by the IoT Box by going to the *Hardware status page* via the IoT Box homepage."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:52
|
||||
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:88
|
||||
msgid "Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:54
|
||||
msgid "An Odoo POS app can be given certified POS capabilities by installing the **Belgian Registered Cash Register** app (technical name: ``pos_blackbox_be``). Because of government restrictions imposed on us, this installation cannot be undone. After this, you will have to ensure that each POS configuration has a unique registered IoT Box associated with it (:menuselection:`Point of Sale --> Configuration --> Point of Sale` and ensure Hardware Proxy / IoT Box and the serial number of your IoT Box is set). The first time you open the Point of Sale and attempt to do a transaction, you will be asked to input the PIN that you received with your VAT signing card."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:69
|
||||
msgid "Certification & On-premise"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:71
|
||||
msgid "The certification granted by the government is restricted to the use on odoo.com Odoo Online instance. The usage of the module from the source or a modified version will **not** be certified. For on-premise users, we also support the Fiscal Data Module in such installations. The main restriction is that this requires an obfuscated version of the ``pos_blackbox_be`` module we will provide on request for Enterprise customers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:79
|
||||
msgid "Restrictions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:81
|
||||
msgid "As mentioned before, in order to get certified the POS application must adhere to strict government guidelines. Because of this, a certified Odoo POS has some limitations not present in the non-certified Odoo POS."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:86
|
||||
msgid "Refunding is disabled"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:87
|
||||
msgid "Modifying orderline prices"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:88
|
||||
msgid "Creating/modifying/deleting POS orders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:89
|
||||
msgid "Selling products without a valid tax"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:90
|
||||
msgid "Multiple Odoo POS configurations per IoT Box are not allowed"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:91
|
||||
msgid "Using the POS without a connection to the IoT Box (and thus FDM)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/belgian_fdm/setup.rst:92
|
||||
msgid "Blacklisted modules: pos_discount, pos_reprint, pos_loyalty"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/overview.rst:5
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
@ -2351,43 +2250,103 @@ msgid "To cancel the payment request, click on **cancel**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:5
|
||||
msgid "Restaurant Features"
|
||||
msgid "Restaurant features"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:7
|
||||
msgid "Managing a restaurant or a bar comes with specific needs. The Point of Sale application provides various features that allow performing all the required tasks in such businesses."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:10
|
||||
msgid "Once the POS is set to be used in a restaurant or a bar, you can:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:12
|
||||
msgid ":doc:`organize your floors and tables to reflect your interior <restaurant/floors_tables>`;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:13
|
||||
msgid ":ref:`take orders <floors_tables/orders>`;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:14
|
||||
msgid ":doc:`communicate with the kitchen or the bar through the POS <restaurant/kitchen_printing>`;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:15
|
||||
msgid ":doc:`print bills in advance and split them <restaurant/bill_printing>`;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:16
|
||||
msgid ":doc:`collect tips <restaurant/tips>`; and"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:17
|
||||
msgid ":doc:`set different taxes for takeaway food <restaurant/fiscal_position>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:22
|
||||
msgid "To enable the restaurant and bar-specific features, go to :menuselection:`Point of Sale --> Configuration --> Settings`, select the POS, and activate :guilabel:`Is a Bar/Restaurant`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:25
|
||||
msgid "These features are displayed in the :guilabel:`Restaurant & Bar` section."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant.rst:None
|
||||
msgid "restaurant and bar-specific features"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:3
|
||||
msgid "Print the Bill"
|
||||
msgid "Bills"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:5
|
||||
msgid "Use the *Bill Printing* feature to print the bill before the payment. This is useful if the bill is still subject to evolve and is thus not the definitive ticket."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10
|
||||
msgid "Configure Bill Printing"
|
||||
msgid "Typical practices in restaurants or bars are to request the bill before proceeding to payment or splitting it based on the items ordered. Odoo POS provides two features to perform these tasks seamlessly: **Bill Printing** and **Bill Splitting**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:12
|
||||
msgid "To activate *Bill Printing*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface."
|
||||
msgid "To activate the features, go to :menuselection:`Point of Sale --> Configuration --> Settings`, select the POS, and activate :guilabel:`Early Receipt Printing` and :guilabel:`Allow Bill Splitting` in the :guilabel:`Restaurant & Bar` section."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:15
|
||||
msgid "Under the Bills & Receipts category, you will find *Bill Printing* option."
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:None
|
||||
msgid "activate the bill printing and bill splitting features in the POS settings"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:22
|
||||
msgid "Split a Bill"
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:21
|
||||
msgid "Bill printing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:24
|
||||
msgid "On your PoS interface, you now have a *Bill* button."
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:23
|
||||
msgid "From an open session, click :menuselection:`Bill --> Print` at any moment to generate and print a bill."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:29
|
||||
msgid "When you use it, you can then print the bill."
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:27
|
||||
msgid "The printed bill is **not** final and will be updated to reflect any changes to the order."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:30
|
||||
msgid "Bill splitting"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:32
|
||||
msgid "From an open session, click :guilabel:`Split` to select the items to regroup. Once everything is selected, click :guilabel:`Payment` and proceed to checkout for these items. Repeat for each guest."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:36
|
||||
msgid "Once you return to the table, the selected items are no longer on order, as they have been paid for."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:38
|
||||
msgid "The feature is available as soon as at least two items are ordered."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:41
|
||||
msgid ":doc:`floors_tables`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:3
|
||||
msgid "Using fiscal positions in PoS"
|
||||
msgid "Tax rates (fiscal positions)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/fiscal_position.rst:5
|
||||
@ -2426,8 +2385,113 @@ msgstr ""
|
||||
msgid "Now, the *tax* button is replaced by a *on site* button when on the *PoS* interface."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:3
|
||||
msgid "Floors and tables management"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:6
|
||||
msgid "Add a floor"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:8
|
||||
msgid "Once your *Point of Sale* has been configured, select *Table Management* under :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, click on *Floors* to create and name your floor and tables."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:None
|
||||
msgid "View of the table management feature. Way to manage and create floors for a pos"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:None
|
||||
msgid "Backend view of a restaurant floor. Table name and number of sits for each table"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:21
|
||||
msgid "Don’t forget to link your floor to your point of sale."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:24
|
||||
msgid "Add tables"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:26
|
||||
msgid "To add tables, you can also open your PoS interface to see your floor(s)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:None
|
||||
msgid "View of the floors menu to manage several floors at the same time"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:33
|
||||
msgid "Then, click on *Edit Mode* (pencil icon on the upper right corner) to be allowed to create, move, modify tables, etc."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:None
|
||||
msgid "View of the floor management. Add tables, the number of sits, their name and their shape"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:41
|
||||
msgid "To make your table easier to be found, you can rename them, change their shape, size or even color. It is also possible to add the maximum number of sits the table can have."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:48
|
||||
msgid "Register your table(s) orders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:50
|
||||
msgid "To register an order, click on the respective table. By doing so, you are taken to your main interface."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:None
|
||||
msgid "View of the pos interface to register orders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:58
|
||||
msgid "Transfer customer(s)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:60
|
||||
msgid "If your customers want to move to another table after they already ordered, use the transfer button. This way, the order is also moved to the new table."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:64
|
||||
msgid "To do so, select the table your customer is currently on."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:None
|
||||
msgid "View of the restaurant tables, one having a pending order"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:70
|
||||
msgid "Now, click on the transfer button and select the table to which you are transferring your customer."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:None
|
||||
msgid "View of the pos interface and transfer button. How to transfer customers from one table\n"
|
||||
"to another"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:79
|
||||
msgid "Register an additional order"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:81
|
||||
msgid "When registering an order, use the + button to simultaneously proceed to another one."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:84
|
||||
msgid "Then, you can shift between your orders and process the payment when needed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:None
|
||||
msgid "View of the - button, allowing employees to close/remove an order"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:92
|
||||
msgid "The - button allows you to remove the order you are currently on."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:3
|
||||
msgid "Print orders at the kitchen or bar"
|
||||
msgid "Orders printing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:5
|
||||
@ -2474,163 +2538,6 @@ msgstr ""
|
||||
msgid "When you press it, it will print the order on your kitchen/bar printer."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:3
|
||||
msgid "Manage your tables"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:5
|
||||
msgid "Restaurants have specific needs that shops don’t have. That’s why Odoo gives restaurant owners several unique features to help them manage their business in the best possible way."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:9
|
||||
msgid "Floor and table management, bill splitting, or even the possibility to print orders from the kitchen, everything is there to help your business shine and your employees to work efficiently."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:16
|
||||
msgid "To activate the bar/restaurant features, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and open your PoS. Now, select *Is a Bar/Restaurant*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None
|
||||
msgid "Restaurant set up. Enabling the is a bar/Restaurant feature on a PoS"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:24
|
||||
msgid "New features are shown with a fork and a knife next to it, indicating that they are restaurant-specific."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None
|
||||
msgid "Several restaurant features. Bill printing, bill splitting and tips"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:32
|
||||
msgid "Add a floor"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:34
|
||||
msgid "Once your *Point of Sale* has been configured, select *Table Management* under :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, click on *Floors* to create and name your floor and tables."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None
|
||||
msgid "View of the table management feature. Way to manage and create floors for a pos"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None
|
||||
msgid "Backend view of a restaurant floor. Table name and number of sits for each table"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:47
|
||||
msgid "Don’t forget to link your floor to your point of sale."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:50
|
||||
msgid "Add tables"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:52
|
||||
msgid "To add tables, you can also open your PoS interface to see your floor(s)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None
|
||||
msgid "View of the floors menu to manage several floors at the same time"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:59
|
||||
msgid "Then, click on *Edit Mode* (pencil icon on the upper right corner) to be allowed to create, move, modify tables, etc."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None
|
||||
msgid "View of the floor management. Add tables, the number of sits, their name and their shape"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:67
|
||||
msgid "To make your table easier to be found, you can rename them, change their shape, size or even color. It is also possible to add the maximum number of sits the table can have."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:72
|
||||
msgid "Register your table(s) orders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:74
|
||||
msgid "To register an order, click on the respective table. By doing so, you are taken to your main interface."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None
|
||||
msgid "View of the pos interface to register orders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:82
|
||||
msgid "Transfer customer(s)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:84
|
||||
msgid "If your customers want to move to another table after they already ordered, use the transfer button. This way, the order is also moved to the new table."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:88
|
||||
msgid "To do so, select the table your customer is currently on."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None
|
||||
msgid "View of the restaurant tables, one having a pending order"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:94
|
||||
msgid "Now, click on the transfer button and select the table to which you are transferring your customer."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None
|
||||
msgid "View of the pos interface and transfer button. How to transfer customers from one table\n"
|
||||
"to another"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:103
|
||||
msgid "Register an additional order"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:105
|
||||
msgid "When registering an order, use the + button to simultaneously proceed to another one."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:108
|
||||
msgid "Then, you can shift between your orders and process the payment when needed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:None
|
||||
msgid "View of the - button, allowing employees to close/remove an order"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:116
|
||||
msgid "The - button allows you to remove the order you are currently on."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:3
|
||||
msgid "Offer a bill-splitting option"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:5
|
||||
msgid "Offering an easy bill splitting solution to your customers will leave them with a positive experience. That's why this feature is available out-of-the-box in the Odoo Point of Sale application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:12
|
||||
msgid "To activate the *Bill Splitting* feature, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:16
|
||||
msgid "Under the Bills & Receipts category, you will find the Bill Splitting option."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:23
|
||||
msgid "Split a bill"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:25
|
||||
msgid "In your PoS interface, you now have a *Split* button."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/split.rst:30
|
||||
msgid "When you use it, you will be able to select what that guest should had and process the payment, repeating the process for each guest."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:3
|
||||
msgid "Tips"
|
||||
msgstr ""
|
||||
@ -3037,15 +2944,11 @@ msgstr ""
|
||||
msgid ":doc:`../restaurant/bill_printing`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:23
|
||||
msgid ":doc:`../restaurant/split`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:26
|
||||
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:25
|
||||
msgid "Reprint a receipt"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:28
|
||||
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:27
|
||||
msgid "From the POS interface, click :guilabel:`Orders`, open the dropdown selection menu next to the search bar, and change the default :guilabel:`All active orders` filter to :guilabel:`Paid`. Then, select the corresponding order and click :guilabel:`Print Receipt`."
|
||||
msgstr ""
|
||||
|
||||
@ -3053,7 +2956,7 @@ msgstr ""
|
||||
msgid "print receipt button from the backend"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:37
|
||||
#: ../../content/applications/sales/point_of_sale/shop/receipts.rst:36
|
||||
msgid "You can filter the list of orders using the search bar. Type in your reference and click :guilabel:`Receipt Number`, :guilabel:`Date`, or :guilabel:`Customer`."
|
||||
msgstr ""
|
||||
|
||||
@ -4693,7 +4596,7 @@ msgid ":doc:`currencies`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:146
|
||||
msgid ":doc:`/applications/websites/ecommerce/maximizing_revenue/pricing`"
|
||||
msgid ":doc:`/applications/websites/ecommerce/managing_products/price_management`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/sales/products_prices/products.rst:5
|
||||
@ -4853,6 +4756,10 @@ msgstr ""
|
||||
msgid "Save your **Search Engine Id**. You’ll need it for the next step in Odoo!"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:88
|
||||
msgid "Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:90
|
||||
msgid "Go to :menuselection:`Settings --> General Settings --> Integrations`, activate **Google Images** and save."
|
||||
msgstr ""
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 16.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-03-03 17:52+0000\n"
|
||||
"POT-Creation-Date: 2023-03-16 11:06+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"
|
||||
@ -295,26 +295,35 @@ msgid ":guilabel:`Mandatory (no guest checkout)`: customers can only checkout if
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:113
|
||||
msgid ":doc:`../ecommerce_management/customer_accounts`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:114
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:24
|
||||
msgid ":doc:`/applications/general/users/portal`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:117
|
||||
msgid "B2B access restriction"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:115
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:119
|
||||
msgid "If you wish to restrict checkout only to **selected B2B customers**, enable :guilabel:`Mandatory (no guest checkout)` and go to :menuselection:`Website --> eCommerce --> Customers`. Select the customer you wish to **grant access to**, click :menuselection:`Action --> Grant portal access`, and click :guilabel:`Grant Access`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:121
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:125
|
||||
msgid "Settings are **website-specific**, which means you can set up a B2C website allowing **guest** checkout, and another for B2B customers with **mandatory sign-in**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:125
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:129
|
||||
msgid "Users can only have one portal access per **email**. They *cannot* be granted access to two different portals with the same **email address**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:129
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:133
|
||||
msgid "Shared customer accounts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:131
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:135
|
||||
msgid "If you enable :guilabel:`Shared Customer Accounts` under :menuselection:`Website --> Configuration --> Settings --> Privacy section`, you can allow or disallow access to *all* websites for one same account."
|
||||
msgstr ""
|
||||
|
||||
@ -327,6 +336,7 @@ msgid "Odoo supports a multitude of online :doc:`payment providers </application
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:10
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:55
|
||||
msgid ":doc:`/applications/sales/sales/products_prices/ewallets_giftcards`"
|
||||
msgstr ""
|
||||
|
||||
@ -365,6 +375,22 @@ msgstr ""
|
||||
msgid "Payment provider selection at checkout"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:41
|
||||
msgid "eWallets and gift cards"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:43
|
||||
msgid "When checking out, customers can pay with an eWallet or gift cards. To enable these, go to :menuselection:`Website --> Configuration --> Settings`, and in the :guilabel:`Shop-Products` section, enable :menuselection:`Discounts, Loyalty & Gift Card`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:47
|
||||
msgid "Once enabled, customers can enter their gift card **code** or pay with their eWallet at the checkout step."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:None
|
||||
msgid "Enter gift card code to process checkout"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:3
|
||||
msgid "Shipping methods"
|
||||
msgstr ""
|
||||
@ -394,10 +420,12 @@ msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/setup/delivery_m
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:35
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83
|
||||
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/invoicing`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:36
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85
|
||||
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/multipack`"
|
||||
msgstr ""
|
||||
|
||||
@ -426,6 +454,7 @@ msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/setup/dhl_creden
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:84
|
||||
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/labels`"
|
||||
msgstr ""
|
||||
|
||||
@ -450,6 +479,179 @@ msgstr ""
|
||||
msgid "Delivery method choice at checkout"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management.rst:5
|
||||
msgid "eCommerce management"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:3
|
||||
#: ../../content/applications/websites/website/publish/multi_website.rst:288
|
||||
msgid "Customer accounts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:5
|
||||
msgid "Having customer accounts on an eCommerce allows customers to access all their documents from a single place. To access their account, customers must be **logged-in** on the eCommerce website, click on their **username** in the top-right corner of the screen, and click :guilabel:`My Account`. From there, customers can access their :guilabel:`quotations`, :guilabel:`orders`, :guilabel:`invoices`, etc."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:None
|
||||
msgid "Customer account log-in"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:16
|
||||
msgid "Customers can only have an account if the :ref:`sign in/up at checkout <checkout-sign>` option allows for accounts creation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:20
|
||||
msgid "Similarly to the rest of the website, the customer account page can be customized with **content blocks** and other features through the **website builder**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:27
|
||||
msgid "Access restriction"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:29
|
||||
msgid "It is possible to allow or restrict the documents to which customers have access through the website builder. Log in your **own** account with your Odoo database credentials, and go to :menuselection:`Edit --> Customize`. From the website builder menu, enable or disable the documents customers can have access to."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:None
|
||||
msgid "Documents to which customers have access to from their account"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:39
|
||||
msgid "Multi-website account"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:41
|
||||
msgid "If you own multiple websites, you can make customer accounts available across **all** websites. Then, the customer only needs one account. To do so, go to :menuselection:`Website --> Configuration --> Settings --> Privacy section`, and enable :guilabel:`Shared Customer Accounts`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:3
|
||||
msgid "Order handling"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:5
|
||||
msgid "When a customer orders on your eCommerce, there are **three** record types required to be handle in Odoo:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:8
|
||||
msgid ":ref:`Sales orders <handling/sales>`;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:9
|
||||
msgid ":ref:`Delivery orders <handling/delivery>`;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:10
|
||||
msgid ":ref:`Invoices & legal requirements <handling/legal>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:15
|
||||
msgid "Sales orders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:18
|
||||
msgid "Order and payment status"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:20
|
||||
msgid "The first step when a customer adds a product to his cart is the creation of a quotation. Orders can be managed either from the **Website** or :doc:`Sales </applications/sales/sales>` app. eCommerce orders can automatically be assigned to a specific sales team by going to :menuselection:`Website --> Configuration --> Settings`. In the **Shop - Checkout Process** section, select a :guilabel:`Sales Team` or :guilabel:`Salesperson` to handle eCommerce orders."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:None
|
||||
msgid "Assignment of online orders to a sales team or salesperson"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:30
|
||||
msgid "Orders can be found under :menuselection:`Website --> eCommerce --> Orders/Unpaid Orders`. Each order goes through a different status:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:33
|
||||
msgid "**Quotation**: a new product is added to the cart, but the customer has *not* gone through the checkout process yet;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:35
|
||||
msgid "**Quotation sent**: the customer has gone through the checkout process and confirmed the order, but the payment is not yet confirmed;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:37
|
||||
msgid "**Order**: the customer has gone through the checkout process, confirmed the order, and the payment is received."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:None
|
||||
msgid "Statuses of eCommerce orders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:45
|
||||
msgid "Abandoned cart"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:47
|
||||
msgid "An **abandoned cart** represents an order for which the customer did **not finish** the checkout confirmation process. For these orders, it is possible to send an **email reminder** to the customer automatically. To enable that feature, go to :menuselection:`Website --> Configuration --> Settings` and in the :guilabel:`Email & Marketing` section, enable :guilabel:`Automatically send abandoned checkout emails`. Once enabled, you can set the **time-lapse** after which the email is sent and customize the **email template** used."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:55
|
||||
msgid "For abandoned cart emails, the customer must either have entered their contact details during the checkout process; or be logged-in when they added the product to their cart."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:61
|
||||
msgid "Delivery orders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:64
|
||||
msgid "Delivery flow"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:66
|
||||
msgid "Once a quotation has been confirmed, a delivery order is automatically created. The next step is to process this delivery."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:69
|
||||
msgid "Packing eCommerce orders usually requires picking the product, preparing the packaging, printing the shipping label(s) and shipping to the customer. Depending on the number of orders, strategy, or resources, those steps can be considered as one or multiple actions in Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:73
|
||||
msgid "An automatic email can be sent to the customer when the transfer status in Odoo is “done”. To do so, enable the feature in the settings of the :doc:`Inventory </applications/inventory_and_mrp/inventory>` app."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:78
|
||||
msgid "If customers are allowed to pay when picking up their order in stores or by wire transfer, the quotation is **not** be confirmed and the stock is **not** be reserved. Orders must be confirmed manually to reserve products in stock."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:88
|
||||
msgid "Returns and refunds"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:90
|
||||
msgid "Customers can only return an order through an online form. It may not be possible to return products depending on the return strategy or type of product."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:93
|
||||
msgid "Full refunds can be directly sent to customers from within the order interface. A refund-compatible payment provider needs to be enabled first."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:97
|
||||
msgid ":doc:`/applications/sales/sales/products_prices/returns`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:98
|
||||
msgid ":doc:`/applications/services/helpdesk/advanced/after_sales`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:99
|
||||
msgid ":doc:`/applications/finance/payment_providers`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:104
|
||||
msgid "Invoice and legal requirements"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:106
|
||||
msgid "The final step of an ecommerce order is to generate the invoice and send it to the customer. Depending on the type of business (B2B or B2C), an invoice can either be generated automatically (B2B) or on demand of the customer (B2C). This process can be automated if (and when) the online payment is :ref:`confirmed <handling/sales>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:111
|
||||
msgid "To automate invoicing, go to :menuselection:`Website --> Configuration --> Settings` and in the :guilabel:`Invoicing` section, enable :guilabel:`Automatic Invoice`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/managing_products.rst:5
|
||||
#: ../../content/applications/websites/website/publish/multi_website.rst:166
|
||||
msgid "Products"
|
||||
@ -887,7 +1089,6 @@ msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:90
|
||||
#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:118
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:35
|
||||
msgid ":doc:`/applications/sales/sales/products_prices/prices/pricing`"
|
||||
msgstr ""
|
||||
|
||||
@ -920,7 +1121,6 @@ msgid "Pricelists selection"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:119
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:36
|
||||
msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`"
|
||||
msgstr ""
|
||||
|
||||
@ -1354,272 +1554,6 @@ msgstr ""
|
||||
msgid "Categories buttons"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue.rst:5
|
||||
msgid "Maximize my revenue"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:3
|
||||
msgid "Adapt prices to website visitors"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:5
|
||||
msgid "This section sheds light on pricing features found in the eCommerce app:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:7
|
||||
msgid "force a price by geo-localization,"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:9
|
||||
msgid "let the customer choose the currency."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:11
|
||||
msgid "As a pre-requisite, check out how to managing product pricing: :doc:`/applications/sales/sales/products_prices/prices/pricing`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:15
|
||||
msgid "Geo-IP automatically applies the right price"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:17
|
||||
msgid "Assign country groups to your pricelists. That way, visitors who aren't logged in yet will get their own currency when landing on your website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:20
|
||||
msgid "Once logged in, they get the pricelist matching their country."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:23
|
||||
msgid "Currency selector"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:25
|
||||
msgid "In the case that you sell in several currencies, you can let your customers choose their own. Check the *Selectable* box to add the pricelist to the website drop-down menu, which can be found in *Pricelists* under the *Products* menu, located in the Website application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:37
|
||||
msgid ":doc:`promo_code`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:3
|
||||
msgid "How to create & share promotional codes"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:5
|
||||
msgid "Want to boost your sales for Xmas? Share promocodes through your marketing campaigns and apply any kind of discounts."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:9
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:13
|
||||
#: ../../content/applications/websites/website/publish/multi_website.rst:18
|
||||
msgid "Setup"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:11
|
||||
msgid "Go to :menuselection:`Sales --> Settings` and choose *Advanced pricing based on formula* for *Sale Price*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:14
|
||||
msgid "Go to :menuselection:`Website Admin --> Catalog --> Pricelists` and create a new pricelist with the discount rule (see :doc:`pricing`). Then enter a code."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:21
|
||||
msgid "Make the promocode field available on your *Shopping Cart* page (option in *Customize* menu). Add a product to cart to reach it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:27
|
||||
msgid "Once turned on you see a new section on the right side. On clicking *Apply* prices get automatically updated in the cart."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:33
|
||||
msgid "The promocode used by the customer is stored in the system so you can analyze the performance of your marketing campaigns."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:39
|
||||
msgid "Show sales per pricelists..."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:43
|
||||
msgid ":doc:`pricing`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:3
|
||||
msgid "How to enable comments & rating"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:5
|
||||
msgid "Publishing and monitoring customer experience will help you gain the trust of new customers and better engage with your community. In 2 clicks, allow your customer to share their feedback!"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:15
|
||||
msgid "Activate comments & rating from the *Customize* menu of the product web page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:21
|
||||
msgid "Visitors must log in to share their comments. Make sure they are able to do so (see Portal documentation)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:25
|
||||
msgid "Review the posts in real time"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:27
|
||||
msgid "Whenever a post is published, the product manager and all the product followers get notified in their Inbox (*Discuss* menu)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:34
|
||||
msgid "By default the user who created the product is automatically set as follower."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:36
|
||||
msgid "Click the product name to open the detail form and review the comment (in the product discussion thread)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:43
|
||||
msgid "Moderate & unpublish"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:45
|
||||
msgid "You can easily moderate by using the chatter, either in the product detail form or on the web page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:48
|
||||
msgid "To unpublish the post, open the product web page and click the *Published* button to turn it red (*Unpublished*)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:56
|
||||
msgid "..tip::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:55
|
||||
msgid "You can access the web page from the detail form by clicking the *Published* smart button (and vice versa)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience.rst:5
|
||||
msgid "Get paid"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:3
|
||||
msgid "Manage orders paid with Payment Providers"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:5
|
||||
msgid "The moment a payment is officially authorized by a Payment Provider, Odoo *automatically* confirms the order, which triggers the delivery. And, if you invoice based on ordered quantities, you are requested to invoice the order, as well."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:9
|
||||
msgid "Let’s take a closer look at how to manage orders paid with Payment Providers."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:12
|
||||
msgid "Checking the status of a payment"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:14
|
||||
msgid "To check the status of a payment, go to :menuselection:`Website --> Orders --> Orders`. Then, simply click on the order you wish to check on."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:17
|
||||
msgid "Once you are on the Sales Order page, you will find the payment is confirmed with an automatic note in the *Chatter*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:None
|
||||
msgid "payment is confirmed in the chatter of sales order"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:24
|
||||
msgid "If the user decides to create an invoice, the payment is directly reconciled. This note in the *Chatter* includes a link to the Payment entry, which contains various details about the transaction, along with a link to the related Journal Entry."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:None
|
||||
msgid "page with details surrounding the specific transaction"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:32
|
||||
msgid "Specific messages are provided to your customers for every payment status whenever they are redirected to Odoo after the transaction. To edit these messages, go to the *Messages* tab of the payment method."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:38
|
||||
msgid "Automatically generate invoices at order"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:40
|
||||
msgid "When the order is confirmed, you can also choose to have an invoice automatically issued and paid. This fully-automated feature is designed for businesses that invoice orders right away."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:47
|
||||
msgid "To do automatically generate invoices at order:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:45
|
||||
msgid "Go to :menuselection:`Website --> Configuration --> Settings --> Invoicing`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:46
|
||||
msgid "Then, under the **Invoicing Policy** option, select *Invoice what is ordered*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:47
|
||||
msgid "Then activate *Automatic Invoices* and *Save*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:None
|
||||
msgid "example of automatic invoice"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:54
|
||||
msgid "Capture payment after the delivery"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:56
|
||||
msgid "If the provider handling the payment is configured to capture amounts manually, the order is confirmed, but the amount is kept on hold. Once the delivery is processed, you can capture the payment from the related Sales Order."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:61
|
||||
msgid ":doc:`../../../finance/payment_providers`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_providers.rst:62
|
||||
msgid ":ref:`Payment Providers: Place a hold on a card <payment_providers/features/manual_capture>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:3
|
||||
msgid "How customers can access their customer account"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:5
|
||||
msgid "It has never been so easy for your customers to access their customer account. Forget endless signup forms, Odoo makes it as easy as ABC. They are suggested to sign up (name, email, password) when the order is placed, and not before. Indeed, nothing is more annoying than going through a signup process before buying something."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:14
|
||||
msgid "Sign up"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:16
|
||||
msgid "The invitation to sign up shows up when the customer wants to visualize the order from order confirmation email."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:23
|
||||
msgid "Customer account"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:25
|
||||
msgid "Once logged in the customer will access the account by clicking *My Account* in the login dropdown menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:31
|
||||
msgid "THere they find all their history. The main address (billing) can also be modified."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:37
|
||||
msgid "If the customer is set as a contact of a company in your address book, they will see all the documents whose the customer belongs to this company."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce/taxes.rst:5
|
||||
msgid "Collect taxes"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:8
|
||||
msgid "Live Chat"
|
||||
msgstr ""
|
||||
@ -2839,6 +2773,10 @@ msgstr ""
|
||||
msgid "Each website can work in a fully independent way, with its theme, branding, domain name, header & footer, pages, languages, products, blog posts, forum, slides, events, live chat channels, etc. Let’s go for a tour!"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/publish/multi_website.rst:18
|
||||
msgid "Setup"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/publish/multi_website.rst:20
|
||||
msgid "To create a new website, go to :menuselection:`Website --> Configuration --> Settings`. The button, *Create a new website*, lays in the first section."
|
||||
msgstr ""
|
||||
@ -3088,7 +3026,7 @@ msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to creat
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/publish/multi_website.rst:270
|
||||
msgid ":doc:`../../ecommerce/maximizing_revenue/pricing`."
|
||||
msgid ":doc:`../../ecommerce/managing_products/price_management`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/publish/multi_website.rst:275
|
||||
@ -3103,10 +3041,6 @@ msgstr ""
|
||||
msgid "By default, published payment providers and delivery methods are deployed in all websites. You could already use specific payment providers per country using Geo IP by defining countries in their configuration. Now you can also do it per website by filling in the *Website* field."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/publish/multi_website.rst:288
|
||||
msgid "Customer accounts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/publish/multi_website.rst:290
|
||||
msgid "There is a setting to choose how to manage customer accounts in Website settings. You can either allow customers to use one account through all the websites or compel them to create one account for each website. This last option is convenient if your websites shouldn’t be related to each other in the visitor mind."
|
||||
msgstr ""
|
||||
|
||||
Loading…
Reference in New Issue
Block a user