Ambiguous note which implied local payment methods were supported even if not listed.
Forward up to V14, create new for V15.
task id: 2942093
closesodoo/documentation#2640
X-original-commit: 4b9517ead1
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
Foreign currency page was V13 only and outdated. Updated for V14.
task - 2904025
closesodoo/documentation#2383
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Even though the documentation was correct, it was confusing the reader
to state that local payment methods are considered enabled if their
related payment icon record does not exist in the database. The intended
meaning was that this statement only holds if the local payment method
is also supported, otherwise it cannot be enabled.
closesodoo/documentation#2587
X-original-commit: 80a9cfb68f
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
In the toctree, "MRP" wasn't capitalized in "Inventory & MRP."
Affects all branches, can be forward ported.
closesodoo/documentation#2561
X-original-commit: 8c665643ce
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
Google deprecated both its "Universal Analytics" and "Google Sign-In"
API. See community counterpart commit for a detailed explanation and
links.
closesodoo/documentation#2441
X-original-commit: 2222142127
Related: odoo/odoo#95847
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
If committed, this will delete mentions of project tasks in the "Invoice
Time Spent on Tickets (Postpaid Support Services)" v14.0 user doc. It
also deletes unnecessary steps and screenshots about creating and
configuring a new Project and updates the steps and screenshots for the
"Create a sales order" and "Link the Helpdesk ticket to the SO" sections.
Fixes PR #1901
Closes Odoo Task 2870104
closesodoo/documentation#2204
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
task - 2904108 I removed the "website/publish" section from the toctree to add a link to the full website documentation inside off the see also.
closesodoo/documentation#2414
X-original-commit: 7307dac6a6
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Task ID:2893426
Since Six payment terminal won't be usable starting in July 2022, I
added this warning.
closesodoo/documentation#2413
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
Both carrier name and tracking reference are now displayed to the
customer, even when using the carrie `Self Delivery`
task-2900803
closesodoo/documentation#2406
X-original-commit: 471d0c2094
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Before this commit, the "Developer/Misc" directory of the doc, and
more particularly the "Developer/Misc/Other" sub-directory, was used as
a garbage dump where we moved all the pages that didn't fit elsewhere.
Due to that, interesting and important pages, such as the Coding
Guidelines, were buried in that directory never to be read again by Odoo
developers.
This commit moves most pages under "Misc" one or two levels up to be
located directly under "Developer" hence making them more accessible. A
new "Contributing/Development" directory is added to host the Coding
Guidelines page and soon many other pages.
task-2897143
closesodoo/documentation#2350
X-original-commit: ad374af15d
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Following a technical task regarding the migration of the Adyen hosted
payment page integration to Adyen PayByLink, some new parameters have
been introduced and some have been removed.
This new addition to the documentation will help users configure their
acquirer.
task-2802921
closesodoo/documentation#2306
X-original-commit: 0db39e3564
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
V13 and V14 do not allow customers with no account on Odoo.com portal to pay through payment acquirers with payment flow "Payment from Odoo"
task - 2711962
closesodoo/documentation#2290
X-original-commit: 103c17f235
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
Deleting the Odoo Tutorials Invoices link since the course has been merged, and the link isn't necessary anymore.
closesodoo/documentation#2244
Forward-port-of: odoo/documentation#2243
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Because of a recent Chrome security update, a lot of customers using peripheral devices (printers, ...) will have to follow this doc.
Therefore, I followed the doc and did the flow on my side.
I modified 'Copy to file' to 'Export' and 'Trusted Root Certification Authorities' to 'Authorities' in order to have the exact same terms as in Chrome (I guess they updated their terms at some point).
closesodoo/documentation#2180
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Added a note to specify that bank synchronization is not available on trial databases
closesodoo/documentation#2132
X-original-commit: e4fc5f07ee
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
Signed-off-by: Aarab Tom (toaa) <toaa@odoo.com>
Starting July 2022, Amazon WMS API is deprecated and we need to use the Selling Partners API.
This brings changes in the authentication flow that are explained.
task-2466636
closesodoo/documentation#2102
X-original-commit: 80408ca
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
If merged, this will update the screenshot for the "Connect a SIX Payment Terminal to your PoS" v14 user doc. In Odoo v14.0, the "Use a Payment Terminal" field only has "Six" as an option, not "Six without IoT Box." The new screenshot reflects this change and I also rewrote the step to reflect this change.
I also added alt text to the images, fixed the image file names, and fixed the image file folder name.
Related issue: https://github.com/odoo/documentation/issues/954closesodoo/documentation#2008
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.
For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:
├── parent_doc/
│ └── doc1/
│ │ └── image.png
│ │ └── download.zip
│ └── doc1.rst
│ └── doc2.rst
├── parent_doc.rst
Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.
In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.
task-2497965
Part-of: odoo/documentation#2026
In case of an unsupported carrier or a self Delivery, Odoo won't block
the user to use the Amazon connector, but explanation were needed for
these cases.
task-2804907
closesodoo/documentation#1958
X-original-commit: 3231d20d92
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
The previous guidelines for titles and headings included an exception to
capitalize feature names as they are written in the apps. However, this
exception seems to have confused most writers as it isn't always clear
what should be considered as a feature name or what should be considered
as a noun or noun group. This commit removes this exception to make the
writing and reviewing processes easier while retaining good titles and
improving consistency across the documentation. It also changes the
titles of the Accounting section to provide a better example to other
writers.
task-id 2843109
closesodoo/documentation#1911
X-original-commit: abc6d99af7
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
Mexican companies very commonly issue invoices in USD, to be fulfiled
in MXN, at the official exchange rate defined by the Banco de Mexico
on the day of payment.
(Presumably, this is to insure against the volatility of the Mexican
peso.)
Odoo supports this workflow, but only if the payment is registered
directly on the invoice using the 'Register Payment' button.
If the payment is created separately, and then reconciled manually
with the invoice, a whole host of problems occur:
- the payment typically can't be reconciled fully with the invoice,
(even though that can usually be solved by manually creating
an exchange move)
- but more problematically, the amounts on the payment CFDI will
be wrong, and even manually creating an exchange move won't solve
that.
So, we absolutely need to warn users not to try to do that.
(We've been encountering lots of tickets lately in the tech-support
pipe because of users who tried this and then wonder why it doesn't
work.)
This is currently an issue in 14.0, 15.0 and master.
closesodoo/documentation#1728
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Codeowner regexes need images to be in the correct location, otherwise
some image files might not be assigned to a GitHub team when the regex
covering the parent folder is split into multiple codeowner rules.
closesodoo/documentation#1773
X-original-commit: 4e0a9b615f
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
