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.

TreeSync base services¶

Author:	Kasper Skårhøj
Created:	2002-11-01T00:32:00
Changed by:	Arkadiy Kuleshov
Changed:	2008-04-25T01:01:29
Author:	Arkadiy Kuleshov
Email:	arkadiy.kuleshov@gmail.com
Info 3:
Info 4:

TreeSync base services¶

Extension Key: treesync_base

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.com

Table of Contents¶

TreeSync base services 1

Introduction 1

What does it do? 1

Implementation details 1

Users manual 1

Configuration 1

Known problems 1

To-Do list 2

Changelog 2

Introduction¶

What does it do?¶

This extension enables Typo3 back-end synchronization of full or partial content tree and dependent files over an XML/HTTP connection endpoint. The use-controlled part of synchronization is implemented in companion extension“treesync” which installs a back-end module that allows selection of site branch and system tables which would be updated on the remote host.

Implementation details¶

This extension also contains An XML-RPC implementation by Keith Devens( http://www.keithdevens.com/software/xmlrpc/ ). The implementation was modified to allow request/response headers modifications and HTTP authorization.

Here's a fully compliant XML-RPC client and server written in pure PHP. Only requirements are PHP, and the XML parser you're guaranteed to have if you're using PHP built into Apache (which most people are).

This library is Open Source and is distributed under Keith Devens open source license (similar to the Artistic License). You can read the release history here .

Users manual¶

Install this extension on all Typo3 instances that are part of synchronization process, i.e. both the master site and mirror sites. Then, install “treesync“ (back-end user module) on the master site.

Configuration¶

Configuration is not needed at this point. Any backend user can login remotely to the service endpoint.

Known problems¶

- Potential security problems of using custom initialization sequence for direct access to service page (not evaluated).

To-Do list¶

Implement configurable permission system.
Separate xml-rpc service into its own extension, similar to xmlrpc_server .
Investigate possiblity of using other xmlrpc library
Investigate use of HTTP attachments for transfer of binary data (payload)

Changelog¶

((generated))¶

1.1.4¶

Enabled reporting of xml parse errors by default

1.1.3¶

Modified export logic: only transfer deleted items from the specified content branch if corresponding option is checked.

1.1.2¶

Added extension manual
Fixed issues related to transferring foreign MM-relations between instances (depends on mmforeign or T3 4.1+)

TreeSync base services - 2