Cleared up some confusion about path menu and feature
Forward to master
taskid-3644544
closesodoo/documentation#7195
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Changed a note that was confusing to end users. Forward to 16.3
16.3 & 16.4 --> Fetch Account/Reconnect
17.0 --> Reconnect
taskid-3619168
closesodoo/documentation#6886
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Install nginx using the nginx configuration found in the documentation
and changes the `listen` port to 8080. Start Odoo in `--proxy-mode`.
listen 8080;
server_name mycompany.odoo.com;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
location / {
proxy_pass http://127.0.0.1:8069;
}
Inside your browser, access "http://mycompany.odoo.com:8080" you are
wrongly redirected to "http://mycompany.odoo.com:80".
Odoo uses the `X-Forwarded-Host` http header value to generate new URls,
in this configuration `$host` only contains the domain (=hostname using
the urllib terminology) instead of the domain+port (=netloc). The
variable that contains both the domain and the port is actually
`$http_host`.
closesodoo/documentation#6885Closes: odoo/odoo#64643
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Updated the chart of accounts page. Forward to master.
16.3 -> Change "ellipsis" menu button
17 -> Change "Setup" to "View"
taskid-3609365
closesodoo/documentation#6617
Signed-off-by: Tom Aarab (toaa) <toaa@odoo.com>
Many customers struggle with their web server configuration, notably
regarding the `--proxy-mode` option and the way `X-Forwarded-*` HTTP
request headers are interpreted within Odoo.
The `--proxy-mode` section has been updated to cover the most common
misunderstandings and to give guidances on how to setup a web server.
Odoo always only takes the last entry of the `X-Forwarded-*` request
header because there are situations where it is not possible to
determine which last n-th entry to use. Employees might access their
odoo database via the internal network: connecting directly to nginx,
while customers might access the database via an additional proxy such
as cloudflare. The real IP of employees would be the last inside the
`X-Forwarded-For` chain, while the real IP of customers would be the
*second* last entry inside the chain. It would be incorrect to always
take the same nth last entry inside the chain. The cloudflare's own IP
address must be discarded from the chain. Web servers usually feature
a way to ignore trusted IP from the chain, a way so that the real IP
of the user is always the last entry inside the chain. Odoo relies on
such feature to be active and configured.
Prior discussions about `X-Forwarded-For`:
* odoo/odoo#104947
* odoo/odoo#118629
* odoo/odoo#139536
All `X-Forwarded-*` headers are ignored in case the `X-Forwarded-Host`
header is missing (even with `--proxy-mode`). System admin might be
tempted to not set this header and to set `Host` instead, this is
broken as this a user-agent would be able to spoof `X-Forwarded-Host`
and Odoo would use that instead of the correct `Host`.
Prior discussions about `X-Forwarded-Host`:
* odoo/odoo#63277
* odoo/odoo#70117closesodoo/documentation#6729
Signed-off-by: Julien Castiaux (juc) <juc@odoo.com>
Without the :show-content: metadata markup, it is not possible to open the
page by navigating from the toctree.
closesodoo/documentation#6522
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
For some reason, the first-person was used throughout the IAP
documentation, and quite inconsistently.
As the rest of the documentation is using second-person writing, IAP
should be no exception.
closesodoo/documentation#6286
X-original-commit: 8d0ae3b5df
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Louis Baudoux (lba) <lba@odoo.com>
It has been decided to remove the possibility for our users to create
their own IAP services.
This decision was motivated by the fact that, in the 5 years of
existence of IAP, very few non-Odoo services have been created and
actively used by our customers.
X-original-commit: d8c7269786
Part-of: odoo/documentation#6286
We have introduced a second version of the Extract API that adds the IAP
account token to the `get_result` and `validate` routes.
There are also other changes in this commit:
- The deprecated stuff has been removed as it's been deprecated for a
while and won't be supported anymore in the future.
- The `status` table of the `get_result` route has been added as it was
missing for some reason.
- The documentation regarding the `/validate` routes have been removed
for security reasons.
closesodoo/documentation#6275
X-original-commit: a8c6272899
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Louis Baudoux (lba) <lba@odoo.com>
In the CLI, `--unaccent` try to enable PostgreSQL unaccent extention
when odoo is responsible to create new database(s).
closesodoo/documentation#6236
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Added a note to make it clearer that for fiduciaries, a single API key
is valid for all databases linked to the user.
taskid-3570700
closesodoo/documentation#6212
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
We used to document the extract API according to the version of the
documentation that is being viewed, i.e. in version 14, we
documented the API version that was used in Odoo 14.
This is actually not a good idea as the extract API isn't strictly
linked to Odoo versions, it has its own versioning system.
It can also be an issue if users don't realize they're viewing an old
version of the API and start implementing customizations based on it.
This commit is an exact copy of the current `master` version of the
extract API documentation.
closesodoo/documentation#6218
X-original-commit: f8adea7845
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Louis Baudoux (lba) <lba@odoo.com>
A new way to disable IAP accounts has been introduced recently.
This feature is mostly used in neutralization scripts to prevent
customers from accidentaly consuming their credits on their
staging/testing databases.
Documenting it will help users re-enable their accounts if they still
wish to use it in a testing environment.
closesodoo/documentation#6132
X-original-commit: fa604a95b0
Signed-off-by: Louis Baudoux (lba) <lba@odoo.com>
Results of seeing a lot of wrong and missing configuration
on consultancy project for Outlook accounts.
The Multi outgoing mail server is harder to maintain than having
a unique mail server with an Odoo db correctly configured.
Insisting on the mail.default.from (ICP) and the From Filtering
parameters that NEEDS TO BE set up.
task-3512379
[FIX] Maintain: Azure_oauth: configuration mail server Outlook
Co-author-by: tiku-odoo <tiku@odoo.com>
Co-author-by: jqu-odoo <jqu@odoo.com>
Results of seeing a lot of wrong and missing configuration
on consultancy project for Outlook accounts.
The Multi outgoing mail server is harder to maintain than having
a unique mail server with an Odoo db correctly configured.
Insisting on the mail.default.from (ICP) and the From Filtering
parameters that NEEDS TO BE set up.
task-3512379
closesodoo/documentation#5909
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Many users don't start odoo-bin in --workers (multi-processing) mode but
instead leave the default configuration which use the development/demo
multi-threaded server, even in production.
This commit rewords the section about the difference between the
built-in servers and highlight the many advantages of the
multi-processing on. It repeats that information when it comes to
running a dedicated cron server, that it should use the multi-processing
server instead of the default multi-threading one.
closesodoo/documentation#5885Fixes: odoo/odoo#88984Closes: odoo/odoo#128571
X-original-commit: 9ee92c3a27
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
Signed-off-by: Julien Castiaux (juc) <juc@odoo.com>
It has always been the case informally but write it in the doc.
closesodoo/documentation#5828
X-original-commit: 80e1065dff
Signed-off-by: Olivier Dony (odo) <odo@odoo.com>
The documentation is unclear about the unit used for the --limit-memory-soft
and --limit-memory-hard options of odoo-bin. The unit used is bytes, but
it isn't mentioned and the default unit is shown in mebibytes, causing
confusion.
closesodoo/documentation#5787
X-original-commit: 9fadc3355d
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
This PR updates the page's content as it is a bit dated in some places
(see task) and takes into consideration the latest rst guidelines.
task-3434787
closesodoo/documentation#5738
X-original-commit: 8e41b58834
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Added a note explaining that the filestores from the upgraded database
and the production database have to be merged for on-premise upgrade,
on both the testing and the production phases
closesodoo/documentation#5722
X-original-commit: 28cacd3b98
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
task-2790245
- Update existing Google Analytics page for GA4
- Move warning from google_analytics_dashboard.rst to GA doc page
- Remove google_analytics_dashboard.rst as it's no longer useful
closesodoo/documentation#5594
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
In the multi-company HMRC submission section, the documentation mentions
that you can connect to HMRC from the user form, after having reset the
credentials.
This is not true, you have to go back to the tax report and click the
"Connect to HMRC" button.
opw-3449939
closesodoo/documentation#5663
X-original-commit: 39c0515208
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Arnaud Sibille (arsi) <arsi@odoo.com>
Updated an outdated screenshot from V14 to V15
Forward to master.
taskid-3467638
closesodoo/documentation#5606
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
This page used to be hosted as an "orphan" page in the documentation
repository. It now is displayed on the support form page at
www.odoo.com/help making this page redundant. This commit deletes that
page and a redirection pointing to the support form has been set.
task-3027584
closesodoo/documentation#5575
X-original-commit: fd2c0b8010
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
This PR moves the introduction about the different installation methods and editions found on the
install/install.rst page directly under the main install/ page. It creates three pages, one per
installation method documented on the install/install.rst page (Docker being documented on
docker.com and maintained by us), and moves the related content there. In addition, it fixes various
typos/grammar issues and improves the content according to the documentation guidelines. Various
references and links across the documentation had to be fixed accordingly.
task-3459070
closesodoo/documentation#5522
X-original-commit: b7d5d04229
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
The current default daily limit for one-app free
is 20 mails only. This commit updates the value.
closesodoo/documentation#5501
X-original-commit: c0ca09cdde
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
Commit f36c612d13 changed the model name
in Chapter 4 without updating the other occurences.
closesodoo/documentation#5499
X-original-commit: 51a2dbd01e
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
This commit also moves all versions from 8.0 to 12.0 from the table to
the "older versions" section.
closesodoo/documentation#5320
X-original-commit: 6225ef9e32
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Forward to master.
Change 16.3 onwards (screenshots)
Improved the doc and added some info on debit notes (was missing).
taskid-3439169
closesodoo/documentation#5190
Signed-off-by: Tom Aarab (toaa) <toaa@odoo.com>
I removed the dot notation in the "_name" variable for the example
model. AKA, "test.model" is now named "test_model".
Dot notation implies a data structure relationship between a <model> and
it's parent (or class etc) <test> (like test.model() or Test.model).
There is no relationship like this between a <test> and <model> - it's
just one thing: a <test model>.
The seeming "benefit" of the ORM translating dots to underscores doesn't
justify this naming convention. Yes, I know it's a string, but still,
this seems confusing for newbies and adds unnecessary complexity (why
name the same thing differently in different places?)
closesodoo/documentation#5135
X-original-commit: f36c612d13
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
In chapter 13 the `property_ids` field is defined as the inverse of a
`user_id` field. But in chapter 8 when the salesperson field is added,
no such name is given to it.
This commit adapts the description to reference the general concept of
the field used to link to the salesperson instead of an actual field
identifier.
task-3381757
closesodoo/documentation#4901
X-original-commit: 3a131c829a
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
The attributes of fields of list views do not mention the `optional`
attribute while it is used by chapter 12 of the R&D Training.
This commit describes this `optional` attribute.
task-3380953
closesodoo/documentation#4900
X-original-commit: 5a446f5c59
Signed-off-by: Benoit Socias (bso) <bso@odoo.com>
