Merge pull request #2136 from MAX-IT-Tech/feat/internal-links-fix

Fix incorrect internal documentation links for the 9.1.x transition

Author: kpodemski

basics/installation/advanced/nginx.md

@@ -175,4 +175,4 @@ server {
 }
 ```
 
-[nginx-scale]: {{< ref "8/scale/webservers/nginx" >}}
+[nginx-scale]: {{< ref "/9/scale/webservers/nginx" >}}

basics/installation/environments/macos-specific.md

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

development/components/console/prestashop-linter-legacy-link.md

@@ -13,4 +13,4 @@ weight: 20
 
 ## Description
 
-This command aims to check if [_legacy_link]({{< relref "/9/development/architecture/migration-guide/controller-routing#routing-in-prestashop" >}}) is configured in BackOffice routes.
+This command aims to check if [_legacy_link]({{< relref "/9/development/architecture/migration-guide/controller-routing.md" >}}) is configured in BackOffice routes.

development/components/export/csv-response.md

@@ -134,7 +134,7 @@ When looping over your `callback function`, the `CsvResponse` is retrieving `$li
 ```
 
 {{% notice note %}}
-A good example implementation of `CsvResponse::MODE_OFFSET` can be seen in [ProductCsvExporter.php](https://github.com/PrestaShop/PrestaShop/blob/8.0.x/src/Core/Product/ProductCsvExporter.php#L56-L97)
+A good example implementation of `CsvResponse::MODE_OFFSET` can be seen in [ProductCsvExporter.php](https://github.com/PrestaShop/PrestaShop/blob/8.0.0/src/Core/Product/ProductCsvExporter.php#L56-L97)
 {{% /notice %}}
 
 #### Manually setting $start parameter

development/components/hook/register-new-hook.md

@@ -52,7 +52,7 @@ The previous step only adds the hook to _new_ shops. We also need to register th
 The last step is to insert the new hooks in the `ps_hooks` table using the upgrade system. Locate the X.Y.Z.sql file that refers to the PrestaShop version that will include your change: for instance, if the release expected to include this change is `1.7.5.0`, locate that file in the `upgrade/sql` folder from the [Update assistant](https://github.com/PrestaShop/autoupgrade) module.
 
 {{% notice tip %}}
-This process is explained here: [Structure and content upgrades]({{< ref "/9/development/database/structure.md#structure-and-content-upgrades" >}})
+This process is explained here: [Structure and content updates]({{< ref "/9/development/database/structure.md#structure-and-content-updates" >}})
 {{% /notice %}}
 
 Once you have located the file, add the corresponding SQL commands to add new hooks:

faq/assets-compilation-problems.md

@@ -9,4 +9,4 @@ If you encounter the error message `Template "@AdminNewTheme/public/preload.html
 
 To resolve this issue please make sure to compile the assets correctly, you can see the [assets compilation documentation][assets-compilation] for more information.
 
-[assets-compilation]: {{< relref "9/development/compile-assets" >}}
+[assets-compilation]: {{< relref "/9/development/compile-assets" >}}

modules/concepts/controllers/admin-controllers/override-decorate-controller.md

@@ -52,7 +52,7 @@ In the above example, the `path` has not been changed, but you can change it to
 {{% /notice %}}
 
 {{% notice warning %}}
-Keep the item `_legacy_controller` if your controller relies on it to configure a [AdminSecurity annotation]({{< relref "8/development/architecture/migration-guide/controller-routing#access-rules-convention" >}}) such as `@AdminSecurity("is_granted('read', request.get('_legacy_controller'))")`
+Keep the item `_legacy_controller` if your controller relies on it to configure a [AdminSecurity annotation]({{< relref "/9/development/architecture/modern/controller-routing.md#access-rules-convention" >}}) such as `@AdminSecurity("is_granted('read', request.get('_legacy_controller'))")`
 
 Keep the items `_legacy_controller` and `_legacy_link` if you want to reroute internal links and legacy URLs like `index.php?controller=AdminOrders` as well.
 {{% /notice %}}
@@ -79,9 +79,9 @@ With the following configuration item, we can override this configuration to mak
 # modules/your-module/config/services.yml
   'PrestaShopBundle\Controller\Admin\Improve\Design\CmsPageController':
     class: MyModule\Controller\DemoController
-
 ```
 
+
 Thanks to this, whenever Symfony forwards a request to the Core controller `PrestaShopBundle\Controller\Admin\Improve\Design\CmsPageController` it will be forwarded to `DemoController` instead.
 
 {{% notice warning %}}
@@ -109,7 +109,7 @@ With the following configuration item, we can decorate it with a custom controll
   custom_controller:
     class: MyModule\Controller\DemoController
     decorates: PrestaShopBundle\Controller\Admin\Improve\Design\CmsPageController
-    arguments: ['@custom_controller.inner']
+    arguments: ["@custom_controller.inner"]
 ```
 
 or if you are using [autowiring](https://symfony.com/doc/4.4/service_container/autowiring.html):

modules/concepts/controllers/admin-controllers/tabs.md

@@ -211,7 +211,7 @@ When you create a new `Tab` it automatically creates the appropriate roles in `T
 - `ROLE_MOD_TAB_ADMINLINKWIDGET_READ`
 - `ROLE_MOD_TAB_ADMINLINKWIDGET_UPDATE`
 
-These roles will allow you to manage detailed permission in your controllers, you can read this documentation if you need more details about [Controller Security]({{< ref "/9/development/architecture/migration-guide/controller-routing.md#security" >}}).
+These roles will allow you to manage detailed permission in your controllers, you can read this documentation if you need more details about [Controller Security]({{< ref "/9/development/architecture/modern/controller-routing.md#security" >}}).
 They are automatically added to the `SUPER_ADMIN` group, and the group of the Employee installing the module, but you can then edit privileges for other Employee groups.
 
 {{% notice note %}}

modules/concepts/doctrine/how-to-handle-multi-lang-doctrine-entity.md

@@ -25,7 +25,7 @@ There are several Doctrine plugins which allows to handle multi lang fields easi
 
 {{% notice note %}}
 **Namespace and autoload**
-The content of this documentation relies on **namespaces** which need to be defined in your module's autoload, we won't cover this part here if you need more information please read [how to setup composer in a module]({{< ref "8/modules/concepts/composer#setup-composer-in-a-module" >}})
+The content of this documentation relies on **namespaces** which need to be defined in your module's autoload, we won't cover this part here if you need more information please read [how to setup composer in a module]({{< ref "/9/modules/concepts/composer#setup-composer-in-a-module" >}})
 {{% /notice %}}
 
 {{% notice tip %}}

modules/concepts/forms/admin-forms.md

@@ -10,7 +10,7 @@ One of the most common tasks for the PrestaShop developers is to alter the data
 {{% notice info %}}
 **This system only works with pages from the "Configure" section of your back office.**
 
-If you want to customize an entity form, you're looking for [Grid]({{<relref "9/development/components/grid/" >}}) and [Identifiable Objects]({{<relref "/9/development/architecture/migration-guide/forms/crud-forms">}}).
+If you want to customize an entity form, you're looking for [Grid]({{<relref "/9/development/components/grid/" >}}) and [Identifiable Objects]({{<relref "/9/development/architecture/migration-guide/forms/crud-forms">}}).
 
 Learn how to achieve this with the [Grid and identifiable object form hooks usage example]({{<relref "/9/modules/sample-modules/grid-and-identifiable-object-form-hooks-usage">}}).
 {{% /notice %}}
@@ -66,7 +66,7 @@ Of course, you can override every template to improve again the rendering of the
             <div class="card-block">
                 <div class="card-text">
                     <div class="form-group">
-                        {{ ps.label_with_help(('Maximum size for attached files'|trans), ('Set the maximum size allowed for attachment files (in megabytes). This value has to be lower or equal to the maximum file upload allotted by your server (currently: %size% MB).'|trans({'%size%': 'PS_ATTACHMENT_MAXIMUM_SIZE'|configuration}, 'Admin.Advparameters.Help'))) }}
+                        {{ ps.label_with_help(('Maximum size for attached files'|trans), ('Set the maximum size allowed for attachment files (in megabytes). This value has to be lower or equal to the maximum file upload allotted by your server (currently: %size% MB).'|trans({'%size%': 'PS_ATTACHMENT_MAXIMUM_SIZE'|configuration}, 'Admin.Advparameters.Help'))) }} 
                         {{ form_errors(uploadQuotaForm.max_size_attached_files) }}
                         {{ form_widget(uploadQuotaForm.max_size_attached_files) }}
                     </div>