This commit rewords a little bit the part of the doc about
supported browsers, with an emphasis on the fact that the browser
must always be up-to-date, which customers sometimes forget (and
report issues because of this).
See https://github.com/odoo/odoo/pull/184894closesodoo/documentation#13079
X-original-commit: c83aed159f
Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
The ticket form page was moved to /help-form following the restructuration of
the /help page. Directly linking to the ticket form page should make it easier
for users.
closesodoo/documentation#12992
X-original-commit: b88c4d0f0e
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Partners and/or fiduciaries need a list of the databases they manage in
order to be able to make some RPC requests to all their databases.
This commit adds a section in the documentation to explain how to query
this new API and provides examples both for XML-RPC and JSON-RPC.
closesodoo/documentation#12879
Related-to: odoo/internal#3492
Task-id: 3229798
X-original-commit: c6f143df17
Signed-off-by: Olivier Dony (odo) <odo@odoo.com>
Signed-off-by: Paul Morelle (pmo) <pmo@odoo.com>
As stated on the sentence above, in case of an issue with the **production**
database, we should open a ticket with the label (production) and not
testing an upgrade.
This commits adapt the test to match the label currently present on
odoo.com/help and the URL to pre-select the correct stage as well
closesodoo/documentation#11559
X-original-commit: 08c43b3deb
Signed-off-by: Nathan Marotte (nama) <nama@odoo.com>
Before odoo.sh had two types of role, `user` and `admin`. A third role, `tester`,
was added between the two, and the user role was renamed `developer`.
closesodoo/documentation#11058
X-original-commit: f53cdc64cb
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
We often get questions from customers about errors they see running the
upgrade-script, which are caused by restrictions of their environment. Add a
note that mentions the most important requirements to maybe avoid some of these
questions.
closesodoo/documentation#10941
X-original-commit: 2a5e686783
Signed-off-by: Carsten Wolff (cawo) <cawo@odoo.com>
1/ Revamp of email_servers to be a introduction and allow correct redirection
+ redirection to other pages linked to mailing + ToC of email_communication folder
2/ Splitting inbound and outbound message into subfiles:
2.a/ email_servers_inbound: all documentation related to incoming emails
2.b/ email_servers_outbound: documentartion related to outgoing emails
3/ email_domain (as before) about authentication protocols to set on domains.
4/ faq: complete revamp to better match usual issues about mailings.
Also: removed unused images, adding anchors on other docs.
RST co-authored-by: jorv-odoo, jqu-odoo, xpl-odoo
doc writers:
- email_servers_inbound by qco-odoo
- email_servers_outbound by EMBR
- email_servers by abridbus
- email_domain by jqu-odoo
- faq by jorv-odoo
related documentation task-3875591
closesodoo/documentation#9935
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
The phrase is confusing and leads customers to contact support to carry out
the upgrade for them.
closesodoo/documentation#9896
X-original-commit: 8e143196f1
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
This commit updates the documentation for neutralized databases to
include information about how search engine indexing is prevented for
these databases.
task-3895772
closesodoo/documentation#9708
X-original-commit: c770eb5618
Signed-off-by: Serge Bayet (seba) <seba@odoo.com>
Prior to this commit, users had to either know in advance or guess the
location of the content they were looking for. Top-level pages of the
"Developer" section of the documentation, in particular the "Developer"
page itself, were listing their sub-pages without directions for users.
This commit brings the following changes to improve the navigation:
- add directions for users on the "Developer" page and list the three
main categories of developer documentation ("Tutorials", "How-to
guides", and "Reference") with explanations of their content and
target audience;
- add categories for content cards on the "Tutorials" and "How-to
guides" pages, and fine-tune the toctree of the "Reference" page to
more easily locate specific topics;
- clarify what are the "Python framework" and the "JavaScript framework"
by relabelling them to "Server framework" and "Web framework" on
top-level pages, as some users were confused to find that the JS
framework was not responsible for the server, and others that the
documentation for QWeb template is located in the Python documentation;
- extract the "Setup guide" from the "Getting started" tutorial and
rename the latter to "Server framework 101" to allow reusing the setup
guide in other tutorials and make clear that the "Server framework 101"
tutorial is not about the Web framework.
task-3802536
closesodoo/documentation#8597
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Co-authored-by: Valeriya (vchu) <vchu@odoo.com>
Screenshot taken from Odoo 16 database with the option to upgrade to Odoo 17
closesodoo/documentation#8212
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
This commit aims to improve the documentation's navigability by
redefining some categories' purposes and titles.
There is a redirection rule for each documentation page moved.
This ensures that users won't have a 404 error message.
task-3217827
closesodoo/documentation#8061
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
