en	Import Action
fr	Importer une action

en	Press "Preview" to see the content of the import file or update the preview display according to changed configurations. Press "Import"/"Update" if you want to perform the actual import. Before importing make sure you change any editable soft references that are shown in the preview data.

en	EXT:impexp/Resources/Public/Images/cshimages/diffview.png
fr	EXT:impexp/cshimages/diffview.png

en	Example of the result view after importing. As you can see the RTE attached images (soft references) has been written to new file names and the difference view tells you that the names changed in the bodytext content.

en	Import/Export
fr	Importer/Exporter

en	Native Import/Export module for TYPO3 data. Can export single records, content of tables, single pages or whole branches of the page tree. Includes attached media like image and preserves relations between records. Exports only to TYPO3 specific format, either a binary format (.T3D) or XML. The format is meant for exchange between TYPO3 systems.
fr	Module d'import/export natif pour les données de TYPO3. Permet l'export d'enregistrements, de contenus de tables, de pages ou de branches complètes de l'arborescence. Inclu les fichiers médias attachés comme les images et préserve les relations entre les enregistrements. Exporte uniquement dans un format spécifique à TYPO3 (soit en binaire ".T3D" soit en XML). Le format est prévu pour l'échange entre systèmes TYPO3.

en	Enable System Logging
fr	Activer le journal système

en	If you set this the system backend log will be filled with entries for all the actions that the import actually performs. By default this is left out for the sake of clarity.

en	Excluded elements
fr	Eléments exclus

en	By the "Exclude" checkbox you can exclude specific records from the preview display of the export. Which records has been picked for specific exclusion is listed here. You can also clear the exclusion configuration.
fr	En cliquant sur la case à cocher "exclure", vous pouvez exclure des enregistrements spécifiques à l'export prévu. Vous pouvez voir la liste des enregistrements à exclure ici. Vous pouvez aussi effacer les paramètres d'exclusion.

en	EXT:impexp/Resources/Public/Images/cshimages/excludebox.png
fr	EXT:impexp/cshimages/excludebox.png

en	Exporting records from TYPO3
fr	Exporter les enregistrements de TYPO3

en	To export TYPO3 T3D/XML files you click any record icon or page in the page tree (including the root page!), select "More options" and then "Export". This will bring up the export interface where you can configure options for your export session.
fr	Pour exporter un fichier TYPO3 T3D/XML, cliquez sur tout enregistrement ou page dans l'arborescence (y compris la page racine !), sélectionnez "Plus d'options" (nécessite que l'extension "extra_page_cms_options" soit installée) puis "Exporter en .t3d". Ceci vous amènera sur l'écran d'export dans lequel vous pourrez configurer les options pour votre export.

en	There are a number of methods by which you can export data from TYPO3: - Export a single page or branch of the page tree (use page icon context menu) - Export a single record from any page (use record icon context menu) - Export all records from a specific table on a specific page (using the Web>List module) - Export an arbitrary selection of records from the clipboard (using the Web>List module) The export format observes all TYPO3s methods for relations between the records in the export file. But you will have to configure how these relations are maintained, at least to some degree. Sometimes you would want to include records referred to, at other times you surely want to keep the original mapping. That depends on your objectives with the export. Regardless of your configuration for export you will always see a complete reflection of all chosen records and their internal relations in the preview display found in the bottom of the export module page. <b>Error messages:</b> Remember to consult the Message-tab before exporting if there are any error messages there!

en	EXT:impexp/Resources/Public/Images/cshimages/export.png, EXT:impexp/Resources/Public/Images/cshimages/export1.png, EXT:impexp/Resources/Public/Images/cshimages/export2.png

en	To export a page or record, simply click the icon and select "Export" from the context menu. With the Web>List module you can also export all records from a table by first clicking the table title to see only this table, then next to the CSV export you will find the export button for a T3D export of the table. You can export the contents of the clipboard as well by simply selecting "Export" in the menu.
fr	Pour export une page ou un enregistrement, cliquez simplement sur son icône et sélectionnez "Export" dans le menu contextuel. Avec le module Web > Liste, vous pouvez également exporter tous les enregistrements d'une table en cliquant sur le titre de la table afin de la sélectionner, puis en cliquant sur le bouton 3export T3D de la table" placé à côté du bouton "Export CSV". Vous pouvez exporter le contenu du presse-papier en utilisant "Export" dans le menu.

en	xMOD_tx_impexp:import

en	Extension Dependencies
fr	Dépendances des extensions

en	Select which extensions should be installed in the import system in order for your exported content to work correctly. Examples could be "templavoila" for templating, "fluid_styled_content" for the template, "tt_news" for a news archive etc.

en	During import warnings will appear for all selected extensions from this list which were not installed.

en	EXT:impexp/Resources/Public/Images/cshimages/extdep.png
fr	EXT:impexp/cshimages/extdep.png

en	File format options
fr	Options de format de fichier

en	You can export your records to a generic XML format which potentially can be imported by other applications. However, the schema of the XML is TYPO3 specific. Alternatively, you can select a TYPO3 specific binary format called "T3D".

en	Generally you should use the XML format. The T3D compressed format is usually smaller, but much harder to read and process. Entering a file name to save makes it possible to write your export directly to a file (pressing "Save to filename") instead of downloading it (pressing "Download export"). The correct file extensions depending on file format is automatically applied. Files are saved in a proper file mount in "fileadmin/". This is shown to you upon saving. Existing files are overwritten.

en	EXT:impexp/Resources/Public/Images/cshimages/fileformat.png
fr	EXT:impexp/cshimages/fileformat.png

en	Exclude resources from HTML and CSS files
fr	Exclure les ressources des fichiers HTML et CSS

en	When an HTML or CSS file is found as a soft reference the files are parsed for references to external media (such as images) and if any are found they are also exported. If you don't want this behaviour, click this option.

en	Notice: Resources found inside an HTML or CSS file are not analyzed further. For instance it means that any CSS files referred to from within an HTML will not be traversed - but CSS files referred to inside the Setup or Constant field of a TypoScript template record will be!

en	EXT:impexp/Resources/Public/Images/cshimages/htmlcss.png
fr	EXT:impexp/cshimages/htmlcss.png

en	In this example you can see that a soft reference has been found pointing to an HTML file inside fileadmin/ Since it was an HTML file it was parsed and further a number of files were found referenced inside it and now included with the export. This feature is specifically created to support export of template configurations where external HTML files play a role.

en	EXT:impexp/Resources/Public/Images/cshimages/impexp.png
fr	EXT:impexp/cshimages/impexp.png

en	Example of the preview display during export configuration of a page. Notice how records on the page are include plus how references inside the record is found and included as well (bottom of screen).
fr	Exemple de prévisualisation durant la configuration de l'export d'une page. Voyez comment les enregistrements d'une page sont inclus et comment les références à l'intérieur de ces enregistrements sont trouvées et inclues (bas de l'écran).

en	Importing TYPO3 records
fr	Importation des enregistrements TYPO3

en	To import TYPO3 T3D/XML files into the page tree you click any page in the page tree (including the root page!), select "More options" and then "Import". This will bring up the import interface where you can select a file to import or upload a new one.

en	<b>Tip: Import into a Folder</b> To make sure that no records are lost during the import, you can make yourself safe by importing into a Folder you create first. After the import you can move all records to the final destinations. An example of such a scenario is if you configured the export to include relations; In that case a number of records may follow the export outside the page tree structure you are exporting. To make sure that all of these external records are written to the database, importing into a Folder is a good idea. <b>Error messages:</b> Remember to consult the Message-tab before/after importing to see if there are any error messages there!

en	Select file to import
fr	Sélectionnez le fichier à importer

en	The files displayed are those with an extension T3D or XML from fileadmin/, fileadmin/export/ and your "TEMP" folder (if any).

en	EXT:impexp/Resources/Public/Images/cshimages/import_selectfile.png
fr	EXT:impexp/cshimages/import_selectfile.png

en	xMOD_tx_impexp:fileFormat

en	EXT:impexp/Resources/Public/Images/cshimages/import.png
fr	EXT:impexp/cshimages/import.png

en	xMOD_tx_impexp:export

en	Include relations
fr	Inclure les relations

en	Configure the tables from which you want to include records that are found as relations in the main export configuration.
fr	Configurez les tables à partir desquelles vous souhaitez inclure des enregistrements qui ont été trouvés dans les relations de la configuration principale du module d'export.

en	Background: When you export a record in TYPO3 it might contain relations to other records in the system. You have to tell the export interface what to do with these relations. Basically there are three scenarios: - If relations are found between records that are all in the export configuration, there is no problem: The relations are automatically mapped to the new id's of those records when imported. - If the records related to are not included the relation will be lost (indicated with an error message in the preview) unless you a) either select that table in this selector box in which case all relations to that table will be included or b) if you set the table as a static table (in which case the relation is untouched and imported as-is - but which will of course break if no record with that UID is found in the import system). <b>Soft References:</b> Soft references are when a record contains pointers to external files or records but in fields where there are no formal relation configured. Examples of this is when a content element contains a "&lt;link 123&gt;" tag that represents a link to the page 123. This is not picked up formally as a reference, but is found anyhow as a "soft reference". The same goes for &lt;img&gt; tags with images from eg. "fileadmin/". By default soft references pointing to records or files will act as normal references; either including the referenced item or showing an error. However you can also choose to exclude the handling of individual soft references or maybe set the value as "editable" upon import. This is done with a selector box in the export preview.

en	EXT:impexp/Resources/Public/Images/cshimages/references.png, EXT:impexp/Resources/Public/Images/cshimages/references1.png, EXT:impexp/Resources/Public/Images/cshimages/references2.png
fr	EXT:impexp/cshimages/references.png, EXT:impexp/cshimages/references1.png, EXT:impexp/cshimages/references2.png

en	This example shows tree examples of references; a) an image attached to a content element, b) a relation to a frontend usergroup UID, and c) a soft reference found in the bodytext field of a record, here it is the link-tag pointing to the page with UID 1. Notice in the previous image how the relation to the frontend user group was lost. This has been corrected in this screenshot where the fe_group table has been selected in the list of table for which to include relations. The result is that the frontend usergroup is included as a record outside the exported pagetree. If you wanted to keep the relation but not include the usergroup you have to set "fe_groups" as a static table instead. See below. This example shows a TypoScript Template Record where multiple soft references has been found. The first one is an email address. Here it is configured to be editable. This means that upon import the user will have a chance to edit the value before the import is actually done. This is very useful when exported files are used as templates. Another example includes a PHP script which we don't want to include in the export and therefore we have selected the exclude option for the soft reference.

en	Meta data setting
fr	Configuration des méta données

en	Set meta data for the export. This is highly encouraged if your exported content goes into eg. a template collection of sorts.

en	The meta data will help users of your exported files to know what they can expect to be inside and what things they should be aware of and take into account during import. The "Title" and "Description" should contain the basic information about the export. The "Notes" field can be used for additional details, especially remarks about intensions or requirements that apply.

en	EXT:impexp/Resources/Public/Images/cshimages/metadata.png
fr	EXT:impexp/cshimages/metadata.png

en	No presets found!

en	Notes

en	Import options
fr	Options d'importation

en	Various options for import.
fr	Diverses options pour l'importation.

en	<b>Do not show differences in records</b> When a structure has been imported you will see a difference view of all records which tells you whether the written content matched the import data or if not, what changed. In many cases content <i>should</i> change (eg. relations and file references) so it is not an error if you see red and green values. Basically the difference view is a feature you can use for visual validation of the import success. It brings piece-of-mind to those who is enlightened to understand what it tells... :-) Green strings represent the actual written data while red represents the original value from the import file and black represents data that is the same.

en	EXT:impexp/Resources/Public/Images/cshimages/impexp_misc3.png, EXT:impexp/Resources/Public/Images/cshimages/phpext.png
fr	EXT:impexp/cshimages/impexp_misc3.png, EXT:impexp/cshimages/phpext.png

en	Options for import. Here you are told that this PHP file cannot be allowed - because you didn't select the option "Allow to write banned file extensions (eg. PHP scripts), if any"

en	Configuration of page tree export
fr	Configuration de l'arborescence à exporter

en	Here you configure how a page or a branch of the page tree should be exported. Using the selector box you can set the number of levels of subpages to include in the export. By default all records belonging to a page is included when a page is exported.
fr	Vous pouvez configurer ici comment une page ou un branche de l'arborescence doit être exportée. En utilisant la boîte de sélection, vous pouvez définir le nombre de niveaux de sous-pages à inclure dans l'exportation. Par défaut, tous les enregistrements de la page sont inclus lorsque la page est exportée.

en	EXT:impexp/Resources/Public/Images/cshimages/pagetreecfg.png

en	Page Tree
fr	Arborescence des pages

en	Based on the levels selected for page tree export this will show the structure that is about to be exported. If any pages are specifically excluded by the exclude option they are not shown either.

en	Levels
fr	Niveaux

en	Here you select how deeply in the page tree from the current starting point to go for this export.
fr	À cet endroit, vous sélectionnez le niveau de profondeur de l'arborescence que vous souhaitez exporter

en	If you select "Expanded tree" it will base the export on the currently expanded levels of the page tree. Another special option is "Tables on this page" which will not include the page record itself but only include records from tables on the page, depending on the table configuration of course.

en	EXT:impexp/Resources/Public/Images/cshimages/impexp_misc.png
fr	EXT:impexp/cshimages/impexp_misc.png

en	Include tables
fr	Inclure les tables

en	When you export a page all records on the page is included by default. By this selector you can pick which tables to include exclusively if there are certain records you are not interested in seeing included.

en	In the box "Max number of records" you can set a limit to how many records are selected from a single table. This is a runaway brake in case you have an unusual large amount of records from a table.
fr	Dans le bloc "Nombre maximum d'enregistrements", vous pouvez paramétrer le nombre maximum d'enregistrements à sélectionner dans la table. Il y a un blocage dans le cas où vous sélectionnez un nombre inhabituel d'enregistrements dans la table.

en	Configuration presets
fr	Présélections de configuration

en	Enables you to save an export configuration for later re-use. Useful if you need to export the same configuration with regular intervals.

en	In the "Select preset" box you can select any previously saved preset to load. If you are exporting a page the presets listed will be those found for the start page ID. For records, any preset can be loaded. To load a preset, select it in the selector and press "Load". If you press "Merge" instead the settings from the preset will be merged with the current configuration. This is meaningful in cases where you select multiple individual tables or records. To save a preset, simply enter a title in the title box and press "Save". This will create a new preset. If you press save while having selected an existing preset you will overwrite it. To delete old presets, simply select it and press "Delete". The checkbox "Public" can be set if you want to share your preset with other users of the system. Otherwise they are personal to you.

en	EXT:impexp/Resources/Public/Images/cshimages/impexp_misc1.png, EXT:impexp/Resources/Public/Images/cshimages/impexp_misc2.png
fr	EXT:impexp/cshimages/impexp_misc1.png, EXT:impexp/cshimages/impexp_misc2.png

en	The preset selector in the export interface.

en	Single record

en	Export single record
fr	Exporter les enregistrements seuls

en	This overview tells you which independent records has been independently selected for export.

en	EXT:impexp/Resources/Public/Images/cshimages/singlerecord.png, EXT:impexp/Resources/Public/Images/cshimages/export2.png
fr	EXT:impexp/cshimages/singlerecord.png, EXT:impexp/cshimages/export2.png

en	The way to export multiple records like this is using the clipboard like shown below.

en	Set static tables
fr	Régler les tables statiques

en	Select which tables in addition to the static TYPO3 tables to keep relations untouched for. Takes precedence over "Include relations" configured tables.

en	By default all relations to static tables in TYPO3 are kept untouched. Of course those static tables should be present in the import system in order for this to work correctly. However there might be circumstances where you move information between two systems where theoretically non-static tables should just keep relations untouched. Examples could be "sys_languages" or TemplaVoila data structures / template objects where two systems might contain the same set of records in those tables while you are importing pages and content elements freely.

en	EXT:impexp/Resources/Public/Images/cshimages/static.png, EXT:impexp/Resources/Public/Images/cshimages/static1.png
fr	EXT:impexp/cshimages/static.png, EXT:impexp/cshimages/static1.png

en	In this example you see how a number of records are pointing to a System Language record which will become lost relations when imported because the record is not included in the export. However; in the target system the System Languages are exactly the same and therefore you just want a static mapping of the relations. The static mapping is obtained by selecting the "sys_language" table as a static template meaning that the relations are kept at their current values assuming that they will be exactly the same in the target system when imported.

en	Table export
fr	Exporter les tables

en	Export of all records on a page from a specific table. This is configured from the Web>List module where you will have to select table-only view and click a button in the top of the page.
fr	Exportation de tous les enregistrements de la page, pour une table spécifique. La configuration est faite dans le module Web>Liste, où vous devez sélectionner l'affichage d'une seule table, en cliquant sur le bouton "+" en dessus de la table.

en	Tip: You can select multiple table lists by simply saving each selecting as a preset and finally load/merge the selections together.

en	EXT:impexp/Resources/Public/Images/cshimages/tablelist.png, EXT:impexp/Resources/Public/Images/cshimages/export1.png
fr	EXT:impexp/cshimages/tablelist.png, EXT:impexp/cshimages/export1.png

en	Here two tables from different pages are selected. This is done by first selecting the one, saving it as a preset, then select the other and merge with the saved preset. Here you see how to use the Web>List module to export all records from a table on a page.

en	Icon
fr	Icône

en	Meta data
fr	Méta-données

en	Own
fr	Propriétaire

en	Owner
fr	Propriétaire

en	Page

en	Path
fr	Chemin

en	Public
fr	Publique

en	Preset title

en	Update instead of Insert
fr	Mettre à jour plutôt que d'insérer

en	By default the import operation inserts new records in the system. Using this option will update existing records.

en	There are certain requirements you have to meet if you want the "Update" process to work. The main thing is that the records updated are those with the SAME uid as the uid in the export file. Thus an update operation only makes real sense if the export and import systems are somehow related and the same UIDs can be expected in both ends. Otherwise it will be a mess! When you update page structures the import operation will automatically try to rearrange records so they also appear in the same hierarchy and order as in the export file. This can be disabled by checking the option "Ignore PID differences globally". In any case you can set individual records to Ignore/Respect the PID with a selectorbox in the preview. In the preview display you can also select if individual records should be flatly ignored during import or if you want them created as new records instead of being updates. As a help for managing updates the preview display will inform you about the path where the existing element with that UID is found. Use this to verify that you get what you expect! <b>Forcing the UID:</b> If you intend to update a system and some elements from the import are not mappable to a UID already (ei. does not exist) you can choose in the preview display to force the UID during creation. This is an unorthodox thing to do since UIDs are normally created automatically by the database. The option makes most sense if you are trying to "synchronize" a copy of another system. The option may mess up certain database internals and the feature is therefore only available for admins.

en	EXT:impexp/Resources/Public/Images/cshimages/impexp_misc4.png, EXT:impexp/Resources/Public/Images/cshimages/update.png
fr	EXT:impexp/cshimages/impexp_misc4.png, EXT:impexp/cshimages/update.png

en	In Update mode you can select various settings for each record. You will also be able to see a diff-view where the differences between the existing record and the one from the import is shown.

en	Upload import file
fr	Envoyer un fichier d'importation

en	Select a file to import from your local computer and upload it here. If the upload completes successfully you can immediately see its content displayed in the preview display.

en	Notice that there are usually limits set by the server (PHP) to the size of uploaded files. If hit, upload fails and an error message is shown.