documentation/redirects/14.0.txt

96 lines
11 KiB
Plaintext
Raw Normal View History

# administration/maintain
administration/maintain/online.rst administration/maintain/odoo_online.rst
# administration/upgrade
administration/upgrade/online_hosting.rst administration/upgrade/odoo_online.rst
# applications/accounting
applications/finance/accounting/fiscal_localizations.rst applications/finance/fiscal_localizations.rst # /accounting/ --> /
applications/finance/accounting/fiscal_localizations/localizations/argentina.rst applications/finance/fiscal_localizations/argentina.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/australia.rst applications/finance/fiscal_localizations/australia.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/chile.rst applications/finance/fiscal_localizations/chile.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/colombia.rst applications/finance/fiscal_localizations/colombia.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/colombia_ES.rst applications/finance/fiscal_localizations/colombia_ES.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/france.rst applications/finance/fiscal_localizations/france.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/germany.rst applications/finance/fiscal_localizations/germany.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/indonesia.rst applications/finance/fiscal_localizations/indonesia.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/italy.rst applications/finance/fiscal_localizations/italy.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/italy_IT.rst applications/finance/fiscal_localizations/italy.rst # italy_IT -> italy
applications/finance/accounting/fiscal_localizations/localizations/luxembourg.rst applications/finance/fiscal_localizations/luxembourg.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/mexico.rst applications/finance/fiscal_localizations/mexico.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/netherlands.rst applications/finance/fiscal_localizations/netherlands.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/peru.rst applications/finance/fiscal_localizations/peru.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/spain.rst applications/finance/fiscal_localizations/spain.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/switzerland.rst applications/finance/fiscal_localizations/switzerland.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/localizations/united_kingdom.rst applications/finance/fiscal_localizations/united_kingdom.rst # /accounting/fiscal_localizations/localizations/* --> /fiscal_localizations/*
applications/finance/accounting/fiscal_localizations/overview/fiscal_localization_packages.rst applications/finance/fiscal_localizations.rst # /accounting/fiscal_localizations/overview/* --> fiscal_localizations
applications/finance/accounting/fiscal_localizations/overview/localizations_list.rst applications/finance/fiscal_localizations.rst # /accounting/fiscal_localizations/overview/* --> fiscal_localizations
applications/finance/accounting/getting_started/memento.rst applications/finance/accounting/getting_started/cheat_sheet.rst # memento -> cheat_sheet
applications/finance/accounting/payables/supplier_bills/manage.rst applications/inventory_and_mrp/purchase/manage_deals/manage.rst # (#3302)
[IMP] redirects: split redirects.txt into multiple, per-version, files The `redirects.txt` file used to specify redirect rules for renamed or moved documentation pages is starting to grow too big to be easily maintainable. The main reason is that the number of redirect rules that were thought to be required has been largely underestimated when implementing the 'redirects' extension. At first, we believed that no guidelines or structure were necessary because only a small amount of redirect rules would be specified. This proved wrong and the file is now becoming a mess, making it increasingly difficult to figure out where, why, when, and if a redirect rule is specified in the file. As the file is versioned, another issue emerges: conflicts occur every time a commit is forward-ported to a later version if that commit adds a redirect rule at the end of the file or at a line that was changed in the later version. As redirect rules are frequently added, and since blocks of redirect rules for new versions are added at the end of the file, this tends to happen a lot. This commit attempts to hit two birds with one stone by splitting the `redirects.txt` file into multiple files, one per version. While doing so, the existing redirect rules are ordered alphabetically and moved into contextual blocks. Instructions and guidelines on how to create redirect rules are also listed in the `redirects/MANUAL.md` file. By sorting the redirect rules and adding them in different files, the number of conflicts should decrease by a lot. task-2891912 closes odoo/documentation#2287 X-original-commit: cc88da1bbaa169a51b53e4f1e06fa26b9de1876e Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
# applications/sales
applications/sales/crm/acquire_leads/generate_from_email.rst applications/sales/crm/acquire_leads/generate_leads.rst # (#986)
applications/sales/crm/acquire_leads/generate_from_website.rst applications/sales/crm/acquire_leads/generate_leads.rst # (#986)
applications/sales/sales/advanced/portal.rst applications/general/users/portal.rst
[IMP] redirects: split redirects.txt into multiple, per-version, files The `redirects.txt` file used to specify redirect rules for renamed or moved documentation pages is starting to grow too big to be easily maintainable. The main reason is that the number of redirect rules that were thought to be required has been largely underestimated when implementing the 'redirects' extension. At first, we believed that no guidelines or structure were necessary because only a small amount of redirect rules would be specified. This proved wrong and the file is now becoming a mess, making it increasingly difficult to figure out where, why, when, and if a redirect rule is specified in the file. As the file is versioned, another issue emerges: conflicts occur every time a commit is forward-ported to a later version if that commit adds a redirect rule at the end of the file or at a line that was changed in the later version. As redirect rules are frequently added, and since blocks of redirect rules for new versions are added at the end of the file, this tends to happen a lot. This commit attempts to hit two birds with one stone by splitting the `redirects.txt` file into multiple files, one per version. While doing so, the existing redirect rules are ordered alphabetically and moved into contextual blocks. Instructions and guidelines on how to create redirect rules are also listed in the `redirects/MANUAL.md` file. By sorting the redirect rules and adding them in different files, the number of conflicts should decrease by a lot. task-2891912 closes odoo/documentation#2287 X-original-commit: cc88da1bbaa169a51b53e4f1e06fa26b9de1876e Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
# developer/howtos
developer/api/external_api.rst developer/reference/external_api.rst # reorganize the developer doc
developer/api/extract_api.rst developer/reference/extract_api.rst # reorganize the developer doc
developer/api/iap.rst developer/howtos/provide_iap_services.rst # reorganize the developer doc
developer/cli.rst developer/reference/cli.rst # reorganize the developer doc
developer/howtos/backend.rst developer/tutorials/backend.rst # reorganize the developer doc
developer/howtos/rdtraining.rst developer/tutorials/getting_started.rst # reorganize the developer doc
developer/howtos/rdtraining/01_architecture.rst developer/tutorials/getting_started/01_architecture.rst # reorganize the developer doc
developer/howtos/rdtraining/02_setup.rst developer/tutorials/getting_started/02_setup.rst # reorganize the developer doc
developer/howtos/rdtraining/03_newapp.rst developer/tutorials/getting_started/03_newapp.rst # reorganize the developer doc
developer/howtos/rdtraining/04_basicmodel.rst developer/tutorials/getting_started/04_basicmodel.rst # reorganize the developer doc
developer/howtos/rdtraining/05_securityintro.rst developer/tutorials/getting_started/05_securityintro.rst # reorganize the developer doc
developer/howtos/rdtraining/06_firstui.rst developer/tutorials/getting_started/06_firstui.rst # reorganize the developer doc
developer/howtos/rdtraining/07_basicviews.rst developer/tutorials/getting_started/07_basicviews.rst # reorganize the developer doc
developer/howtos/rdtraining/08_relations.rst developer/tutorials/getting_started/08_relations.rst # reorganize the developer doc
developer/howtos/rdtraining/09_compute_onchange.rst developer/tutorials/getting_started/09_compute_onchange.rst # reorganize the developer doc
developer/howtos/rdtraining/10_actions.rst developer/tutorials/getting_started/10_actions.rst # reorganize the developer doc
developer/howtos/rdtraining/11_constraints.rst developer/tutorials/getting_started/11_constraints.rst # reorganize the developer doc
developer/howtos/rdtraining/12_sprinkles.rst developer/tutorials/getting_started/12_sprinkles.rst # reorganize the developer doc
developer/howtos/rdtraining/13_inheritance.rst developer/tutorials/getting_started/13_inheritance.rst # reorganize the developer doc
developer/howtos/rdtraining/14_other_module.rst developer/tutorials/getting_started/14_other_module.rst # reorganize the developer doc
developer/howtos/rdtraining/15_qwebintro.rst developer/tutorials/getting_started/15_qwebintro.rst # reorganize the developer doc
developer/howtos/rdtraining/16_guidelines_pr.rst developer/tutorials/getting_started/16_guidelines_pr.rst # reorganize the developer doc
developer/howtos/rdtraining/B_acl_irrules.rst developer/tutorials/restrict_data_access.rst # reorganize the developer doc
developer/howtos/rdtraining/C_data.rst developer/tutorials/define_module_data.rst # reorganize the developer doc
developer/howtos/rdtraining/E_unittest.rst developer/tutorials/unit_tests.rst # reorganize the developer doc
developer/howtos/rdtraining/J_reports.rst developer/tutorials/pdf_reports.rst # reorganize the developer doc
developer/howtos/rdtraining/K_dashboard.rst developer/tutorials/dashboards.rst # reorganize the developer doc
developer/howtos/web.rst developer/tutorials/web.rst # reorganize the developer doc
developer/howtos/website.rst developer/tutorials/website.rst # reorganize the developer doc
developer/iot.rst developer/howtos/connect_device.rst # reorganize the developer doc
[IMP] redirects: split redirects.txt into multiple, per-version, files The `redirects.txt` file used to specify redirect rules for renamed or moved documentation pages is starting to grow too big to be easily maintainable. The main reason is that the number of redirect rules that were thought to be required has been largely underestimated when implementing the 'redirects' extension. At first, we believed that no guidelines or structure were necessary because only a small amount of redirect rules would be specified. This proved wrong and the file is now becoming a mess, making it increasingly difficult to figure out where, why, when, and if a redirect rule is specified in the file. As the file is versioned, another issue emerges: conflicts occur every time a commit is forward-ported to a later version if that commit adds a redirect rule at the end of the file or at a line that was changed in the later version. As redirect rules are frequently added, and since blocks of redirect rules for new versions are added at the end of the file, this tends to happen a lot. This commit attempts to hit two birds with one stone by splitting the `redirects.txt` file into multiple files, one per version. While doing so, the existing redirect rules are ordered alphabetically and moved into contextual blocks. Instructions and guidelines on how to create redirect rules are also listed in the `redirects/MANUAL.md` file. By sorting the redirect rules and adding them in different files, the number of conflicts should decrease by a lot. task-2891912 closes odoo/documentation#2287 X-original-commit: cc88da1bbaa169a51b53e4f1e06fa26b9de1876e Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
# developer/misc
developer/misc/api/external_api.rst developer/api/external_api.rst # better location for misc/ content (#2350)
[IMP] redirects: split redirects.txt into multiple, per-version, files The `redirects.txt` file used to specify redirect rules for renamed or moved documentation pages is starting to grow too big to be easily maintainable. The main reason is that the number of redirect rules that were thought to be required has been largely underestimated when implementing the 'redirects' extension. At first, we believed that no guidelines or structure were necessary because only a small amount of redirect rules would be specified. This proved wrong and the file is now becoming a mess, making it increasingly difficult to figure out where, why, when, and if a redirect rule is specified in the file. As the file is versioned, another issue emerges: conflicts occur every time a commit is forward-ported to a later version if that commit adds a redirect rule at the end of the file or at a line that was changed in the later version. As redirect rules are frequently added, and since blocks of redirect rules for new versions are added at the end of the file, this tends to happen a lot. This commit attempts to hit two birds with one stone by splitting the `redirects.txt` file into multiple files, one per version. While doing so, the existing redirect rules are ordered alphabetically and moved into contextual blocks. Instructions and guidelines on how to create redirect rules are also listed in the `redirects/MANUAL.md` file. By sorting the redirect rules and adding them in different files, the number of conflicts should decrease by a lot. task-2891912 closes odoo/documentation#2287 X-original-commit: cc88da1bbaa169a51b53e4f1e06fa26b9de1876e Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
# legal
legal/others/cla.rst legal/cla.rst
legal/licenses/licenses.rst legal/licenses.rst
# others
crm/optimize/mail_client_extension.rst applications/sales/crm/optimize/outlook_extension.rst # mail_client_extension -> outlook_extension | mail_client_extension is the first link provided as a tip in Odoo 14 but should be updated and point directly to outlook_extension
crm/optimize/google_calendar_credentials.rst applications/general/calendars/google/google_calendar_credentials.rst # (#765)
purchase/purchases/tender/blanket_orders.rst applications/inventory_and_mrp/purchase/manage_deals/agreements.rst # (#823)
purchase/purchases/tender/call_for_tender.rst applications/inventory_and_mrp/purchase/manage_deals/agreements.rst # (#823)
purchase/purchases/rfq/3_way_matching.rst applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst # (#829)
purchase/purchases/rfq/bills.rst applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst # (#829)
purchase/purchases/master/uom.rst applications/inventory_and_mrp/purchase/products/uom.rst # (#814)
purchase/replenishment/flows/compute_date.rst applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst # (#814)
purchase/replenishment/flows/purchase_triggering.rst applications/inventory_and_mrp/purchase/products/reordering.rst # (#814)
purchase/replenishment/flows/setup_stock_rule.rst applications/inventory_and_mrp/purchase/products/reordering.rst # (#814)
purchase/replenishment/multicompany/setup.rst applications/general/multi_companies/manage_multi_companies.rst # (#814)