EXT: Page and Extension Sitemap¶

What does it do?¶

Instead of a normal sitemap of pages, this extension realizes a complete sitemap where detailview-links of extensions are included. For correct implementation programmers knowledge is needed → SQL for Detailview-Records has to be defined in records (see Configuration). There is also an alternative XML-Sitemap view.

Screenshots¶

Insert Extension¶

After installation of the extension in the Extension Manager, you can insert the Sitemapon each page as a Content Element. At first select the Content Element “General Plugin”. Afterwards specify the extension-type by selecting “Sitemap for pages and extensions (additional config needed)” for “Selected Plugin” in the tab “Plugin”:

For a XML-Sitemap-Output, change the View to “XML-Sitemap”:

Then you can insert the startingpoint (rootpage) for the complete sitemap in the field “Record Storage Page” in the tab “Behaviour”. All output-pages need to be under this rootpage!

For getting extension-detailview-links within the sitemap additional config is needed! You can add a new folder within your TYPO3-Backend for “Sitemap” “Extension Definitions”-Records. Insert new “Extension Definitions” in your created folder via the “List”-Module in TYPO3-Backend:

Fill out “Extension Definitions”-Fields (programmers knowledge needed!):

1. Select page on which the detailview-output is performed

2. Insert the SQL-SELECT Statement with which you want to get the records for which links should be produced. This is identical to the SQL-SELECT Satement of the extension's listview but without LIMIT ! You probably have to search in the extension and do some debug-output for getting the correct statement. The limit is inserted via this extension. Furthermore “SELECT” is replaced with ''SELECT SQL_CALC_FOUND_ROWS“ for record counting → paging within ajax-mode. And for standard-localization you can insert 'AND sys_language_uid = ###sys_language_uid###' in the where-clause. '###sys_language_uid###' will be replaced with the correct value for each statement. Be sure to name the Primary Key (which normally should be uid) “uid AS uid” [for id it would be “id AS uid”] and the title “title AS title” [for name it would be “name AS title”]. Furthermore you have to get all other params out of the table which you need for the detailview link (next step).

3. Insert all variables you need for the detailviewlink. You can insert every value you got out of the SQL-SELECT Statement by ###value### [for “uid AS uid” this would be ###uid###; for “category” this would be ###category###]. If you have Real-Url enabled you can look up the variable names in the “/typo3conf/realurl_conf.php” - otherwise you see them in the Link to your detailviews directly. E.g. for tt_news you need the param “tx_ttnews[tt_news]” which represents the uid of the record. So this would be “&tx_ttnews[tt_news]=###uid###”. More variables aren't needed for representing the record. But if you use the backPid for tt_news you could also insert the variable “tx_ttnews[backPid]” like this “&tx_ttnews[backPid]=10” (10 is an example for a page-id of your tt _news-Listview) => “&tx_ttnews[tt_news]=###uid###&tx_ttnews[backPid]=10”.

4. Define if you want to load the pages afterwards via AJAX. If you want to use this mode on a record you first have to insert the static Typoscript-Template “PageExtSitemap Ajax-Default” to your Maintemplate. If you configured the plugin via Typoscript-Setup you have to include the AJAX-Integration after your configuration again. Otherwise you use the old configuration for AJAX-Mode because static Templates are normally included before Maintemplate-TS-Setup! Best way is to not include the static template (EXT:mbpageandextensionsitemap/static/setup.txt) but copy all code to your Typoscript-Setup instead and configure it to your needs.

((generated))¶