Header Tabs

### Overview

This is your friendly ATContentTypes tool. It is a frontend to several important functions like

Version migration
  used to migrate ATContentTypes to a newer version just like the `plone_migration` tool
Image scales
  to recreate image scales
Type Migration
  to migrate old CMF style types to new ATContentTypes types
Recatalog
  to recatalog CMF and ATCT content types. Types migration requires an up to date `portal_catalog`.
Properties
  to set certain properties for migration, album view and more

### Version information

#### File System

#### Plone Site

### Properties

`image_types`
  A list of portal type names to be treated as image. The types must be AT based, have an image field named `image` and implemented the `IImageContent` interface with the api methods `getImage()`, `setImage()` and `tag(scale=None)`.
`folder_types`
  A list of portal types to be treated as subalbums in the photo album view.
`album_batch_size`
  The default batch size for the photo album view.
`album_image_scale`
  The default image scale name for the photo ablum view.
`single_image_scale`
  The default image scale name used when showing a single image.
`migration_catalog_patch`
  Use the portal catalog patch for migration. Enabling the patch might increase the migration speed dramatically. Especially folder migration speed can gain up to several 100%.
`migration_transaction_size`
  Amount of objects before a subtransaction, full transaction or savepoint is created. A lower value will slow down migration but decrease the memory usage. A higher value could increase the amount of objects you have to migrate again in the case of an error.
`migration_transaction_style`
  `None`
    Don't use any special transaction handling. A subtransaction is going to be committed after `migration_transaction_size` in order to decrease the memory usage.
  `full transaction`
    A full transaction is going to be committed after `migration_transaction_size` objects are migrated. In a case of an error you can resume the migration at the last full transaction. There is a slim chance that this setting can corrupt your database
  `savepoint`
    Requires Zope 2.8.1 or higher! A savepoint is created after `migration_transaction_size` objects are migrated. In the case of an error the transaction is rolled back to the last savepoint. All objects migrated between the last savepoint and the error are reverted to their original state. After the migration is finished you should fix the error and migrate the remaining old objects.

### README

footer