Update relative links from v8 to v9

.github/PULL_REQUEST_TEMPLATE.md

@@ -4,7 +4,7 @@ Thank you for contributing to the PrestaShop developer documentation!
 Please take the time to edit the "Answers" rows below with the necessary information.
 
 Check out our contribution guidelines on how to contribute:
-https://devdocs.prestashop-project.org/8/contribute/documentation/how/
+https://devdocs.prestashop-project.org/9/contribute/documentation/how/
 ------------------------------------------------------------------------------>
 
 | Questions     | Answers

README.md

@@ -7,10 +7,10 @@ This documentation is available at [https://devdocs.prestashop-project.org/](htt
 
 ## Contributing
 
-Contributions are more than welcome! [Find out how](https://devdocs.prestashop-project.org/8/contribute/documentation/how/).
+Contributions are more than welcome! [Find out how](https://devdocs.prestashop-project.org/9/contribute/documentation/how/).
 
 > [!NOTE]
-> This repository has specific contribution rules, please [read them](https://github.com/PrestaShop/docs/blob/8.x/.github/CONTRIBUTION_PROCESS.md).
+> This repository has specific contribution rules, please [read them](https://github.com/PrestaShop/docs/blob/9.x/.github/CONTRIBUTION_PROCESS.md).
 
 ## Rendering the site locally
 

basics/deployment/distribution.md

@@ -21,4 +21,4 @@ To include modules in your distribution, put them in the `modules/` folder befor
 
 During the install process, every module inside `modules/` folder will be installed. Be careful to test that your module is compatible with this step.
 
-[create-release]: {{< ref "/8/project/maintainers-guide/releasing-prestashop/create-build.md" >}}
+[create-release]: {{< ref "/9/project/maintainers-guide/releasing-prestashop/create-build.md" >}}

basics/installation/_index.md

@@ -6,7 +6,7 @@ mostViewedPage: true
 useMermaid: true
 showOnHomepage: true
 aliases: 
-    - /8/basics/installation/locahost
+    - /9/basics/installation/locahost
 ---
 
 # Installing PrestaShop locally for development or testing
@@ -47,7 +47,7 @@ timeline
     : You are ready to go
 </div>
 
-{{<cta relref="/8/basics/installation/environments/docker" type="primary">}}
+{{<cta relref="/9/basics/installation/environments/docker" type="primary">}}
   Install PrestaShop locally with Docker
 {{</cta>}}
 
@@ -76,15 +76,15 @@ Read [System Requirements][system-requirements].
 
 #### Install an *AMP stack on your operating system
 
-{{<cta relref="/8/basics/installation/environments/unix-specific">}}
+{{<cta relref="/9/basics/installation/environments/unix-specific">}}
   Install an *AMP stack on Unix
 {{</cta>}}
 
-{{<cta relref="/8/basics/installation/environments/windows-specific">}}
+{{<cta relref="/9/basics/installation/environments/windows-specific">}}
   Install an *AMP stack on Windows
 {{</cta>}}
 
-{{<cta relref="/8/basics/installation/environments/macos-specific">}}
+{{<cta relref="/9/basics/installation/environments/macos-specific">}}
   Install an *AMP stack on MacOS
 {{</cta>}}
 
@@ -279,7 +279,7 @@ You can read the [Getting Started guide][getting-started-guide] for more details
 
 #### With CLI
 
-You can also install PrestaShop with CLI, [please refer to this guide]({{< relref "/8/basics/installation/advanced/install-from-cli">}})
+You can also install PrestaShop with CLI, [please refer to this guide]({{< relref "/9/basics/installation/advanced/install-from-cli">}})
 
 ### Troubleshooting
 
@@ -290,9 +290,9 @@ You may find this error message the first time you open up the Back Office.
 This problem may arise in case-insensitive file systems like MacOS due to a misconfiguration. Check your Apache configuration and make sure that the root directory path to your PrestaShop matches the capitalization of the actual system path exactly. A typical error is for example having a folder named `/path/to/PrestaShop` (capital P, capital S) and then configuring it in Apache as `/path/to/Prestashop` (missing the capital S).
 
 [getting-started-guide]: https://docs.prestashop-project.org/v.8-documentation/v/english/getting-started
-[system-requirements]: {{< relref "/8/basics/installation/system-requirements" >}}
-[clone-the-repository]: {{< relref "/8/themes/getting-started/setting-up-your-local-environment" >}}
-[compile-assets]: {{< relref "/8/development/compile-assets" >}}
+[system-requirements]: {{< relref "/9/basics/installation/system-requirements" >}}
+[clone-the-repository]: {{< relref "/9/themes/getting-started/setting-up-your-local-environment" >}}
+[compile-assets]: {{< relref "/9/development/compile-assets" >}}
 [webpack]: https://webpack.js.org/
 [composer]: https://getcomposer.org/download/
 [nodejs]: https://nodejs.org/

basics/installation/advanced/httpd.md

@@ -3,7 +3,7 @@ title: Configure Apache Http
 menuTitle: Apache Http
 weight: 20
 aliases:
-    - /8/basics/installation/httpd
+    - /9/basics/installation/httpd
 ---
 
 # Configure Apache Httpd

basics/installation/advanced/install-from-cli.md

@@ -3,7 +3,7 @@ title: Installing PrestaShop from CLI
 menuTitle: Installation with CLI
 weight: 15
 aliases:
-    - /8/basics/installation/install-from-cli
+    - /9/basics/installation/install-from-cli
 ---
 
 # Installing PrestaShop from CLI

basics/installation/advanced/nginx.md

@@ -3,7 +3,7 @@ title: Configure Nginx
 menuTitle: Nginx
 weight: 25
 aliases:
-    - /8/basics/installation/nginx
+    - /9/basics/installation/nginx
 ---
 
 # Configure Nginx

basics/installation/advanced/prestashop-flashlight.md

@@ -33,15 +33,15 @@ This installation method is not for production and should not be exposed to publ
 please use it locally only, or at your own risks.
 
 Are you looking for production-grade images? 
-{{<cta relref="/8/basics/installation/environments/docker" type="primary">}}
+{{<cta relref="/9/basics/installation/environments/docker" type="primary">}}
   Install PrestaShop with Docker
 {{</cta>}}
 
 {{% /notice %}}
 
 ## Install prerequisites
 
-Follow this guide: [Install PrestaShop with Docker]({{<relref "/8/basics/installation/environments/docker">}}) at steps: 
+Follow this guide: [Install PrestaShop with Docker]({{<relref "/9/basics/installation/environments/docker">}}) at steps: 
 
 - Install Docker
 - Install Docker Compose

basics/installation/environments/docker.md

@@ -32,7 +32,7 @@ timeline
 {{% notice note %}}
 Looking for a quicker way to test and develop on PrestaShop?
 
-{{<cta relref="/8/basics/installation/advanced/prestashop-flashlight" type="primary">}}
+{{<cta relref="/9/basics/installation/advanced/prestashop-flashlight" type="primary">}}
   Install PrestaShop locally with Docker and PrestaShop Flashlight
 {{</cta>}}
 {{% /notice %}}

basics/installation/environments/macos-specific.md

@@ -20,6 +20,6 @@ Several options are available, such as:
 
 Another good option when it comes to run PrestaShop on MacOS, is to use `Docker`: [More informations on this dedicated page]({{< relref "8/basics/installation/environments/docker">}}).
 
-{{<cta relref="/8/basics/installation" type="primary">}}
+{{<cta relref="/9/basics/installation" type="primary">}}
   Back to installation guide
 {{</cta>}}

basics/installation/environments/unix-specific.md

@@ -18,6 +18,6 @@ Basically, you need to install:
 
 Please [read this page](https://linuxhandbook.com/lamp-stack-ubuntu/) or [this one](https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu-22-04) for guides to get started on installing Apache + MySQL + PHP on Ubuntu.
 
-{{<cta relref="/8/basics/installation" type="primary">}}
+{{<cta relref="/9/basics/installation" type="primary">}}
   Back to installation guide
 {{</cta>}}

basics/installation/environments/windows-specific.md

@@ -42,6 +42,6 @@ When installed, [use this tutorial to install the AMP stack](https://www.digital
 
 Another good option when it comes to run PrestaShop on Windows, is to use `Docker`: [More informations on this dedicated page]({{< relref "8/basics/installation/environments/docker">}}).
 
-{{<cta relref="/8/basics/installation" type="primary">}}
+{{<cta relref="/9/basics/installation" type="primary">}}
   Back to installation guide
 {{</cta>}}

basics/installation/system-requirements.md

@@ -19,7 +19,7 @@ PrestaShop needs the following server configuration in order to run:
 PrestaShop works best in Unix-based systems such as Linux and macOS, and while Windows might work, it is not actively supported.
 
 {{% notice note %}}
-PrestaShop can also work with Nginx 1.0 or later. [More informations on settings here]({{< relref "/8/basics/installation/advanced/nginx">}}).
+PrestaShop can also work with Nginx 1.0 or later. [More informations on settings here]({{< relref "/9/basics/installation/advanced/nginx">}}).
 {{% /notice %}}
 
 ## How to verify your server meets PrestaShop's requirements

basics/introduction.md

@@ -15,9 +15,9 @@ PrestaShop’s customization is based on four possibilities:
 * Hooks,
 * Overriding.
 
-Themes are explored in full in the [Themes]({{< ref "/8/themes" >}}) section.
+Themes are explored in full in the [Themes]({{< ref "/9/themes" >}}) section.
 
-Modules, hooks and the override system are explored in this page and in the [Modules]({{< ref "/8/modules" >}}) section.
+Modules, hooks and the override system are explored in this page and in the [Modules]({{< ref "/9/modules" >}}) section.
 
 {{% notice note %}}
 By default, PrestaShop is provided with more than 50 modules, enabling you to launch your online business quickly and for free.

basics/keeping-up-to-date/migration.md

@@ -609,7 +609,7 @@ developers to request the database.
 This can be used while developing a module responsible for the export
 and/or import of the objects from/to the database.
 
-For more details, see the page dedicated to [ObjectModel]({{< relref "/8/development/components/database/objectmodel" >}})
+For more details, see the page dedicated to [ObjectModel]({{< relref "/9/development/components/database/objectmodel" >}})
 
 ### Web service (API)
 
@@ -636,4 +636,4 @@ Useful links:
 
 -   [How to use the webservice API][web-service]
 
-[web-service]: {{< relref "/8/webservice" >}}
+[web-service]: {{< relref "/9/webservice" >}}

basics/keeping-up-to-date/upgrade-module/_index.md

@@ -2,14 +2,14 @@
 title: Upgrade Module
 weight: 80
 aliases:
-  - /8/development/upgrade-module/
+  - /9/development/upgrade-module/
 ---
 
 # Upgrade module
 
 Also known as the "Autoupgrade module" or the "1-click upgrade module", PrestaShop upgrade assistant aims to automatize the upgrade process.
 
-Details on how to use the web interface are documented in [Keep up-to-date: Upgrade Assistant page]({{< ref "/8/basics/keeping-up-to-date/use-autoupgrade-module.md" >}}).
+Details on how to use the web interface are documented in [Keep up-to-date: Upgrade Assistant page]({{< ref "/9/basics/keeping-up-to-date/use-autoupgrade-module.md" >}}).
 
 {{% children /%}}
 

basics/keeping-up-to-date/upgrade-module/channels.md

@@ -2,7 +2,7 @@
 title: Upgrade channels
 weight: 40
 aliases:
-  - /8/development/upgrade-module/channels
+  - /9/development/upgrade-module/channels
 ---
 
 # Upgrade channels

basics/keeping-up-to-date/upgrade-module/upgrade-cli.md

@@ -2,7 +2,7 @@
 title: Upgrade CLI
 weight: 40
 aliases:
-  - /8/development/upgrade-module/upgrade-cli
+  - /9/development/upgrade-module/upgrade-cli
 ---
 
 # Module CLI
@@ -23,8 +23,8 @@ The following parameters are mandatory:
 
 You can also use these parameters:
 
-* **--channel**: Specify the [channel to use]({{< ref "/8/basics/keeping-up-to-date/upgrade-module/channels.md" >}})
-* **--action**: Specify the [step you want to start from]({{< ref "/8/basics/keeping-up-to-date/upgrade-module/upgrade-process-steps.md" >}}) (Default: `UpgradeNow`)
+* **--channel**: Specify the [channel to use]({{< ref "/9/basics/keeping-up-to-date/upgrade-module/channels.md" >}})
+* **--action**: Specify the [step you want to start from]({{< ref "/9/basics/keeping-up-to-date/upgrade-module/upgrade-process-steps.md" >}}) (Default: `UpgradeNow`)
 
 If you use default `action` parameter, it will run the full upgrade process.
 

basics/keeping-up-to-date/upgrade-module/upgrade-module-internal-behavior.md

@@ -2,7 +2,7 @@
 title: Upgrade Module internal behavior
 weight: 20
 aliases:
-  - /8/development/upgrade-module/upgrade-module-internal-behavior
+  - /9/development/upgrade-module/upgrade-module-internal-behavior
 ---
 
 # Upgrade module internal behavior

basics/keeping-up-to-date/upgrade-module/upgrade-process-steps.md

@@ -2,7 +2,7 @@
 title: Upgrade Process Steps
 weight: 30
 aliases:
-  - /8/development/upgrade-module/
+  - /9/development/upgrade-module/
 useMermaid: true
 ---
 

basics/keeping-up-to-date/upgrade.md

@@ -12,25 +12,25 @@ weight: 30
 
 Do not go further if you haven’t made a backup of your shop.
 Rollback will be the only way to go back if something does not go well, and this requires a backup.
-Learn [how to backup your shop]({{< ref "/8/basics/keeping-up-to-date/backup" >}})
+Learn [how to backup your shop]({{< ref "/9/basics/keeping-up-to-date/backup" >}})
 {{% /notice %}}
 
 There are a few ways of upgrading the PrestaShop store. This chapter provides information about two methods of getting the software to the latest version.
 
 ## Upgrade assistant module (formerly 1-click upgrade module)
 
-You can use provided `autoupgrade` module to upgrade your store to the newest version using web interface. You can read more about the module and how to use it [here]({{< ref "/8/basics/keeping-up-to-date/use-autoupgrade-module" >}}).
+You can use provided `autoupgrade` module to upgrade your store to the newest version using web interface. You can read more about the module and how to use it [here]({{< ref "/9/basics/keeping-up-to-date/use-autoupgrade-module" >}}).
 
 ## Upgrade assistant module (formerly 1-click upgrade module) - CLI method
 
-Upgrade assistant module (autoupgrade) is fully accessible through `cli`. You can read all the details [here]({{< ref "/8/basics/keeping-up-to-date/upgrade-module/upgrade-cli" >}}).
+Upgrade assistant module (autoupgrade) is fully accessible through `cli`. You can read all the details [here]({{< ref "/9/basics/keeping-up-to-date/upgrade-module/upgrade-cli" >}}).
 
 ## Manual upgrade
 
 {{% notice warning %}}
 **Important**
 
-Manual upgrade without `autoupgrade` module is not possible at the moment. We recommend using [cli]({{< ref "/8/basics/keeping-up-to-date/upgrade-module/upgrade-cli" >}})
+Manual upgrade without `autoupgrade` module is not possible at the moment. We recommend using [cli]({{< ref "/9/basics/keeping-up-to-date/upgrade-module/upgrade-cli" >}})
 mechanism from the upgrade assistant module.
 {{% /notice %}}
 

basics/keeping-up-to-date/use-autoupgrade-module.md

@@ -8,7 +8,7 @@ weight: 40
 
 Also known as the "Autoupgrade module" or the "1-click upgrade module", PrestaShop upgrade assistant aims to automatize the upgrade process.
 
-It is available from your shop administration panel. It executes the [upgrade process]({{< ref "/8/basics/keeping-up-to-date/upgrade.md" >}}) automatically, and is available for almost all versions of PrestaShop.
+It is available from your shop administration panel. It executes the [upgrade process]({{< ref "/9/basics/keeping-up-to-date/upgrade.md" >}}) automatically, and is available for almost all versions of PrestaShop.
 
 {{% notice note %}}
 The same note as above, in order to have this module working you must have set in `/app/config/parameters.php` database account with full privileges.

contribute/contribute-pull-requests/contribute_using_docker.md

@@ -95,7 +95,7 @@ A good practice is to write meaningful commits messages: it's better to have "co
 ### Launch the test suite
 
 Your changes now sounds ok, and you're almost ready to share your changes with the community.
-Before all, you may ensure your changes don't break everything: this is why we have multiple test suites you can use. Want to read more about tests in PrestaShop? Head to [this]({{< relref "/8/testing/" >}}) page.
+Before all, you may ensure your changes don't break everything: this is why we have multiple test suites you can use. Want to read more about tests in PrestaShop? Head to [this]({{< relref "/9/testing/" >}}) page.
 
 You can execute it in your dockerized PrestaShop application without altering your website (it uses a specific database).
 
@@ -105,4 +105,4 @@ docker compose exec prestashop-git composer test-all
 
 ### Publish your work
 
-See [Submit a Pull Request]({{< relref "/8/contribute/contribute-pull-requests/create-pull-request" >}}).
+See [Submit a Pull Request]({{< relref "/9/contribute/contribute-pull-requests/create-pull-request" >}}).

contribute/contribute-pull-requests/contribute_using_localhost.md

@@ -144,5 +144,5 @@ A good practice is to write meaningful commits labels: it's better to have "Corr
 See [Submit a Pull Request]({{< relref "create-pull-request" >}}).
 
 [getting-started-guide]: https://docs.prestashop-project.org/1.7-documentation/user-guide
-[system-requirements]: {{< relref "/8/basics/installation/system-requirements" >}}
-[compile-assets]: {{< relref "/8/development/compile-assets" >}}
+[system-requirements]: {{< relref "/9/basics/installation/system-requirements" >}}
+[compile-assets]: {{< relref "/9/development/compile-assets" >}}

contribute/contribution-guidelines/_index.md

@@ -87,11 +87,11 @@ Before proposing to add a new dependency, make sure you do this:
 
 ## Related topics
 
-- [What happens after you submit a contribution]({{< relref "/8/contribute/contribution-process/how-pull-requests-are-processed" >}})
+- [What happens after you submit a contribution]({{< relref "/9/contribute/contribution-process/how-pull-requests-are-processed" >}})
 
 ## Read more
 
 {{% children /%}}
 
-[how-to-compile-assets]: {{% relref "/8/development/compile-assets.md" %}}
+[how-to-compile-assets]: {{% relref "/9/development/compile-assets.md" %}}
 [compatible-licenses]: {{% relref "compatible-licenses" %}}

contribute/contribution-guidelines/project-modules.md

@@ -39,7 +39,7 @@ A license file must be stored inside the module (usually it's a `LICENSE.md` fil
 
 ### File headers
 
-All files within a module must include the AFL license header, as provided in the [coding standards chapter]({{< relref "/8/development/coding-standards/_index.md#module-files" >}}).
+All files within a module must include the AFL license header, as provided in the [coding standards chapter]({{< relref "/9/development/coding-standards/_index.md#module-files" >}}).
 
 They can easily be applied by using the `header-stamp` binary from [PrestaShop modules developer tools][php-dev-tools].
 
@@ -79,8 +79,8 @@ $this->ps_versions_compliancy = array(
 Because the `max` value will always use the latest PrestaShop version, it means the module must remain compatible with upcoming (not released) PrestaShop versions too.
 
 [report-issue]: https://github.com/PrestaShop/PrestaShop/issues/new/choose
-[1]: {{< relref "/8/development/coding-standards/" >}}
-[2]: {{< relref "/8/contribute/contribution-guidelines" >}}
+[1]: {{< relref "/9/development/coding-standards/" >}}
+[2]: {{< relref "/9/contribute/contribution-guidelines" >}}
 [3]: https://help.github.com/articles/using-pull-requests
 [AFL-3.0]: https://opensource.org/licenses/AFL-3.0
 [php-dev-tools]: https://github.com/PrestaShop/php-dev-tools

contribute/documentation/how/writing-markdown.md

@@ -13,4 +13,4 @@ If you don't know Markdown yet, have a look at this [quick Markdown guide from G
 
 ## Extended features: Shortcodes
 
-Hugo uses special short codes for many things. [Read about them here]({{< relref "/8/contribute/documentation/shortcodes/" >}}).
+Hugo uses special short codes for many things. [Read about them here]({{< relref "/9/contribute/documentation/shortcodes/" >}}).

contribute/documentation/shortcodes/ref.md

@@ -9,13 +9,13 @@ weight: 1
 
 To link to another page in the documentation, use `ref`:
 
-    [This is a link to Configuration]({{</* ref "/8/development/configuration" */>}})
+    [This is a link to Configuration]({{</* ref "/9/development/configuration" */>}})
 
 
 Rendered result:
 
 {{% callout %}}
-[This is a link to Configuration]({{< ref "/8/development/configuration" >}})
+[This is a link to Configuration]({{< ref "/9/development/configuration" >}})
 {{% /callout %}}
 
 {{% notice tip %}}

development/architecture/domain/cqrs.md

@@ -30,7 +30,7 @@ Fortunately, by implementing CQRS it allows PrestaShop to quickly build new API,
 
 ## CQRS Principles in PrestaShop
 
-1. All input validation SHOULD be done during the object construction (see [Validation]({{< relref "/8/development/architecture/migration-guide/validation">}})).
+1. All input validation SHOULD be done during the object construction (see [Validation]({{< relref "/9/development/architecture/migration-guide/validation">}})).
 2. All objects SHOULD be immutable unless it's impractical to do so.
 3. The `Core\Domain` namespace _describes_ business objects, actions and messages. It DOES NOT contain behavior (at least for now).