- the section is renamed
- the folder's name is renamed
- all references to documents in that section are updated
- previous redirections (redirects.txt) are fixed and new ones are added
Prepare the incoming documentation refactoring, ensuring the files used by a doc page
are correcly moved together with the page, avoiding broken links during the reorganisation.
Partial backport of f7bedfce2e
to ease forward-ports
When synchronizing Outlook's Calendar with Odoo for the first time, if Odoo Calendar has events with attendees created, Outlook will "recreate" these events and send a reminder as well. Meaning that attendees receive duplicated reminders (from Odoo and Outlook).
Therefore, a couple of workarounds were found (in Odoo Calendar) and added as a note in the doc.
- moving VoIP docs from "CRM" to "general"
- renaming "setup.rst" as "asterisk.rst" which is more accurate
- redirections:
* crm/optimize/onsip --> general/voip/onsip
* crm/optimize/setup --> general/voip/asterisk
For Authorize.net configuration, you need individual Receipt and Relay Response URL's.
The previous version featured the same URL twice.
The Relay Response URL is here updated to reflect proper configuration.
- Included Fiscal Positions + Journal links under Inter-Company Transactions title + remove note about it
- Include doc Multi-Company Guidelines on seealso
- Include manage_multi_companies.rst on seealso in add_user.rst
- Updates the main current doc about Payment Acquirers with a completely new doc
- Moves some docs from ecommerce to general
- redirects
- ecommerce/shopper_experience/payment --> general/payment_acquirers/payment_acquirers
- ecommerce/shopper_experience/authorize --> general/payment_acquirers/authorize
- ecommerce/shopper_experience/paypal --> general/payment_acquirers/paypal
- ecommerce/shopper_experience/wire_transfer --> general/payment_acquirers/wire_transfer
- Removed the doc version and absolute path from all user doc redirections.
- Made developer doc redirections use 13.0 instead of online, master or earlier version string.
- Fixed outdated links.
- Enforced the use of :doc:, :ref: and :download: directives for redirections.
- Replaced google drive/docs links by doc redirections.
- Removed the numbering from headings because it was either inconsistent, breaking the implicit hyperlink target or useless.
- Fixed incorrect heading formattings.
- Replaced hand-written flows by the :menuselection: directive
Unsplash CEO asked us to stop exposing our key client side (even if it was
only in the browser network and allowed by Unsplash API team leader).
Also, all our Odoo instance, on premise or not should share the same
production key, which is not possible for us obviously.
After multiple exchange, it has been negociated that:
1. Our non saas user won't be able to apply for a production key and should
prefix they Unsplash application name by 'Odoo:'. Their key will remain in
test mode.
Indeed, Unsplash won't be able to review every Odoo application and ensure
it respects the API terms and it is a real application.
2. Our saas user will query Unsplash server side so the key remain hidden.
3. The documentation should explain it all
