[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
# applications/finance
|
2020-04-01 22:00:52 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
applications/finance/accounting/overview/main_concepts/in_odoo.rst applications/finance/accounting.rst # finance/accounting/overview/main_concepts/in_odoo -> finance/accounting.rst
|
|
|
|
|
applications/finance/accounting/overview/main_concepts/memento.rst applications/finance/accounting/getting_started/memento.rst # overview/main_concepts/* -> getting_started/*
|
|
|
|
|
applications/finance/accounting/overview/getting_started/chart_of_accounts.rst applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst # overview/getting_started/* -> getting_started/initial_configuration/*
|
|
|
|
|
applications/finance/accounting/overview/getting_started/setup.rst applications/finance/accounting/getting_started/initial_configuration/setup.rst # overview/getting_started/* -> getting_started/initial_configuration/*
|
|
|
|
|
applications/finance/accounting/overview/process_overview/customer_invoice.rst applications/finance/accounting/getting_started/process_overview/customer_invoice.rst # overview/* -> getting_started/*
|
|
|
|
|
applications/finance/accounting/overview/process_overview/supplier_bill.rst applications/finance/accounting/getting_started/process_overview/supplier_bill.rst # overview/* -> getting_started/*
|
2020-04-01 22:00:52 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
applications/finance/expense/expense.rst applications/finance/expenses.rst #expense/expense -> expenses
|
2020-04-01 22:00:52 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
applications/finance/sign/overview/signature_validity.rst applications/finance/sign.rst # sign/overview/signature_validity -> sign/*
|
2020-04-01 22:00:52 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
# applications/general
|
2020-04-01 22:00:52 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
applications/general/auth/google_spreadsheets.rst applications/sales/crm/performance/google_spreadsheets.rst # general/auth/* -> sales/crm/performance/
|
2021-06-04 21:12:25 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
applications/general/base_import.rst applications/general/export_import_data.rst # base_import -> export_import_data
|
|
|
|
|
applications/general/base_import/import_faq.rst applications/general/export_import_data.rst
|
|
|
|
|
applications/general/base_import/adapt_template.rst applications/general/export_import_data.rst
|
2021-08-03 20:21:24 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
applications/general/developer_mode/activate.rst applications/general/developer_mode.rst # developer_mode/activate -> developer_mode
|
2020-04-01 22:00:52 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
applications/general/in_app_purchase/in_app_purchase.rst applications/general/in_app_purchase.rst # in_app_purchase/in_app_purchase -> in_app_purchase
|
2021-06-07 14:09:43 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
applications/general/mobile.rst applications/general.rst # general/mobile -> general
|
2020-04-01 22:00:52 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
applications/general/multi_companies/manage_multi_companies.rst applications/general/companies.rst # multi_companies/manage_multi_companies -> companies
|
|
|
|
|
applications/general/multi_companies.rst applications/general/users/companies.rst # multi_companies -> companies
|
|
|
|
|
|
|
|
|
|
applications/general/odoo_basics/choose_language.rst applications/general/users/language.rst # odoo_basics/choose_language -> users/language
|
|
|
|
|
applications/general/odoo_basics/export-data.rst applications/general/export_import_data.rst # odoo_basics/export-data -> export_import_data
|
|
|
|
|
applications/general/odoo_basics/users.rst applications/general/users.rst # odoo_basics/users -> users
|
|
|
|
|
|
|
|
|
|
applications/general/payment_acquirers/payment_acquirers.rst applications/finance/payment_acquirers.rst # general/payment_acquirers/payment_acquirers -> finance/payment_acquirers
|
|
|
|
|
applications/general/payment_acquirers.rst applications/finance/payment_acquirers.rst # general/payment_acquirers/* --> finance/payment_acquirers/*
|
|
|
|
|
applications/general/payment_acquirers/authorize.rst applications/finance/payment_acquirers/authorize.rst # general/payment_acquirers/* --> finance/payment_acquirers/*
|
|
|
|
|
applications/general/payment_acquirers/paypal.rst applications/finance/payment_acquirers/paypal.rst # general/payment_acquirers/* --> finance/payment_acquirers/*
|
|
|
|
|
applications/general/payment_acquirers/stripe.rst applications/finance/payment_acquirers/stripe.rst # general/payment_acquirers/* --> finance/payment_acquirers/*
|
|
|
|
|
applications/general/payment_acquirers/wire_transfer.rst applications/finance/payment_acquirers/wire_transfer.rst # general/payment_acquirers/* --> finance/payment_acquirers/*
|
|
|
|
|
|
|
|
|
|
applications/general/unsplash/unsplash_access_key.rst applications/websites/website/optimize/unsplash.rst # general/unsplash/unsplash_access_key -> general/unsplash
|
|
|
|
|
applications/general/unsplash/unsplash_application_id.rst applications/websites/website/optimize/unsplash.rst # general/unsplash/unsplash_application_id -> general/unsplash
|
|
|
|
|
applications/general/unsplash.rst applications/websites/website/optimize/unsplash.rst # general/unsplash -> websites/website/optimize/unsplash
|
|
|
|
|
|
|
|
|
|
# applications/marketing
|
|
|
|
|
|
|
|
|
|
applications/marketing/survey/overview/create.rst applications/marketing/surveys/overview/create.rst # /survey/* -> /surveys/*
|
|
|
|
|
applications/marketing/survey/overview/scoring.rst applications/marketing/surveys/overview/scoring.rst # /survey/* -> /surveys/*
|
|
|
|
|
applications/marketing/survey/overview/time_random.rst applications/marketing/surveys/overview/time_random.rst # /survey/* -> /surveys/*
|
|
|
|
|
|
|
|
|
|
# applications/productivity
|
|
|
|
|
|
|
|
|
|
applications/productivity/discuss/advanced/email_servers.rst applications/general/email_communication/email_servers.rst # productivity/discuss/advanced/* -> general/email_communication/*
|
|
|
|
|
applications/productivity/discuss/advanced/email_template.rst applications/general/email_communication/email_template.rst # productivity/discuss/advanced/* -> general/email_communication/*
|
|
|
|
|
|
|
|
|
|
# applications/settings
|
|
|
|
|
|
|
|
|
|
applications/settings/users_and_features.rst applications/general.rst # settings/users_and_features -> general
|
|
|
|
|
|
2022-06-28 21:19:03 +07:00
|
|
|
# developer/misc
|
|
|
|
|
|
|
|
|
|
developer/misc/api/iap.rst developer/api/iap.rst # better location for misc/ content (#2337)
|
|
|
|
|
developer/misc/api/odoo.rst developer/api/external_api.rst # better location for misc/ content (#2350) /!\ renamed to external_api.rst in 14.0 /!\
|
|
|
|
|
developer/misc/i18n/localization.rst developer/howtos/localization.rst # better location for misc/ content (#2337) /!\ already moved in 15.0 /!\
|
|
|
|
|
developer/misc/i18n/translations.rst developer/howtos/translations.rst # better location for misc/ content (#2337) /!\ already moved in 15.0 /!\
|
|
|
|
|
developer/misc/other/cmdline.rst developer/cli.rst # better location for misc/ content (#2337)
|
|
|
|
|
developer/misc/other/guidelines.rst contributing/development/coding_guidelines.rst # better location for misc/ content (#2337)
|
|
|
|
|
developer/misc/other/iot.rst developer/iot.rst # better location for misc/ content (#2337)
|
|
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
# services
|
|
|
|
|
|
|
|
|
|
services/support/supported_versions.rst administration/maintain/supported_versions.rst # services/support/* -> administration/maintain/*
|
|
|
|
|
|
|
|
|
|
# others
|
2021-05-04 22:38:50 +07:00
|
|
|
|
|
|
|
|
accounting/localizations/nederlands.rst applications/finance/accounting/localizations/netherlands.rst # (#514)
|
|
|
|
|
accounting/receivables/customer_invoices/refund.rst applications/finance/accounting/receivables/customer_invoices/credit_notes.rst # refund --> credit_notes (#475)
|
|
|
|
|
accounting/receivables/customer_payments/payment_sepa.rst applications/finance/accounting/receivables/customer_payments/batch_sdd.rst # payment_sepa --> batch_sdd (#475)
|
|
|
|
|
accounting/bank/feeds/synchronize.rst applications/finance/accounting/bank/feeds/bank_synchronization.rst # synchronize --> bank_synchronization (#535)
|
|
|
|
|
accounting/others/adviser/assets.rst applications/finance/accounting/payables/supplier_bills/assets.rst # others/adviser/* --> payables/supplier_bills/* (#541)
|
2021-05-20 21:10:22 +07:00
|
|
|
accounting/others/configuration/account_type.rst applications/finance/accounting/getting_started/initial_configuration/chart_of_accounts.rst # others/configuration/account_type --> getting_started/initial_configuration/chart_of_accounts (#554)
|
2021-05-04 22:38:50 +07:00
|
|
|
accounting/bank/feeds/manual.rst applications/finance/accounting/bank/feeds/bank_statements.rst # manual --> bank_statements [merged] (#569)
|
|
|
|
|
accounting/bank/feeds/coda.rst applications/finance/accounting/bank/feeds/bank_statements.rst # coda --> bank_statements [merged] (#569)
|
|
|
|
|
accounting/bank/feeds/ofx.rst applications/finance/accounting/bank/feeds/bank_statements.rst # ofx --> bank_statements [merged] (#569)
|
|
|
|
|
accounting/bank/feeds/qif.rst applications/finance/accounting/bank/feeds/bank_statements.rst # qif --> bank_statements [merged] (#569)
|
|
|
|
|
accounting/receivables/customer_invoices/installment_plans.rst applications/finance/accounting/receivables/customer_invoices/payment_terms.rst # installment_plans --> payment_terms [merged] (#573)
|
|
|
|
|
accounting/others/adviser/fiscalyear.rst applications/finance/accounting/taxation/fiscal_year/close_fiscal_year.rst # others/adviser/fiscalyear --> taxation/fiscal_year/close_fiscal_year (#575)
|
|
|
|
|
accounting/others/configuration/fiscal_year.rst applications/finance/accounting/taxation/fiscal_year/fiscal_year.rst # others/configuration/* --> taxation/fiscal_year/* (#575)
|
|
|
|
|
accounting/others/taxes.rst applications/finance/accounting/taxation/taxes.rst # others/* --> taxation/* (#575)
|
|
|
|
|
accounting/others/taxes/B2B_B2C.rst applications/finance/accounting/taxation/taxes/B2B_B2C.rst # others/* --> taxation/* (#575)
|
|
|
|
|
accounting/others/taxes/application.rst applications/finance/accounting/taxation/taxes/application.rst # others/* --> taxation/* (#575)
|
|
|
|
|
accounting/others/taxes/cash_basis_taxes.rst applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst # others/* --> taxation/* (#575)
|
|
|
|
|
accounting/others/taxes/create.rst applications/finance/accounting/taxation/taxes/create.rst # others/* --> taxation/* (#575)
|
|
|
|
|
accounting/others/taxes/default_taxes.rst applications/finance/accounting/taxation/taxes/default_taxes.rst # others/* --> taxation/* (#575)
|
|
|
|
|
accounting/others/taxes/retention.rst applications/finance/accounting/taxation/taxes/retention.rst # others/* --> taxation/* (#575)
|
|
|
|
|
accounting/others/taxes/tax_included.rst applications/finance/accounting/taxation/taxes/tax_included.rst # others/* --> taxation/* (#575)
|
|
|
|
|
accounting/others/taxes/taxcloud.rst applications/finance/accounting/taxation/taxes/taxcloud.rst # others/* --> taxation/* (#575)
|
2021-05-21 21:41:03 +07:00
|
|
|
accounting/payables/misc/employee_expense.rst finance/expenses.rst # applications/finance/accounting/payables/misc/employee_expense --> expenses [merged]
|
2021-05-04 22:38:50 +07:00
|
|
|
accounting/others/reporting/customize.rst applications/finance/accounting/reporting/overview/customize.rst # others/reporting/* --> reporting/overview/*
|
|
|
|
|
accounting/others/reporting/main_reports.rst applications/finance/accounting/reporting/overview/main_reports.rst # others/reporting/* --> reporting/overview/*
|
|
|
|
|
accounting/fiscality/taxes/tax_returns.rst applications/finance/accounting/reporting/declarations/tax_returns.rst # fiscality/taxes/* --> reporting/declarations/*
|
|
|
|
|
accounting/bank/setup/create_bank_account.rst applications/finance/accounting/bank/setup/bank_accounts.rst # create_bank_account -> bank_accounts
|
|
|
|
|
accounting/localizations.rst applications/finance/accounting/fiscal_localizations/localizations.rst # localizations --> fiscal_localizations/localizations
|
|
|
|
|
accounting/localizations/argentina.rst applications/finance/accounting/fiscal_localizations/localizations/argentina.rst # localizations/* --> fiscal_localizations/localizations/*
|
|
|
|
|
accounting/localizations/colombia.rst applications/finance/accounting/fiscal_localizations/localizations/colombia.rst # localizations/* --> fiscal_localizations/localizations/*
|
|
|
|
|
accounting/localizations/colombia_ES.rst applications/finance/accounting/fiscal_localizations/localizations/colombia_ES.rst # localizations/* --> fiscal_localizations/localizations/*
|
|
|
|
|
accounting/localizations/france.rst applications/finance/accounting/fiscal_localizations/localizations/france.rst # localizations/* --> fiscal_localizations/localizations/*
|
|
|
|
|
accounting/localizations/germany.rst applications/finance/accounting/fiscal_localizations/localizations/germany.rst # localizations/* --> fiscal_localizations/localizations/*
|
|
|
|
|
accounting/localizations/italy_IT.rst applications/finance/accounting/fiscal_localizations/localizations/italy_IT.rst # localizations/* --> fiscal_localizations/localizations/*
|
|
|
|
|
accounting/localizations/mexico.rst applications/finance/accounting/fiscal_localizations/localizations/mexico.rst # localizations/* --> fiscal_localizations/localizations/*
|
|
|
|
|
accounting/localizations/netherlands.rst applications/finance/accounting/fiscal_localizations/localizations/netherlands.rst # localizations/* --> fiscal_localizations/localizations/*
|
|
|
|
|
accounting/localizations/spain.rst applications/finance/accounting/fiscal_localizations/localizations/spain.rst # localizations/* --> fiscal_localizations/localizations/*
|
|
|
|
|
accounting/localizations/switzerland.rst applications/finance/accounting/fiscal_localizations/localizations/switzerland.rst # localizations/* --> fiscal_localizations/localizations/*
|
|
|
|
|
accounting/payables/supplier_bills/bills_or_receipts.rst applications/finance/accounting/payables/supplier_bills/purchase_receipts.rst # bills_or_receipts.rst -> purchase_receipts.rst
|
|
|
|
|
accounting/bank/reconciliation/configure.rst applications/finance/accounting/bank/reconciliation/reconciliation_models.rst # configure -> reconciliation_models (#613)
|
|
|
|
|
accounting/receivables/customer_payments/credit_cards.rst applications/finance/accounting/receivables/customer_payments/online_payment.rst # credit_cards -> online_payment
|
|
|
|
|
accounting/fiscality/taxes/application.rst applications/finance/accounting/taxation/taxes/fiscal_positions.rst # fiscality/*/application -> taxation/*/fiscal_positions
|
|
|
|
|
accounting/fiscality/taxes/create.rst applications/finance/accounting/taxation/taxes/taxes.rst # fiscality/*/create -> taxation/*/taxes
|
|
|
|
|
accounting/fiscality/taxes/tax_included.rst applications/finance/accounting/taxation/taxes/taxes.rst # fiscality/*/tax_included -> taxation/*/taxes
|
|
|
|
|
accounting/bank/misc/batch.rst applications/finance/accounting/receivables/customer_payments/batch.rst # bank/misc/* -> receivables/customer_payments/*
|
|
|
|
|
accounting/fiscality/fiscal_year/close_fiscal_year.rst applications/finance/accounting/taxation/fiscal_year/close_fiscal_year.rst # fiscality/* -> taxation/*
|
|
|
|
|
accounting/fiscality/fiscal_year/fiscal_year.rst applications/finance/accounting/taxation/fiscal_year/fiscal_year.rst # fiscality/* -> taxation/*
|
|
|
|
|
accounting/fiscality/taxes/B2B_B2C.rst applications/finance/accounting/taxation/taxes/B2B_B2C.rst # fiscality/* -> taxation/*
|
|
|
|
|
accounting/fiscality/taxes/cash_basis_taxes.rst applications/finance/accounting/taxation/taxes/cash_basis_taxes.rst # fiscality/* -> taxation/*
|
|
|
|
|
accounting/fiscality/taxes/default_taxes.rst applications/finance/accounting/taxation/taxes/default_taxes.rst # fiscality/* -> taxation/*
|
|
|
|
|
accounting/fiscality/taxes/fiscal_positions.rst applications/finance/accounting/taxation/taxes/fiscal_positions.rst # fiscality/* -> taxation/*
|
|
|
|
|
accounting/fiscality/taxes/retention.rst applications/finance/accounting/taxation/taxes/retention.rst # fiscality/* -> taxation/*
|
|
|
|
|
accounting/fiscality/taxes/taxcloud.rst applications/finance/accounting/taxation/taxes/taxcloud.rst # fiscality/* -> taxation/*
|
|
|
|
|
accounting/fiscality/taxes/taxes.rst applications/finance/accounting/taxation/taxes/taxes.rst # fiscality/* -> taxation/*
|
|
|
|
|
accounting/fiscality/taxes/vat_validation.rst applications/finance/accounting/taxation/taxes/vat_validation.rst # fiscality/* -> taxation/*
|
2021-06-30 16:21:32 +07:00
|
|
|
|
2022-10-19 23:26:01 +07:00
|
|
|
administration/db_management/db_online.rst administration/maintain/odoo_online.rst # /db_management/db_online -> /maintain/odoo_online
|
2021-06-30 16:21:32 +07:00
|
|
|
administration/db_management/db_premise.rst administration/maintain/db_premise.rst # /db_management/* -> /maintain/*
|
|
|
|
|
administration/db_management/hosting_changes.rst administration/maintain/hosting_changes.rst # /db_management/* -> /maintain/*
|
2021-10-11 20:49:30 +07:00
|
|
|
administration/db_upgrade.rst administration/upgrade/process.rst # db_upgrade -> /upgrade/process
|
2021-06-30 16:21:32 +07:00
|
|
|
administration/enterprise.rst administration/maintain/enterprise.rst # /* -> /maintain/*
|
|
|
|
|
administration/update.rst administration/maintain/update.rst # administration/* -> administration/maintain/*
|
2024-01-12 17:38:42 +07:00
|
|
|
# administration/install.rst administration/install/install.rst # /* -> /install/*
|
2021-06-30 16:21:32 +07:00
|
|
|
administration/deployment/cdn.rst administration/install/cdn.rst # /deployment/* -> /install/*
|
|
|
|
|
administration/deployment/deploy.rst administration/install/deploy.rst # /deployment/* -> /install/*
|
|
|
|
|
administration/deployment/email_gateway.rst administration/install/email_gateway.rst # /deployment/* -> /install/*
|
|
|
|
|
administration/deployment/install.rst administration/install/install.rst # /deployment/* -> /install/*
|
2021-10-11 23:04:46 +07:00
|
|
|
administration/maintain/db_premise.rst administration/maintain/on_premise.rst # db_premise -> on_premise
|
2021-10-11 20:49:30 +07:00
|
|
|
administration/maintain/db_upgrade.rst administration/upgrade/process.rst # maintain/db_upgrade -> upgrade/process
|
|
|
|
|
administration/odoo_sh/advanced/upgrade_your_database.rst administration/upgrade/odoo_sh.rst # odoo_sh/advanced/upgrade_your_database -> upgrade/odoo_sh
|
2022-03-02 17:19:33 +07:00
|
|
|
applications/websites/website/publish/domain_name.rst administration/maintain/domain_names.rst # applications/[...]/domain_name -> administration/maintain/domain_names
|
2022-03-28 19:16:49 +07:00
|
|
|
administration/upgrade/process.rst administration/upgrade.rst # upgrade/process -> upgrade
|
|
|
|
|
administration/upgrade/service_level.rst administration/upgrade.rst # upgrade/service_level -> upgrade
|
2021-06-30 16:21:32 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
crm/optimize/onsip.rst applications/general/voip/onsip.rst # crm/optimize/* --> general/voip/*
|
|
|
|
|
crm/optimize/setup.rst applications/general/voip/asterisk.rst # crm/optimize/setup --> general/voip/asterisk
|
|
|
|
|
|
2021-06-30 16:21:32 +07:00
|
|
|
developer/webservices/iap.rst developer/misc/api/iap.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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
developer/webservices/odoo.rst developer/misc/api/odoo.rst
|
2021-06-30 16:21:32 +07:00
|
|
|
developer/webservices/localizations.rst developer/misc/i18n/localization.rst
|
|
|
|
|
developer/reference/translations.rst developer/misc/i18n/translations.rst
|
|
|
|
|
developer/reference/cmdline.rst developer/misc/other/cmdline.rst
|
|
|
|
|
developer/reference/guidelines.rst developer/misc/other/guidelines.rst
|
|
|
|
|
developer/reference/iot.rst developer/misc/other/iot.rst
|
2021-08-03 16:57:02 +07:00
|
|
|
developer/reference/actions.rst developer/reference/addons/actions.rst
|
|
|
|
|
developer/reference/data.rst developer/reference/addons/data.rst
|
|
|
|
|
developer/reference/http.rst developer/reference/addons/http.rst
|
|
|
|
|
developer/reference/mixins.rst developer/reference/addons/mixins.rst
|
|
|
|
|
developer/reference/module.rst developer/reference/addons/module.rst
|
|
|
|
|
developer/reference/orm.rst developer/reference/addons/orm.rst
|
|
|
|
|
developer/reference/reports.rst developer/reference/addons/reports.rst
|
|
|
|
|
developer/reference/security.rst developer/reference/addons/security.rst
|
|
|
|
|
developer/reference/testing.rst developer/reference/addons/testing.rst
|
|
|
|
|
developer/reference/views.rst developer/reference/addons/views.rst
|
|
|
|
|
developer/reference/javascript_cheatsheet.rst developer/reference/javascript/javascript_cheatsheet.rst
|
|
|
|
|
developer/reference/javascript_reference.rst developer/reference/javascript/javascript_reference.rst
|
|
|
|
|
developer/reference/mobile.rst developer/reference/javascript/mobile.rst
|
|
|
|
|
developer/reference/qweb.rst developer/reference/javascript/qweb.rst
|
2021-06-30 16:21:32 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
discuss/monitoring.rst applications/productivity/discuss/overview/get_started.rst # (#655)
|
|
|
|
|
discuss/mentions.rst applications/productivity/discuss/overview/get_started.rst # (#655)
|
|
|
|
|
discuss/tracking.rst applications/services/project/tasks/collaborate.rst # (#655)
|
|
|
|
|
discuss/email_servers.rst applications/general/email_communication/email_servers.rst # (#655)
|
|
|
|
|
discuss/plan_activities.rst applications/productivity/discuss/overview/plan_activities.rst # (#655)
|
|
|
|
|
discuss/team_communication.rst applications/productivity/discuss/overview/team_communication.rst # (#655)
|
|
|
|
|
discuss/overview.rst applications/productivity/discuss/overview/get_started.rst # (#655)
|
|
|
|
|
|
|
|
|
|
ecommerce/shopper_experience/payment.rst applications/finance/payment_acquirers.rst # ecommerce/shopper_experience/payment --> finance/payment_acquirers/payment_acquirers
|
|
|
|
|
ecommerce/shopper_experience/authorize.rst applications/finance/payment_acquirers/authorize.rst # ecommerce/shopper_experience/* --> finance/payment_acquirers/*
|
|
|
|
|
ecommerce/shopper_experience/paypal.rst applications/finance/payment_acquirers/paypal.rst # ecommerce/shopper_experience/* --> finance/payment_acquirers/*
|
|
|
|
|
ecommerce/shopper_experience/wire_transfer.rst applications/finance/payment_acquirers/wire_transfer.rst # ecommerce/shopper_experience/* --> finance/payment_acquirers/*
|
|
|
|
|
|
|
|
|
|
general/odoo_basics/add_user.rst applications/general/odoo_basics/users.rst # add_user -> users
|
|
|
|
|
|
|
|
|
|
helpdesk/getting_started.rst applications/services/helpdesk/overview/getting_started.rst # (#565)
|
|
|
|
|
helpdesk/after_sales.rst applications/services/helpdesk/advanced/after_sales.rst # (#565)
|
|
|
|
|
helpdesk/close_tickets.rst applications/services/helpdesk/advanced/close_tickets.rst # (#565)
|
|
|
|
|
helpdesk/invoice_time.rst applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst # (#565)
|
|
|
|
|
helpdesk/reinvoice_from_project.rst applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst # (#565)
|
|
|
|
|
|
|
|
|
|
inventory/barcode/operations/delivery.rst applications/inventory_and_mrp/inventory/barcode/operations/internal.rst # delivery --> internal (#436)
|
|
|
|
|
inventory/barcode/operations/receipts.rst applications/inventory_and_mrp/inventory/barcode/operations/internal.rst # delivery --> internal (#436)
|
|
|
|
|
inventory/barcode/operations/lots_serial_numbers.rst applications/inventory_and_mrp/inventory/barcode/operations/internal.rst # delivery --> internal (#436)
|
|
|
|
|
inventory/barcode/operations/internal.rst applications/inventory_and_mrp/inventory/barcode/operations/internal.rst # delivery --> internal (#436)
|
|
|
|
|
inventory/routes/costing/landed_costs.rst applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst # routes/costing/landed_costs --> management/reporting/integrating_landed_costs (#503)
|
|
|
|
|
inventory/management/misc/schedulers.rst applications/inventory_and_mrp/inventory/management/planning/schedulers.rst # misc/* --> planning/* (#443)
|
|
|
|
|
inventory/settings/products/variants.rst applications/inventory_and_mrp/inventory/management/products/variants.rst # settings/* --> management/* (#424)
|
|
|
|
|
inventory/management/products/variants.rst sales/products_prices/products/variants.rst # applications/inventory_and_mrp/inventory/management/products/variants --> sales/products_prices/products/variants (#448)
|
|
|
|
|
inventory/settings/products.rst applications/inventory_and_mrp/inventory/management/products.rst # settings/* --> management/* (#424)
|
|
|
|
|
inventory/settings/products/strategies.rst applications/inventory_and_mrp/inventory/management/products/strategies.rst # settings/* --> management/* (#424)
|
|
|
|
|
inventory/settings/products/uom.rst applications/inventory_and_mrp/inventory/management/products/uom.rst # settings/* --> management/* (#424)
|
|
|
|
|
inventory/settings/products/usage.rst applications/inventory_and_mrp/inventory/management/products/usage.rst # settings/* --> management/* (#424)
|
|
|
|
|
inventory/management/adjustment/min_stock_rule_vs_mto.rst applications/inventory_and_mrp/inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst # adjustment/* --> replenishment_strategies/* (#424)
|
|
|
|
|
inventory/management/adjustment/virtual_warehouses.rst applications/inventory_and_mrp/inventory/management/replenishment_strategies/virtual_warehouses.rst # adjustment/* --> replenishment_strategies/* (#424)
|
|
|
|
|
inventory/settings/warehouses.rst applications/inventory_and_mrp/inventory/management/warehouses.rst # settings/* --> management/* (#424)
|
|
|
|
|
inventory/settings/warehouses/difference_warehouse_location.rst applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst # settings/* --> management/* (#424)
|
|
|
|
|
inventory/settings/warehouses/location_creation.rst applications/inventory_and_mrp/inventory/management/warehouses/location_creation.rst # settings/* --> management/* (#424)
|
|
|
|
|
inventory/management/delivery/scheduled_dates.rst applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst # delivery/scheduled_dates --> planning/scheduled_dates (#660)
|
|
|
|
|
inventory/management/planning/scheduled_date.rst applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst # scheduled_date --> scheduled_dates (#660)
|
|
|
|
|
inventory/routes/concept/procurement_rule.rst applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst # procurement_rule --> use-routes (#693)
|
|
|
|
|
inventory/routes/concept/push_rule.rst applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst # push_rule --> use-routes (#693)
|
|
|
|
|
inventory/routes/concept/use_routes.rst applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst # use_routes --> use-routes (#693)
|
|
|
|
|
|
|
|
|
|
iot/connect.rst applications/productivity/iot/config/connect.rst # /* --> config/* (#446)
|
|
|
|
|
iot/pos.rst applications/productivity/iot/config/pos.rst # /* --> config/* (#446)
|
|
|
|
|
iot/iot_notfound.rst applications/productivity/iot/config/iot_notfound.rst # /* --> config/* (#446)
|
|
|
|
|
iot/flash_sdcard.rst applications/productivity/iot/config/flash_sdcard.rst # /* --> config/* (#446)
|
|
|
|
|
iot/devices/payment_terminal.rst applications/sales/point_of_sale/payment/ingenico.rst # iot/devices/payment_terminal --> applications/sales/point_of_sale/payment/ingenico (#446)
|
|
|
|
|
|
|
|
|
|
livechat/livechat.rst applications/websites/livechat/overview.rst # livechat/* -> overveiw/* (#601)
|
|
|
|
|
|
|
|
|
|
planning/duplicate_a_planning.rst applications/services/planning/overview/duplicate_a_planning.rst # (#567)
|
|
|
|
|
planning/send_planned_shifts.rst applications/services/planning/overview/send_planned_shifts.rst # (#567)
|
|
|
|
|
|
|
|
|
|
point_of_sale/advanced/barcode.rst applications/sales/point_of_sale/shop/barcode.rst # advanced/* --> shop/* (#612)
|
|
|
|
|
point_of_sale/advanced/multicashiers.rst applications/sales/point_of_sale/shop/multicashiers.rst # advanced/* --> shop/* (#612)
|
2023-01-27 17:49:26 +07:00
|
|
|
point_of_sale/advanced/reprint.rst applications/sales/point_of_sale/shop/receipts.rst # advanced/* --> shop/* (#612)
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
point_of_sale/advanced/cash_rounding.rst applications/sales/point_of_sale/shop/cash_rounding.rst # advanced/* --> shop/* (#612)
|
|
|
|
|
point_of_sale/overview/start.rst applications/sales/point_of_sale/overview/getting_started.rst # start --> getting_started (#600)
|
|
|
|
|
point_of_sale/shop/refund.rst applications/sales/point_of_sale/overview/getting_started.rst # shop/refund --> overview/getting_started (#600)
|
|
|
|
|
point_of_sale/analyze/statistics.rst applications/sales/point_of_sale/overview/getting_started.rst # analyze/statistics --> overview/getting_started (#600)
|
|
|
|
|
point_of_sale/advanced_pricing_features/manual_discount.rst applications/sales/point_of_sale/advanced_pricing_features/discounts.rst # manual_discount --> discounts (#611)
|
|
|
|
|
point_of_sale/advanced_pricing_features/seasonal_discount.rst applications/sales/point_of_sale/advanced_pricing_features/discounts.rst # seasonal_discount --> discounts (#611)
|
|
|
|
|
point_of_sale/restaurant/setup.rst applications/sales/point_of_sale/restaurant/restaurant.rst # setup --> restaurant (#610)
|
|
|
|
|
point_of_sale/restaurant/table.rst applications/sales/point_of_sale/restaurant/restaurant.rst # table --> restaurant (#610)
|
|
|
|
|
point_of_sale/restaurant/multi_orders.rst applications/sales/point_of_sale/restaurant/restaurant.rst # multi_orders --> restaurant (#610)
|
|
|
|
|
point_of_sale/restaurant/transfer.rst applications/sales/point_of_sale/restaurant/restaurant.rst # transfer --> restaurant (#610)
|
|
|
|
|
|
|
|
|
|
project/planning/assignments.rst applications/services/project/planning/forecast.rst # assignments/* -> forecast/* (#583)
|
|
|
|
|
project/overview/main_concepts/introduction.rst applications/services/project/overview/setup.rst # main_concepts/* -> overview/* (#581)
|
|
|
|
|
project/configuration/collaboration.rst applications/services/project/tasks/collaborate.rst # configuration/collaboration -> tasks/collaborate (#581)
|
|
|
|
|
project/application/intro.rst applications/services/project/record_and_invoice/time_record.rst # application/intro -> record_and_invoice/time_record (#581)
|
|
|
|
|
project/configuration/setup.rst applications/services/project/overview/setup.rst # configuration/setup -> overview/setup (#581)
|
|
|
|
|
project/configuration/visualization.rst applications/services/project/tasks/get_started.rst # configuration/visualization -> tasks/get_started (#581)
|
|
|
|
|
project/configuration/time_record.rst applications/services/project/record_and_invoice/time_record.rst # configuration/time_record -> record_and_invoice/time_record (#581)
|
2021-05-21 22:21:55 +07:00
|
|
|
|
[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#2292
X-original-commit: 0417b955142331c16d82e0f4bafe5609f8b39da0
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-06-22 19:07:05 +07:00
|
|
|
quality/control_points.rst applications/inventory_and_mrp/quality/control/control_points.rst # /* --> control/* (#469)
|
|
|
|
|
quality/alert_mo.rst applications/inventory_and_mrp/quality/alert/alert_mo.rst # /* --> alert/* (#469)
|
|
|
|
|
quality/alert_transfer.rst applications/inventory_and_mrp/quality/alert/alert_transfer.rst # /* --> alert/* (#469)
|
|
|
|
|
quality/quality_mo.rst applications/inventory_and_mrp/quality/checks/quality_mo.rst # /* --> checks/* (#469)
|
|
|
|
|
quality/quality_transfers.rst applications/inventory_and_mrp/quality/checks/quality_transfers.rst # /* --> checks/* (#469)
|
|
|
|
|
|
|
|
|
|
sales/sale_amazon.rst applications/sales/sales/amazon_connector.rst # sale_amazon -> amazon_connector (#524)
|
|
|
|
|
sales/sale_amazon/apply.rst applications/sales/sales/amazon_connector/apply.rst # sale_amazon/* -> amazon_connector/* (#524)
|
|
|
|
|
sales/sale_amazon/setup.rst applications/sales/sales/amazon_connector/setup.rst # sale_amazon/* -> amazon_connector/* (#524)
|
|
|
|
|
sales/sale_amazon/manage.rst applications/sales/sales/amazon_connector/manage.rst # sale_amazon/* -> amazon_connector/* (#524)
|
|
|
|
|
sales/amazon_connector/apply.rst applications/sales/sales/amazon_connector/update.rst # (#728)
|
|
|
|
|
sales/sale_ebay.rst applications/sales/sales/ebay_connector.rst # sale_ebay -> ebay_connector (#524)
|
|
|
|
|
sales/ebay/setup.rst applications/sales/sales/ebay_connector/setup.rst # ebay/* moved to ebay_connector/* (#524)
|
|
|
|
|
sales/ebay/manage.rst applications/sales/sales/ebay_connector/manage.rst # ebay/* moved to ebay_connector/* (#524)
|
|
|
|
|
sales/send_quotations/optional_items.rst applications/sales/sales/send_quotations/optional_products.rst # (#533)
|
|
|
|
|
|
|
|
|
|
social_marketing/social_marketing.rst applications/marketing/social_marketing/overview.rst # social_marketing/* -> overview/* (#578)
|