[FIX] *: RST cleanup
RST cleanup to comply with the RST guidelines. This is required so we can use "make test", as there are currently hundreds of errors. For now, it is unusable because of the oldest code in this repo. closes odoo/documentation#3568 Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
This commit is contained in:
@@ -1,6 +1,7 @@
|
||||
========================
|
||||
Credit notes and refunds
|
||||
========================
|
||||
|
||||
A **credit note**, or **credit memo**, is a document issued
|
||||
to a customer that notifies them that they have been credited
|
||||
a certain amount.
|
||||
@@ -18,6 +19,7 @@ There are several reasons that can lead to a credit note, such as:
|
||||
|
||||
Issue a Credit Note
|
||||
===================
|
||||
|
||||
You can create a credit note from scratch by going to
|
||||
:menuselection:`Accounting --> Customers --> Credit Notes`,
|
||||
and by clicking on *Create*. Filling the Credit Note’s form
|
||||
@@ -42,6 +44,7 @@ You can choose between three options:
|
||||
|
||||
Partial Refund
|
||||
--------------
|
||||
|
||||
Odoo creates a draft credit note already prefilled with all the
|
||||
necessary information from the original invoice.
|
||||
|
||||
@@ -53,6 +56,7 @@ want to modify any detail on the credit note.
|
||||
|
||||
Full Refund
|
||||
-----------
|
||||
|
||||
Odoo creates a credit note, automatically validates it, and
|
||||
reconciles the original invoice with it.
|
||||
|
||||
@@ -64,6 +68,7 @@ a validated invoice.
|
||||
|
||||
Full refund and new draft invoice
|
||||
---------------------------------
|
||||
|
||||
Odoo creates a credit note, automatically validates it, reconciles
|
||||
the original invoice with it, and open a new draft invoice
|
||||
prefilled with the same details from the original invoice.
|
||||
@@ -72,6 +77,7 @@ This is the option to choose to modify the content of a validated invoice.
|
||||
|
||||
Record a Vendor Refund
|
||||
======================
|
||||
|
||||
**Vendor Refunds** are recorded the same way you would do with invoices’ credit notes:
|
||||
|
||||
You can either create a credit note from scratch by going
|
||||
@@ -81,6 +87,7 @@ and clicking on *Add Credit Note*.
|
||||
|
||||
Journal Entries
|
||||
===============
|
||||
|
||||
Issuing a credit note from an invoice creates a **reverse entry**
|
||||
that zeroes out the journal items generated by the original invoice.
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
============================
|
||||
Add EPC QR Codes to invoices
|
||||
============================
|
||||
|
||||
European Payments Council Quick Response Code,
|
||||
or **EPC QR Code**, are two-dimensional barcodes
|
||||
that customers can scan with their **mobile banking
|
||||
@@ -18,6 +19,7 @@ make for payment issues.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Go to :menuselection:`Accounting --> Configuration --> Settings`
|
||||
and activate the **SEPA QR Code** feature.
|
||||
|
||||
@@ -26,6 +28,7 @@ and activate the **SEPA QR Code** feature.
|
||||
|
||||
Configure your Bank Account’s journal
|
||||
-------------------------------------
|
||||
|
||||
Make sure that your *Bank Account* is correctly configured
|
||||
on Odoo with your IBAN and BIC.
|
||||
|
||||
@@ -38,6 +41,7 @@ To do so, go to :menuselection:`Accounting --> Configuration
|
||||
|
||||
Issue Invoices with EPC QR Codes
|
||||
================================
|
||||
|
||||
EPC QR Codes are added automatically to your invoices, as
|
||||
long as you issue them to customers that are located in a
|
||||
country where this feature is available.
|
||||
|
||||
@@ -149,7 +149,7 @@ It remains possible to resequence the invoices but with some restrictions:
|
||||
current year without starting over from the beginning.
|
||||
|
||||
Invoice digitization with optical character recognition (OCR)
|
||||
---------------------------------------------------------------
|
||||
-------------------------------------------------------------
|
||||
|
||||
**Invoice digitization** is the process of automatically encoding traditional paper invoices into
|
||||
invoices forms in your accounting.
|
||||
|
||||
@@ -86,8 +86,7 @@ into the **Production** environment. As these two environments are completely is
|
||||
other, the digital certificates of one instance are not valid in the other one.
|
||||
|
||||
To select a database environment, go to :menuselection:`Accounting --> Settings --> Argentinean
|
||||
Localization` and choose either :guilabel:`Prueba (Testing)` or :guilabel:`Produccion (Production)`
|
||||
.
|
||||
Localization` and choose either :guilabel:`Prueba (Testing)` or :guilabel:`Produccion (Production)`.
|
||||
|
||||
.. image:: argentina/select-environment.png
|
||||
:align: center
|
||||
|
||||
@@ -22,14 +22,12 @@ requires the next modules:
|
||||
required for the Integration with Carvajal and generate the
|
||||
electronic invoice, based on the DIAN legal requirements.
|
||||
|
||||
|
||||
Workflow
|
||||
========
|
||||
|
||||
.. image:: colombia/colombia01.png
|
||||
:align: center
|
||||
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
@@ -42,7 +40,6 @@ filter and search for "Colombia". Then click on *Install* for the first two modu
|
||||
.. image:: colombia/colombia02.png
|
||||
:align: center
|
||||
|
||||
|
||||
Configure credentials for Carvajal web service
|
||||
----------------------------------------------
|
||||
|
||||
@@ -72,7 +69,6 @@ CSC is the default for new databases.
|
||||
Once that Odoo and Carvajal are fully configured and ready for
|
||||
production the testing environment can be disabled.
|
||||
|
||||
|
||||
Configure your report data
|
||||
--------------------------
|
||||
|
||||
@@ -86,7 +82,6 @@ look for the *Colombian Electronic Invoice* section.
|
||||
.. image:: colombia/colombia04.png
|
||||
:align: center
|
||||
|
||||
|
||||
Configure data required in the XML
|
||||
----------------------------------
|
||||
|
||||
@@ -94,7 +89,7 @@ Partner
|
||||
~~~~~~~
|
||||
|
||||
Identification
|
||||
^^^^^^^^^^^^^^
|
||||
**************
|
||||
|
||||
As part of the Colombian Localization, the document types defined by
|
||||
the DIAN are now available on the Partner form. Colombian partners
|
||||
@@ -108,9 +103,8 @@ have to have their identification number and document type set:
|
||||
will split this number when the data to the third party vendor is
|
||||
sent.
|
||||
|
||||
|
||||
Fiscal structure (RUT)
|
||||
^^^^^^^^^^^^^^^^^^^^^^
|
||||
**********************
|
||||
|
||||
The partner's responsibility codes (section 53 in the RUT document)
|
||||
are included as part of the electronic invoice module given that is
|
||||
@@ -125,7 +119,6 @@ Purchase Tab --> Fiscal Information`
|
||||
Additionally two booleans fields were added in order to specify the
|
||||
fiscal regimen of the partner.
|
||||
|
||||
|
||||
Taxes
|
||||
~~~~~
|
||||
|
||||
@@ -143,7 +136,6 @@ to correctly display taxes in the invoice PDF.
|
||||
.. image:: colombia/colombia08.png
|
||||
:align: center
|
||||
|
||||
|
||||
Journals
|
||||
~~~~~~~~
|
||||
|
||||
@@ -162,7 +154,6 @@ should be configured and synchronized with the CEN Financiero.
|
||||
.. image:: colombia/colombia10.png
|
||||
:align: center
|
||||
|
||||
|
||||
Users
|
||||
~~~~~
|
||||
|
||||
@@ -173,7 +164,6 @@ configured:
|
||||
.. image:: colombia/colombia11.png
|
||||
:align: center
|
||||
|
||||
|
||||
Usage and testing
|
||||
=================
|
||||
|
||||
@@ -183,7 +173,6 @@ Invoice
|
||||
When all your master data and credentials has been configured, it's
|
||||
possible to start testing the electronic invoice workflow.
|
||||
|
||||
|
||||
Invoice creation
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
@@ -206,7 +195,6 @@ There are three types of documents:
|
||||
this invoice is added to the ERP, this invoice type should be
|
||||
selected.
|
||||
|
||||
|
||||
Invoice validation
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
@@ -224,7 +212,6 @@ displayed with the Electronic Invoice status, with the initial value
|
||||
.. image:: colombia/colombia14.png
|
||||
:align: center
|
||||
|
||||
|
||||
Reception of legal XML and PDF
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
@@ -247,7 +234,6 @@ After this:
|
||||
|
||||
- The Electronic Invoice status changes to "Accepted"
|
||||
|
||||
|
||||
Common errors
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
@@ -268,7 +254,6 @@ button:
|
||||
.. image:: colombia/colombia19.png
|
||||
:align: center
|
||||
|
||||
|
||||
Additional use cases
|
||||
--------------------
|
||||
|
||||
|
||||
@@ -208,7 +208,7 @@ Odoo is compliant with the **Indian Goods and Services Tax (GST) E-waybill syste
|
||||
.. _india/e-waybill-api:
|
||||
|
||||
API Registration on your NIC E-waybill web portal
|
||||
--------------------------------------------------
|
||||
-------------------------------------------------
|
||||
|
||||
You must register on the **NIC E-waybill** web portal to create your **API credentials**. You need
|
||||
these credentials to :ref:`configure your Odoo Accounting app <india/e-waybill-configuration>`.
|
||||
|
||||
@@ -60,6 +60,7 @@ section, click :guilabel:`Update info`. From here, fill out the fields:
|
||||
|
||||
PEC mail
|
||||
--------
|
||||
|
||||
The **PEC email** is a specific type of **certified** email providing a legal equivalent to the
|
||||
traditional registered mail. The **PEC email** of the main company must be the same as the one
|
||||
registered by the **Agenzia delle Entrate** authorities.
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
===========
|
||||
Netherlands
|
||||
===========
|
||||
|
||||
XAF Export
|
||||
----------
|
||||
==========
|
||||
|
||||
With the Dutch accounting localization installed, you will be able to
|
||||
export all your accounting entries in XAF format. For this, you have to
|
||||
@@ -11,13 +12,11 @@ define the entries you want to export using the filters (period, journals, ...)
|
||||
and then you click on the button **EXPORT (XAF)**.
|
||||
|
||||
Dutch Accounting Reports
|
||||
------------------------
|
||||
========================
|
||||
|
||||
If you install the Dutch accounting localization, you will have access
|
||||
to some reports that are specific to the Netherlands such as :
|
||||
|
||||
- Profit & Loss
|
||||
|
||||
- Tax Report (Aangifte omzetbelasting)
|
||||
|
||||
- Intrastat Report (ICP)
|
||||
|
||||
@@ -533,9 +533,8 @@ Advance Payments
|
||||
#. Reconcile the Credit note with the final invoice.
|
||||
#. The remaining balance on the final invoice should be paid with a regular payment transaction.
|
||||
|
||||
|
||||
Detraction Invoices
|
||||
********************
|
||||
*******************
|
||||
|
||||
When creating invoices that is subject to Detractions, take into account the next considerations:
|
||||
|
||||
@@ -578,9 +577,8 @@ To finish the workflow please follow the instructions on :doc:`our page about Cr
|
||||
.. note::
|
||||
The EDI workflow for the Credit notes works in the same way as the invoices.
|
||||
|
||||
|
||||
Debit Notes
|
||||
------------
|
||||
-----------
|
||||
|
||||
As part of the Peruvian localization, besides creating credit notes from an existing document
|
||||
you can also create debit Notes. For this just use the button “Add Debit Note”.
|
||||
|
||||
@@ -13,7 +13,7 @@ improving their overall experience with the company.
|
||||
making customizations more robust as you don’t have to edit code.
|
||||
|
||||
Defining a default reply to on your mail template
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
=================================================
|
||||
|
||||
Although the field *reply to* is available within the mail templates, **this field is only used
|
||||
for mass mailing** mode (this means when sending templates on what we call bulk emailing). You
|
||||
@@ -37,7 +37,7 @@ communication between your customer and your Odoo database. For more information
|
||||
the catchall works, please check :ref:`how to manage inbound messages <email_communication/inbound_messages>`.
|
||||
|
||||
Transactional emails and corresponding URL for each company
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
===========================================================
|
||||
|
||||
When using Odoo, multiple events trigger the sending of automated emails. These emails are known
|
||||
as transactional emails and sometimes contain links pointing to your Odoo database.
|
||||
@@ -72,7 +72,7 @@ For more information about how to configure your domains, we invite you to check
|
||||
documentation </administration/maintain/domain_names>`.
|
||||
|
||||
Updating translations within email templates
|
||||
********************************************
|
||||
--------------------------------------------
|
||||
|
||||
Email templates are automatically translated. Changing the translations shouldn’t be necessary.
|
||||
However, if for a specific reason you’d like to change some of the translations, this can be done.
|
||||
|
||||
@@ -6,7 +6,7 @@ Installing Asterisk server
|
||||
==========================
|
||||
|
||||
Dependencies
|
||||
~~~~~~~~~~~~
|
||||
------------
|
||||
|
||||
Before installing Asterisk you need to install the following dependencies:
|
||||
|
||||
@@ -32,7 +32,8 @@ In order to install libsrtp, follow the instructions below:
|
||||
./configure CFLAGS=-fPIC --prefix=/usr/local/lib
|
||||
make && make install
|
||||
|
||||
You also need to install PJSIP, you can download the source `here <http://www.pjsip.org/download.htm>`_. Once the source directory is extracted:
|
||||
You also need to install PJSIP, you can download the source `here
|
||||
<http://www.pjsip.org/download.htm>`_. Once the source directory is extracted:
|
||||
|
||||
- **Change to the pjproject source directory:**
|
||||
|
||||
@@ -83,9 +84,10 @@ You also need to install PJSIP, you can download the source `here <http://www.pj
|
||||
libpj.so (libc6,x86-64) => /usr/lib/libpj.so
|
||||
|
||||
Asterisk
|
||||
~~~~~~~~
|
||||
--------
|
||||
|
||||
- In order to install Asterisk 13.7.0, you can download the source directly `there <http://downloads.asterisk.org/pub/telephony/asterisk/old-releases/asterisk-13.7.0.tar.gz>`_.
|
||||
- In order to install Asterisk 13.7.0, you can download the source directly `there
|
||||
<http://downloads.asterisk.org/pub/telephony/asterisk/old-releases/asterisk-13.7.0.tar.gz>`_.
|
||||
|
||||
- Extract Asterisk:
|
||||
|
||||
@@ -111,7 +113,9 @@ Asterisk
|
||||
|
||||
make menuselect
|
||||
|
||||
- In the menuselect, go to the resources option and ensure that res_srtp is enabled. If there are 3 x’s next to res_srtp, there is a problem with the srtp library and you must reinstall it. Save the configuration (press x). You should also see stars in front of the res_pjsip lines.
|
||||
- In the menuselect, go to the resources option and ensure that res_srtp is enabled. If there are
|
||||
3 x’s next to res_srtp, there is a problem with the srtp library and you must reinstall it. Save
|
||||
the configuration (press x). You should also see stars in front of the res_pjsip lines.
|
||||
|
||||
- Compile and install Asterisk:
|
||||
|
||||
@@ -119,10 +123,11 @@ Asterisk
|
||||
|
||||
make && make install
|
||||
|
||||
- If you need the sample configs you can run 'make samples' to install the sample configs. If you need to install the Asterisk startup script you can run 'make config'.
|
||||
- If you need the sample configs you can run 'make samples' to install the sample configs. If you
|
||||
need to install the Asterisk startup script you can run 'make config'.
|
||||
|
||||
DTLS Certificates
|
||||
~~~~~~~~~~~~~~~~~
|
||||
-----------------
|
||||
|
||||
- After you need to setup the DTLS certificates.
|
||||
|
||||
@@ -136,7 +141,8 @@ DTLS Certificates
|
||||
|
||||
cd /asterisk*/contrib/scripts
|
||||
|
||||
- Create the DTLS certificates (replace pbx.mycompany.com with your ip address or dns name, replace My Super Company with your company name):
|
||||
- Create the DTLS certificates (replace pbx.mycompany.com with your ip address or dns name, replace
|
||||
My Super Company with your company name):
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
@@ -145,7 +151,9 @@ DTLS Certificates
|
||||
Configure Asterisk server
|
||||
=========================
|
||||
|
||||
For WebRTC, a lot of the settings that are needed MUST be in the peer settings. The global settings do not flow down into the peer settings very well. By default, Asterisk config files are located in /etc/asterisk/. Start by editing http.conf and make sure that the following lines are uncommented:
|
||||
For WebRTC, a lot of the settings that are needed MUST be in the peer settings. The global settings
|
||||
do not flow down into the peer settings very well. By default, Asterisk config files are located in
|
||||
/etc/asterisk/. Start by editing http.conf and make sure that the following lines are uncommented:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
@@ -155,7 +163,10 @@ For WebRTC, a lot of the settings that are needed MUST be in the peer settings.
|
||||
bindaddr=127.0.0.1 ; Replace this with your IP address
|
||||
bindport=8088 ; Replace this with the port you want to listen on
|
||||
|
||||
Next, edit sip.conf. The WebRTC peer requires encryption, avpf, and icesupport to be enabled. In most cases, directmedia should be disabled. Also under the WebRTC client, the transport needs to be listed as ‘ws’ to allow websocket connections. All of these config lines should be under the peer itself; setting these config lines globally might not work:
|
||||
Next, edit sip.conf. The WebRTC peer requires encryption, avpf, and icesupport to be enabled. In
|
||||
most cases, directmedia should be disabled. Also under the WebRTC client, the transport needs to be
|
||||
listed as ‘ws’ to allow websocket connections. All of these config lines should be under the peer
|
||||
itself; setting these config lines globally might not work:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
@@ -207,11 +218,13 @@ In Odoo, the configuration should be done in the user's preferences.
|
||||
.. image:: asterisk/voip_config01.png
|
||||
:align: center
|
||||
|
||||
- The SIP Login/Browser's Extension is the number you configured previously in the sip.conf file (in our example: 1060).
|
||||
- The SIP Login/Browser's Extension is the number you configured previously in the sip.conf file (in
|
||||
our example: 1060).
|
||||
|
||||
- The SIP Password is the secret you chose in the sip.conf file.
|
||||
|
||||
- The extension of your office's phone is not a required field but it is used if you want to transfer your call from Odoo to an external phone also configured in the sip.conf file.
|
||||
- The extension of your office's phone is not a required field but it is used if you want to
|
||||
transfer your call from Odoo to an external phone also configured in the sip.conf file.
|
||||
|
||||
|
||||
The configuration should also be done in the General Settings under the "Integrations" section.
|
||||
@@ -221,4 +234,5 @@ The configuration should also be done in the General Settings under the "Integra
|
||||
|
||||
- The PBX Server IP should be the same as the IP you define in the http.conf file.
|
||||
|
||||
- The WebSocket should be: ws://localhost:XXXX/ws where "localhost" needs to be the same as the IP defined previously and "XXXX" needs to be the port defined in the http.conf file.
|
||||
- The WebSocket should be: ws://localhost:XXXX/ws where "localhost" needs to be the same as the IP
|
||||
defined previously and "XXXX" needs to be the port defined in the http.conf file.
|
||||
|
||||
@@ -15,7 +15,7 @@ to reorganize products and load another truck.
|
||||
<https://www.odoo.com/blog/business-hacks-1/post/what-is-cross-docking-and-is-it-for-me-270>`_
|
||||
|
||||
Configuration
|
||||
==============
|
||||
=============
|
||||
|
||||
In the *Inventory* app, open :menuselection:`Configuration --> Settings` and activate the
|
||||
*Multi-Step Routes*.
|
||||
|
||||
@@ -81,8 +81,8 @@ Open the products you want to ship and set a weight on it.
|
||||
Don't forget to do the conversion if you are used to the imperial
|
||||
measurement system.
|
||||
|
||||
How to print shipping labels ?
|
||||
===============================
|
||||
How to print shipping labels?
|
||||
=============================
|
||||
|
||||
The delivery order created from the sale order will take the shipping
|
||||
information from it, but you can change the carrier if you want to.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
=================
|
||||
===============
|
||||
Quality Control
|
||||
=================
|
||||
===============
|
||||
|
||||
Whether you want to control the quality of your production, or the production
|
||||
of your subcontractor, before registering the products into your stock, you can
|
||||
|
||||
@@ -195,7 +195,7 @@ From the location form, you are then able to access the Current Stock.
|
||||
|
||||
|
||||
Manual Replenishment
|
||||
--------------------------------
|
||||
--------------------
|
||||
|
||||
You can also choose to replenish your subcontractors manually.
|
||||
|
||||
|
||||
@@ -6,11 +6,13 @@ SMS Pricing and FAQ
|
||||
|
||||
What do I need to send SMSs?
|
||||
============================
|
||||
|
||||
SMS Text Messaging is an In-App Purchase (IAP) service that *requires prepaid credits* to work.
|
||||
|
||||
|
||||
How many types of SMSs are there?
|
||||
=================================
|
||||
|
||||
There are 2 types: GSM7 and UNICODE.
|
||||
|
||||
**GSM7** is the standard format, with a limit of 160 characters per message, that includes the
|
||||
@@ -34,6 +36,7 @@ Limit per SMS: 70 characters.
|
||||
|
||||
How much does it cost to send an SMS?
|
||||
=====================================
|
||||
|
||||
| The price of an SMS depends on the destination and the length (number of characters) of the message.
|
||||
| To see the **price per country,
|
||||
please consult**: `Odoo SMS - FAQ <https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_.
|
||||
@@ -49,6 +52,7 @@ The number of SMSs a message represents will be always available to you in your
|
||||
|
||||
How do I buy credits?
|
||||
=====================
|
||||
|
||||
Go to :menuselection:`Settings --> Buy Credits`.
|
||||
|
||||
|
||||
|
||||
@@ -18,18 +18,18 @@ Follow the steps to connect your IoT Box.
|
||||
:align: center
|
||||
|
||||
Ethernet Connection
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
===================
|
||||
|
||||
1. Connect to the IoT Box all the devices that have to be connected with
|
||||
#. Connect to the IoT Box all the devices that have to be connected with
|
||||
cables (ethernet, usb devices, etc.).
|
||||
|
||||
2. Power on the IoT Box.
|
||||
#. Power on the IoT Box.
|
||||
|
||||
3. Read the Pairing Code from a screen or a receipt printer connected to the IoT Box.
|
||||
#. Read the Pairing Code from a screen or a receipt printer connected to the IoT Box.
|
||||
|
||||
.. image:: connect/connect04.png
|
||||
|
||||
4. Input the Pairing Code and click on the Pair button.
|
||||
#. Input the Pairing Code and click on the Pair button.
|
||||
|
||||
.. note::
|
||||
Recent changes in modern web browsers forced us to modify the connection wizard.
|
||||
@@ -37,20 +37,20 @@ Ethernet Connection
|
||||
``iot_pairing`` module is installed.
|
||||
|
||||
WiFi Connection
|
||||
~~~~~~~~~~~~~~~
|
||||
===============
|
||||
|
||||
1. Power on the IoT Box
|
||||
#. Power on the IoT Box
|
||||
|
||||
2. Copy the token
|
||||
#. Copy the token
|
||||
|
||||
.. image:: connect/connect05.png
|
||||
|
||||
3. Connect to the IoT Box WiFi Network (make sure there is no ethernet
|
||||
#. Connect to the IoT Box WiFi Network (make sure there is no ethernet
|
||||
cable plugged in your computer).
|
||||
|
||||
.. image:: connect/connect06.png
|
||||
|
||||
4. You will be redirected to the IoT Box Homepage (if it doesn't work,
|
||||
#. You will be redirected to the IoT Box Homepage (if it doesn't work,
|
||||
connect to the IP address of the box). Give a name to your IoT Box (not
|
||||
required) and paste the token, then click on next.
|
||||
|
||||
@@ -63,7 +63,7 @@ WiFi Connection
|
||||
should become
|
||||
**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\|4957098401**).
|
||||
|
||||
5. Choose the WiFi network you want to connect with (enter the password
|
||||
#. Choose the WiFi network you want to connect with (enter the password
|
||||
if there is one) and click on Submit. Wait a few seconds before being
|
||||
redirected to your database.
|
||||
|
||||
@@ -75,7 +75,7 @@ You should now see the IoT Box.
|
||||
:align: center
|
||||
|
||||
IoT Box Schema
|
||||
~~~~~~~~~~~~~~
|
||||
==============
|
||||
|
||||
.. image:: connect/connect10.png
|
||||
:align: center
|
||||
|
||||
@@ -3,10 +3,10 @@ Use the IoT Box for the PoS
|
||||
===========================
|
||||
|
||||
.. image:: pos/pos01.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
Prerequisites
|
||||
~~~~~~~~~~~~~
|
||||
=============
|
||||
|
||||
Before starting, make sure you have the following:
|
||||
|
||||
@@ -27,7 +27,7 @@ Before starting, make sure you have the following:
|
||||
page <https://www.odoo.com/page/point-of-sale-hardware>`__
|
||||
|
||||
Set Up
|
||||
~~~~~~~
|
||||
======
|
||||
|
||||
To connect hardware to the PoS, the first step is to connect an IoT Box
|
||||
to your database. For this, follow this
|
||||
@@ -62,6 +62,6 @@ and select the devices you want to use in this Point of Sale. Save the
|
||||
changes.
|
||||
|
||||
.. image:: pos/pos02.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
Set up is done, you can launch a new PoS Session.
|
||||
|
||||
@@ -6,7 +6,7 @@ IoT Box Connection
|
||||
==================
|
||||
|
||||
I can't find the pairing code to connect my IoT Box
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
---------------------------------------------------
|
||||
|
||||
The pairing code should be printed on receipt printers connected to the
|
||||
IoT Box and should also be displayed on connected monitors.
|
||||
@@ -30,7 +30,7 @@ has correctly started, by checking that a fixed green LED is showing next to
|
||||
the micro-USB port.
|
||||
|
||||
I've connected my IoT Box but it's not showing in my database
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
-------------------------------------------------------------
|
||||
|
||||
When you connect an IoT Box to a database, the IoT Box might restart, if
|
||||
that is the case, it might take up to one minute before appearing in your
|
||||
@@ -39,7 +39,7 @@ your database can be reached from the IoT Box and that your server doesn't
|
||||
use a multi-database environment.
|
||||
|
||||
My IoT Box is connected to my database, but cannot be reached
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
-------------------------------------------------------------
|
||||
|
||||
Make sure that the IoT Box and the device running the browser are located
|
||||
on the same network as the IoT Box cannot be reached from outside the local
|
||||
@@ -49,7 +49,7 @@ Printer
|
||||
=======
|
||||
|
||||
My printer is not detected
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
--------------------------
|
||||
|
||||
If one of your printers doesn't show up in your devices list, go to the
|
||||
IoT Box homepage and make sure that it is listed under *Printers*.
|
||||
@@ -63,7 +63,7 @@ If your printer is not present on the IoT Box homepage, hit
|
||||
not connected properly.
|
||||
|
||||
My printer outputs random text
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
------------------------------
|
||||
|
||||
For most printers, the correct driver should be automatically detected
|
||||
and selected. However, in some cases, the automatic detection mechanism
|
||||
@@ -85,7 +85,7 @@ corresponding to your printer.
|
||||
printers.
|
||||
|
||||
My Zebra Printer doesn't print anything
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
---------------------------------------
|
||||
|
||||
Zebra printers are quite sensitive to the format of the ZPL code that is
|
||||
printed. If nothing comes out of the printer or blank labels are printed,
|
||||
@@ -97,7 +97,7 @@ Barcode Scanner
|
||||
===============
|
||||
|
||||
The characters read by the barcode scanner don't match the barcode
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
------------------------------------------------------------------
|
||||
|
||||
By default, we assume that your barcode scanner is configured in US
|
||||
QWERTY. This is the default configuration of most barcode readers.
|
||||
@@ -105,14 +105,14 @@ If your barcode scanner uses a different layout, please go to the
|
||||
form view of your device and select the correct one.
|
||||
|
||||
Nothing happens when a barcode is scanned
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
-----------------------------------------
|
||||
|
||||
Make sure that the correct device is selected in your Point of Sale
|
||||
configuration and that your barcode is configured to send an ENTER
|
||||
character (keycode 28) at the end of every barcode.
|
||||
|
||||
The barcode scanner is detected as a keyboard
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
---------------------------------------------
|
||||
|
||||
Some poorly built barcode scanners do not advertise themselves as
|
||||
barcode scanners but as a USB keyboard instead, and will not be
|
||||
@@ -128,7 +128,7 @@ Cashdrawer
|
||||
==========
|
||||
|
||||
The cashdrawer does not open
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
----------------------------
|
||||
|
||||
The cashdrawer should be connected to the printer and the *Cashdrawer*
|
||||
checkbox should be ticked in the POS configuration.
|
||||
|
||||
@@ -10,9 +10,8 @@ connected, the screen can be used to display a :abbr:`PoS (Point of Sale)` order
|
||||
:alt: An example of a PoS (point of sale) order on a screen display.
|
||||
|
||||
.. note::
|
||||
Access the customer display from any other computer by going to the :abbr:`IoT (Internet of Things)`
|
||||
Box homepage and clicking on the :guilabel:`POS Display` button.
|
||||
|
||||
Access the customer display from any other computer by going to the :abbr:`IoT (Internet of
|
||||
Things)` Box homepage and clicking on the :guilabel:`POS Display` button.
|
||||
|
||||
Connection
|
||||
==========
|
||||
@@ -24,21 +23,22 @@ on the model.
|
||||
|
||||
.. tab:: IoT Box model 4
|
||||
|
||||
Connect up to two screens with Micro-HDMI cables on the side of the :abbr:`IoT (Internet of Things)`
|
||||
Box. If two screens are connected, they can display distinct content (see usage below).
|
||||
Connect up to two screens with Micro-HDMI cables on the side of the :abbr:`IoT (Internet of
|
||||
Things)` Box. If two screens are connected, they can display distinct content (see usage
|
||||
below).
|
||||
|
||||
.. tab:: IoT Box model 3
|
||||
|
||||
Connect the screen with an HDMI cable on the side of the :abbr:`IoT (Internet of Things)` Box.
|
||||
|
||||
.. important::
|
||||
Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` Box is switched on. If it
|
||||
is already on, connect the screen(s), and then restart the :abbr:`IoT (Internet of Things)` Box by
|
||||
unplugging it and plugging it back into its power source.
|
||||
Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` Box is switched on. If
|
||||
it is already on, connect the screen(s), and then restart the :abbr:`IoT (Internet of Things)`
|
||||
Box by unplugging it and plugging it back into its power source.
|
||||
|
||||
.. warning::
|
||||
The usage of HDMI/Micro-HDMI adapters may cause issues which will result in a blank, black screen on
|
||||
the screen display. Cable usage is recommended.
|
||||
The usage of HDMI/Micro-HDMI adapters may cause issues which will result in a blank, black screen
|
||||
on the screen display. Cable usage is recommended.
|
||||
|
||||
If the connection was successful, the screen should display the :guilabel:`POS Client display`
|
||||
screen.
|
||||
@@ -56,7 +56,8 @@ Things)` Box homepage.
|
||||
:alt: An example of a screen display name shown on the IoT Box homepage.
|
||||
|
||||
.. note::
|
||||
If no screen is detected, a default display named :guilabel:`Distant Display` will be used instead.
|
||||
If no screen is detected, a default display named :guilabel:`Distant Display` will be used
|
||||
instead.
|
||||
|
||||
.. image:: screen/screen-no-screen.png
|
||||
:align: center
|
||||
@@ -66,7 +67,7 @@ Usage
|
||||
=====
|
||||
|
||||
Show Point of Sales orders to customers
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
---------------------------------------
|
||||
|
||||
To use the screen in the :guilabel:`Point of Sale` app, go to :menuselection:`Point of Sale -->
|
||||
Configuration --> Point of Sale`, open the desired screen, click on :guilabel:`Edit`, and enable the
|
||||
@@ -84,17 +85,18 @@ in the top bar to inform the connection status with the screen.
|
||||
|
||||
.. image:: screen/screen-pos-icon.png
|
||||
:align: center
|
||||
:alt: The "screen" icon on the Point of Sale display shows the connection status with the screen.
|
||||
:alt: The "screen" icon on the Point of Sale display shows the connection status with the
|
||||
screen.
|
||||
|
||||
The screen will automatically show the :abbr:`PoS (Point of Sale)` orders and update when changes are
|
||||
performed on the order.
|
||||
The screen will automatically show the :abbr:`PoS (Point of Sale)` orders and update when changes
|
||||
are performed on the order.
|
||||
|
||||
.. image:: screen/screen-pos-client-display.png
|
||||
:align: center
|
||||
:alt: An example of a PoS order on a screen display.
|
||||
|
||||
Display a website
|
||||
~~~~~~~~~~~~~~~~~
|
||||
-----------------
|
||||
|
||||
Opening the screen form view at :menuselection:`IoT --> Devices --> (screen device)` allows the user
|
||||
to choose a particular website URL to display on the screen with the :guilabel:`Screen URL` field.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
====
|
||||
===
|
||||
SIX
|
||||
====
|
||||
===
|
||||
|
||||
Connecting a SIX payment terminal allows you to offer a fluid payment flow to your customers and
|
||||
ease the work of your cashiers.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
-------------
|
||||
=============
|
||||
Portal access
|
||||
-------------
|
||||
=============
|
||||
|
||||
Portal access is given to users who need the ability to view certain documents or information
|
||||
within an Odoo database.
|
||||
@@ -24,7 +24,8 @@ all of the following in Odoo:
|
||||
database.
|
||||
|
||||
Provide portal access to customers
|
||||
----------------------------------
|
||||
==================================
|
||||
|
||||
From the main Odoo dashboard, select the :guilabel:`Contacts` application. If the contact is not
|
||||
yet created in the database, click on the :guilabel:`Create` button, enter the details of the
|
||||
contact, and then click :guilabel:`Save`. Otherwise, choose an existing contact, and then click on
|
||||
|
||||
@@ -4,7 +4,8 @@ How to adapt your prices to your customers and apply discounts
|
||||
|
||||
Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business.
|
||||
A pricelist is a list of prices or price rules that Odoo searches to determine the suggested price.
|
||||
You can set several criteria to use a specific price: periods, min. sold quantity (meet a minimum order quantity and get a price break), etc.
|
||||
You can set several criteria to use a specific price: periods, min. sold quantity (meet a minimum
|
||||
order quantity and get a price break), etc.
|
||||
|
||||
As pricelists only suggest prices, they can be overridden by vendors completing sales orders.
|
||||
Choose your pricing strategy from :menuselection:`Sales --> Settings`.
|
||||
@@ -14,10 +15,10 @@ Choose your pricing strategy from :menuselection:`Sales --> Settings`.
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
|
||||
* *A single sale price per product :* doesn't let you adapt prices, it use default product price ;
|
||||
* *Different prices per customer segment :* you will set several prices per products ;
|
||||
* *Advanced pricing based on formula :* will let you apply discounts, margins and roundings.
|
||||
* *A single sale price per product:* doesn't let you adapt prices, it use default product
|
||||
price ;
|
||||
* *Different prices per customer segment:* you will set several prices per products ;
|
||||
* *Advanced pricing based on formula:* will let you apply discounts, margins and roundings.
|
||||
|
||||
Several prices per product
|
||||
==========================
|
||||
@@ -81,16 +82,16 @@ use e-Commerce).
|
||||
.. image:: pricing/pricing_formula.png
|
||||
:align: center
|
||||
|
||||
Each pricelist item can be associated to either all products, to a product internal category (set of products) or to a specific product. Like in second option, you can set dates and minimum quantities.
|
||||
Each pricelist item can be associated to either all products, to a product internal category (set of
|
||||
products) or to a specific product. Like in second option, you can set dates and minimum quantities.
|
||||
|
||||
.. image:: pricing/pricelist_apply.png
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
|
||||
* Once again the system is smart. If a rule is set for a particular item and another one for its category, Odoo will take the rule of the item.
|
||||
|
||||
* Make sure at least one pricelist item covers all your products.
|
||||
* Once again the system is smart. If a rule is set for a particular item and another one for its
|
||||
category, Odoo will take the rule of the item.
|
||||
* Make sure at least one pricelist item covers all your products.
|
||||
|
||||
There are 3 modes of computation: fix price, discount & formula.
|
||||
|
||||
@@ -117,8 +118,10 @@ e.g. sale price = 2*cost (100% markup) with $5 of minimal margin.
|
||||
|
||||
Prices per country
|
||||
==================
|
||||
Pricelists can be set by countries group.
|
||||
Any new customer recorded in Odoo gets a default pricelist, i.e. the first one in the list matching the country. In case no country is set for the customer, Odoo takes the first pricelist without any country group.
|
||||
|
||||
Pricelists can be set by countries group. Any new customer recorded in Odoo gets a default
|
||||
pricelist, i.e. the first one in the list matching the country. In case no country is set for the
|
||||
customer, Odoo takes the first pricelist without any country group.
|
||||
|
||||
The default pricelist can be replaced when creating a sales order.
|
||||
|
||||
@@ -127,9 +130,11 @@ The default pricelist can be replaced when creating a sales order.
|
||||
Compute and show discount % to customers
|
||||
========================================
|
||||
|
||||
In case of discount, you can show the public price and the computed discount % on printed sales orders and in your eCommerce catalog. To do so:
|
||||
In case of discount, you can show the public price and the computed discount % on printed sales
|
||||
orders and in your eCommerce catalog. To do so:
|
||||
|
||||
* Check *Allow discounts on sales order lines* in :menuselection:`Sales --> Configuration --> Settings --> Quotations & Sales --> Discounts`.
|
||||
* Check *Allow discounts on sales order lines* in :menuselection:`Sales --> Configuration -->
|
||||
Settings --> Quotations & Sales --> Discounts`.
|
||||
* Apply the option in the pricelist setup form.
|
||||
|
||||
.. image:: pricing/discount_options.png
|
||||
|
||||
@@ -1,11 +1,13 @@
|
||||
================================================
|
||||
===============================================
|
||||
Plan onsite interventions from helpdesk tickets
|
||||
================================================
|
||||
===============================================
|
||||
|
||||
The integration with the Helpdesk app lets your helpdesk team manage intervention requests directly.
|
||||
Planning field service tasks from tickets speeds up your processes.
|
||||
|
||||
Configure the helpdesk team
|
||||
===========================
|
||||
|
||||
Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select a team and enable
|
||||
*Onsite Interventions*.
|
||||
|
||||
|
||||
@@ -1,21 +1,19 @@
|
||||
=============================================
|
||||
Create onsite interventions from sales orders
|
||||
=============================================
|
||||
|
||||
Allowing your sales team to open onsite interventions creates a seamless experience for your
|
||||
customers. They can receive a quotation they first have to approve before the work even starts.
|
||||
|
||||
Configure a product
|
||||
===================
|
||||
|
||||
Go to :menuselection:`Field Service --> Configuration --> Products` and create or edit a product.
|
||||
|
||||
#. Under the *General Information* tab, select *Service* as *Product Type*.
|
||||
|
||||
#. Under the *Sales* tab, select *Timesheets on tasks* as *Service Invoicing Policy*.
|
||||
|
||||
#. Select *Create a task in an existing project* as *Service Tracking*.
|
||||
|
||||
#. Select your *Project*.
|
||||
|
||||
#. If you use them, select your *Worksheet Template* and then click on *Save*.
|
||||
|
||||
.. image:: onsite_tasks_from_sales_orders/product-configuration-tasks-from-sales-orders.png
|
||||
|
||||
@@ -7,7 +7,7 @@ track trends, identify areas for improvement, manage employees’ workloads and,
|
||||
meet your customer’s expectations.
|
||||
|
||||
Cases
|
||||
~~~~~
|
||||
=====
|
||||
|
||||
Some examples of the reports Odoo Helpdesk can generate include:
|
||||
|
||||
@@ -45,7 +45,7 @@ customers not only expect fast responses but they also want their issues to be h
|
||||
Odoo Helpdesk
|
||||
|
||||
Save filters
|
||||
~~~~~~~~~~~~
|
||||
============
|
||||
|
||||
Save the filters you use the most and avoid having to reconstruct them every time they are
|
||||
needed. To do so, set the groups, filters, and measures needed. Then, go to *Favorites*.
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
:nosearch:
|
||||
|
||||
=================
|
||||
===========
|
||||
Get started
|
||||
=================
|
||||
===========
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
==================================
|
||||
================================
|
||||
How to customize my catalog page
|
||||
==================================
|
||||
================================
|
||||
|
||||
Product Catalog
|
||||
===============
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
============================
|
||||
===========================
|
||||
How to build a product page
|
||||
============================
|
||||
===========================
|
||||
|
||||
On the website click *New Page* in the top-right corner.
|
||||
|
||||
@@ -23,9 +23,9 @@ See how to configure your products from links here below.
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`../managing_products/variants`
|
||||
* :doc:`/applications/sales/sales/products_prices/taxes`
|
||||
* :doc:`../maximizing_revenue/cross_selling`
|
||||
* :doc:`../maximizing_revenue/reviews`
|
||||
* :doc:`../maximizing_revenue/pricing`
|
||||
* :doc:`../../website/optimize/seo`
|
||||
- :doc:`../managing_products/variants`
|
||||
- :doc:`/applications/sales/sales/products_prices/taxes`
|
||||
- :doc:`../maximizing_revenue/cross_selling`
|
||||
- :doc:`../maximizing_revenue/reviews`
|
||||
- :doc:`../maximizing_revenue/pricing`
|
||||
- :doc:`../../website/optimize/seo`
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
=================================================
|
||||
===============================================
|
||||
How customers can access their customer account
|
||||
=================================================
|
||||
===============================================
|
||||
|
||||
It has never been so easy for your customers to access their
|
||||
customer account. Forget endless signup forms,
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
:nosearch:
|
||||
|
||||
=================
|
||||
=============
|
||||
Collect taxes
|
||||
=================
|
||||
=============
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
@@ -33,10 +33,11 @@ finetune them. Make sure they fit the content of the page, otherwise you will
|
||||
be downgraded by search engines.
|
||||
|
||||
.. image:: seo/seo01.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
Keywords
|
||||
--------
|
||||
|
||||
In order to write quality content and boost your traffic, Odoo provides
|
||||
a ``<keyword>`` finder. Those keywords are the searches you want to head
|
||||
towards your website. For each keyword, you see how it is used in the content
|
||||
@@ -44,7 +45,7 @@ towards your website. For each keyword, you see how it is used in the content
|
||||
searches in Google. The more keywords are used the better.
|
||||
|
||||
.. image:: seo/seo02.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
If your website is in multiple languages, you can use the Promote
|
||||
@@ -93,7 +94,7 @@ Odoo allows to link all your social network accounts in your website footer.
|
||||
All you have to do is to refer all your accounts in your company settings.
|
||||
|
||||
.. image:: seo/seo03.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
Social Share
|
||||
------------
|
||||
@@ -103,14 +104,14 @@ By clicking the icon, they are prompted to share the page in their social media
|
||||
wall.
|
||||
|
||||
.. image:: seo/seo04.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
Most social media use a picture of the picture to decorate the share post.
|
||||
Odoo uses the website logo by default but you can choose any other image
|
||||
of your page in the Promote tool.
|
||||
|
||||
.. image:: seo/seo05.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
Facebook Page
|
||||
-------------
|
||||
@@ -564,7 +565,7 @@ CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop).
|
||||
Here is the slide that summarizes the scalability of Odoo Website & eCommerce.
|
||||
|
||||
.. image:: seo/seo13.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
Search Engines Files
|
||||
====================
|
||||
@@ -615,7 +616,7 @@ pages to be displayed in Google using extra information like the price
|
||||
and rating of a product:
|
||||
|
||||
.. image:: seo/seo14.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
robots.txt
|
||||
----------
|
||||
|
||||
@@ -42,6 +42,7 @@ Installation
|
||||
|
||||
How To Test GeoIP Geolocation In Your Odoo Website
|
||||
==================================================
|
||||
|
||||
1. Go to your website. Open the web page that you want to test ``GeoIP``.
|
||||
2. Choose :menuselection:`Customize --> HTML/CSS/JS Editor`.
|
||||
3. Add the following piece of XML in the page :
|
||||
@@ -58,7 +59,9 @@ You should end up with a dictionary indicating the location of the IP address.
|
||||
.. note::
|
||||
If the curly braces are empty ``{}``, it can be for any of the following reasons :
|
||||
|
||||
- The browsing IP address is the localhost (``127.0.0.1``) or a local area network one (``192.168.*.*``)
|
||||
- If a reversed proxy is used, make sure to configure it correctly. See :option:`proxy mode <odoo-bin --proxy-mode>`
|
||||
- The browsing IP address is the localhost (``127.0.0.1``) or a local area network one
|
||||
(``192.168.*.*``)
|
||||
- If a reversed proxy is used, make sure to configure it correctly. See :option:`proxy mode
|
||||
<odoo-bin --proxy-mode>`
|
||||
- ``geoip2`` is not installed or the GeoIP database file wasn't found
|
||||
- The GeoIP database was unable to resolve the given IP address
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
===============================
|
||||
===========================
|
||||
How to translate my website
|
||||
===============================
|
||||
===========================
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
Reference in New Issue
Block a user