[I18N] *: export 16.0 translations
closes odoo/documentation#7452
X-original-commit: 3917094efd
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux (mat)
parent
a787a2652f
commit
aecf49d6c8
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-12-21 13:43+0000\n"
|
||||
"POT-Creation-Date: 2024-01-19 15:28+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"
|
||||
@ -890,6 +890,82 @@ msgstr ""
|
||||
msgid "If you don't have access/manage your email server, use :ref:`inbound messages <email_communication/inbound_messages>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:3
|
||||
msgid "Geo IP"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:6
|
||||
msgid "This documentation only applies to On-premise databases."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:9
|
||||
msgid "Installation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:11
|
||||
msgid "Download both the GeoLite2 City and Country `databases <https://dev.maxmind.com/geoip/geoip2/geolite2/>`_. You should end up with two files called :file:`GeoLite2-City.mmdb` and :file:`GeoLite2-Country.mmdb`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:15
|
||||
msgid "Move the files to the folder :file:`/usr/share/GeoIP/`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:22
|
||||
msgid "Restart the server"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:25
|
||||
msgid "If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`, use the :option:`--geoip-city-db <odoo-bin --geoip-city-db>` and :option:`--geoip-country-db <odoo-bin --geoip-country-db>` options of the Odoo command line interface. These options take the absolute path to the GeoIP database file and use it as the GeoIP database. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:36
|
||||
msgid ":doc:`CLI documentation </developer/reference/cli>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:39
|
||||
msgid "Test GeoIP geolocation in your Odoo website"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:41
|
||||
msgid "Edit a web page to include some geo-ip information such as the country name of the current request IP address. To do so:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:44
|
||||
msgid "Go to your website. Open the web page that you want to test ``GeoIP``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:45
|
||||
msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:46
|
||||
msgid "Add the following piece of XML in the page :"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:52
|
||||
msgid "Save and refresh the page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:54
|
||||
msgid "Geo-ip is working if you read your country name displayed in bold in the middle of the page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:56
|
||||
msgid "In case you read \"**geoip failure**\" instead then the geolocalization failed. The common causes are:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:58
|
||||
msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one. If you don't know, you can access your website using mobile data."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:60
|
||||
msgid "You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't start Odoo with the proxy-mode enabled. See :option:`proxy mode <odoo-bin --proxy-mode>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/geo_ip.rst:62
|
||||
msgid "The GeoIP database is corrupt, missing or unaccessible. In such case a warning was logged in the server logs."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/install/online.rst:3
|
||||
msgid "Online"
|
||||
msgstr ""
|
||||
@ -910,8 +986,8 @@ msgstr ""
|
||||
#: ../../content/administration/maintain/domain_names.rst:166
|
||||
#: ../../content/administration/maintain/domain_names.rst:236
|
||||
#: ../../content/administration/maintain/supported_versions.rst:29
|
||||
#: ../../content/administration/upgrade.rst:92
|
||||
#: ../../content/administration/upgrade.rst:309
|
||||
#: ../../content/administration/upgrade.rst:90
|
||||
#: ../../content/administration/upgrade.rst:307
|
||||
msgid "Odoo Online"
|
||||
msgstr ""
|
||||
|
||||
@ -2005,8 +2081,8 @@ msgstr ""
|
||||
#: ../../content/administration/maintain/domain_names.rst:250
|
||||
#: ../../content/administration/maintain/supported_versions.rst:30
|
||||
#: ../../content/administration/odoo_sh.rst:5
|
||||
#: ../../content/administration/upgrade.rst:122
|
||||
#: ../../content/administration/upgrade.rst:320
|
||||
#: ../../content/administration/upgrade.rst:120
|
||||
#: ../../content/administration/upgrade.rst:318
|
||||
msgid "Odoo.sh"
|
||||
msgstr ""
|
||||
|
||||
@ -6031,58 +6107,58 @@ msgid "Migrating from another ERP to Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:42
|
||||
msgid "If your database contains a **custom module**, you must first upgrade its source code to be compatible with the new version of Odoo **before upgrading**."
|
||||
msgid "If your database contains custom modules, it cannot be upgraded until a version of your custom modules is available for the target version of Odoo. For customers maintaining their own custom modules, we recommend to parallelize the process by :ref:`requesting an upgraded database <upgrade/request-test-database>` while also :doc:`upgrading the source code of your custom modules </developer/howtos/upgrade_custom_db>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:49
|
||||
#: ../../content/administration/upgrade.rst:50
|
||||
msgid "Upgrading in a nutshell"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:51
|
||||
#: ../../content/administration/upgrade.rst:52
|
||||
msgid "Request an upgraded test database (see :ref:`obtaining an upgraded test database <upgrade/request-test-database>`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:54
|
||||
#: ../../content/administration/upgrade.rst:55
|
||||
msgid "If applicable, upgrade the source code of your custom module to be compatible with the new version of Odoo (see :doc:`/developer/howtos/upgrade_custom_db`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:58
|
||||
msgid "Thoroughly test the upgraded database (see :ref:`testing the new version of the database <upgrade/test_your_db>`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:57
|
||||
#: ../../content/administration/upgrade.rst:61
|
||||
msgid "Report any issue encountered during the testing to Odoo via the `support page <https://odoo.com/help?stage=migration>`__."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:60
|
||||
msgid "(If applicable) : upgrade the source code of your custom module to be compatible with the new version of Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:63
|
||||
#: ../../content/administration/upgrade.rst:64
|
||||
msgid "Once all issues are resolved and you are confident that the upgraded database can be used as your main database without any issues, plan the upgrade of your production database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:66
|
||||
#: ../../content/administration/upgrade.rst:67
|
||||
msgid "Request the upgrade for the production database, rendering it unavailable for the time it takes to complete the process (see :ref:`upgrading the production database <upgrade/upgrade-prod>`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:69
|
||||
#: ../../content/administration/upgrade.rst:70
|
||||
msgid "Report any issue encountered during the upgrade to Odoo via the `support page <https://odoo.com/help?stage=post_upgrade>`__."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:78
|
||||
#: ../../content/administration/upgrade.rst:76
|
||||
msgid "Obtaining an upgraded test database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:80
|
||||
#: ../../content/administration/upgrade.rst:78
|
||||
msgid "The `Upgrade page <https://upgrade.odoo.com/>`_ is the main platform for requesting an upgraded database. However, depending on the hosting type, you can upgrade from the command line (on-premise), the `Odoo Online database manager <https://odoo.com/my/databases>`_, or your `Odoo.sh project <https://odoo.sh/project>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:86
|
||||
#: ../../content/administration/upgrade.rst:84
|
||||
msgid "The Upgrade platform follows the same `Privacy Policy <https://www.odoo.com/privacy>`_ as the other Odoo.com services. Visit the `General Data Protection Regulation page <https://www.odoo.com/gdpr>`_ to learn more about how Odoo handles your data and privacy."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:94
|
||||
#: ../../content/administration/upgrade.rst:92
|
||||
msgid "Odoo Online databases can be manually upgraded via the `database manager <https://odoo.com/my/databases>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:97
|
||||
#: ../../content/administration/upgrade.rst:95
|
||||
msgid "The database manager displays all databases associated with the user's account. Databases not on the most recent version of Odoo display an arrow in a circle icon next to their name, indicating that they can be upgraded."
|
||||
msgstr ""
|
||||
|
||||
@ -6090,19 +6166,19 @@ msgstr ""
|
||||
msgid "The database manager with an upgrade button next to the name of a database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:104
|
||||
#: ../../content/administration/upgrade.rst:102
|
||||
msgid "Click the **arrow in a circle** icon to start the upgrade process. In the popup, fill in:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:106
|
||||
#: ../../content/administration/upgrade.rst:104
|
||||
msgid "The **version** of Odoo you want to upgrade to, usually the latest version"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:107
|
||||
#: ../../content/administration/upgrade.rst:105
|
||||
msgid "The **email** address that should receive the link to the upgraded database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:108
|
||||
#: ../../content/administration/upgrade.rst:106
|
||||
msgid "The :guilabel:`Purpose` of the upgrade, which is automatically set to :guilabel:`Test` for your first upgrade request"
|
||||
msgstr ""
|
||||
|
||||
@ -6110,7 +6186,7 @@ msgstr ""
|
||||
msgid "The \"Upgrade your database\" popup."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:114
|
||||
#: ../../content/administration/upgrade.rst:112
|
||||
msgid "The :guilabel:`Upgrade in progress` tag is displayed next to the database name until completion. Once the process succeeds, an email containing a link to the upgraded test database is sent to the address provided. The database can also be accessed from the database manager by clicking the dropdown arrow before the database name."
|
||||
msgstr ""
|
||||
|
||||
@ -6118,7 +6194,7 @@ msgstr ""
|
||||
msgid "Clicking the menu arrow displays the upgraded test database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:124
|
||||
#: ../../content/administration/upgrade.rst:122
|
||||
msgid "Odoo.sh is integrated with the upgrade platform to simplify the upgrade process."
|
||||
msgstr ""
|
||||
|
||||
@ -6126,272 +6202,280 @@ msgstr ""
|
||||
msgid "Odoo.sh project and tabs"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:129
|
||||
#: ../../content/administration/upgrade.rst:127
|
||||
msgid "The **latest production daily automatic backup** is then sent to the `upgrade platform <https://upgrade.odoo.com>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:132
|
||||
#: ../../content/administration/upgrade.rst:130
|
||||
msgid "Once the upgrade platform is done upgrading the backup and uploading it on the branch, it is put in a **special mode**: each time a **commit is pushed** on the branch, a **restore operation** of the upgraded backup and an **update of all the custom modules** occur. This allows you to test your custom modules on a pristine copy of the upgraded database. The log file of the upgrade process can be found in your newly upgraded staging build by going to :file:`~/logs/upgrade.log`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:140
|
||||
#: ../../content/administration/upgrade.rst:138
|
||||
msgid "In databases where custom modules are installed, their source code must be up-to-date with the target version of Odoo before the upgrade can be performed. If there are none, the \"update on commit\" mode is skipped, the upgraded database is built as soon as it is transferred from the upgrade platform, and the upgrade mode is exited."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:152
|
||||
#: ../../content/administration/upgrade.rst:344
|
||||
#: ../../content/administration/upgrade.rst:143
|
||||
msgid "Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:145
|
||||
#: ../../content/administration/upgrade.rst:341
|
||||
msgid "On-premise"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:154
|
||||
#: ../../content/administration/upgrade.rst:147
|
||||
msgid "The standard upgrade process can be initiated by entering the following command line on the machine where the database is hosted:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:161
|
||||
#: ../../content/administration/upgrade.rst:154
|
||||
msgid "The following command can be used to display the general help and the main commands:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:167
|
||||
#: ../../content/administration/upgrade.rst:160
|
||||
msgid "An upgraded test database can also be requested via the `Upgrade page <https://upgrade.odoo.com/>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:171
|
||||
#: ../../content/administration/upgrade.rst:164
|
||||
msgid "In databases where custom modules are installed, their source code must be up-to-date with the target version of Odoo before the upgrade can be performed. Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:169
|
||||
msgid "For security reasons, only the person who submitted the upgrade request can download it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:172
|
||||
#: ../../content/administration/upgrade.rst:170
|
||||
msgid "For storage reasons, the database's copy is submitted without a filestore to the upgrade server. Therefore, the upgraded database does not contain the production filestore."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:174
|
||||
#: ../../content/administration/upgrade.rst:172
|
||||
msgid "Before restoring the upgraded database, its filestore must be merged with the production filestore to be able to perform tests in the same conditions as it would be in the new version."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:177
|
||||
#: ../../content/administration/upgrade.rst:175
|
||||
msgid "The upgraded database contains:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:179
|
||||
#: ../../content/administration/upgrade.rst:177
|
||||
msgid "A `dump.sql` file containing the upgraded database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:180
|
||||
#: ../../content/administration/upgrade.rst:178
|
||||
msgid "A `filestore` folder containing files extracted from in-database records into attachments (if there are any) and new standard Odoo files from the targeted Odoo version (e.g., new images, icons, payment provider's logos, etc.). This is the folder that should be merged with the production filestore in order to get the full upgraded filestore."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:187
|
||||
#: ../../content/administration/upgrade.rst:185
|
||||
msgid "You can request multiple test databases if you wish to test an upgrade more than once."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:192
|
||||
#: ../../content/administration/upgrade.rst:190
|
||||
msgid "When an upgrade request is completed, an upgrade report is attached to the successful upgrade email, and it becomes available in the Discuss app for users who are part of the \"Administration / Settings\" group. This report provides important information about the changes introduced by the new version."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:200
|
||||
#: ../../content/administration/upgrade.rst:198
|
||||
msgid "Testing the new version of the database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:202
|
||||
#: ../../content/administration/upgrade.rst:200
|
||||
msgid "It is essential to spend some time testing the upgraded test database to ensure that you are not stuck in your day-to-day activities by a change in views, behavior, or an error message once the upgrade goes live."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:207
|
||||
#: ../../content/administration/upgrade.rst:205
|
||||
msgid "Test databases are neutralized, and some features are disabled to prevent them from impacting the production database:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:210
|
||||
#: ../../content/administration/upgrade.rst:208
|
||||
msgid "Scheduled actions are disabled."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:211
|
||||
#: ../../content/administration/upgrade.rst:209
|
||||
msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake one."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:212
|
||||
#: ../../content/administration/upgrade.rst:210
|
||||
msgid "Payment providers and delivery carriers are reset to the test environment."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:213
|
||||
#: ../../content/administration/upgrade.rst:211
|
||||
msgid "Bank synchronization is disabled. Should you want to test the synchronization, contact your bank synchronization provider to get sandbox credentials."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:216
|
||||
#: ../../content/administration/upgrade.rst:214
|
||||
msgid "Testing as many of your business flows as possible is strongly recommended to ensure they are working correctly and to get more familiar with the new version."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:219
|
||||
#: ../../content/administration/upgrade.rst:217
|
||||
msgid "Basic test checklist"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:221
|
||||
#: ../../content/administration/upgrade.rst:219
|
||||
msgid "Are there views that are deactivated in your test database but active in your production database?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:223
|
||||
#: ../../content/administration/upgrade.rst:221
|
||||
msgid "Are your usual views still displayed correctly?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:224
|
||||
#: ../../content/administration/upgrade.rst:222
|
||||
msgid "Are your reports (invoice, sales order, etc.) correctly generated?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:225
|
||||
#: ../../content/administration/upgrade.rst:223
|
||||
msgid "Are your website pages working correctly?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:226
|
||||
#: ../../content/administration/upgrade.rst:224
|
||||
msgid "Are you able to create and modify records? (sales orders, invoices, purchases, users, contacts, companies, etc.)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:228
|
||||
#: ../../content/administration/upgrade.rst:226
|
||||
msgid "Are there any issues with your mail templates?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:229
|
||||
#: ../../content/administration/upgrade.rst:227
|
||||
msgid "Are there any issues with saved translations?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:230
|
||||
#: ../../content/administration/upgrade.rst:228
|
||||
msgid "Are your search filters still present?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:231
|
||||
#: ../../content/administration/upgrade.rst:229
|
||||
msgid "Can you export your data?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:235
|
||||
#: ../../content/administration/upgrade.rst:233
|
||||
msgid "Checking a random product in your product catalog and comparing its test and production data to verify everything is the same (product category, selling price, cost price, vendor, accounts, routes, etc.)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:238
|
||||
#: ../../content/administration/upgrade.rst:236
|
||||
msgid "Buying this product (Purchase app)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:239
|
||||
#: ../../content/administration/upgrade.rst:237
|
||||
msgid "Confirming the reception of this product (Inventory app)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:240
|
||||
#: ../../content/administration/upgrade.rst:238
|
||||
msgid "Checking if the route to receive this product is the same in your production database (Inventory app)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:242
|
||||
#: ../../content/administration/upgrade.rst:240
|
||||
msgid "Selling this product (Sales app) to a random customer."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:243
|
||||
#: ../../content/administration/upgrade.rst:241
|
||||
msgid "Opening your customer database (Contacts app), selecting a customer (or company), and checking its data."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:245
|
||||
#: ../../content/administration/upgrade.rst:243
|
||||
msgid "Shipping this product (Inventory app)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:246
|
||||
#: ../../content/administration/upgrade.rst:244
|
||||
msgid "Checking if the route to ship this product is the same as in your production database (Inventory app)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:248
|
||||
#: ../../content/administration/upgrade.rst:246
|
||||
msgid "Validating a customer invoice (Invoicing or Accounting app)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:249
|
||||
#: ../../content/administration/upgrade.rst:247
|
||||
msgid "Crediting the invoice (issuing a credit note) and checking if it behaves as in your production database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:251
|
||||
#: ../../content/administration/upgrade.rst:249
|
||||
msgid "Checking your reports' results (Accounting app)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:252
|
||||
#: ../../content/administration/upgrade.rst:250
|
||||
msgid "Randomly checking your taxes, currencies, bank accounts, and fiscal year (Accounting app)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:253
|
||||
#: ../../content/administration/upgrade.rst:251
|
||||
msgid "Making an online order (Website apps) from the product selection in your shop until the checkout process and checking if everything behaves as in your production database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:256
|
||||
#: ../../content/administration/upgrade.rst:254
|
||||
msgid "This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:258
|
||||
#: ../../content/administration/upgrade.rst:256
|
||||
msgid "If you face an issue while testing your upgraded test database, you can request the assistance of Odoo via the `support page <https://odoo.com/help?stage=migration>`__ by selecting the option related to testing the upgrade. In any case, it is essential to report any problem encountered during the testing to fix it before upgrading your production database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:263
|
||||
#: ../../content/administration/upgrade.rst:261
|
||||
msgid "You might encounter significant differences with standard views, features, fields, and models during testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced by a new version breaks a customization, it is the responsibility of the maintainer of your custom module to make it compatible with the new version of Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:269
|
||||
#: ../../content/administration/upgrade.rst:267
|
||||
msgid "Do not forget to test:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:271
|
||||
#: ../../content/administration/upgrade.rst:269
|
||||
msgid "Integrations with external software (EDI, APIs, etc.)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:272
|
||||
#: ../../content/administration/upgrade.rst:270
|
||||
msgid "Workflows between different apps (online sales with eCommerce, converting a lead all the way to a sales order, delivery of products, etc.)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:274
|
||||
#: ../../content/administration/upgrade.rst:272
|
||||
msgid "Data exports"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:275
|
||||
#: ../../content/administration/upgrade.rst:273
|
||||
msgid "Automated actions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:276
|
||||
#: ../../content/administration/upgrade.rst:274
|
||||
msgid "Server actions in the action menu on form views, as well as by selecting multiple records on list views"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:282
|
||||
#: ../../content/administration/upgrade.rst:280
|
||||
msgid "Upgrading the production database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:284
|
||||
#: ../../content/administration/upgrade.rst:282
|
||||
msgid "Once the :ref:`tests <upgrade/test_your_db>` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day. It can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page <https://odoo.com/help>`__."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:289
|
||||
#: ../../content/administration/upgrade.rst:287
|
||||
msgid "Your production database will be unavailable during its upgrade. Therefore, we recommend planning the upgrade at a time when the use of the database is minimal."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:292
|
||||
msgid "As the standard upgrade scripts and your database are constantly evolving, it is also recommended to frequently request another upgraded test database to ensure that the upgrade process is still successful, especially if it takes a long time to finish. Fully rehearsing the upgrade process the day before upgrading the production database is also recommended."
|
||||
#: ../../content/administration/upgrade.rst:290
|
||||
msgid "As the standard upgrade scripts and your database are constantly evolving, it is also recommended to frequently request another upgraded test database to ensure that the upgrade process is still successful, especially if it takes a long time to finish. **Fully rehearsing the upgrade process the day before upgrading the production database is also recommended.**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:298
|
||||
#: ../../content/administration/upgrade.rst:296
|
||||
msgid "Going into production without first testing may lead to:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:300
|
||||
#: ../../content/administration/upgrade.rst:298
|
||||
msgid "Users failing to adjust to the changes and new features"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:301
|
||||
#: ../../content/administration/upgrade.rst:299
|
||||
msgid "Business interruptions (e.g., no longer having the possibility to validate an action)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:302
|
||||
#: ../../content/administration/upgrade.rst:300
|
||||
msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:304
|
||||
#: ../../content/administration/upgrade.rst:302
|
||||
msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:311
|
||||
#: ../../content/administration/upgrade.rst:309
|
||||
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade/request-test-database>`, except for the purpose option, which must be set to :guilabel:`Production` instead of :guilabel:`Test`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:316
|
||||
#: ../../content/administration/upgrade.rst:314
|
||||
msgid "Once the upgrade is requested, the database will be unavailable until the upgrade is finished. Once the process is completed, it is impossible to revert to the previous version."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:322
|
||||
#: ../../content/administration/upgrade.rst:320
|
||||
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade/request-test-database>` on the :guilabel:`Production` branch."
|
||||
msgstr ""
|
||||
|
||||
@ -6399,98 +6483,98 @@ msgstr ""
|
||||
msgid "View from the upgrade tab"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:328
|
||||
#: ../../content/administration/upgrade.rst:326
|
||||
msgid "The process is **triggered as soon as a new commit is made** on the branch. This allows the upgrade process to be synchronized with the deployment of the custom modules' upgraded source code. If there are no custom modules, the upgrade process is triggered immediately."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:334
|
||||
#: ../../content/administration/upgrade.rst:332
|
||||
msgid "The database is unavailable throughout the process. If anything goes wrong, the platform automatically reverts the upgrade, as it would be for a regular update. In case of success, a backup of the database before the upgrade is created."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:338
|
||||
msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production."
|
||||
#: ../../content/administration/upgrade.rst:336
|
||||
msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production. More information on how to upgrade your custom modules can be found on :doc:`/developer/howtos/upgrade_custom_db`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:346
|
||||
#: ../../content/administration/upgrade.rst:343
|
||||
msgid "The command to upgrade a database to production is similar to the one of upgrading a test database except for the argument `test`, which must be replaced by `production`:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:353
|
||||
#: ../../content/administration/upgrade.rst:350
|
||||
msgid "An upgraded production database can also be requested via the `Upgrade page <https://upgrade.odoo.com/>`_. Once the database is uploaded, any modification to your production database will **not** be present on your upgraded database. This is why we recommend not using it during the upgrade process."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:360
|
||||
#: ../../content/administration/upgrade.rst:357
|
||||
msgid "When requesting an upgraded database for production purposes, the copy is submitted without a filestore. Therefore, the upgraded database filestore must be merged with the production filestore before deploying the new version."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:364
|
||||
#: ../../content/administration/upgrade.rst:361
|
||||
msgid "In case of an issue with your production database, you can request the assistance of Odoo via the `support page <https://odoo.com/help?stage=post_upgrade>`__ by selecting the option related to the upgrade in production."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:372
|
||||
#: ../../content/administration/upgrade.rst:369
|
||||
msgid "Service-level agreement (SLA)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:374
|
||||
#: ../../content/administration/upgrade.rst:371
|
||||
msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:377
|
||||
#: ../../content/administration/upgrade.rst:374
|
||||
msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement <upgrade>`. However, this section clarifies what upgrade services you can expect."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:382
|
||||
#: ../../content/administration/upgrade.rst:379
|
||||
msgid "Upgrade services covered by the SLA"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:384
|
||||
#: ../../content/administration/upgrade.rst:381
|
||||
msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:387
|
||||
#: ../../content/administration/upgrade.rst:384
|
||||
msgid "the upgrade of all **standard applications**;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:388
|
||||
#: ../../content/administration/upgrade.rst:385
|
||||
msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:390
|
||||
#: ../../content/administration/upgrade.rst:387
|
||||
msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:393
|
||||
#: ../../content/administration/upgrade.rst:390
|
||||
msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:397
|
||||
#: ../../content/administration/upgrade.rst:394
|
||||
msgid "Upgrade services not covered by the SLA"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:399
|
||||
#: ../../content/administration/upgrade.rst:396
|
||||
msgid "The following upgrade-related services are **not** included:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:401
|
||||
#: ../../content/administration/upgrade.rst:398
|
||||
msgid "the **cleaning** of pre-existing data and configurations while upgrading;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:402
|
||||
#: ../../content/administration/upgrade.rst:399
|
||||
msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:403
|
||||
#: ../../content/administration/upgrade.rst:400
|
||||
msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code <studio/automated-actions/action>`; and"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:406
|
||||
#: ../../content/administration/upgrade.rst:403
|
||||
msgid "**training** on using the upgraded version's features and workflows."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:409
|
||||
#: ../../content/administration/upgrade.rst:406
|
||||
msgid ":doc:`Odoo.sh documentation <odoo_sh>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/administration/upgrade.rst:410
|
||||
#: ../../content/administration/upgrade.rst:407
|
||||
msgid ":doc:`Supported Odoo versions <maintain/supported_versions>`"
|
||||
msgstr ""
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-12-21 13:43+0000\n"
|
||||
"POT-Creation-Date: 2024-01-19 15:28+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"
|
||||
@ -956,6 +956,7 @@ msgid "When the field `company_id` is made required on a model, a good practice
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/company.rst:168
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:132
|
||||
#: ../../content/developer/howtos/website_themes/setup.rst:75
|
||||
#: ../../content/developer/howtos/website_themes/theming.rst:496
|
||||
#: ../../content/developer/reference/frontend/javascript_reference.rst:1154
|
||||
@ -1599,6 +1600,7 @@ msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/scss_tips.rst:85
|
||||
#: ../../content/developer/howtos/scss_tips.rst:86
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:114
|
||||
#: ../../content/developer/howtos/website_themes/shapes.rst:139
|
||||
msgid "..."
|
||||
msgstr ""
|
||||
@ -1999,6 +2001,351 @@ msgstr ""
|
||||
msgid "**Do** in the case where the translation lookup is done when the JS file is *read*, use `_lt` instead of `_t` to translate the term when it is *used*::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:3
|
||||
msgid "Upgrade a customized database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:5
|
||||
msgid "Upgrading to a new version of Odoo can be challenging, especially if the database you work on contains custom modules. This page intent is to explain the technical process of upgrading a database with customized modules. Refer to :doc:`Upgrade documentation </administration/upgrade>` for guidance on how to upgrade a database without customized modules."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:10
|
||||
msgid "We consider a custom module, any module that extends the standard code of Odoo and that was not built with the Studio app. Before upgrading such a module, or before requesting its upgrade, have a look at the :ref:`upgrade/sla` to make sure who's responsible for it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:14
|
||||
msgid "While working on what we refer to as the **custom upgrade** of your database, keep in mind the goals of an upgrade:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:17
|
||||
msgid "Stay supported"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:18
|
||||
msgid "Get the latest features"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:19
|
||||
msgid "Enjoy the performance improvement"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:20
|
||||
msgid "Reduce the technical debt"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:21
|
||||
msgid "Benefit from security improvements"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:23
|
||||
msgid "With every new version of Odoo, changes are introduced. These changes can impact modules on which customization have been developed. This is the reason why upgrading a database that contains custom modules requires additional steps in order to upgrade the source code."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:27
|
||||
msgid "These are the steps to follow to upgrade customized databases:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:29
|
||||
msgid ":ref:`Stop the devolopments and challenge them <upgrade_custom/stop_developments>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:30
|
||||
msgid ":ref:`Request an upgraded database <upgrade_custom/request_upgrade>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:31
|
||||
msgid ":ref:`Make your module installable on an empty database <upgrade_custom/empty_database>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:32
|
||||
msgid ":ref:`Make your module installable on the upgraded database <upgrade_custom/upgraded_database>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:33
|
||||
msgid ":ref:`Test extensively and do a rehearsal <upgrade_custom/testing_rehearsal>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:34
|
||||
msgid ":ref:`Upgrade the production database <upgrade_custom/production>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:40
|
||||
msgid "Step 1: Stop the developments"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:42
|
||||
msgid "Starting an upgrade requires commitment and development resources. If developments keep being made at the same time, those features will need to be re-upgraded and tested every time you change them. This is why we recommend a complete freeze of the codebase when starting the upgrade process. Needless to say, bug fixing is exempt from this recommendation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:47
|
||||
msgid "Once you have stopped development, it is a good practice to assess the developments made and compare them with the features introduced between your current version and the version you are targeting. Challenge the developments as much as possible and find functional workarounds. Removing redundancy between your developments and the standard version of Odoo will lead to an eased upgrade process and reduce technical debt."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:54
|
||||
msgid "You can find information on the changes between versions in the `Release Notes <https:/odoo.com/page/release-notes>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:61
|
||||
msgid "Step 2: Request an upgraded database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:63
|
||||
msgid "Once the developments have stopped for the custom modules and the implemented features have been challenged to remove redundancy and unnecessary code, the next step is to request an upgraded test database. To do so, follow the steps mentioned in :ref:`upgrade/request-test-database`, depending on the hosting type of your database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:68
|
||||
msgid "The purpose of this stage is not to start working with the custom modules in the upgraded database, but to make sure the standard upgrade process works seamlessly, and the test database is delivered properly. If that's not the case, and the upgrade request fails, request the assistance of Odoo via the `support page <https://odoo.com/help?stage=migration>`_ by selecting the option related to testing the upgrade."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:78
|
||||
msgid "Step 3: Empty database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:80
|
||||
msgid "Before working on an upgraded test database, we recommend to make the custom developments work on an empty database in the targeted version of your upgrade. This ensures that the customization is compatible with the new version of Odoo, allows to analyze how it behaves and interacts with the new features, and guarantees that they will not cause any issues when upgrading the database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:85
|
||||
msgid "Making the custom modules work in an empty database also helps avoid changes and wrong configurations that might be present in the production database (like studio customization, customized website pages, email templates or translations). They are not intrinsically related to the custom modules and that can raise unwanted issues in this stage of the upgraded process."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:90
|
||||
msgid "To make custom modules work on an empty database we advise to follow these steps:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:92
|
||||
msgid ":ref:`upgrade_custom/empty_database/modules_installable`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:93
|
||||
msgid ":ref:`upgrade_custom/empty_database/test_fixes`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:94
|
||||
msgid ":ref:`upgrade_custom/empty_database/clean_code`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:95
|
||||
msgid ":ref:`Make standard tests run successfully <upgrade_custom/empty_database/standard_test>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:100
|
||||
msgid "Make custom modules installable"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:102
|
||||
msgid "The first step is to make the custom modules installable in the new Odoo version. This means, starting by ensuring there are no tracebacks or warnings during their installation. For this, install the custom modules, one by one, in an empty database of the new Odoo version and fix the tracebacks and warnings that arise from that."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:107
|
||||
msgid "This process will help detect issues during the installation of the modules. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:109
|
||||
msgid "Invalid module dependencies."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:110
|
||||
msgid "Syntax change: assets declaration, OWL updates, attrs."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:111
|
||||
msgid "References to standard fields, models, views not existing anymore or renamed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:112
|
||||
msgid "Xpath that moved or were removed from views."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:113
|
||||
msgid "Methods renamed or removed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:119
|
||||
msgid "Test and fixes"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:121
|
||||
msgid "Once there are no more tracebacks when installing the modules, the next step is to test them. Even if the custom modules are installable on an empty database, this does not guarantee there are no errors during their execution. Because of this, we encourage to test thoroughly all the customization to make sure everything is working as expected."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:126
|
||||
msgid "This process will help detect further issues that are not identified during the module installation and can only be detected in runtime. For example, deprecated calls to standard python or OWL functions, non-existing references to standard fields, etc."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:130
|
||||
msgid "We recommend to test all the customization, especially the following elements:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:133
|
||||
msgid "Email templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:134
|
||||
msgid "Reports"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:135
|
||||
msgid "Server actions and automated actions"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:136
|
||||
msgid "Changes in the standard workflows"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:137
|
||||
#: ../../content/developer/tutorials/backend.rst:716
|
||||
msgid "Computed fields"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:139
|
||||
msgid "We also encourage to write automated tests to save time during the testing iterations, increase the test coverage, and ensure that the changes and fixes introduced do not break the existing flows. If there are tests already implemented in the customization, make sure they are upgraded to the new Odoo version and run successfully, fixing issues that might be present."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:147
|
||||
msgid "Clean the code"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:149
|
||||
msgid "At this stage of the upgrade process, we also suggest to clean the code as much as possible. This includes:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:152
|
||||
msgid "Remove redundant and unnecessary code."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:153
|
||||
msgid "Remove features that are now part of Odoo standard, as described in :ref:`upgrade_custom/stop_developments`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:155
|
||||
msgid "Clean commented code if it is not needed anymore."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:156
|
||||
msgid "Refactor the code (functions, fields, views, reports, etc.) if needed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:161
|
||||
msgid "Standard tests"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:163
|
||||
msgid "Once the previous steps are completed, we advise to make sure all standard tests associated to the dependencies of the custom module pass. Standard tests ensure the validation of the code logic and prevent data corruption. They will help you identify bugs or unwanted behavior before you work on your database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:168
|
||||
msgid "In case there are standard test failing, we suggest to analyze the reason for their failure:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:170
|
||||
msgid "The customization changes the standard workflow: Adapt the standard test to your workflow."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:171
|
||||
msgid "The customization did not take into account a special flow: Adapt your customization to ensure it works for all the standard workflows."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:178
|
||||
msgid "Step 4: Upgraded database"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:180
|
||||
msgid "Once the custom modules are installable and working properly in an empty database, it is time to make them work on an :ref:`upgraded database <upgrade/request-test-database>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:183
|
||||
msgid "To make sure the custom code is working flawlessly in the new version, follow these steps:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:185
|
||||
msgid ":ref:`upgrade_custom/upgraded_database/migrate_data`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:186
|
||||
msgid ":ref:`upgrade_custom/upgraded_database/test_custom`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:191
|
||||
msgid "Migrate the data"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:193
|
||||
msgid "During the upgrade of the custom modules, you might have to use migration scripts to reflect changes from the source code to their corresponding data."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:196
|
||||
msgid "Any technical data that was renamed during the upgrade of the custom code (models, fields, external identifiers) should be renamed using migration scripts to avoid data loss during the module upgrade."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:199
|
||||
msgid "Data from standard models removed from the source code of the newer Odoo version and from the database during the standard upgrade process might need to be recovered from the old model table if it is still present."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:203
|
||||
msgid "Migration scripts can also be used to:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:205
|
||||
msgid "Ease the processing time of an upgrade. For example, to store the value of computed stored fields on models with an excessive number of records by using SQL queries."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:207
|
||||
msgid "Recompute fields in case the computation of their value has changed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:208
|
||||
msgid "Uninstall unwanted custom modules."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:209
|
||||
msgid "Correct faulty data or wrong configurations."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:214
|
||||
msgid "Test the custom modules"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:216
|
||||
msgid "To make sure the custom modules work properly with your data in the upgraded database, they need to be tested as well. This helps ensure both the standard and the custom data stored in the database are consistent and that nothing was lost during the upgrade process."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:220
|
||||
msgid "Things to pay attention to:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:222
|
||||
msgid "Views not working: During the upgrade, if a view causes issues because of its content, it gets disabled. You can find the information on disabled views on the :ref:`Upgrade report <upgrade/upgrade_report>`. This view needs to be activated again. To achieve this, we recommend the use of migration scripts."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:226
|
||||
msgid ":doc:`Module data <../tutorials/define_module_data>` not updated: Custom records that have the ``noupdate`` flag are not updated when upgrading the module in the new database. For the custom data that needs to be updated due to changes in the new version, we recommend to use migration scripts to do so."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:235
|
||||
msgid "Step 5: Testing and rehearsal"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:237
|
||||
msgid "When the custom modules are working properly in the upgraded database, it is crucial to do another round of testing to assess the database usability and detect any issues that might have gone unnoticed in previous tests. For further information about testing the upgraded database, check :ref:`upgrade/test_your_db`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:242
|
||||
msgid "As mentioned in :ref:`upgrade/upgrade-prod`, both standard upgrade scripts and your database are constantly evolving. Therefore it is highly recommended to frequently request new upgraded test databases and ensure that the upgrade process is still successful."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:246
|
||||
msgid "In addition to that, make a full rehearsal of the upgrade process the day before upgrading the production database to avoid undesired behavior during the upgrade and to detect any issue that might have occurred with the migrated data."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:254
|
||||
msgid "Step 6: Production upgrade"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/upgrade_custom_db.rst:256
|
||||
msgid "Once you are confident about upgrading your production database, follow the process described on :ref:`upgrade/upgrade-prod`, depending on the hosting type of your database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/web_services.rst:3
|
||||
msgid "Web Services"
|
||||
msgstr ""
|
||||
@ -4186,7 +4533,7 @@ msgid ":option:`--addons-path <odoo-bin --addons-path>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/howtos/website_themes/setup.rst:213
|
||||
#: ../../content/developer/reference/cli.rst:807
|
||||
#: ../../content/developer/reference/cli.rst:829
|
||||
msgid "Comma-separated list of directories in which modules are stored. These directories are scanned for modules."
|
||||
msgstr ""
|
||||
|
||||
@ -14114,435 +14461,447 @@ msgid "Logging"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:472
|
||||
msgid "By default, Odoo displays all logging of level_ ``info`` except for workflow logging (``warning`` only), and log output is sent to ``stdout``. Various options are available to redirect logging to other destinations and to customize the amount of logging output."
|
||||
msgid "By default, Odoo displays all logging of level_ ``INFO``, ``WARNING`` and ``ERROR``. All logs independently of the level are output on ``stderr``. Various options are available to redirect logging to other destinations and to customize the verbosity."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:479
|
||||
msgid "sends logging output to the specified file instead of stdout. On Unix, the file `can be managed by external log rotation programs <https://docs.python.org/3/library/logging.handlers.html#watchedfilehandler>`_ and will automatically be reopened when replaced"
|
||||
#: ../../content/developer/reference/cli.rst:478
|
||||
msgid "sends logging output to the specified file instead of ``stderr``. On Unix, the file `can be managed by external log rotation programs <https://docs.python.org/3/library/logging.handlers.html#watchedfilehandler>`_ and will automatically be reopened when replaced"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:486
|
||||
#: ../../content/developer/reference/cli.rst:485
|
||||
msgid "logs to the system's event logger: `syslog on unices <https://docs.python.org/3/library/logging.handlers.html#sysloghandler>`_ and `the Event Log on Windows <https://docs.python.org/3/library/logging.handlers.html#nteventloghandler>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:489
|
||||
#: ../../content/developer/reference/cli.rst:488
|
||||
msgid "Neither is configurable"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:493
|
||||
#: ../../content/developer/reference/cli.rst:492
|
||||
msgid "logs to the ``ir.logging`` model (``ir_logging`` table) of the specified database. The database can be the name of a database in the \"current\" PostgreSQL, or `a PostgreSQL URI`_ for e.g. log aggregation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:499
|
||||
#: ../../content/developer/reference/cli.rst:498
|
||||
msgid ":samp:`{LOGGER}:{LEVEL}`, enables ``LOGGER`` at the provided ``LEVEL`` e.g. ``odoo.models:DEBUG`` will enable all logging messages at or above ``DEBUG`` level in the models."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:503
|
||||
#: ../../content/developer/reference/cli.rst:502
|
||||
msgid "The colon ``:`` is mandatory"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:504
|
||||
#: ../../content/developer/reference/cli.rst:503
|
||||
msgid "The logger can be omitted to configure the root (default) handler"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:505
|
||||
#: ../../content/developer/reference/cli.rst:504
|
||||
msgid "If the level is omitted, the logger is set to ``INFO``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:507
|
||||
#: ../../content/developer/reference/cli.rst:506
|
||||
msgid "The option can be repeated to configure multiple loggers e.g."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:515
|
||||
#: ../../content/developer/reference/cli.rst:514
|
||||
msgid "enables DEBUG logging of HTTP requests and responses, equivalent to ``--log-handler=odoo.http:DEBUG``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:520
|
||||
#: ../../content/developer/reference/cli.rst:519
|
||||
msgid "enables DEBUG logging of SQL querying, equivalent to ``--log-handler=odoo.sql_db:DEBUG``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:525
|
||||
#: ../../content/developer/reference/cli.rst:524
|
||||
msgid "Shortcut to more easily set predefined levels on specific loggers. \"real\" levels (``critical``, ``error``, ``warn``, ``debug``) are set on the ``odoo`` and ``werkzeug`` loggers (except for ``debug`` which is only set on ``odoo``)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:530
|
||||
#: ../../content/developer/reference/cli.rst:529
|
||||
msgid "Odoo also provides debugging pseudo-levels which apply to different sets of loggers:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:535
|
||||
#: ../../content/developer/reference/cli.rst:534
|
||||
msgid "``debug_sql``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:534
|
||||
#: ../../content/developer/reference/cli.rst:533
|
||||
msgid "sets the SQL logger to ``debug``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:536
|
||||
#: ../../content/developer/reference/cli.rst:535
|
||||
msgid "equivalent to ``--log-sql``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:539
|
||||
#: ../../content/developer/reference/cli.rst:538
|
||||
msgid "``debug_rpc``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:538
|
||||
#: ../../content/developer/reference/cli.rst:537
|
||||
msgid "sets the ``odoo`` and HTTP request loggers to ``debug``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:540
|
||||
#: ../../content/developer/reference/cli.rst:539
|
||||
msgid "equivalent to ``--log-level debug --log-request``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:545
|
||||
#: ../../content/developer/reference/cli.rst:544
|
||||
msgid "``debug_rpc_answer``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:542
|
||||
#: ../../content/developer/reference/cli.rst:541
|
||||
msgid "sets the ``odoo`` and HTTP request and response loggers to ``debug``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:545
|
||||
#: ../../content/developer/reference/cli.rst:544
|
||||
msgid "equivalent to ``--log-level debug --log-request --log-response``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:549
|
||||
#: ../../content/developer/reference/cli.rst:548
|
||||
msgid "In case of conflict between :option:`--log-level` and :option:`--log-handler`, the latter is used"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:555
|
||||
#: ../../content/developer/reference/cli.rst:554
|
||||
msgid "Multiprocessing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:559
|
||||
#: ../../content/developer/reference/cli.rst:558
|
||||
msgid "if ``count`` is not 0 (the default), enables multiprocessing and sets up the specified number of HTTP workers (sub-processes processing HTTP and RPC requests)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:563
|
||||
#: ../../content/developer/reference/cli.rst:562
|
||||
msgid "multiprocessing mode is only available on Unix-based systems"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:565
|
||||
#: ../../content/developer/reference/cli.rst:564
|
||||
msgid "A number of options allow limiting and recycling workers:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:569
|
||||
#: ../../content/developer/reference/cli.rst:568
|
||||
msgid "Number of requests a worker will process before being recycled and restarted."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:572
|
||||
#: ../../content/developer/reference/cli.rst:571
|
||||
msgid "Defaults to *8196*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:576
|
||||
#: ../../content/developer/reference/cli.rst:575
|
||||
msgid "Maximum allowed virtual memory per worker in bytes. If the limit is exceeded, the worker is killed and recycled at the end of the current request."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:579
|
||||
#: ../../content/developer/reference/cli.rst:578
|
||||
msgid "Defaults to *2048MiB (2048\\*1024\\*1024B)*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:583
|
||||
#: ../../content/developer/reference/cli.rst:582
|
||||
msgid "Hard limit on virtual memory in bytes, any worker exceeding the limit will be immediately killed without waiting for the end of the current request processing."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:587
|
||||
#: ../../content/developer/reference/cli.rst:586
|
||||
msgid "Defaults to *2560MiB (2560\\*1024\\*1024B)*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:591
|
||||
#: ../../content/developer/reference/cli.rst:590
|
||||
msgid "Prevents the worker from using more than <limit> CPU seconds for each request. If the limit is exceeded, the worker is killed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:594
|
||||
#: ../../content/developer/reference/cli.rst:593
|
||||
msgid "Defaults to *60*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:598
|
||||
#: ../../content/developer/reference/cli.rst:597
|
||||
msgid "Prevents the worker from taking longer than <limit> seconds to process a request. If the limit is exceeded, the worker is killed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:601
|
||||
#: ../../content/developer/reference/cli.rst:600
|
||||
msgid "Differs from :option:`--limit-time-cpu` in that this is a \"wall time\" limit including e.g. SQL queries."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:604
|
||||
#: ../../content/developer/reference/cli.rst:603
|
||||
msgid "Defaults to *120*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:608
|
||||
#: ../../content/developer/reference/cli.rst:607
|
||||
msgid "number of workers dedicated to :ref:`cron <reference/actions/cron>` jobs. Defaults to *2*. The workers are threads in multi-threading mode and processes in multi-processing mode."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:611
|
||||
#: ../../content/developer/reference/cli.rst:610
|
||||
msgid "For multi-processing mode, this is in addition to the HTTP worker processes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:616
|
||||
#: ../../content/developer/reference/cli.rst:615
|
||||
msgid "Configuration file"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:620
|
||||
#: ../../content/developer/reference/cli.rst:619
|
||||
msgid "Most of the command-line options can also be specified via a configuration file. Most of the time, they use similar names with the prefix ``-`` removed and other ``-`` are replaced by ``_`` e.g. :option:`--db-template` becomes ``db_template``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:625
|
||||
#: ../../content/developer/reference/cli.rst:624
|
||||
msgid "Some conversions don't match the pattern:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:627
|
||||
#: ../../content/developer/reference/cli.rst:626
|
||||
msgid ":option:`--db-filter` becomes ``dbfilter``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:628
|
||||
#: ../../content/developer/reference/cli.rst:627
|
||||
msgid ":option:`--no-http` corresponds to the ``http_enable`` boolean"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:629
|
||||
#: ../../content/developer/reference/cli.rst:628
|
||||
msgid "logging presets (all options starting with ``--log-`` except for :option:`--log-handler` and :option:`--log-db`) just add content to ``log_handler``, use that directly in the configuration file"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:632
|
||||
#: ../../content/developer/reference/cli.rst:631
|
||||
msgid ":option:`--smtp` is stored as ``smtp_server``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:633
|
||||
#: ../../content/developer/reference/cli.rst:632
|
||||
msgid ":option:`--database` is stored as ``db_name``"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:634
|
||||
#: ../../content/developer/reference/cli.rst:633
|
||||
msgid ":option:`--i18n-import` and :option:`--i18n-export` aren't available at all from configuration files"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:639
|
||||
#: ../../content/developer/reference/cli.rst:638
|
||||
msgid "The default configuration file is :file:`{$HOME}/.odoorc` which can be overridden using :option:`--config <odoo-bin -c>`. Specifying :option:`--save <odoo-bin -s>` will save the current configuration state back to that file. The configuration items relative to the command-line are to be specified in the section ``[options]``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:645
|
||||
#: ../../content/developer/reference/cli.rst:644
|
||||
msgid "Here is a sample file:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:670
|
||||
#: ../../content/developer/reference/cli.rst:669
|
||||
msgid "Shell"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:672
|
||||
msgid "Odoo command-line also allows to launch odoo as a python console environment. This enables direct interaction with the :ref:`orm <reference/orm>` and its functionalities."
|
||||
#: ../../content/developer/reference/cli.rst:671
|
||||
msgid "The Odoo command line also allows launching Odoo as a Python console environment, enabling direct interaction with the :ref:`orm <reference/orm>` and its functionalities."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:682
|
||||
msgid "Specify a preferred REPL to use in shell mode."
|
||||
#: ../../content/developer/reference/cli.rst:680
|
||||
msgid "Adding an exclamation mark to all contacts' names:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:688
|
||||
msgid "Scaffolding"
|
||||
#: ../../content/developer/reference/cli.rst:696
|
||||
msgid "By default, the shell is running in transaction mode. This means that any change made to the database is rolled back when exiting the shell. To commit changes, use `env.cr.commit()`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:692
|
||||
msgid "Scaffolding is the automated creation of a skeleton structure to simplify bootstrapping (of new modules, in the case of Odoo). While not necessary it avoids the tedium of setting up basic structures and looking up what all starting requirements are."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:697
|
||||
msgid "Scaffolding is available via the :command:`odoo-bin scaffold` subcommand."
|
||||
#: ../../content/developer/reference/cli.rst:701
|
||||
msgid "Specify a preferred REPL to use in shell mode. This shell is started with the `env` variable already initialized to be able to access the ORM and other Odoo modules."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:705
|
||||
msgid "the name of the module to create, may munged in various manners to generate programmatic names (e.g. module directory name, model names, …)"
|
||||
msgid ":ref:`reference/orm/environment`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:710
|
||||
msgid "directory in which to create the new module, defaults to the current directory"
|
||||
msgid "Scaffolding"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:715
|
||||
msgid "a template directory, files are passed through jinja2_ then copied to the ``destination`` directory"
|
||||
#: ../../content/developer/reference/cli.rst:714
|
||||
msgid "Scaffolding is the automated creation of a skeleton structure to simplify bootstrapping (of new modules, in the case of Odoo). While not necessary it avoids the tedium of setting up basic structures and looking up what all starting requirements are."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:719
|
||||
msgid "Scaffolding is available via the :command:`odoo-bin scaffold` subcommand."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:727
|
||||
msgid "the name of the module to create, may munged in various manners to generate programmatic names (e.g. module directory name, model names, …)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:732
|
||||
msgid "directory in which to create the new module, defaults to the current directory"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:737
|
||||
msgid "a template directory, files are passed through jinja2_ then copied to the ``destination`` directory"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:741
|
||||
msgid "This will create module *my_module* in directory */addons/*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:724
|
||||
#: ../../content/developer/reference/cli.rst:746
|
||||
msgid "Database Population"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:728
|
||||
#: ../../content/developer/reference/cli.rst:750
|
||||
msgid "Odoo CLI supports database population features. If the feature is :ref:`implemented on a given model <reference/performance/populate/methods>`, it allows automatic data generation of the model's records to test your modules in databases containing non-trivial amounts of records."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:739
|
||||
#: ../../content/developer/reference/cli.rst:761
|
||||
msgid "list of models for which the database should be filled"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:743
|
||||
#: ../../content/developer/reference/cli.rst:765
|
||||
msgid "population size, the actual records number depends on the model's `_populate_sizes` attribute. The generated records content is specified by the :meth:`~odoo.models._populate_factories` method of a given model (cf. the :file:`populate` folder of modules for further details)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:748
|
||||
#: ../../content/developer/reference/cli.rst:770
|
||||
msgid ":ref:`reference/performance/populate`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:753
|
||||
#: ../../content/developer/reference/cli.rst:775
|
||||
msgid "Cloc"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:757
|
||||
#: ../../content/developer/reference/cli.rst:779
|
||||
msgid "Odoo Cloc is a tool to count the number of relevant lines written in Python, Javascript, CSS, SCSS, or XML. This can be used as a rough metric for pricing maintenance of extra modules."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:762
|
||||
#: ../../content/developer/reference/cli.rst:784
|
||||
msgid "Command-line options"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:767
|
||||
#: ../../content/developer/reference/cli.rst:789
|
||||
msgid "Process the code of all extra modules installed on the provided database, and of all server actions and computed fields manually created in the provided database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:769
|
||||
#: ../../content/developer/reference/cli.rst:791
|
||||
msgid "The :option:`--addons-path` option is required to specify the path(s) to the module folder(s)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:772
|
||||
#: ../../content/developer/reference/cli.rst:794
|
||||
msgid "If combined with :option:`--path`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:779
|
||||
#: ../../content/developer/reference/cli.rst:801
|
||||
msgid ":ref:`reference/cmdline/cloc/database-option`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:784
|
||||
#: ../../content/developer/reference/cli.rst:806
|
||||
msgid "Process the files in the provided path."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:787
|
||||
#: ../../content/developer/reference/cli.rst:809
|
||||
msgid "If combined with :option:`--database`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:794
|
||||
#: ../../content/developer/reference/cli.rst:816
|
||||
msgid "Multiple paths can be provided by repeating the option."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:801
|
||||
#: ../../content/developer/reference/cli.rst:823
|
||||
msgid ":ref:`reference/cmdline/cloc/path-option`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:808
|
||||
#: ../../content/developer/reference/cli.rst:830
|
||||
msgid "Required if the :option:`--database` option is used."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:813
|
||||
#: ../../content/developer/reference/cli.rst:835
|
||||
msgid "Specify a configuration file to use in place of the :option:`--addons-path` option."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:822
|
||||
#: ../../content/developer/reference/cli.rst:844
|
||||
msgid "Show the details of lines counted for each file."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:826
|
||||
#: ../../content/developer/reference/cli.rst:848
|
||||
msgid "Processed files"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:831
|
||||
#: ../../content/developer/reference/cli.rst:853
|
||||
msgid "With the :option:`--database` option"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:833
|
||||
#: ../../content/developer/reference/cli.rst:855
|
||||
msgid "Odoo Cloc counts the lines in each file of extra installed modules in a given database. In addition, it counts the Python lines of server actions and custom computed fields that have been directly created in the database or imported. Finally, it counts the lines of code of Javascript, CSS, and SCSS files, and of QWeb views from imported modules."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:839
|
||||
#: ../../content/developer/reference/cli.rst:861
|
||||
msgid "Some files are excluded from the count by default:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:841
|
||||
#: ../../content/developer/reference/cli.rst:863
|
||||
msgid "The manifest (:file:`__manifest__.py` or :file:`__openerp__.py`)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:842
|
||||
#: ../../content/developer/reference/cli.rst:864
|
||||
msgid "The contents of the folder :file:`static/lib`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:843
|
||||
#: ../../content/developer/reference/cli.rst:865
|
||||
msgid "The tests defined in the folder :file:`tests` and :file:`static/tests`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:844
|
||||
#: ../../content/developer/reference/cli.rst:866
|
||||
msgid "The migrations scripts defined in the folder :file:`migrations` and `upgrades`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:845
|
||||
#: ../../content/developer/reference/cli.rst:867
|
||||
msgid "The XML files declared in the ``demo`` or ``demo_xml`` sections of the manifest"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:847
|
||||
#: ../../content/developer/reference/cli.rst:869
|
||||
msgid "For special cases, a list of files that should be ignored by Odoo Cloc can be defined per module. This is specified by the ``cloc_exclude`` entry of the manifest:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:860
|
||||
#: ../../content/developer/reference/cli.rst:882
|
||||
msgid "The pattern ``**/*`` can be used to ignore an entire module. This can be useful to exclude a module from maintenance service costs."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:862
|
||||
#: ../../content/developer/reference/cli.rst:884
|
||||
msgid "For more information about the pattern syntax, see `glob <https://docs.python.org/3/library/pathlib.html#pathlib.Path.glob>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:867
|
||||
#: ../../content/developer/reference/cli.rst:889
|
||||
msgid "With the :option:`--path` option"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:869
|
||||
#: ../../content/developer/reference/cli.rst:891
|
||||
msgid "This method works the same as with the :ref:`--database option <reference/cmdline/cloc/database-option>` if a manifest file is present in the given folder. Otherwise, it counts all files."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:875
|
||||
#: ../../content/developer/reference/cli.rst:897
|
||||
msgid "Identifying Extra Modules"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:877
|
||||
#: ../../content/developer/reference/cli.rst:899
|
||||
msgid "To distinguish between standard and extra modules, Odoo Cloc uses the following heuristic: modules that are located (real file system path, after following symbolic links) in the same parent directory as the ``base``, ``web`` or ``web_enterprise`` standard modules are considered standard. Other modules are treated as extra modules."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:884
|
||||
#: ../../content/developer/reference/cli.rst:906
|
||||
#: ../../content/developer/reference/frontend/services.rst:662
|
||||
msgid "Error Handling"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:886
|
||||
#: ../../content/developer/reference/cli.rst:908
|
||||
msgid "Some file cannot be counted by Odoo Cloc. Those file are reported at the end of the output."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:890
|
||||
#: ../../content/developer/reference/cli.rst:912
|
||||
msgid "Max file size exceeded"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:892
|
||||
#: ../../content/developer/reference/cli.rst:914
|
||||
msgid "Odoo Cloc rejects any file larger than 25MB. Usually, source files are smaller than 1 MB. If a file is rejected, it may be:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:895
|
||||
#: ../../content/developer/reference/cli.rst:917
|
||||
msgid "A generated XML file that contains lots of data. It should be excluded in the manifest."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:896
|
||||
#: ../../content/developer/reference/cli.rst:918
|
||||
msgid "A JavaScript library that should be placed in the :file:`static/lib` folder."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:899
|
||||
#: ../../content/developer/reference/cli.rst:921
|
||||
msgid "Syntax Error"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:901
|
||||
#: ../../content/developer/reference/cli.rst:923
|
||||
msgid "Odoo Cloc cannot count the lines of code of a Python file with a syntax problem. If an extra module contains such files, they should be fixed to allow the module to load. If the module works despite the presence of those files, they are probably not loaded and should therefore be removed from the module, or at least excluded in the manifest via ``cloc_exclude``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:908
|
||||
#: ../../content/developer/reference/cli.rst:930
|
||||
msgid "TSConfig Generator"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:912
|
||||
#: ../../content/developer/reference/cli.rst:934
|
||||
msgid "When working on javascript, there are ways to help your editor providing you with powerful auto-completion. One of those ways is the use of a tsconfig.json file. Originally meant for typescript, editors can use its information with plain javascript also. With this config file, you will now have full auto-completion across modules."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/cli.rst:917
|
||||
#: ../../content/developer/reference/cli.rst:939
|
||||
msgid "The command to generate this files takes as many unnamed arguments as you need. Those are relative paths to your addon directories. In the example below, we move up one folder to save the tsconfig file in the folder containing community and enterprise."
|
||||
msgstr ""
|
||||
|
||||
@ -28856,7 +29215,7 @@ msgid "the content of the inheritance spec should be ``attribute`` elements with
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/user_interface/view_records.rst:299
|
||||
msgid "if the ``attribute`` element has a body, a new attributed named after its ``name`` is created on the matched node with the ``attribute`` element's text as value"
|
||||
msgid "if the ``attribute`` element has a body, a new attribute named after its ``name`` is created on the matched node with the ``attribute`` element's text as value"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/reference/user_interface/view_records.rst:302
|
||||
@ -29774,10 +30133,6 @@ msgstr ""
|
||||
msgid "The value of a computed field usually depends on the values of other fields on the computed record. The ORM expects the developer to specify those dependencies on the compute method with the decorator :func:`~odoo.api.depends`. The given dependencies are used by the ORM to trigger the recomputation of the field whenever some of its dependencies have been modified::"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/tutorials/backend.rst:716
|
||||
msgid "Computed fields"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/tutorials/backend.rst:718
|
||||
msgid "Add the percentage of taken seats to the *Session* model"
|
||||
msgstr ""
|
||||
@ -34004,7 +34359,7 @@ msgid "One could argue that we can already do these things by changing the state
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/tutorials/getting_started/10_actions.rst:20
|
||||
msgid "Action Type"
|
||||
msgid "Object Type"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/tutorials/getting_started/10_actions.rst:22
|
||||
@ -34112,7 +34467,7 @@ msgid "Pay attention: in real life only one offer can be accepted for a given pr
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/tutorials/getting_started/10_actions.rst:126
|
||||
msgid "Object Type"
|
||||
msgid "Action Type"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/developer/tutorials/getting_started/10_actions.rst:128
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-12-21 13:43+0000\n"
|
||||
"POT-Creation-Date: 2024-01-19 15:28+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"
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
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 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-12-21 13:43+0000\n"
|
||||
"POT-Creation-Date: 2024-01-19 15:28+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"
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-12-21 13:43+0000\n"
|
||||
"POT-Creation-Date: 2024-01-19 15:28+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"
|
||||
@ -5989,22 +5989,22 @@ msgid "Type `/` in the editor box to structure and format your content. You can
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:23
|
||||
msgid "You can create a new to-do on the fly from anywhere in Odoo by clicking the clock button and then :guilabel:`Add a To-Do`."
|
||||
msgid "You can create a new to-do on the fly from anywhere in Odoo by opening the **command palette tool** with the keyboard shortcut ´ctrl+k´ and clicking :guilabel:`Add a To-Do`, or by clicking the clock button and then :guilabel:`Add a To-Do`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:0
|
||||
msgid "Adding a to-do on the fly"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:30
|
||||
#: ../../content/applications/productivity/to_do.rst:31
|
||||
msgid "Converting to-dos into project tasks"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:32
|
||||
#: ../../content/applications/productivity/to_do.rst:33
|
||||
msgid "If you use the :doc:`Project app <../services/project>`, you can convert to-dos into project tasks. To do so, open a to-do and click the gear button (:guilabel:`⚙`), then :guilabel:`Convert to Task`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:35
|
||||
#: ../../content/applications/productivity/to_do.rst:36
|
||||
msgid "Next, select the :guilabel:`Project`, :guilabel:`Assignees`, and :guilabel:`Tags`, then click :guilabel:`Convert to Task`. The to-do is now a project task and appears in the selected project."
|
||||
msgstr ""
|
||||
|
||||
@ -6012,11 +6012,11 @@ msgstr ""
|
||||
msgid "Converting a to-do into a task"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:42
|
||||
#: ../../content/applications/productivity/to_do.rst:43
|
||||
msgid "Managing the to-do pipeline"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:44
|
||||
#: ../../content/applications/productivity/to_do.rst:45
|
||||
msgid "Your assigned **to-dos** are displayed on the app dashboard. You can drag and drop a to-do to move it from one stage to another."
|
||||
msgstr ""
|
||||
|
||||
@ -6024,11 +6024,11 @@ msgstr ""
|
||||
msgid "Example of a to-do pipeline"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:51
|
||||
#: ../../content/applications/productivity/to_do.rst:52
|
||||
msgid "Click the :guilabel:`+ Personal Stage` button on the left of the pipeline to create a new stage."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:53
|
||||
#: ../../content/applications/productivity/to_do.rst:54
|
||||
msgid "Click the gear button (:guilabel:`⚙`) next to a stage to :guilabel:`Fold`, :guilabel:`Edit`, or :guilabel:`Delete` it."
|
||||
msgstr ""
|
||||
|
||||
@ -6036,11 +6036,11 @@ msgstr ""
|
||||
msgid "Stage settings button"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:60
|
||||
#: ../../content/applications/productivity/to_do.rst:61
|
||||
msgid "Scheduling activities"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:62
|
||||
#: ../../content/applications/productivity/to_do.rst:63
|
||||
msgid "To schedule an activity on a to-do, click the clock button on the app dashboard, then the :guilabel:`+ Schedule an activity` button."
|
||||
msgstr ""
|
||||
|
||||
@ -6048,39 +6048,39 @@ msgstr ""
|
||||
msgid "Scheduling an activity from the To-do dashboard"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:68
|
||||
#: ../../content/applications/productivity/to_do.rst:69
|
||||
msgid "To create the activity:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:70
|
||||
#: ../../content/applications/productivity/to_do.rst:71
|
||||
msgid "Select an :guilabel:`Activity Type`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:71
|
||||
#: ../../content/applications/productivity/to_do.rst:72
|
||||
msgid "Select a :guilabel:`Due date`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:72
|
||||
#: ../../content/applications/productivity/to_do.rst:73
|
||||
msgid "Choose who the activity should be :guilabel:`Assigned to`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:73
|
||||
#: ../../content/applications/productivity/to_do.rst:74
|
||||
msgid "Add a brief :guilabel:`Summary` if needed. You can add a more elaborate description in the :guilabel:`Log a note` box."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:76
|
||||
#: ../../content/applications/productivity/to_do.rst:77
|
||||
msgid "Click :guilabel:`Schedule` to complete the action."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:79
|
||||
#: ../../content/applications/productivity/to_do.rst:80
|
||||
msgid "The :guilabel:`To Do` activity is *not* a to-do task. Selecting it does not create a to-do task."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:82
|
||||
#: ../../content/applications/productivity/to_do.rst:83
|
||||
msgid "Viewing to-dos in the Project app"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:84
|
||||
#: ../../content/applications/productivity/to_do.rst:85
|
||||
msgid "If you use the :doc:`Project app <../services/project>`, your to-dos also appear as private tasks under the :guilabel:`My Tasks` view."
|
||||
msgstr ""
|
||||
|
||||
@ -6088,7 +6088,7 @@ msgstr ""
|
||||
msgid "Example of a \"My Tasks\" pipeline in the Project app"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/productivity/to_do.rst:91
|
||||
#: ../../content/applications/productivity/to_do.rst:92
|
||||
msgid "A padlock icon is visible on your private tasks to quickly identify them among your project tasks."
|
||||
msgstr ""
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-12-21 13:43+0000\n"
|
||||
"POT-Creation-Date: 2024-01-19 15:28+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"
|
||||
@ -2537,7 +2537,7 @@ msgid "Project settings"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/services/project/project_management.rst:58
|
||||
msgid "`Odoo Tutorials: Customize your project <https://www.odoo.com/slides/slide/customize-your-project-1662?fullscreen=1>`_"
|
||||
msgid "`Odoo Tutorials: Customize projects <https://www.odoo.com/slides/slide/customize-projects-3615?fullscreen=1>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/services/project/project_management.rst:61
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-12-21 13:43+0000\n"
|
||||
"POT-Creation-Date: 2024-01-19 15:28+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"
|
||||
@ -20,6 +20,206 @@ msgstr ""
|
||||
msgid "Websites"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:3
|
||||
msgid "Blog"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:5
|
||||
msgid "**Odoo Blog** allows you to create and manage blog posts on your website to engage your audience and build a community."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:9
|
||||
msgid "If the Blog module is not yet installed, click :guilabel:`+New` on the website builder, select :guilabel:`Blog Post`, and click :guilabel:`Install`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:13
|
||||
msgid "Creating a blog"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:15
|
||||
msgid "To create or edit a blog, go to :menuselection:`Website --> Configuration --> Blogs: Blogs`. Click :guilabel:`New`, and enter the :guilabel:`Blog Name` and the :guilabel:`Blog Subtitle`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:18
|
||||
msgid "The :guilabel:`Blog` menu item is added to your website's menu the first time you create a blog and gathers all your blogs."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:22
|
||||
msgid "Adding a blog post"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:24
|
||||
msgid "Go to your website, click :guilabel:`+New` in the top-right corner, and select :guilabel:`Blog Post`. In the pop-up, **select the blog** where the post should appear, write the post's :guilabel:`Title`, and :guilabel:`Save`. You can then write the post's content and customize the page using the website builder."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:30
|
||||
msgid "Illustrate your articles with copyright-free images from :doc:`Unsplash <website/configuration/unsplash>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:32
|
||||
msgid "Type `/` in the text editor to format and add elements to your text."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:35
|
||||
msgid "Don't forget to toggle the :guilabel:`Unpublished` switch in the top-right corner to publish your post."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:39
|
||||
msgid "Using tags"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:41
|
||||
msgid "Tags let visitors filter all posts sharing the same tag. By default, they are displayed at the bottom of posts, but can also be displayed on the blog's main page. To do so, click :menuselection:`Edit --> Customize` and enable the :guilabel:`Sidebar`. By default, the sidebar's :guilabel:`Tags List` is enabled."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:46
|
||||
msgid "To create a tag, go to :menuselection:`Website --> Configuration --> Blogs: Tags` and click :guilabel:`New`. Fill in the:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:49
|
||||
msgid ":guilabel:`Name`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:50
|
||||
msgid ":guilabel:`Category`: tag categories let you group tags displayed on the sidebar by theme."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:51
|
||||
msgid ":guilabel:`Used in`: to apply the tag to existing blog posts, click :guilabel:`Add a line`, select the posts, and click :guilabel:`Select`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:54
|
||||
msgid "You can add and create tags directly from posts by clicking :menuselection:`Edit --> Customize` and select the post's cover. Under :guilabel:`Tags`, click :guilabel:`Choose a record...`, and select or create a tag."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:-1
|
||||
msgid "Adding a tag to a blog post"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:62
|
||||
msgid "To manage tag categories, go to :menuselection:`Website --> Configuration --> Blogs: Tag Categories`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:66
|
||||
msgid "Customizing blog homepages"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:68
|
||||
msgid "Customize the content of blog homepages by opening a blog homepage and clicking :menuselection:`Edit --> Customize`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:72
|
||||
msgid "Settings apply to **all** blogs homepages."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:74
|
||||
msgid ":guilabel:`Top Banner`: :guilabel:`Name/Latest Post` displays the title of the latest post on the top banner, while :guilabel:`Drop Zone for Building Blocks` removes the top banner and lets you use any building block instead."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:78
|
||||
msgid ":guilabel:`Layout`: organizes posts as a :guilabel:`Grid` or :guilabel:`List`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:80
|
||||
msgid ":guilabel:`Cards`: adds a *card* effect."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:81
|
||||
msgid ":guilabel:`Increase Readability`: improves the text's readability."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:83
|
||||
msgid ":guilabel:`Sidebar`: displays a sidebar containing an :guilabel:`About us` section."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:85
|
||||
msgid ":guilabel:`Archives`: allows visitors to select a month and filter all posts created during that month."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:87
|
||||
msgid ":guilabel:`Follow Us`: displays links to your social media networks. They can be configured using the Social Media building block somewhere on your website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:89
|
||||
msgid ":guilabel:`Tags List`: displays all tags related to a blog. Visitors can select a tag to filter all related posts."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:92
|
||||
msgid ":guilabel:`Posts List`: :guilabel:`Cover` displays the posts' images, and :guilabel:`No Cover` hides them."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:95
|
||||
msgid ":guilabel:`Author`: displays the posts' authors."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:96
|
||||
msgid ":guilabel:`Comments/Views Stats`: displays the posts' number of comments and views."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:97
|
||||
msgid ":guilabel:`Teaser & Tags`: displays the posts' first sentences and tags."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:100
|
||||
msgid "Customizing blog posts"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:102
|
||||
msgid "Customize posts by opening a blog post and clicking :menuselection:`Edit --> Customize`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:105
|
||||
msgid "Settings apply to **all** posts."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:107
|
||||
msgid ":guilabel:`Layout`: :guilabel:`Title Inside Cover` displays the title inside the cover image, and :guilabel:`Title above Cover` displays it above."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:110
|
||||
msgid ":guilabel:`Increase Readability`: increases the text's readability."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:112
|
||||
msgid ":guilabel:`Sidebar`: displays the :guilabel:`Sidebar` and additional options:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:114
|
||||
msgid ":guilabel:`Archive`: allows visitors to select a month and filter all posts created during that month."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:116
|
||||
msgid ":guilabel:`Author`: displays the post's author and creation date."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:117
|
||||
msgid ":guilabel:`Blog List`: displays links to all your blogs."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:118
|
||||
msgid ":guilabel:`Share Links`: displays share buttons to several social networks."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:119
|
||||
msgid ":guilabel:`Tags`: displays the post's tags."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:121
|
||||
msgid ":guilabel:`Breadcrumb`: displays the path to the post."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:123
|
||||
msgid ":guilabel:`Bottom`: :guilabel:`Next Article` displays the next post at the bottom, and :guilabel:`Comments` enable visitors to comment on the post."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:126
|
||||
msgid ":guilabel:`Select To Tweet`: visitors are offered to tweet the text they select."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/blog.rst:129
|
||||
msgid "Use :ref:`Plausible <website/analytics/plausible>` to keep track of the traffic on your blog."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/ecommerce.rst:8
|
||||
msgid "eCommerce"
|
||||
msgstr ""
|
||||
@ -3007,26 +3207,26 @@ msgid "If this channel should only be available to site visitors in specific cou
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:185
|
||||
msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps </applications/websites/website/configuration/on-premise_geo-ip-installation>`."
|
||||
msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps </administration/install/geo_ip>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:191
|
||||
#: ../../content/applications/websites/livechat.rst:190
|
||||
msgid "Widget"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:193
|
||||
#: ../../content/applications/websites/livechat.rst:192
|
||||
msgid "The :guilabel:`Widget` tab on the live chat channel details form provides the shortcode for an embeddable website widget. This code can be added to a website to provide access to a live chat window."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:197
|
||||
#: ../../content/applications/websites/livechat.rst:196
|
||||
msgid "The live chat widget can be added to websites created through Odoo by navigating to the :menuselection:`Website --> Configuration --> Settings`. Then scroll to the :guilabel:`Livechat` section, and select the channel to add to the site. Click :guilabel:`Save` to apply."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:201
|
||||
#: ../../content/applications/websites/livechat.rst:200
|
||||
msgid "To add the widget to a website created on a third-party platform, click the first :guilabel:`COPY` button on the :guilabel:`Widget` tab and paste the code into the `<head>` tag on the site."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:204
|
||||
#: ../../content/applications/websites/livechat.rst:203
|
||||
msgid "Likewise, to send a live chat session to a customer, click the second :guilabel:`COPY` button on the :guilabel:`Widget` tab. This link can be sent directly to a customer, and once they click the link, it will open a new chat."
|
||||
msgstr ""
|
||||
|
||||
@ -3034,23 +3234,23 @@ msgstr ""
|
||||
msgid "View of the widget tab for Odoo Live Chat."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:213
|
||||
#: ../../content/applications/websites/livechat.rst:212
|
||||
msgid "Participate in a conversation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:215
|
||||
#: ../../content/applications/websites/livechat.rst:214
|
||||
msgid "As explained above, *operators* are the users who will respond to live chat requests from customers. The information below outlines the necessary steps for operators participating in live chat conversations on an Odoo database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:220
|
||||
#: ../../content/applications/websites/livechat.rst:219
|
||||
msgid "Set an online chat name"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:222
|
||||
#: ../../content/applications/websites/livechat.rst:221
|
||||
msgid "Before participating in a live chat, operators should update their *Online Chat Name*. This is the name that will be displayed to site visitors in the live chat conversation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:225
|
||||
#: ../../content/applications/websites/livechat.rst:224
|
||||
msgid "To update the :guilabel:`Online Chat Name`, click on the user name in the upper-right corner of any page in the database. Select :guilabel:`My Profile` to open the Profile page. On the right side of the :guilabel:`Preferences` tab, locate the :guilabel:`Online Chat Name` field and enter the preferred name."
|
||||
msgstr ""
|
||||
|
||||
@ -3058,11 +3258,11 @@ msgstr ""
|
||||
msgid "View of the My Profile option in Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:234
|
||||
#: ../../content/applications/websites/livechat.rst:233
|
||||
msgid "If a users :guilabel:`Online Chat Name` is not set, the name displayed will default to the :guilabel:`User Name`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:238
|
||||
#: ../../content/applications/websites/livechat.rst:237
|
||||
msgid "A user has their full name as their :guilabel:`User Name`, but they do not want to include their last name in a live chat conversation. They would then set their :guilabel:`Online Chat Name` to include only their first name."
|
||||
msgstr ""
|
||||
|
||||
@ -3070,15 +3270,15 @@ msgstr ""
|
||||
msgid "View of user profile in Odoo, emphasizing the Online Chat name field."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:247
|
||||
#: ../../content/applications/websites/livechat.rst:246
|
||||
msgid "Join or leave a channel"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:249
|
||||
#: ../../content/applications/websites/livechat.rst:248
|
||||
msgid "To join a live chat channel, go to the :menuselection:`Live Chat` app and click the :guilabel:`JOIN` button on the kanban card for the appropriate channel."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:252
|
||||
#: ../../content/applications/websites/livechat.rst:251
|
||||
msgid "Any channel where the user is currently active will show a :guilabel:`LEAVE` button. Click this button to disconnect from the channel."
|
||||
msgstr ""
|
||||
|
||||
@ -3086,19 +3286,19 @@ msgstr ""
|
||||
msgid "View of a channel form and the option to join a channel for Odoo Live Chat."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:260
|
||||
#: ../../content/applications/websites/livechat.rst:259
|
||||
msgid "*Operators* that do not show any activity in Odoo for more than thirty minutes will be considered disconnected, and subsequently removed from the channel."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:264
|
||||
#: ../../content/applications/websites/livechat.rst:263
|
||||
msgid "Manage live chat requests"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:266
|
||||
#: ../../content/applications/websites/livechat.rst:265
|
||||
msgid "When an operator is active in a channel, chat windows will open in the bottom right corner of the screen, no matter where they are in the database. They can participate in conversations without leaving their current location."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:271
|
||||
#: ../../content/applications/websites/livechat.rst:270
|
||||
msgid "Conversations can also be accessed by clicking the :guilabel:`Conversations` icon in the menu bar."
|
||||
msgstr ""
|
||||
|
||||
@ -3106,7 +3306,7 @@ msgstr ""
|
||||
msgid "View of the menu bar in Odoo emphasizing the conversations icon."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:278
|
||||
#: ../../content/applications/websites/livechat.rst:277
|
||||
msgid "Live chat conversations can also be viewed by navigating to :menuselection:`Dashboard --> Discuss`. New conversations will appear in bold under the :guilabel:`LIVECHAT` heading along the left panel."
|
||||
msgstr ""
|
||||
|
||||
@ -3114,15 +3314,15 @@ msgstr ""
|
||||
msgid "View of the discuss application with a message sent through live chat in Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:285
|
||||
#: ../../content/applications/websites/livechat.rst:284
|
||||
msgid "Click on a conversation in the left panel to select it. This will open the conversation. From this view, an operator can participate in the chat the same as they would in the normal chat window."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:289
|
||||
#: ../../content/applications/websites/livechat.rst:288
|
||||
msgid ":doc:`Get Started with Discuss </applications/productivity/discuss/overview/get_started>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/livechat.rst:290
|
||||
#: ../../content/applications/websites/livechat.rst:289
|
||||
msgid ":doc:`/applications/websites/livechat/responses`"
|
||||
msgstr ""
|
||||
|
||||
@ -3819,6 +4019,94 @@ msgstr ""
|
||||
msgid "Discover the best **Open-Source Website Builder** and learn how to build beautiful websites that convert visitors into leads or revenues."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:3
|
||||
msgid "Address autocomplete"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:5
|
||||
msgid "You can use the Google Places API on your website to ensure that your users' delivery addresses exist and are understood by the carrier. The Google Places API allows developers to access detailed information about places using HTTP requests. The autocompletion predicts a list of places when the user starts typing the address."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:-1
|
||||
msgid "Address autocomplete example"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:13
|
||||
msgid "`Google Maps Platform <https://mapsplatform.google.com/maps-products>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:14
|
||||
msgid "`Google Developers Documentation: Google Places API <https://developers.google.com/maps/documentation/places/web-service/autocomplete>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:18
|
||||
msgid "To do so, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Address Autocomplete` in the :guilabel:`SEO` section."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:-1
|
||||
msgid "Enable address autocomplete"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:24
|
||||
msgid "Insert your :guilabel:`Google Places API key` in the :guilabel:`API Key` field. If you don't have one, create yours on the `Google Cloud Console <https://console.cloud.google.com/getting-started>`_ and follow these steps."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:28
|
||||
msgid "Step 1: Enable the Google Places API"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:30
|
||||
msgid "**Create a New Project:**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:32
|
||||
msgid "To enable the **Google Places API**, you first need to create a project. To do so, click :guilabel:`Select a project` in the top left corner, :guilabel:`New Project`, and follow the prompts to set up your project."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:34
|
||||
msgid "**Enable the Google Places API:**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:36
|
||||
msgid "Go to the :guilabel:`Enabled APIs & Services` and click :guilabel:`+ ENABLE APIS AND SERVICES.` Search for :guilabel:`\"Places API\"` and select it. Click on the :guilabel:`\"Enable\"` button."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:39
|
||||
msgid "Google's pricing depends on the number of requests and their complexity."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:42
|
||||
msgid "Step 2: Create API Credentials"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:44
|
||||
msgid "Go to `APIs & Services --> Credentials <https://console.cloud.google.com/apis/credentials>`_."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:46
|
||||
msgid "**Create credentials:**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:48
|
||||
msgid "To create your credentials, go to :guilabel:`Credentials`, click :guilabel:`Create Credentials`, and select :guilabel:`API key`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:50
|
||||
msgid "Restrict the API Key (Optional)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:52
|
||||
msgid "For security purposes, you can restrict the usage of your API key. You can go to the :guilabel:`API restrictions` section to specify which APIs your key can access. For the Google Places API, you can restrict it to only allow requests from specific websites or apps."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:57
|
||||
msgid "Save Your API Key: Copy your API key and securely store it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:58
|
||||
msgid "Do not share it publicly or expose it in client-side code."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/cookies_bar.rst:3
|
||||
msgid "Cookies bar"
|
||||
msgstr ""
|
||||
@ -4117,78 +4405,6 @@ msgstr ""
|
||||
msgid "Other reporting data such as eCommerce dashboard data, online sales analyses and visitors can be grouped by website if necessary. Open the search panel and select :guilabel:`Group by --> Website`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:3
|
||||
msgid "Geo IP Installation (On-Premises Database)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:6
|
||||
msgid "Installation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:8
|
||||
msgid "Download both the GeoLite2 City and Country `databases <https://dev.maxmind.com/geoip/geoip2/geolite2/>`_. You should end up with two files called :file:`GeoLite2-City.mmdb` and :file:`GeoLite2-Country.mmdb`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:12
|
||||
msgid "Move the files to the folder :file:`/usr/share/GeoIP/`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:19
|
||||
msgid "Restart the server"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:22
|
||||
msgid "If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`, use the :option:`--geoip-city-db <odoo-bin --geoip-city-db>` and :option:`--geoip-country-db <odoo-bin --geoip-country-db>` options of the Odoo command line interface. These options take the absolute path to the GeoIP database file and use it as the GeoIP database. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:33
|
||||
msgid ":doc:`CLI documentation </developer/reference/cli>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:36
|
||||
msgid "Test GeoIP Geolocation In Odoo Website"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:38
|
||||
msgid "Edit a web page to include some geo-ip information such as the country name of the current request IP address. To do so:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:41
|
||||
msgid "Go to your website. Open the web page that you want to test ``GeoIP``."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:42
|
||||
msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:43
|
||||
msgid "Add the following piece of XML in the page :"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:49
|
||||
msgid "Save and refresh the page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:51
|
||||
msgid "Geo-ip is working if you read your country name displayed in bold in the middle of the page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:53
|
||||
msgid "In case you read \"**geoip failure**\" instead then the geolocalization failed. The common causes are:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:55
|
||||
msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one. If you don't know, you can access your website using mobile data."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:57
|
||||
msgid "You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't start Odoo with the proxy-mode enabled. See :option:`proxy mode <odoo-bin --proxy-mode>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:59
|
||||
msgid "The GeoIP database is corrupt, missing or unaccessible. In such case a warning was logged in the server logs."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/websites/website/configuration/spam_protection.rst:3
|
||||
msgid "Forms spam protection"
|
||||
msgstr ""
|
||||
|
||||
Loading…
Reference in New Issue
Block a user