Subrequestless view fallback is now the default

bundle/Resources/config/ezplatform_default_settings.yml

@@ -37,8 +37,8 @@ parameters:
 
     # Default Site API settings under eZ Platform 'ezpublish/system' configuration node
     ezsettings.default.ng_site_api.site_api_is_primary_content_view: false
-    ezsettings.default.ng_site_api.fallback_to_secondary_content_view: false
-    ezsettings.default.ng_site_api.fallback_without_subrequest: false
+    ezsettings.default.ng_site_api.fallback_to_secondary_content_view: true
+    ezsettings.default.ng_site_api.fallback_without_subrequest: true
     ezsettings.default.ng_site_api.richtext_embed_without_subrequest: false
     ezsettings.default.ng_site_api.use_always_available_fallback: true
     ezsettings.default.ng_site_api.fail_on_missing_field: '%kernel.debug%'

docs/reference/configuration.rst

@@ -118,8 +118,8 @@ through two configuration options (showing default values):
         system:
             frontend_group:
                 ng_site_api:
-                    fallback_to_secondary_content_view: false
-                    fallback_without_subrequest: false
+                    fallback_to_secondary_content_view: true
+                    fallback_without_subrequest: true
 
 - ``fallback_to_secondary_content_view``
 
@@ -142,12 +142,6 @@ through two configuration options (showing default values):
     turned off, links in the preview in the admin UI will not be correctly generated. To work around
     that problem, turn the option on.
 
-.. note::
-
-    For backward compatibility reasons, ``fallback_to_secondary_content_view`` and
-    ``fallback_without_subrequest`` are turned off, but in next major release that will be
-    reversed by default.
-
 .. note::
 
     When fallback is enabled default templates for the primary view will not be used. Otherwise the