@@ -72,7 +72,6 @@ Configuration
7272 * `version_strategy `_
7373 * `version `_
7474 * `version_format `_
75- * `version_strategy `_
7675* `templating `_
7776 * `hinclude_default_template `_
7877 * :ref: `form <reference-templating-form >`
@@ -894,8 +893,6 @@ collection each time it generates an asset's path:
894893 ),
895894 ));
896895
897- reference-framework-assets-packages :
898-
899896
900897........
901898
@@ -965,7 +962,6 @@ Each package can configure the following options:
965962* :ref: `version_strategy <reference-assets-version-strategy >`
966963* :ref: `version <reference-framework-assets-version >`
967964* :ref: `version_format <reference-assets-version-format >`
968- * :ref: `version_strategy <reference-framework-assets-version_strategy >`
969965
970966.. _reference-templating-version-strategy :
971967.. _reference-assets-version-strategy :
@@ -1063,7 +1059,6 @@ option.
10631059 ``version ``. This makes it easier to increment the cache on each
10641060 deployment.
10651061
1066- .. _reference-framework-assets-version-format :
10671062.. _reference-templating-version-format :
10681063.. _reference-assets-version-format :
10691064
@@ -1104,16 +1099,6 @@ is set to ``5``, the asset's path would be ``/images/logo.png?version=5``.
11041099 any URL rewriting. The latter option is useful
8A6B
if you would like older
11051100 asset versions to remain accessible at their original URL.
11061101
1107- .. _reference-framework-assets-version_strategy :
1108-
1109- version_strategy
1110- ................
1111-
1112- **type **: ``string `` **default **: null
1113-
1114- The service id of the :doc: `asset version strategy </frontend/custom_version_strategy >`
1115- applied to the assets.
1116-
11171102templating
11181103~~~~~~~~~~
11191104
0 commit comments