Skip to content
This repository was archived by the owner on May 12, 2026. It is now read-only.

Overview

Jump to bottom
Artus Kolanowski edited this page Jan 21, 2014 · 34 revisions

This project is a fork of Flagbit's TypoGento project and licensed under the GNU General Public License (GPL-2.0) Version 2. For general information about what TypoGento does and how it works see also http://www.typogento.com.

What's new

The following features are introduced:

  • TYPO3 cache for Magento blocks
  • Integration of the Magento compiler
  • TYPO3 cache for Magento API requests (SOAP)
  • Magento page meta access through TypoScript
  • Extbase and Fluid for the TYPO3 extension

Beside them, the following features have improved:

  • Autoloader for the Magento framework
  • Single sign-on to Magento and TYPO3
  • Integration of Magento HTML header
  • Routing between Magento URLs and TYPO3 URLs
  • Handling Magento Redirects and Ajax Responses

The working principle

The following diagram provides an overview of the general working principle of TypoGento (see below for further details):

TypoGento Working Principle

1. Rendering TYPO3 frontend page
TYPO3 starts rendering the content elements, after the requested page 4711 with its template and the current user have been initialized.

2. Dispatching Magento controller action
The dispatching will only performed once, to provide TYPO3 access to the necessary Magento blocks by the TypoGento frontend plugins (tx_typogento_pi1). This causes TypoGento to:

  • Determine the target request /index.php/catalog/category/view/id/123 by its routing configuration
  • Initialize Magento and dispatch the determined request

3. Processing Magento controller action
Magento starts processing the previously generated request and renders the response layout which will be preserved by TypoGento for the final steps below. The transformation of the URLs will be performed by TypoGento (also by its routing configuration) during the rendering process of Magento. TypoGento is now ready to deliver the Magento blocks to TYPO3.

4. Passing the rendered blocks to TYPO3
From this point on, every TypoGento frontend plugin (tx_typogento_pi1) delivers directly its configured Magento block or it throws an Exception, when the Block does not exist in the Magento layout (see above).

5. See above

Overview
Installation
Configuration
FAQ

Clone this wiki locally