CUPS the server will never be installed on an Odoo.sh machine.
That being said you can use a remote printer with a cups client.
The problem lays in the sorry state of libcups dependencies so we will
try to get a reliable section in the documentation for 20.04 as soon as
we can get a testcase.
Meanwhile, it has been reported that the command line `lp` cups cli
client tool could be used as a workaround in the OCA concerned module:
https://gist.github.com/rm-jamotion/0453e91ff3e13350a1e46a11ebb02e8d
It's not really obvious that payments and invoices need to be fully
reconciled before their currency exchange entries get created, so this
is a warning about that.
Make explicit which permissions you need to grant in a personal access
token. I verified `repo` suffices to complete the tutorial, and I'm
assuming Odoo.sh doesn't need any of the admin and site permissions.
The original description says calling unidecode will remove special
characters, but this is not entirely accurate. For example, when I
inserted unicode emojis in the name, they were not removed. I was then
confused whether my module had correctly updated or not.
Instead, what unidecode will do is convert text characters to their
nearest ASCII equivalent, so "trés" becomes "tres" for example. The
description has been updated to reflect that.
The current certificates for demo in the documentation will to expire
the October 21. For this reason were updated by new files.
The new CSD files need to stamp with the VAT ``EKU9003173C9``.
Both values are updated.
Closesodoo/documentation-user#771
We had to modify the connection method due to changes that will be
introduced soon in modern web browsers. (See odoo/odoo#51088)
We also fix the numbering of the connection steps.
e.g.
.. meta::
:description: blah blah blah
:keywords lang=en: x y z
should yield
<meta name="description" content="blah blah blah">
<meta name="keywords" lang="en" content="x y z">
Also cleaned up `layout.html` a tad while at it:
* we're now properly setting the default metas via the translator so
setting them in the template is unnecessary
* there's a flag to use an html5 doctype (also has a few other
positive side-effects with respect to the metas sphinx generates in
the template)
