Fix several [[= symfony_doc =]] links

Author: adriendupuis

docs/api/field_type_type_and_value.md

@@ -118,7 +118,7 @@ services:
 
 #### `parent`
 
-As described in the [Symfony service container documentation]([[= symfony_doc =]]/components/dependency_injection/parentservices.html), the `parent` config key indicates that you want your service to inherit from the parent's dependencies, including constructor arguments and method calls. This helps avoiding repetition in your Field Type configuration and keeps consistency between all Field Types.
+As described in the [Symfony service container documentation]([[= symfony_doc =]]/service_container/parent_services.html), the `parent` config key indicates that you want your service to inherit from the parent's dependencies, including constructor arguments and method calls. This helps avoiding repetition in your Field Type configuration and keeps consistency between all Field Types.
 If you need to inject other services into your Type class, skip using the `parent` config key.
 
 #### `tags`
@@ -128,7 +128,7 @@ Like most API components, Field Types use the [Symfony service tag mechanism]([[
 A service can be assigned one or several tags, with specific parameters.
 When the [service container](../api/public_php_api.md#service-container) is compiled into a PHP file, 
 tags are read by `CompilerPass` implementations that add extra handling for tagged services.
-Each service tagged as `ezplatform.field_type` is added to a [registry](http://martinfowler.com/eaaCatalog/registry.html) using the `alias` key as its unique `fieldTypeIdentifier` e.g. `ezstring`.
+Each service tagged as `ezplatform.field_type` is added to a [registry](https://martinfowler.com/eaaCatalog/registry.html) using the `alias` key as its unique `fieldTypeIdentifier` e.g. `ezstring`.
 Each Field Type must also inherit from the abstract `ezplatform.field_type` service.
 This ensures that the initialization steps shared by all Field Types are executed.
 

docs/api/public_php_api.md

@@ -134,7 +134,7 @@ $permissionResolver->setCurrentUserReference($user);
 
 ## Exception handling
 
-PHP API uses [Exceptions](http://php.net/exceptions) to handle errors.
+PHP API uses [Exceptions](https://www.php.net/exceptions) to handle errors.
 Each API method may throw different exceptions, depending on what it does.
 
 It is good practice to cover every exception you expect to happen.
@@ -156,9 +156,9 @@ try {
 
 ## Service container
 
-[[= product_name =]] uses the [Symfony service container]([[=symfony_doc=]]/service_container.html) for dependency resolution.
+[[= product_name =]] uses the [Symfony service container]([[= symfony_doc =]]/service_container.html) for dependency resolution.
 
-[Symfony dependency injection]([[=symfony_doc=]]/components/dependency_injection.html) ensures that any required services are available in your custom code
+[Symfony dependency injection]([[= symfony_doc =]]/components/dependency_injection.html) ensures that any required services are available in your custom code
 (for example, controllers) when you inject them into the constructor.
 
 Symfony service container uses service tags to dedicate services to a specific purpose. They are usually used for extension points.
@@ -167,4 +167,4 @@ Symfony service container uses service tags to dedicate services to a specific p
 
 !!! tip
 
-    For a list of all service tags exposed by Symfony, see its [reference documentation]([[=symfony_doc=]]/reference/dic_tags.html).
+    For a list of all service tags exposed by Symfony, see its [reference documentation]([[= symfony_doc =]]/reference/dic_tags.html).

docs/api/rest_api_extension_resource.md

@@ -187,7 +187,7 @@ ez_publish_rest:
 ```
 
 The `router.generate` renders a URI based on the name of the route and its parameters. The parameter values can be a real value or a placeholder. For example, `'router.generate("ibexa.rest.load_location", {locationPath: "1/2"})'` results in `/api/ezp/v2/content/locations/1/2` while `'router.generate("ibexa.rest.load_location", {locationPath: "{locationPath}"})'` gives `/api/ezp/v2/content/locations/{locationPath}`.
-This syntax is based on Symfony's [expression language]([[= symfony_doc =]]/components/expression_language/index.html), an extensible component that allows limited/readable scripting to be used outside the code context.
+This syntax is based on Symfony's [expression language]([[= symfony_doc =]]/components/expression_language.html), an extensible component that allows limited/readable scripting to be used outside the code context.
 
 In this example, `app.rest.greeting` is available in every SiteAccess (`default`):
 

docs/getting_started/install_ez_platform.md

@@ -21,11 +21,11 @@ description: Install Ibexa DXP on a Linux system and prepare your installation f
 
 To install [[= product_name =]] you need a stack with your operating system, MySQL or MariaDB, and PHP.
 
-You can install it by following your favorite tutorial, for example: [Install LAMP stack on Ubuntu](https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-ubuntu-18-04).
+You can install it by following your favorite tutorial, for example: [Install LAMP stack on Ubuntu](https://www.digitalocean.com/community/tutorials/how-to-install-lamp-stack-on-ubuntu).
 
 Additional requirements:
 
-- [Node.js](https://nodejs.org/en/) and [Yarn](https://yarnpkg.com/lang/en/docs/install/#debian-stable) for asset management.
+- [Node.js](https://nodejs.org/en/) and [Yarn](https://classic.yarnpkg.com/en/docs/install/) for asset management.
 - `git` for version control.
 - to use search in the shop front end, you must [install a search engine](#install-and-configure-a-search-engine).
 
@@ -183,7 +183,7 @@ run the following command:
 
 !!! note "Platform.sh"
 
-    If you are deploying your installation on [Platform.sh](https://docs.platform.sh/frameworks/ibexa.html),
+    If you are deploying your installation on [Platform.sh](https://docs.platform.sh/guides/ibexa/deploy.html),
     run the following command:
 
     ``` bash
@@ -227,7 +227,7 @@ Choose a [secret]([[= symfony_doc =]]/reference/configuration/framework.html#sec
 and provide it in the `APP_SECRET` parameter in `.env`.
 It should be a random string, made up of at least 32 characters, numbers, and symbols.
 This is used by Symfony when generating [CSRF tokens]([[= symfony_doc =]]/security/csrf.html),
-[encrypting cookies]([[= symfony_doc =]]/cookbook/security/remember_me.html),
+[encrypting cookies]([[= symfony_doc =]]/security/remember_me.html),
 and for creating signed URIs when using [ESI (Edge Side Includes)]([[= symfony_doc =]]/http_cache/esi.html).
 
 !!! caution
@@ -264,7 +264,7 @@ You may choose to replace the [default search engine](../guide/search/search.md#
 
 === "Solr"
 
-    Follow [How to set up Solr search engine](../guide/search/solr.md#how-to-set-up-solr-search-engine) to install Solr.
+    Follow [How to set up Solr search engine](solr.md#set-up-solr-search-engine) to install Solr.
 
 === "Elasticsearch"
 
@@ -423,7 +423,7 @@ Finally, remove the temporary file:
 
 ### Enable the Link manager
 
-To make use of the [Link Manager](../guide/url_management.md), you must [set up cron](../guide/url_management.md#enable-automatic-url-validation).
+To make use of the [Link Manager](../guide/url_management.md), you must [set up cron](url_management.md#enabling-automatic-url-validation).
 
 #### JMS payment secret [[% include 'snippets/commerce_badge.md' %]]
 

docs/guide/configuration/configuration.md

@@ -29,7 +29,7 @@ These files contain additional settings and point to the general (not environmen
 
 !!! tip
 
-    Read more about [how configuration is handled in Symfony]([[= symfony_doc =]]/best_practices/configuration.html).
+    Read more about [how configuration is handled in Symfony]([[= symfony_doc =]]/best_practices.html).
 
 !!! caution "Special characters"
 

docs/guide/forms/using_recaptcha.md

@@ -24,7 +24,7 @@ You can configure the following reCAPTCHA options in the Back Office:
 
 ### 1\. Generate the reCAPTCHA API-Key pair
 
-Go to: http://www.google.com/recaptcha/admin and log in.
+Go to: https://www.google.com/recaptcha/admin and log in.
 
 Register a new domain to get a pair of keys.
 

docs/guide/personalization/recommendation_client.md

@@ -464,7 +464,7 @@ if the content Fields were previously exported by the export script.
 You can retrieve data returned from the recommendation engine and modify it before it is shown to the user.
 
 To modify recommendation data, subscribe to `RecommendationResponseEvent`.
-See [`Event/Subscriber/RecommendationEventSubscriber.php`](https://github.com/ezsystems/ezrecommendation-client/blob/master/src/lib/Event/Subscriber/RecommendationEventSubscriber.php) for example:
+See [`Event/Subscriber/RecommendationEventSubscriber.php`](https://github.com/ezsystems/ezrecommendation-client/blob/2.1/src/lib/Event/Subscriber/RecommendationEventSubscriber.php) for example:
 
 ``` php
 public static function getSubscribedEvents(): array
@@ -482,7 +482,7 @@ The `-10` refers to priority, which must be negative so this action is performed
 Displaying image variations is not readily supported yet.
 
 You can work around this limitation by creating a template
-(based on [recommendations.html.twig](https://github.com/ezsystems/ezrecommendation-client/blob/master/src/bundle/Resources/views/recommendations.html.twig)).
+(based on [recommendations.html.twig](https://github.com/ezsystems/ezrecommendation-client/blob/2.1/src/bundle/Resources/views/recommendations.html.twig)).
 
 To access a specific image variation through API, add the `image` parameter to the request URL with the name of the variation as its value.
 For example, to retrieve the `rss` variation of the image, use:
@@ -493,7 +493,7 @@ For example, to retrieve the `rss` variation of the image, use:
 
 ### Logging
 
-Most operations are logged via the `ez_recommendation` [Monolog channel]([[= symfony_doc =]]/cookbook/logging/channels_handlers.html).
+Most operations are logged via the `ez_recommendation` [Monolog channel]([[= symfony_doc =]]/logging/channels_handlers.html).
 To log everything about Recommendation to `dev.recommendation.log`, add the following to the `ezplatform.yaml`:
 
 ``` yaml

docs/guide/search/search.md

@@ -166,7 +166,7 @@ eZ\Publish\Core\Search\Legacy\Content\Location\Gateway\SortClauseHandler\Locatio
 
 !!! note "See also"
 
-    For more information about passing parameters, see [Symfony Service Container documentation]([[= symfony_doc =]]/book/service_container.html#service-parameters).
+    For more information about passing parameters, see [Symfony Service Container documentation]([[= symfony_doc =]]/service_container.html#service-parameters).
 
 ### Search using custom Field Criterion [REST]
 

docs/guide/security.md

@@ -46,17 +46,17 @@ logout:
     You can fully customize the routes and/or the controller used for login.
     However, remember to match `login_path`, `check_path` and `logout.path` from `security.yaml`.
 
-    See [security configuration reference]([[= symfony_doc =]]/reference/configuration/security.html) and [standard login form documentation]([[= symfony_doc =]]/security/form_login_setup.html).
+    See [security configuration reference]([[= symfony_doc =]]/reference/configuration/security.html) and [standard login form documentation]([[= symfony_doc =]]/security.html#form-login).
 
 ### Authentication using Symfony Security component
 
 Authentication is provided using the Symfony Security component.
 
-[Native and universal `form_login`]([[= symfony_doc =]]/security/form_login_setup.html) is used, in conjunction with an extended `DaoAuthenticationProvider` (DAO stands for *Data Access Object*), the `RepositoryAuthenticationProvider`. Native behavior of `DaoAuthenticationProvider` has been preserved, making it possible to still use it for pure Symfony applications.
+[Native and universal `form_login`]([[= symfony_doc =]]/security.html#form-login) is used, in conjunction with an extended `DaoAuthenticationProvider` (DAO stands for *Data Access Object*), the `RepositoryAuthenticationProvider`. Native behavior of `DaoAuthenticationProvider` has been preserved, making it possible to still use it for pure Symfony applications.
 
 #### Security controller
 
-A `SecurityController` is used to manage all security-related actions and is thus used to display the login form. It follows all standards explained in [Symfony security documentation]([[= symfony_doc =]]/security/form_login_setup.html).
+A `SecurityController` is used to manage all security-related actions and is thus used to display the login form. It follows all standards explained in [Symfony security documentation]([[= symfony_doc =]]/security.html#form-login).
 
 The base template used is [`EzPublishCore/Security/login.html.twig`](https://github.com/ezsystems/ezplatform-kernel/blob/v1.0.0/eZ/Bundle/EzPublishCoreBundle/Resources/views/Security/login.html.twig).
 
@@ -94,7 +94,7 @@ If you want to use this feature, you must at least extend the login template in
 
 #### Login handlers / SSO
 
-Symfony provides native support for [multiple user providers]([[= symfony_doc =]]/security/multiple_user_providers.html). This makes it easy to integrate any kind of login handlers, including SSO and existing third-party bundles (e.g. [FR3DLdapBundle](https://github.com/Maks3w/FR3DLdapBundle), [HWIOauthBundle](https://github.com/hwi/HWIOAuthBundle), [FOSUserBundle](https://github.com/FriendsOfSymfony/FOSUserBundle), [BeSimpleSsoAuthBundle](http://github.com/BeSimple/BeSimpleSsoAuthBundle), etc.).
+Symfony provides native support for [multiple user providers]([[= symfony_doc =]]/security/user_providers.html). This makes it easy to integrate any kind of login handlers, including SSO and existing third-party bundles (e.g. [FR3DLdapBundle](https://github.com/Maks3w/FR3DLdapBundle), [HWIOauthBundle](https://github.com/hwi/HWIOAuthBundle), [FOSUserBundle](https://github.com/FriendsOfSymfony/FOSUserBundle), [BeSimpleSsoAuthBundle](https://github.com/BeSimple/BeSimpleSsoAuthBundle), etc.).
 
 See [Authenticating a user with multiple user provider](users/user_authentication.md#authenticate-user-with-multiple-user-providers) for more information.
 

docs/guide/sessions.md

@@ -83,7 +83,7 @@ See [shared sessions in the clustering guide](clustering.md#shared-sessions).
 
 To set up [[= product_name =]] using [Memcached](https://pecl.php.net/package/memcached) you need to:
 
-- [Configure the session save handler settings in `php.ini`](http://php.net/manual/en/memcached.sessions.php)
+- [Configure the session save handler settings in `php.ini`](https://www.php.net/manual/en/memcached.sessions.php)
 - Set `%ezplatform.session.handler_id%` to `~` (null) in `config/packages/ezplatform.yaml`
 
 Alternatively if you need to configure Memcached servers dynamically:
@@ -99,9 +99,9 @@ Alternatively if you need to configure Memcached servers dynamically:
 ```
 
 - Set `%ezplatform.session.handler_id%` (or `SESSION_HANDLER_ID` env var) to `app.session.handler.native_memcached`
-- Set `%ezplatform.session.save_path%` (or `SESSION_SAVE_PATH` env var) to [`save_path` config for Memcached](http://php.net/manual/en/memcached.sessions.php)
+- Set `%ezplatform.session.save_path%` (or `SESSION_SAVE_PATH` env var) to [`save_path` config for Memcached](https://www.php.net/manual/en/memcached.sessions.php)
 
-Optionally tweak [`php-memcached` session settings](http://php.net/manual/en/memcached.configuration.php) for things like
+Optionally tweak [`php-memcached` session settings](https://www.php.net/manual/en/memcached.configuration.php) for things like
 session locking.
 
 ##### Handling sessions with Redis
@@ -124,18 +124,18 @@ If you are on `php-redis` v4.2.0 and higher, you can optionally tweak [`php-redi
 
 Ideally keep [persistence cache](persistence_cache.md) and session data separated:
 
-- Sessions can't risk getting [randomly evicted](https://redis.io/topics/lru-cache#eviction-policies) when you run out of memory for cache.
+- Sessions can't risk getting [randomly evicted](https://redis.io/docs/latest/develop/reference/eviction/#eviction-policies) when you run out of memory for cache.
 - You can't completely disable eviction either, as Redis will then start to refuse new entries once full, including new sessions.
   - Either way, you should monitor your Redis instances and make sure you have enough memory set aside for active sessions/cache items.
 
-If you want to make sure sessions survive Redis or server restarts, consider using a [persistent Redis](https://redis.io/topics/persistence) instance for sessions.
+If you want to make sure sessions survive Redis or server restarts, consider using a [persistent Redis](https://redis.io/docs/latest/operate/oss_and_stack/management/persistence/) instance for sessions.
 
 ##### Alternative storing sessions in database using PDO
 
 For setups where database is preferred for storing sessions, you may use Symfony's PdoSessionHandler,
 although it is not currently recommended from performance perspective.
 
-Below is a configuration example for [[= product_name =]]. Refer to the [Symfony Cookbook]([[= symfony_doc =]]/doctrine/pdo_session_storage.html) for full documentation.
+Below is a configuration example for [[= product_name =]]. Refer to the [Symfony Cookbook]([[= symfony_doc =]]/session.html#session-database-pdo) for full documentation.
 
 ``` yaml
 framework: