Sitemap modules
There are several extensions for creating a sitemap. There is also a standard element built into type3 natively. In general, a sitemap is useful for users as a usability element as it allows you to quickly find the pages you need if the navigation is very confusing. In this blog, I have already reviewed the Google sitemap TYPO3 extension from Dmitry Dulepov, who builds a map for search engines. The same thing that the Google XML Sitemaps plugin does in WordPress. But today I want to talk about other sitemaps – which are visible to users, in WP the dagon design sitemap generator copes with this, what is in TYPO3. Let me remind you that the post “From the archive”.
Standard sitemap sitemap.gs
1. To install a standard sitemap, you need to add a Sitemap content element on the page, specify sitemap as the menu type. Next, we define Startingpoint – a link to the beginning of the site tree.
2. In the template, include the styles.sitemap.gs static template, and in the Setup, write the code:
tt_content.menu.20 & lt; styles.sitemap.gs
3. Next, through the Constant Editor, select the GS-SITEMAP category and make the necessary settings: fonts, bullets, excluded pages, etc.
4. You can make a sitemap in its usual form. To do this, instead of styles.sitemap.gs, include the styles.sitemap.text static template and write the appropriate code in Setup:
tt_content.menu.20 & lt; styles.sitemap.text
The design of such a sitemap is done in CSS as for regular links. In addition, there are no settings in the template, in particular the exclusion of unnecessary pages.
Sitemap ks_sitemap
Install the extension through the extension manager. Settings for the template:
plugin.tx_kssitemap_pi1 {
htmlTemplate = EXT: ks_sitemap / template.html
ignoreList =
}
Add the Sitemap content element to the required page, specify ks_sitemap as the menu type, and define a link to the beginning of the site tree – Startingpoint.
Ws_sitemap sitemap extension
1. Install the extension through the extension manager. Create an additional template, where we copy the contents of the ext_typoscript_constants.txt and ext_typoscript_setup.txt files, respectively, in the field of constants and settings. Remember to add this template as static to the main one.
2. There are several settings in the Constant Editor, category TX-WSSITEMAP_PI1. You can simply write in the template through the menu of constants (slightly modified ext_typoscript_constants.txt code):
plugin.tx_wssitemap_pi1 {
# Name of the root page (site)
rootPageName = * Sitemap Site *
#PageID of the root page
rootPagePID = 21
# Icon for the root page
rootImg = menu_root.png
#Prefix for the title tag ???
titlePrefix = Shaw for a prefix?
# List of PID pages separated by commas for HMENU, subpages are automatically added
menuSpecialValue = 21
#PID of pages excluded from the menu
menuExcludeUidList = 36.37
# cat = tx_wssitemap_pi1 / typo; type = text; label = Link target for the sitemap.
menuTarget =
# Path to the folder with icons
standardImgFolder = typo3conf / ext / ws_sitemap / res / img /
# Icon for the separator in the menu
splitImg = menu_split.png
# Vertical line in the menu
vertlineImg = menu_vertline.png
# Icon for corner in menu
cornerImg = menu_corner.png
#Iconda for space
spaceImg = menu_space.png
# cat = tx_wssitemap_pi1 / file; type = text; label = Default icon for a page in the tree.
itemImg = menu_link_default.png
# Icon for a page in a menu with subpages
ifsubImg = menu_link_ifsub.png
}
The purpose and settings of titlePrefix and menuTarget remain unclear. It is possible to set images on the pages in the Image for graphical sitemap field to display the page in the sitemap!
Dropdown sitemap mak_dropdownmenu
1. Install the extension through the extension manager. Next, on the page, you need to add a Sitemap content element, specify the drop-down menu as the menu type.
2. To add items to the menu – sitemap, you need to insert the corresponding pages into the Startingpoint.
3. In the pi1 / class.tx_mak file, dropdownmenu_pi1.php to the line:
if ($ menuItem [‘doktype’]! = 199) $ link = “/”.$this->pi_getPageLink($menuPid);
replace with:
if ($ menuItem [‘doktype’]! = 199) $ link = $ this- & gt; pi_getPageLink ($ menuPid);
Menu items can be separated by “Spacer pages”. They will not be used as links.
That’s all the modules that I once found for the implementation of the sitemap. Since the post is “From the archive”, it is possible that some of them no longer work or are configured differently.
