[IMP] general: add notes about dev mode toggle #2485
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
closes #1183 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Changed commands that were still referring to Odoo 14.0 to 15.0 closes #1868 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
closes #1645 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
critarias -> criteria closes #1886 Signed-off-by: Antoine Vandevenne (anv) <anv@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. closes #1913 Forward-port-of: #1728 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 closes #1912 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
Also add a condition on some directives to ignore them when we have no relative/absolute path. Part-of: #1334
This new directive is generating documentation from Odoo fields. This can be used to build documentation about business classes. This will help developpers import/export data and build localization modules for instance. Part-of: #1334
closes #1334 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Co-authored-by: William Andre <wan@odoo.com> Co-authored-by: Ivan Yelizariev <iel@odoo.com>
export PLAUSIBLE_SCRIPT=https://plausible.io/js/script.js export PLAUSIBLE_DOMAIN=yourdomain.com closes #1951 X-original-commit: 4c526eb Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Jérémy Kersten <jke@odoo.com>
Companion of [1]. [1]: odoo/odoo#47186 opw-2824263 closes #1976 X-original-commit: f6bf118 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Desausoi Laurent (lade) <lade@odoo.com>
Task-id 2744131 closes #1887 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Only `no_create` is required to hide both the 'Create "xxx"' and the 'Create and Edit...' dropdown menu options. closes #1545 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
closes #1975 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
StraubCreative
commented
Dec 2, 2022
Contributor
Author
StraubCreative
left a comment
StraubCreative
left a comment
There was a problem hiding this comment.
Hi @tiku-odoo
Change requests below for your reference.
I've already made the changes on my local copy and will push up momentarily.
Unless you object I'll be tagging in DR to close this out 🚀
StraubCreative
force-pushed
the
15.0-general-add-notes-about-dev-mode-toggle-tiku
branch
from
8672fa2 to
ffbc4b9
Compare
Contributor
Author
|
Hi @odoo/doc-review this doc's ready for you :) |
closes #2849 Taskid: 2890089 Signed-off-by: Platteau Xavier (xpl) <xpl@odoo.com>
closes #2430 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Updated to reflect how to download Gmail Plugin from Google Workspace Marketplace for Odoo Online users; added new images Closes Odoo Task 3001713 closes #2773 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Task: 2543815 Cherry pick from #998 Omitted changes proposed in the **track_leads** directory (e.g. `lead_scoring.rst` + image folder). Both the content and image updates were already pushed from another PR so what was proposed on #998 was outdated and no longer necessary. What’s left over are the original proposed changes in #998, within the **acquire_leads** directory which include updates to `lead_mining.rst` and corresponding image files. On top of these proposals, I went ahead and made the following changes: - renamed the image files in the asset directory, since they were using outdated naming convention (e.g. LM1.png, LM6.png, LM7.png) - cleaned up rst formatting issues (headings, line breaks, added guilabels, etc.) - rewrote document so content was more concise + followed content guidelines. You can see the first version of proposals here to compare the changes made. closes #3118 X-original-commit: 02ef871 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
tiku-odoo
force-pushed
the
15.0-general-add-notes-about-dev-mode-toggle-tiku
branch
from
ffbc4b9 to
70f8ef8
Compare
Contributor
|
CC: @StraubCreative, @samueljlieber Thanks for your review. 👍 I've made the requested changes to this document. I just noticed that this PR was initially filed for 15.0 when this should apply to V14 ->V16, if I'm not mistaken. Here is the original PR: #1560 What are your thoughts on this? Thanks, Tim |
AntoineVDV
requested changes
Dec 7, 2022
Collaborator
AntoineVDV
left a comment
AntoineVDV
left a comment
There was a problem hiding this comment.
What are your thoughts on this?
Sounds like a good idea!
For this, you need to retarget the base of this PR and "rebase" your branch onto 14.0.
| @@ -0,0 +1,2928 @@ | |||
| [33me7f0d6ae[m[33m ([m[1;36mHEAD -> [m[1;32m16.0-inventory-sendcloud-shipping-connector-tiku[m[33m)[m mivu updates dec6 | |||
Collaborator
There was a problem hiding this comment.
You might want to remove this
Contributor
|
Re-targeted via cherry pick: #3140 |
Collaborator
|
@samueljlieber @StraubCreative Instead of creating new PRs for new base branches, you could keep this PR open and force-push your new base on this one. It works just fine, keeps the history of the PR and its reviews, and allows reviewers to track which files are already reviewed. |
This was referenced Dec 15, 2022
samueljlieber
added
the
cancelled
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry pick of #1560.