Compare commits
9 Commits
fvz-odoo-p
...
14.0-iot_h
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
c6e3853edf |
[IMP] iot: add documentation regarding HTTPS certificate
Also include details/troubleshoot/solutions for redundant support issues: - Error code details for HTTPS certificate generation (see: https://github.com/odoo/odoo/pull/114993 ) - DNS issue with HTTPS domain OPW-3227004 |
||
|
|
5ef339fe82 |
[l10n_mx] Update exempt tax configuration.
In Mexico there are two 0% taxes, 0% VAT and 0% exempt VAT. This change makes the tip clearer so users do not confuse both taxes. Forward to master. closes odoo/documentation#2515 Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com> |
||
|
|
b0911a00ad |
[MOV] calendar: "Calendar" app from "Misc" to "Productivity"
To improve the structure of the documentation, the "Miscellaneous" section should be limited as much as possible. This commit: - renames "Calendars" into "Calendar" (as the app name) - moves the app from the "Miscellaneous" section to the "Productivity" section - fixes the wrong file structure to follow the toc (e.g. general/calendars/outlook/outlook_calendar -> productivity/calendar/outlook) task-3217827 closes odoo/documentation#4032 Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com> |
||
|
|
3056c7b62d |
[IMP] odoo_theme: design improvements
Revamp of the side menu; Round all borders for consistency with the buttons; Improve .sig-* and .o_code elements; Improve sphinx-tabs hover effect; task-3046383 closes odoo/documentation#3264 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
620e3c33ef |
[IMP] odoo_theme: general cleanup
A general reorganization of the code was needed for more clarity. The different markup styles have been grouped together under a common "chapter", comments have been rewritten and example pages have been added for context. Some levels have been removed Where there were too many for no reason. By removing one level of styles (e.g.: `#wrap`) we avoid needing to force overrides or adding `!important` to our code. ⌙ e.g.: before commit 9ef86cd93d8c6fc0fd96b437f629237e7a562c6e, `.o_spoilers .accordion-body >:first-child` was being involuntarily overridden. task-3046383 Part-of: odoo/documentation#3264 |
||
|
|
877d1de3c2 |
[IMP] odoo_theme: tweak the HTML structure of TOC entries
task-3046383 Part-of: odoo/documentation#3264 |
||
|
|
281a893540 |
[IMP] extensions/custom_admonitions: tweak the HTML structure of dfn
The structure of the `dfn` role is changed from its default `<em class="dfn">text</em>` to `<span class="dfn"><span>text</span></span>` to ease the styling. task-3046383 Part-of: odoo/documentation#3264 |
||
|
|
e98cf5f54a |
[MOV] live chat: structure
task-3269837 closes odoo/documentation#4101 Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com> |
||
|
|
ce4a0c3e35 |
[MOV] website: structure
As a first step to update the doc - at last! - we first need to update its structure. task-3269837 Part-of: odoo/documentation#4101 |
|
|
@@ -13,7 +13,7 @@ personal email address or an address created by a custom domain.
|
|||
|
||||
.. seealso::
|
||||
- :doc:`/applications/general/auth/azure`
|
||||
- :doc:`/applications/general/calendars/outlook/outlook_calendar`
|
||||
- :doc:`/applications/productivity/calendar/outlook`
|
||||
|
||||
Setup in Microsoft Azure Portal
|
||||
===============================
|
||||
|
|
|
|||
|
|
@@ -71,7 +71,7 @@ way to verify the ownership of your domain name is by adding a DNS record. You c
|
|||
other providers.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`/applications/websites/website/optimize/seo`
|
||||
- :doc:`/applications/websites/website/pages/seo`
|
||||
- `Google Search Console Help - Verify your site ownership <https://support.google.com/webmasters/answer/9008080>`_
|
||||
- `Bing Webmaster Tools - Add and Verify site <https://www.bing.com/webmasters/help/add-and-verify-site-12184f8b>`_
|
||||
|
||||
|
|
|
|||
|
|
@@ -13,7 +13,7 @@ email address or an address created by a custom domain.
|
|||
|
||||
.. seealso::
|
||||
- :doc:`/applications/general/auth/google`
|
||||
- :doc:`/applications/general/calendars/google/google_calendar_credentials`
|
||||
- :doc:`/applications/productivity/calendar/google`
|
||||
|
||||
Setup in Google
|
||||
===============
|
||||
|
|
|
|||
|
|
@@ -10,6 +10,5 @@ Miscellaneous
|
|||
general/export_import_data
|
||||
general/email_communication
|
||||
general/voip
|
||||
general/calendars
|
||||
general/in_app_purchase
|
||||
general/developer_mode
|
||||
|
|
|
|||
|
|
@@ -6,5 +6,5 @@ Due to specific requirements in Azure's OAuth implementation, Microsoft Azure OA
|
|||
is NOT compatible with Odoo at the moment.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`/applications/general/calendars/outlook/outlook_calendar`
|
||||
- :doc:`../../productivity/calendar/outlook`
|
||||
- :doc:`/administration/maintain/azure_oauth`
|
||||
|
|
|
|||
|
|
@@ -9,7 +9,7 @@ This is particularly helpful if your organization uses Google Workforce and you
|
|||
within your organization to connect to Odoo with their Google Accounts.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`/applications/general/calendars/google/google_calendar_credentials`
|
||||
- :doc:`../../productivity/calendar/google`
|
||||
- :doc:`/administration/maintain/google_oauth`
|
||||
|
||||
.. _google-sign-in/configuration:
|
||||
|
|
|
|||
|
|
@@ -1,11 +0,0 @@
|
|||
:nosearch:
|
||||
|
||||
=========
|
||||
Calendars
|
||||
=========
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
calendars/outlook/outlook_calendar
|
||||
calendars/google/google_calendar_credentials
|
||||
|
|
@@ -58,4 +58,4 @@ can change the Language to any previously installed language and click
|
|||
:align: center
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../websites/website/publish/translate`
|
||||
* :doc:`../../websites/website/configuration/translate`
|
||||
|
|
|
|||
|
|
@@ -8,5 +8,6 @@ Productivity
|
|||
.. toctree::
|
||||
|
||||
productivity/discuss
|
||||
productivity/calendar
|
||||
productivity/iot
|
||||
productivity/studio
|
||||
|
|
|
|||
11
content/applications/productivity/calendar.rst
Normal file
|
|
@@ -0,0 +1,11 @@
|
|||
:nosearch:
|
||||
|
||||
========
|
||||
Calendar
|
||||
========
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
calendar/outlook
|
||||
calendar/google
|
||||
|
|
@@ -1,6 +1,6 @@
|
|||
=====================================
|
||||
Synchronize Google Calendar with Odoo
|
||||
=====================================
|
||||
===============================
|
||||
Google Calendar synchronization
|
||||
===============================
|
||||
|
||||
Synchronize Google Calendar with Odoo to see and manage meetings from both platforms (updates go
|
||||
in both directions). This integration helps organize your schedule so you never miss a meeting.
|
||||
|
|
@@ -25,7 +25,7 @@ Begin by creating a new Google API project and enabling the Google Calendar API.
|
|||
|
||||
Next, click :guilabel:`Select a project` and select or create an API project to store credentials.
|
||||
|
||||
.. image:: google_calendar_credentials/new-api-project.png
|
||||
.. image:: google/new-api-project.png
|
||||
:align: center
|
||||
:alt: Create a new API project to store credentials.
|
||||
|
||||
|
|
@@ -34,14 +34,14 @@ Next, click :guilabel:`Select a project` and select or create an API project to
|
|||
|
||||
Then, open the API Project and click :guilabel:`Enable APIs and Services`.
|
||||
|
||||
.. image:: google_calendar_credentials/enable-apis-services.png
|
||||
.. image:: google/enable-apis-services.png
|
||||
:align: center
|
||||
:alt: Enable APIs and Services on the API Project.
|
||||
|
||||
After that, search for *Google Calendar API* using the search bar and select :guilabel:`Google
|
||||
Calendar API` from the search results. Click :guilabel:`Enable`.
|
||||
|
||||
.. image:: google_calendar_credentials/enable-google-cal-api.png
|
||||
.. image:: google/enable-google-cal-api.png
|
||||
:align: center
|
||||
:alt: Enable the Google Calendar API.
|
||||
|
||||
|
|
@@ -55,7 +55,7 @@ four steps to create your API credentials.
|
|||
- In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google Calendar API` and
|
||||
:guilabel:`User Data` options. Then, click :guilabel:`Next`.
|
||||
|
||||
.. image:: google_calendar_credentials/credential-type.png
|
||||
.. image:: google/credential-type.png
|
||||
:align: center
|
||||
:alt: Select Google Calendar API and User Data for the Credential Type.
|
||||
|
||||
|
|
@@ -76,7 +76,7 @@ four steps to create your API credentials.
|
|||
your company's Odoo URL address followed by */google_account/authentication*. Finally, click
|
||||
:guilabel:`Create` and :guilabel:`Done`.
|
||||
|
||||
.. image:: google_calendar_credentials/uri.png
|
||||
.. image:: google/uri.png
|
||||
:align: center
|
||||
:alt: Add the authorized JavaScript origins and the authorized redirect URIs.
|
||||
|
||||
|
|
@@ -94,7 +94,7 @@ Next, locate the credentials you just created for the Google Calendar API. Then,
|
|||
:guilabel:`Edit OAuth Client` (the pencil icon). The page will redirect to the edit page, where you
|
||||
can view the Client ID and the Client Secret.
|
||||
|
||||
.. image:: google_calendar_credentials/edit-oauth-2.png
|
||||
.. image:: google/edit-oauth-2.png
|
||||
:align: center
|
||||
:alt: Click Edit OAuth Client to view the credential details.
|
||||
|
||||
|
|
@@ -105,7 +105,7 @@ Once the Client ID and the Client Secret are located, open the Odoo database and
|
|||
:menuselection:`Settings --> General Settings --> Integrations --> Google Calendar`. Check the box
|
||||
next to :guilabel:`Google Calendar`.
|
||||
|
||||
.. image:: google_calendar_credentials/settings-google-cal.png
|
||||
.. image:: google/settings-google-cal.png
|
||||
:align: center
|
||||
:alt: The Google Calendar checkbox in General Settings.
|
||||
|
||||
|
|
@@ -116,7 +116,7 @@ page into their respective fields below the :guilabel:`Google Calendar` checkbox
|
|||
Finally, open the Calendar module in Odoo and click on the :guilabel:`Google` sync button to sync
|
||||
Google Calendar with Odoo.
|
||||
|
||||
.. image:: google_calendar_credentials/sync-google.png
|
||||
.. image:: google/sync-google.png
|
||||
:align: center
|
||||
:alt: Click the Google sync button in Odoo Calendar to sync Google Calendar with Odoo.
|
||||
|
||||
|
|
@@ -124,12 +124,12 @@ Google Calendar with Odoo.
|
|||
The first time you sync your Google Calendar with Odoo, the page will redirect to your Google
|
||||
Account. Click :guilabel:`OK` and :guilabel:`Allow` to authorize Odoo to access Google Calendar.
|
||||
|
||||
.. image:: google_calendar_credentials/trust-odoo.png
|
||||
.. image:: google/trust-odoo.png
|
||||
:align: center
|
||||
:alt: Give Odoo permission to access Google Calendar.
|
||||
|
||||
Now, Odoo Calendar is successfully synced with Google Calendar!
|
||||
|
||||
.. image:: google_calendar_credentials/successful-sync.png
|
||||
.. image:: google/successful-sync.png
|
||||
:align: center
|
||||
:alt: Successfully sync between Odoo and Google Calendar.
|
||||
|
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 30 KiB |
|
Before Width: | Height: | Size: 8.3 KiB After Width: | Height: | Size: 8.3 KiB |
|
Before Width: | Height: | Size: 8.4 KiB After Width: | Height: | Size: 8.4 KiB |
|
Before Width: | Height: | Size: 9.7 KiB After Width: | Height: | Size: 9.7 KiB |
|
Before Width: | Height: | Size: 8.4 KiB After Width: | Height: | Size: 8.4 KiB |
|
Before Width: | Height: | Size: 6.6 KiB After Width: | Height: | Size: 6.6 KiB |
|
Before Width: | Height: | Size: 32 KiB After Width: | Height: | Size: 32 KiB |
|
Before Width: | Height: | Size: 31 KiB After Width: | Height: | Size: 31 KiB |
|
Before Width: | Height: | Size: 27 KiB After Width: | Height: | Size: 27 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
|
|
@@ -1,6 +1,6 @@
|
|||
======================================
|
||||
Synchronize Outlook Calendar with Odoo
|
||||
======================================
|
||||
================================
|
||||
Outlook Calendar synchronization
|
||||
================================
|
||||
|
||||
Synchronizing a user's Outlook Calendar with Odoo is useful for keeping track of their tasks and
|
||||
appointments across all related applications.
|
||||
|
|
@@ -33,7 +33,7 @@ URI (URL) followed by `/microsoft_account/authentication`.
|
|||
Enter `https://www.companyname.odoo.com/microsoft_account/authentication` for the
|
||||
:guilabel:`Redirect URI`.
|
||||
|
||||
.. image:: outlook_calendar/azure-register-application.png
|
||||
.. image:: outlook/azure-register-application.png
|
||||
:align: center
|
||||
:alt: The "Supported account type" and "Redirect URI" settings in the Microsoft Azure AD portal.
|
||||
|
||||
|
|
@@ -58,27 +58,27 @@ Configuration in Odoo
|
|||
In the Odoo database, go to :menuselection:`Settings --> General Settings --> Integrations` and
|
||||
activate the :guilabel:`Outlook Calendar` setting.
|
||||
|
||||
.. image:: outlook_calendar/outlook-calendar-setting.png
|
||||
.. image:: outlook/outlook-calendar-setting.png
|
||||
:align: center
|
||||
:alt: The "Outlook Calendar" setting activated in Odoo.
|
||||
|
||||
From the Microsoft Azure portal, under the :guilabel:`Overview` section of the application, copy
|
||||
the :guilabel:`Application (Client) ID`, and paste it into the :guilabel:`Client ID` field in Odoo.
|
||||
|
||||
.. image:: outlook_calendar/client-id.png
|
||||
.. image:: outlook/client-id.png
|
||||
:align: center
|
||||
:alt: The "Client ID" in the Microsoft Azure portal.
|
||||
|
||||
In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` section, copy the
|
||||
:guilabel:`Client Secret Value` and paste it into the :guilabel:`Client Secret` field in Odoo.
|
||||
|
||||
.. image:: outlook_calendar/client-secret-value.png
|
||||
.. image:: outlook/client-secret-value.png
|
||||
:align: center
|
||||
:alt: The "Client Secret" token to be copied from Microsoft to Odoo.
|
||||
|
||||
Finally, on the Odoo :menuselection:`Settings --> General Settings` page, click :guilabel:`Save`.
|
||||
|
||||
.. _outlook_calendar/sync_with_outlook:
|
||||
.. _outlook/sync:
|
||||
|
||||
Sync with Outlook
|
||||
=================
|
||||
|
|
@@ -125,7 +125,7 @@ In the Odoo database, go to the :guilabel:`Calendar` module and click the :guila
|
|||
button. The page will redirect to a Microsoft login page, and the user is asked to log in to
|
||||
their account, if they are not already, and grant the required permissions.
|
||||
|
||||
.. image:: outlook_calendar/outlook-sync-button.png
|
||||
.. image:: outlook/outlook-sync-button.png
|
||||
:align: center
|
||||
:alt: The "Outlook" sync button in Odoo Calendar.
|
||||
|
||||
|
|
@@ -134,11 +134,11 @@ The synchronization is a two-way process, meaning that events are reconciled in
|
|||
|
||||
.. note::
|
||||
All users that want to use the synchronization simply need to :ref:`sync their calendar with
|
||||
Outlook <outlook_calendar/sync_with_outlook>`. The configuration of Microsoft's Azure account
|
||||
Outlook <outlook/sync>`. The configuration of Microsoft's Azure account
|
||||
is only done once, as Azure AD tenants' Client IDs and Client Secrets are unique, and represent
|
||||
an organization that helps the user to manage a specific instance of Microsoft cloud services
|
||||
for their internal and external users.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../sales/crm/optimize/outlook_extension`
|
||||
- :doc:`../google/google_calendar_credentials`
|
||||
- :doc:`../../sales/crm/optimize/outlook_extension`
|
||||
- :doc:`google`
|
||||
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 41 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 5.5 KiB After Width: | Height: | Size: 5.5 KiB |
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
|
|
@@ -10,5 +10,6 @@ Configuration
|
|||
|
||||
config/connect
|
||||
config/pos
|
||||
config/https_certificate_iot
|
||||
config/flash_sdcard
|
||||
config/troubleshooting
|
||||
|
|
|
|||
|
|
@@ -0,0 +1,260 @@
|
|||
.. _iot/https_certificate_iot:
|
||||
|
||||
=======================
|
||||
HTTPS certificate (IoT)
|
||||
=======================
|
||||
|
||||
What is HTTPS?
|
||||
==============
|
||||
|
||||
*Hypertext Transfer Protocol Secure* (HTTPS) is the secure version of *Hypertext Transfer Protocol*
|
||||
(HTTP), which is the primary protocol used to send data back and forth between a web browser and a
|
||||
website. :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` is encrypted in order to increase the
|
||||
security of data transfer.
|
||||
|
||||
:abbr:`HTTPS (Hypertext Transfer Protocol Secure)` uses an encryption protocol to encrypt
|
||||
communications. The protocol is called *Transport Layer Security* (TLS), although formerly it was
|
||||
known as *Secure Sockets Layer* (SSL).
|
||||
|
||||
:abbr:`HTTPS (Hypertext Transfer Protocol Secure)` occurs based upon the transmission of :abbr:`TLS
|
||||
(Transport Layer Security)`/:abbr:`SSL (Secure Sockets Layer)` certificates, which verify that a
|
||||
particular provider is who they say they are.
|
||||
|
||||
.. note::
|
||||
In this documentation and throughout Odoo the term "HTTPS certificate" will be used to define the
|
||||
fact that the :abbr:`SSL (Secure Sockets Layer)` certificate is valid and allows a :abbr:`HTTPS
|
||||
(Hypertext Transfer Protocol Secure)` connection.
|
||||
|
||||
Why is it needed?
|
||||
-----------------
|
||||
|
||||
In order to communicate with certain network devices (in particular for payment terminals), the
|
||||
usage of :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` is mandatory. If the :abbr:`HTTPS
|
||||
(Hypertext Transfer Protocol Secure)` certificate isn't valid, some devices won't be able to
|
||||
interact with the :abbr:`IoT (Internet of Things)` Box.
|
||||
|
||||
How to obtain a Hypertext Transfer Protocol Secure (HTTPS) certificate
|
||||
======================================================================
|
||||
|
||||
The generation of the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate is automatic.
|
||||
|
||||
The :abbr:`IoT (Internet of Things)` Box will send a specific request to `<https://www.odoo.com>`_
|
||||
which will send back the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate if the
|
||||
:abbr:`IoT (Internet of Things)` box and database are eligible.
|
||||
|
||||
.. _iot/iot-eligibility:
|
||||
|
||||
Internet of Things (IoT) eligibility
|
||||
------------------------------------
|
||||
|
||||
#. The database should be a **production** instance. The database instance should not be a copy, a
|
||||
duplicate, a staging, or a development environment.
|
||||
#. The Odoo subscription must:
|
||||
|
||||
- Have an :guilabel:`IoT Box Subscription` line.
|
||||
- :guilabel:`Status` must be :guilabel:`In Progress`.
|
||||
|
||||
If the subscription is linked to a `<https://www.odoo.com>`_ portal user check the information
|
||||
on the portal subscription page.
|
||||
|
||||
.. figure:: https_certificate_iot/sub-example-in-progress.png
|
||||
:align: center
|
||||
:alt: Odoo.com portal subscriptions filtered by "in progress".
|
||||
|
||||
In this case, both subscriptions are considered "in progress" as the :guilabel:`Filter By\:
|
||||
In Progress` was used.
|
||||
|
||||
.. note::
|
||||
If the subscription is in question, contact the database's Account Manager or Partner
|
||||
regarding the matter.
|
||||
|
||||
Troubleshooting Hypertext Transfer Protocol Secure (HTTPS) certificate errors
|
||||
=============================================================================
|
||||
|
||||
If anything goes wrong during the process of the "HTTPS certificate" generation or reception, a
|
||||
specific error will code be given on the :abbr:`IoT (Internet of Things)` box home page.
|
||||
|
||||
.. tip::
|
||||
Accessing the :abbr:`IoT (Internet of Things)` box homepage will check for the presence of the
|
||||
"HTTPS certificate" and will attempt its generation if it is missing. As such, if there is an
|
||||
error on the :abbr:`IoT (Internet of Things)` box home page, refresh the :abbr:`IoT (Internet of
|
||||
Things)` home page to see if the error disappears.
|
||||
|
||||
`ERR_IOT_HTTPS_CHECK_NO_SERVER`
|
||||
-------------------------------
|
||||
|
||||
Reason:
|
||||
The configuration regarding the server is missing. In other words, the Odoo instance is not
|
||||
connected with the IoT box.
|
||||
|
||||
Solution:
|
||||
Ensure that the server is configured.
|
||||
|
||||
.. seealso::
|
||||
:doc:`/applications/productivity/iot/config/connect`
|
||||
|
||||
`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`
|
||||
-----------------------------------------
|
||||
|
||||
Reason:
|
||||
An unhandled error happened when trying to read the existing :abbr:`HTTPS (Hypertext Transfer
|
||||
Protocol Secure)` certificate.
|
||||
|
||||
Solution:
|
||||
Ensure that the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate file is readable.
|
||||
|
||||
`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`
|
||||
----------------------------------
|
||||
|
||||
Reason:
|
||||
The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is missing.
|
||||
|
||||
Solution:
|
||||
Ensure that both values are configured as intended. To modify them, go to the :abbr:`IoT
|
||||
(Internet of Things)` box home page, and navigate to :guilabel:`Credential`.
|
||||
|
||||
`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`
|
||||
--------------------------------------
|
||||
|
||||
Reason:
|
||||
An unexpected error happened when the :abbr:`IoT (Internet of Things)` box tried to reach
|
||||
`<https://www.odoo.com>`_. The causes are likely due to the network
|
||||
infrastructure/configuration:
|
||||
|
||||
- The :abbr:`IoT (Internet of Things)` box does not have access to internet.
|
||||
- The network does not allow the :abbr:`IoT (Internet of Things)` box to communicate with
|
||||
`<https://www.odoo.com>`_. This may be due to network devices preventing the communication
|
||||
(firewalls, etc.) or the network configuration (:abbr:`VPN (Virtual Private Network)`,
|
||||
etc.).
|
||||
|
||||
.. note::
|
||||
More information regarding the error that occurred can be found in the full request
|
||||
exception details, which are in the :abbr:`IoT (Internet of Things)` box logs.
|
||||
|
||||
Solution:
|
||||
.. warning::
|
||||
Consult with your system or network administrator should this issue arise. This error code
|
||||
depends on the network infrastructure and goes beyond :doc:`Odoo support's service scope
|
||||
</services/support/what_can_i_expect>`.
|
||||
|
||||
`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`
|
||||
-----------------------------------
|
||||
|
||||
Reason:
|
||||
The IoT-box was able to reach `<https://www.odoo.com>`_ but received an unusual
|
||||
`HTTP response (status codes)
|
||||
<https://developer.mozilla.org/en-US/docs/Web/HTTP/Status>`_.
|
||||
|
||||
This error code will also give the HTTP response status codes. For example, if the error reads
|
||||
`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` it means that the page returned a 404 error, which is
|
||||
the "Page Not Found" code.
|
||||
|
||||
Solution:
|
||||
Check if `<https://www.odoo.com>`_ is down using a web browser, as it's possible that it is down
|
||||
due to maintenance.
|
||||
|
||||
- If `<https://www.odoo.com>`_ is down due to maintenance, unfortunately there is nothing that
|
||||
can be done but instead wait for it to recover.
|
||||
- If `<https://www.odoo.com>`_ is not down due to maintenance, open a `support ticket
|
||||
<https://www.odoo.com/help>`_ on the matter. Ensure that the 3 digits status code next to the
|
||||
code error is included in the support ticket.
|
||||
|
||||
`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`
|
||||
--------------------------------------
|
||||
|
||||
Reason:
|
||||
The :abbr:`IoT (Internet of Things)` box was able to reach `<https://www.odoo.com>`_ but it
|
||||
refused to deliver the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate.
|
||||
|
||||
Solution:
|
||||
Ensure that the :abbr:`IoT (Internet of Things)` box and database are eligible for a
|
||||
certificate: :ref:`Internet of Things (IoT) eligibility <iot/iot-eligibility>`.
|
||||
|
||||
How to ensure that the HTTPS certificate is correct
|
||||
===================================================
|
||||
|
||||
If the certificate has been applied successfully, a new :abbr:`HTTPS (Hypertext Transfer Protocol
|
||||
Secure)` :abbr:`URL (Uniform Resource Locator)` for the :abbr:`IoT (Internet of Things)` box ending
|
||||
with `.odoo-iot.com` will appear on the Odoo database, inside of the :menuselection:`IoT`
|
||||
application on that specific device's form.
|
||||
|
||||
.. image:: https_certificate_iot/odoo-new-domain.png
|
||||
:align: center
|
||||
:alt: Odoo IoT app IoT box with .odoo-iot.com domain.
|
||||
|
||||
When navigating to the :abbr:`URL (Uniform Resource Locator)` in a browser a secured :abbr:`HTTPS
|
||||
(Hypertext Transfer Protocol Secure)` connection will be established.
|
||||
|
||||
.. figure:: https_certificate_iot/secured-connection.png
|
||||
:align: center
|
||||
:alt: Example of valid SSL certificate details on the browser.
|
||||
|
||||
Padlock in Chrome on Windows 10 attesting the fact that the connection is secured in :abbr:`HTTPS
|
||||
(Hypertext Transfer Protocol Secure)`.
|
||||
|
||||
The IoT-box homepage will now display an `OK` status next to `HTTPS certificate`. The
|
||||
drop-down menu icon, when clicked, will reveal information regarding the certificate.
|
||||
|
||||
.. image:: https_certificate_iot/status-ok.png
|
||||
:align: center
|
||||
:alt: IoT box homepage with HTTPS certificate OK status.
|
||||
|
||||
Domain Name System (DNS) issue
|
||||
==============================
|
||||
|
||||
If the :abbr:`IoT (Internet of Things)` box can be accessed from its :abbr:`IP (Intrernet Protocol)`
|
||||
address but not the Odoo assigned domain: `.odoo-iot.com`; then the :abbr:`IoT (Internet of Things)`
|
||||
box is likely running into a :abbr:`DNS (Domain Name System)` issue. On some browsers, it will give
|
||||
an error code mentioning :abbr:`DNS (Domain Name System)` (like `DNS_PROBE_FINISHED_NXDOMAIN`).
|
||||
|
||||
These :abbr:`DNS (Domain Name System)` issues may appear as the following in different browsers:
|
||||
|
||||
.. tabs::
|
||||
|
||||
.. tab:: Chrome
|
||||
|
||||
.. figure:: https_certificate_iot/dns-chrome.png
|
||||
:align: center
|
||||
:alt: DNS issue on Chrome browser on Windows 10.
|
||||
|
||||
DNS issue on Chrome browser on Windows 10.
|
||||
|
||||
|
||||
.. tab:: Firefox
|
||||
|
||||
.. figure:: https_certificate_iot/dns-firefox.png
|
||||
:align: center
|
||||
:alt: DNS issue on Firefox browser on Windows 10.
|
||||
|
||||
DNS issue on Firefox browser on Windows 10.
|
||||
|
||||
.. tab:: Edge
|
||||
|
||||
.. figure:: https_certificate_iot/dns-edge.png
|
||||
:align: center
|
||||
:alt: DNS issue on Edge browser on Windows 10.
|
||||
|
||||
DNS issue on Edge browser on Windows 10.
|
||||
|
||||
|
||||
Domain Name System (DNS) issue solution
|
||||
---------------------------------------
|
||||
|
||||
#. Should the router allow the :abbr:`DNS (Domain Name System)` to be manually changed, change the
|
||||
DNS to use `Google DNS <https://developers.google.com/speed/public-dns>`_.
|
||||
#. If your router doesn't allow for this, then a change will need to be made on the :abbr:`DNS
|
||||
(Domain Name System)` settings of each of the devices using `Google DNS
|
||||
<https://developers.google.com/speed/public-dns>`_. This will need to occur on **every** device
|
||||
that plans to interact with the :abbr:`IoT (Internet of Things)` box (e.g. computer, tablet or
|
||||
phone). The individual device configuration processes can be found on the website of the
|
||||
device's manufacturer.
|
||||
|
||||
.. note::
|
||||
Other :abbr:`IoT (Internet of Things)` devices such as payment terminals likely won't need
|
||||
their :abbr:`DNS (Domain Name System)` settings changed as they are already configured with
|
||||
custom :abbr:`DNS (Domain Name System)`.
|
||||
|
||||
.. warning::
|
||||
Consult with your system or network administrator should this issue arise. This error code
|
||||
depends on the network infrastructure, and it goes beyond :doc:`Odoo support's service scope
|
||||
</services/support/what_can_i_expect>`.
|
||||
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 6.2 KiB |
|
After Width: | Height: | Size: 34 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
|
@@ -58,7 +58,7 @@ Live Chat
|
|||
| Through live interactions with your website visitors, helpdesk tickets can be instantly created
|
||||
and redirected to the right person.
|
||||
| Click on your helpdesk team's name - for the example below: *Customer Care* -
|
||||
and :doc:`set up your channel </applications/websites/livechat/overview/get_started>`.
|
||||
and :doc:`set up your channel </applications/websites/livechat>`.
|
||||
|
||||
.. image:: receiving_tickets/live_chat.png
|
||||
:align: center
|
||||
|
|
@@ -66,7 +66,7 @@ Live Chat
|
|||
in Odoo Helpdesk
|
||||
|
||||
Now, your operators can create tickets by using the
|
||||
:doc:`command </applications/websites/livechat/overview/responses>` */helpdesk (subject_of_ticket)*.
|
||||
:doc:`command </applications/websites/livechat/responses>` */helpdesk (subject_of_ticket)*.
|
||||
|
||||
Prioritize tickets
|
||||
==================
|
||||
|
|
|
|||
|
|
@@ -28,4 +28,4 @@ See how to configure your products from links here below.
|
|||
- :doc:`../maximizing_revenue/cross_selling`
|
||||
- :doc:`../maximizing_revenue/reviews`
|
||||
- :doc:`../maximizing_revenue/pricing`
|
||||
- :doc:`../../website/optimize/seo`
|
||||
- :doc:`../../website/pages/seo`
|
||||
|
|
|
|||
|
|
@@ -1,16 +1,87 @@
|
|||
:nosearch:
|
||||
:show-content:
|
||||
:hide-page-toc:
|
||||
:show-toc:
|
||||
|
||||
=========
|
||||
Live Chat
|
||||
=========
|
||||
|
||||
Live Chat has the highest satisfaction rating of any communication tool. It allows fast responses
|
||||
and it is accessible and convenient, as your customers can keep doing what they are doing while
|
||||
interacting with you. Remember: your customers want to talk to you, so let's make it easy.
|
||||
|
||||
.. seealso::
|
||||
- `Live Chat: product page <https://www.odoo.com/app/live-chat>`_
|
||||
- :doc:`livechat/ratings`
|
||||
- :doc:`livechat/responses`
|
||||
|
||||
Set up
|
||||
======
|
||||
|
||||
Once *Live Chat* is installed on your database, if your website was created with Odoo, the
|
||||
application is automatically added to it. All that is left to do is to go to
|
||||
:menuselection:`Website --> Configuration --> Settings --> Live Chat`.
|
||||
|
||||
.. image:: livechat/livechat_settings.png
|
||||
:height: 300
|
||||
:alt: View of the settings page and the live chat feature for Odoo Live Chat
|
||||
|
||||
Select the channel to be linked to your website or create one on the fly.
|
||||
|
||||
.. image:: livechat/channels.png
|
||||
:alt: View of a live chat channel form for Odoo Live Chat
|
||||
|
||||
| For both scenarios, under:
|
||||
| - **Operators**: add agents to respond to the chat requests. Add as many as you like, and keep in
|
||||
mind that operators that do not show any activity in Odoo for more than 30min are considered
|
||||
disconnected.
|
||||
| - **Options**: set the default text to be shown on the live chat button; an automated welcome
|
||||
message to be seen by visitors when a conversation is initiated, and the text that prompts the
|
||||
user to initiate a chat.
|
||||
| - **Channel Rules**: choose an action for a given URL, and/or per country. In the example below,
|
||||
the chat window automatically pops-up 3 seconds after users (from any country) land on the
|
||||
contact us page.
|
||||
|
||||
.. image:: livechat/rules.png
|
||||
:alt: View of a channel’s rules form for Odoo Live Chat
|
||||
|
||||
.. note::
|
||||
GeoIP, which refers to the process of finding a computer terminal’s geographical location by its
|
||||
IP address, must be installed on your server. Otherwise, under *Channel Rules*, countries are
|
||||
not taken into account.
|
||||
|
||||
External options
|
||||
----------------
|
||||
|
||||
| If your website was not created with Odoo, you can find the code to be added to your own, under
|
||||
the *Widget* tab.
|
||||
| Odoo also offers an URL you can send to users so they can have access to a single live chat page.
|
||||
|
||||
.. image:: livechat/widget.png
|
||||
:alt: View of the widget tab for Odoo Live Chat
|
||||
|
||||
Managing chat requests
|
||||
======================
|
||||
|
||||
Conversations initiated by visitors pop up as a direct message, and are shown in *Discuss*.
|
||||
Therefore, inquiries can be answered wherever you are in Odoo.
|
||||
|
||||
.. image:: livechat/discuss.png
|
||||
:alt: View of the discuss application with a message sent through live chat in Odoo
|
||||
|
||||
.. note::
|
||||
Conversations are dispatched based on the current workload of the online operators.
|
||||
|
||||
Leave or join a channel
|
||||
=======================
|
||||
|
||||
Go to :menuselection:`Website --> Configuration --> Settings`, access your channel under
|
||||
*Live Chat*, and *Join Channel* or *Leave Channel*.
|
||||
|
||||
.. image:: livechat/joinchannel.png
|
||||
:alt: View of a channel form and the option to join a channel for Odoo Live Chat
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
livechat/overview
|
||||
livechat/ratings
|
||||
livechat/responses
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 37 KiB After Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 42 KiB After Width: | Height: | Size: 42 KiB |
|
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 44 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
|
@@ -1,12 +0,0 @@
|
|||
:nosearch:
|
||||
|
||||
========
|
||||
Overview
|
||||
========
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
overview/get_started
|
||||
overview/ratings
|
||||
overview/responses
|
||||
|
|
@@ -1,83 +0,0 @@
|
|||
==========================
|
||||
Get Started with Live Chat
|
||||
==========================
|
||||
|
||||
Live Chat has the highest satisfaction rating of any communication tool. It allows fast responses
|
||||
and it is accessible and convenient, as your customers can keep doing what they are doing while
|
||||
interacting with you. Remember: your customers want to talk to you, so let's make it easy.
|
||||
|
||||
Set up
|
||||
======
|
||||
|
||||
Once *Live Chat* is installed on your database, if your website was created with Odoo, the
|
||||
application is automatically added to it. All that is left to do is to go to
|
||||
:menuselection:`Website --> Configuration --> Settings --> Live Chat`.
|
||||
|
||||
.. image:: get_started/livechat_settings.png
|
||||
:align: center
|
||||
:height: 300
|
||||
:alt: View of the settings page and the live chat feature for Odoo Live Chat
|
||||
|
||||
Select the channel to be linked to your website or create one on the fly.
|
||||
|
||||
.. image:: get_started/channels.png
|
||||
:align: center
|
||||
:alt: View of a live chat channel form for Odoo Live Chat
|
||||
|
||||
| For both scenarios, under:
|
||||
| - **Operators**: add agents to respond to the chat requests. Add as many as you like, and keep in
|
||||
mind that operators that do not show any activity in Odoo for more than 30min are considered
|
||||
disconnected.
|
||||
| - **Options**: set the default text to be shown on the live chat button; an automated welcome
|
||||
message to be seen by visitors when a conversation is initiated, and the text that prompts the
|
||||
user to initiate a chat.
|
||||
| - **Channel Rules**: choose an action for a given URL, and/or per country. In the example below,
|
||||
the chat window automatically pops-up 3 seconds after users (from any country) land on the
|
||||
contact us page.
|
||||
|
||||
.. image:: get_started/rules.png
|
||||
:align: center
|
||||
:alt: View of a channel’s rules form for Odoo Live Chat
|
||||
|
||||
.. note::
|
||||
GeoIP, which refers to the process of finding a computer terminal’s geographical location by its
|
||||
IP address, must be installed on your server. Otherwise, under *Channel Rules*, countries are
|
||||
not taken into account.
|
||||
|
||||
External options
|
||||
----------------
|
||||
|
||||
| If your website was not created with Odoo, you can find the code to be added to your own, under
|
||||
the *Widget* tab.
|
||||
| Odoo also offers an URL you can send to users so they can have access to a single live chat page.
|
||||
|
||||
.. image:: get_started/widget.png
|
||||
:align: center
|
||||
:alt: View of the widget tab for Odoo Live Chat
|
||||
|
||||
Managing chat requests
|
||||
======================
|
||||
|
||||
Conversations initiated by visitors pop up as a direct message, and are shown in *Discuss*.
|
||||
Therefore, inquiries can be answered wherever you are in Odoo.
|
||||
|
||||
.. image:: get_started/discuss.png
|
||||
:align: center
|
||||
:alt: View of the discuss application with a message sent through live chat in Odoo
|
||||
|
||||
.. note::
|
||||
Conversations are dispatched based on the current workload of the online operators.
|
||||
|
||||
Leave or join a channel
|
||||
=======================
|
||||
|
||||
Go to :menuselection:`Website --> Configuration --> Settings`, access your channel under
|
||||
*Live Chat*, and *Join Channel* or *Leave Channel*.
|
||||
|
||||
.. image:: get_started/joinchannel.png
|
||||
:align: center
|
||||
:alt: View of a channel form and the option to join a channel for Odoo Live Chat
|
||||
|
||||
.. seealso::
|
||||
- :doc:`ratings`
|
||||
- :doc:`responses`
|
||||
|
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 29 KiB |
|
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 30 KiB |
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 41 KiB |
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 24 KiB |
|
Before Width: | Height: | Size: 5.4 KiB After Width: | Height: | Size: 5.4 KiB |
|
Before Width: | Height: | Size: 6.9 KiB After Width: | Height: | Size: 6.9 KiB |
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
|
|
@@ -23,5 +23,6 @@ convert visitors into leads or revenues.
|
|||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
website/publish
|
||||
website/optimize
|
||||
website/pages
|
||||
website/configuration
|
||||
website/reporting
|
||||
|
|
|
|||
13
content/applications/websites/website/configuration.rst
Normal file
|
|
@@ -0,0 +1,13 @@
|
|||
:nosearch:
|
||||
|
||||
=============
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
configuration/translate
|
||||
configuration/multi_website
|
||||
configuration/unsplash
|
||||
configuration/on-premise_geo-ip-installation
|
||||
|
|
@@ -1,6 +1,6 @@
|
|||
=====================
|
||||
Manage Multi Websites
|
||||
=====================
|
||||
=================
|
||||
Multiple websites
|
||||
=================
|
||||
|
||||
.. image:: multi_website/multi_website04.png
|
||||
:align: center
|
||||
|
Before Width: | Height: | Size: 3.5 KiB After Width: | Height: | Size: 3.5 KiB |
|
Before Width: | Height: | Size: 4.0 KiB After Width: | Height: | Size: 4.0 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 116 KiB After Width: | Height: | Size: 116 KiB |
|
Before Width: | Height: | Size: 3.5 KiB After Width: | Height: | Size: 3.5 KiB |
|
Before Width: | Height: | Size: 6.3 KiB After Width: | Height: | Size: 6.3 KiB |
|
Before Width: | Height: | Size: 8.5 KiB After Width: | Height: | Size: 8.5 KiB |
|
Before Width: | Height: | Size: 228 KiB After Width: | Height: | Size: 228 KiB |
|
Before Width: | Height: | Size: 5.2 KiB After Width: | Height: | Size: 5.2 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 5.7 KiB After Width: | Height: | Size: 5.7 KiB |
|
Before Width: | Height: | Size: 7.5 KiB After Width: | Height: | Size: 7.5 KiB |
|
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 6.1 KiB After Width: | Height: | Size: 6.1 KiB |
|
Before Width: | Height: | Size: 4.1 KiB After Width: | Height: | Size: 4.1 KiB |
|
Before Width: | Height: | Size: 4.8 KiB After Width: | Height: | Size: 4.8 KiB |
|
Before Width: | Height: | Size: 5.9 KiB After Width: | Height: | Size: 5.9 KiB |
|
Before Width: | Height: | Size: 73 KiB After Width: | Height: | Size: 73 KiB |
|
|
@@ -1,9 +1,6 @@
|
|||
===========================
|
||||
How to translate my website
|
||||
===========================
|
||||
|
||||
Overview
|
||||
========
|
||||
============
|
||||
Translations
|
||||
============
|
||||
|
||||
In addition to creating great modern websites, Odoo gives you the
|
||||
possibility to translate it in different languages.
|
||||
|
Before Width: | Height: | Size: 38 KiB After Width: | Height: | Size: 38 KiB |
|
Before Width: | Height: | Size: 9.9 KiB After Width: | Height: | Size: 9.9 KiB |
|
Before Width: | Height: | Size: 38 KiB After Width: | Height: | Size: 38 KiB |
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 47 KiB After Width: | Height: | Size: 47 KiB |
|
Before Width: | Height: | Size: 37 KiB After Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 8.5 KiB After Width: | Height: | Size: 8.5 KiB |
|
Before Width: | Height: | Size: 39 KiB After Width: | Height: | Size: 39 KiB |
|
|
@@ -1,14 +0,0 @@
|
|||
:nosearch:
|
||||
|
||||
========
|
||||
Optimize
|
||||
========
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
optimize/seo
|
||||
optimize/google_analytics
|
||||
optimize/google_analytics_dashboard
|
||||
optimize/link_tracker
|
||||
optimize/unsplash
|
||||
10
content/applications/websites/website/pages.rst
Normal file
|
|
@@ -0,0 +1,10 @@
|
|||
:nosearch:
|
||||
|
||||
=====
|
||||
Pages
|
||||
=====
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
pages/seo
|
||||
|
|
@@ -1,6 +1,6 @@
|
|||
==================================================
|
||||
How to do Search Engine Optimisation (SEO) in Odoo
|
||||
==================================================
|
||||
================================
|
||||
Search Engine Optimisation (SEO)
|
||||
================================
|
||||
|
||||
Search Engine Optimization (SEO) is a set of good practices to optimize
|
||||
your website so that you get a better ranking in search engines like
|
||||
|
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 21 KiB |
|
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 58 KiB |
|
Before Width: | Height: | Size: 6.8 KiB After Width: | Height: | Size: 6.8 KiB |
|
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 58 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 56 KiB |
|
Before Width: | Height: | Size: 9.2 KiB After Width: | Height: | Size: 9.2 KiB |