[TASK] Explain "recursive" in record sitemap 03/58903/3
authorJonas Eberle <flightvision@googlemail.com>
Fri, 16 Nov 2018 11:07:20 +0000 (12:07 +0100)
committerMathias Brodala <mbrodala@pagemachine.de>
Fri, 16 Nov 2018 13:45:24 +0000 (14:45 +0100)
Follow-up commit to provide explanation for parameter `recursive` in:
A recursive configuration makes it a lot easier to provide
a sitemap for all records without touching the configuration
if a new sysfolder is created.

Resolves: #86826
Releases: master
Change-Id: I8c51d6ca066ecae684e4ab5a655c71e2dbe4fc24
Reviewed-on: https://review.typo3.org/58903
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Jonas Eberle <flightvision@googlemail.com>
Reviewed-by: Daniel Goerz <daniel.goerz@posteo.de>
Tested-by: Daniel Goerz <daniel.goerz@posteo.de>
Reviewed-by: Mathias Brodala <mbrodala@pagemachine.de>
Tested-by: Mathias Brodala <mbrodala@pagemachine.de>
typo3/sysext/core/Documentation/Changelog/9.5.x/Feature-86826-RecursiveRecordSitemap.rst

index 36e0cf4..6c36782 100644 (file)
@@ -11,12 +11,12 @@ Description
 
 The :php:`RecordsXmlSitemapDataProvider` supports now the configuration `recursive` to include
 records not only from provided list of page ids but also its subpages.
-
+`recursive` refers to the number of levels taken into account beyond the `pid` page. (default: 0)
 
 Impact
 ======
 
-A full example looks is:
+A full example:
 
 .. code-block:: typoscript
 
@@ -49,4 +49,4 @@ A full example looks is:
     }
   }
 
-.. index:: Frontend, ext:seo, NotScanned
\ No newline at end of file
+.. index:: Frontend, ext:seo, NotScanned