@@ -75,7 +75,6 @@ Configuration
75
75
* `packages `_
76
76
* `version `_
77
77
* `version_format `_
78
- * `version_strategy `_
79
78
* `templating `_
80
79
* `hinclude_default_template `_
81
80
* :ref: `form <reference-templating-form >`
@@ -963,8 +962,6 @@ collection each time it generates an asset's path:
963
962
),
964
963
));
965
964
966
- .. _reference-framework-assets-packages :
967
-
968
965
packages
969
966
........
970
967
@@ -1033,7 +1030,6 @@ Each package can configure the following options:
1033
1030
* :ref: `base_urls <reference-assets-base-urls >`
1034
1031
* :ref: `version <reference-framework-assets-version >`
1035
1032
* :ref: `version_format <reference-assets-version-format >`
1036
- * :ref: `version_strategy <reference-framework-assets-version_strategy >`
1037
1033
1038
1034
.. _reference-framework-assets-version :
1039
1035
.. _ref-framework-assets-version :
@@ -1111,7 +1107,6 @@ option.
1111
1107
``version ``. This makes it easier to increment the cache on each
1112
1108
deployment.
1113
1109
1114
- .. _reference-framework-assets-version-format :
1115
1110
.. _reference-templating-version-format :
1116
1111
.. _reference-assets-version-format :
1117
1112
@@ -1152,16 +1147,6 @@ is set to ``5``, the asset's path would be ``/images/logo.png?version=5``.
1152
1147
any URL rewriting. The latter option is useful if you would like older
1153
1148
asset versions to remain accessible at their original URL.
1154
1149
1155
- .. _reference-framework-assets-version_strategy :
1156
-
1157
- version_strategy
1158
- ................
1159
-
1160
- **type **: ``string `` **default **: null
1161
-
1162
- The service id of the :doc: `asset version strategy </frontend/custom_version_strategy >`
1163
- applied to the assets.
1164
-
1165
1150
templating
1166
1151
~~~~~~~~~~
1167
1152
0 commit comments