DEPRECATION WARNING

This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.

EXT: srcxmlprovider

Created:2010-02-18T17:33:18
Changed by:Torsten Tiltack
Changed:2014-08-04T22:37:32
Classification:srcxmlprovider
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
Email:info@sourcecrew.org
Info 4:
Language:en

img-1 img-2 EXT: srcxmlprovider - srcxmlprovider

EXT: srcxmlprovider

Extension Key: srcxmlprovider

Language: en

Keywords: XML provider, XML, sourcecrew.

Copyright 2000-2014, Torsten Tiltack & Mihir Bhatt, <info@sourcecrew.org>

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

EXT: Readable name of your extension 1

`Introduction 3 <#__RefHeading__5612_592635767>`_

What does it do? 3

Screenshots 3

Installation 3

Configuration 3

Additional 4

Introduction

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 ;)

Screenshots

Pagewise configuration. In that case we are able to mark a page for the XML output.

img-3

Installation

Upload the EXT with the help of the extension manager.

Don´t forget to include the static template files

Installation is completed …

Configuration

Open your TS Setup file

Create a new pageNum. (With that help we are able to provide XML like this:

http://yourdomain.com?type=1234

The TS creates the new typeNum and also use our plugin and it´s action for providing the XML in FE:

sitemap = PAGE

sitemap {

typeNum = 1234

config {

# 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

10 {

userFunc = TYPO3CMSExtbaseCoreBootstrap->run

pluginName = Sitemap

extensionName = Srcxmlprovider

controller = Sitemap

vendorName = Sourcecrew

action = exportXml

switchableControllerActions {

Sitemap {

1 = exportXml

}

}

}

}

Additional

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

img-2 4