This documentation is not using the current rendering mechanism and will be deleted by December 31st, 2020. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
|Changed by:||Torsten Tiltack|
|Description:||We are able to provide pages which we marked within BE and also can define special values to show within the XML file. We can define (for example) CSS Classes as additional information. We can add additional pathes we want to provide within XML too. Many more things. Be creative ;)|
|Keywords:||XML provider, XML, sourcecrew.|
|Author:||Torsten Tiltack & Mihir Bhatt|
EXT: srcxmlprovider - srcxmlprovider
Extension Key: srcxmlprovider
Keywords: XML provider, XML, sourcecrew.
Copyright 2000-2014, Torsten Tiltack & Mihir Bhatt, <email@example.com>
This document is published under the Open Content License
available from http://www.opencontent.org/opl.shtml
The content of this document is related to TYPO3
- a GNU/GPL CMS/Framework available from www.typo3.org
Table of Contents¶
`Introduction 3 <#__RefHeading__5612_592635767>`_
What does it do?¶
- We are able to provide pages which we marked within BE and also can define special values to show within the XML file.
- We can define (for example) CSS Classes as additional information.
- We can add additional pathes we want to provide within XML too.
- Many more things. Be creative ;)
Pagewise configuration. In that case we are able to mark a page for the XML output.
Upload the EXT with the help of the extension manager.
Don´t forget to include the static template files
Installation is completed …
Open your TS Setup file
Create a new pageNum. (With that help we are able to provide XML like this:
The TS creates the new typeNum and also use our plugin and it´s action for providing the XML in FE:
sitemap = PAGE
typeNum = 1234
# Charset soll utf-8 sein
metaCharset = utf-8
# TYPO3 Header Code deaktivieren
disableAllHeaderCode = 1
# Content-type anpassen
additionalHeaders = Content-type:text/xml;charset=utf-8
# Seite nicht Cachen
no_cache = 1
# Kein xhtml cleaning durch TYPO3
xhtml_cleaning = 0
10 = USER_INT
userFunc = TYPO3CMSExtbaseCoreBootstrap->run
pluginName = Sitemap
extensionName = Srcxmlprovider
controller = Sitemap
vendorName = Sourcecrew
action = exportXml
1 = exportXml
We are able to provide additional informations with the help of Typoscript... Here comes some demonstration for an include of a CSS file path within the XML file:
This configs can be done within the constants:
# x_srcxmlprovider CSS path settings
plugin.tx_srcxmlprovider.settings.cssFile = fileadmin/templetes/mobile/css/navigation.css