In `conf.py`, we try to find a Odoo sources folder among `odoo` and
`../odoo` directories without really checking that they really are
Odoo sources folders, leading to doc generation error if it's not the case.
So, to improve that, this commit checks that the selected Odoo sources folder
contains `odoo-bin`.
While we're at it, the logging is also improved to always display the
matching odoo sources' folder and version.
closesodoo/documentation#1333
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Co-authored-by: Antoine Vandevenne <anv@odoo.com>
New taxes generated by the TaxCloud integration are by default created without an income or an expense account specified. By default, the journal items corresponding to these taxes therefore end up in the default income account, which is usually the 'Sales' account, when they should in fact go to the 'Tax Payable' account. Because these taxes are automatically generated on-the-fly, the user is usually not able to manually specify the Tax Payable account before the journal items are posted, leading to incorrect accounting entries which then need to be manually repaired through the use of miscellaneous operations.
To solve this issue, our video on TaxCloud integration (https://www.youtube.com/watch?v=JE-NeRNIWeU&t=616s) tells us to create a User-Defined Default for the account field of the tax.repartition.line model. This sets the default account with which new taxes are created. However, this information is missing from the documentation.
This PR brings the documentation up-to-date by explaining how to create this User-Defined Default that specifies the correct Tax Payable account.
closesodoo/documentation#1271
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Syntax was added to explicitly specify a module, class or function with
`--test-tags`: b729a11a12
The documentation was not updated to reflect this, leading to confusion
as people tried to reconcile the documentation with the actual behavior,
without necessarily having seen `odoo-bin --help` which is explicit
about it.
closesodoo/documentation#1258
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
As of sphinx 3.5.4, docutils >0.17 is no longer supported. To avoid
forcing the install of an unsupported version of docutils, we let
sphinx install the appropriate version through its dependencies.
closesodoo/documentation#1273
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Update the test server link that was updated in the English documentation
(colombia.rst) in the Spanish version as well (colombia_ES.rst).
Remove the incorrect link to the production server (which was a duplicate
of the test link instead) to be consistent with other versions of the
document.
closesodoo/documentation#1144
X-original-commit: ad36915bf7
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Signed-off-by: Raf Geens <raf-odoo@users.noreply.github.com>
Gengo won't work by default on Odoo Online and Odoo.sh. To
prevent confusing customers, be explicit about this and explain
the platforms on which it can work.
closesodoo/documentation#1105
X-original-commit: 989a447dc8
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
When locally building the doc (aka make), CURRENT_LANG is not defined,
which results in HTML_BUILD_DIR = _build/html//, resulting in commands
& logs like the following
mkdir -p _build/html//_static
pysassc extensions/odoo_theme/static/style.scss _build/html//_static/style.css
This has no impact on linux builds, but could be unclear/confusing for some non tech
users (can it have any impact on other OS's/distros ?)
closesodoo/documentation#1094
X-original-commit: d8684e8963
Signed-off-by: Antoine Vandevenne (anv) <AntoineVDV@users.noreply.github.com>
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
The previous makefile was compiling css beside the style.scss and
the style.css was copied at the end.
The new makefile compile css directly in the build dir.
Since this file was still present in the source because of the .gitignore,
sphinx was using this old version of style.css, overriding the new compiled
css file at the end.
Removing it from gitignore should helpFix this problem.
This commit also fix some path in makefile.
(not critical but this should fix a potential error in static command)
closesodoo/documentation#1085
X-original-commit: fd56d8c170
Signed-off-by: Antoine Vandevenne (anv) <AntoineVDV@users.noreply.github.com>
Signed-off-by: Xavier Dollé (xdo) <xdo@odoo.com>
Commit 547d90a allowed `BUILD_DIR` to be defined from the CLI but didn't
update usages of `HTML_BUILD_DIR`. When building the documentation for
multiple versions and/or languages, we should rely on `HTML_BUILD_DIR`
to point to the appropriate directory.
closesodoo/documentation#1076
X-original-commit: 9bad0540b0
Signed-off-by: Antoine Vandevenne (anv) <AntoineVDV@users.noreply.github.com>
Building documentation implies some constraints: the source folder is
readonly, mainly because the sources are shared accros builds.
This implies that nor a symlink and a _build dir cannot be added in the
source directory.
The symlink will work in most cases localy for user with strange
multiverse structure, but if not found, the fallback will check in
parent directory. Most users and runbot will have all sources in the
same directory (both in universe and basic multiverse cases)
-(version?)
-odoo
-enterprise
-upgrade
-documentation
The second change will check if BUILD_DIR is defined before setting it,
allowing to use 'make BUILD_DIR=../build' to output the documentation
somewhere else.
This doc page is still frequently used by the support.
This commit partly reverts 16418c020b
to keep the page as a hidden orphan page.
In the future, the content of this page should be moved
in the support contract and/or an independent odoo.com page
