Difference between revisions of "PT Import Content"
From ADF Docs
| Line 1: | Line 1: | ||
[[PT Import Content Installation|Installation]] | [[PT Import Content Installation|Installation]] | ||
[[PT Import Content Known Issues and Bugs|Known Issues and Bugs]] | [[PT Import Content Known Issues and Bugs|Known Issues and Bugs]] | ||
| + | |||
| + | == Overview == | ||
| + | The PT Import Content project will allow CS Owners to easily import content via the Content Creation API. The basic controls are to import subsites based on a formatted spread sheet and to import page content into Formatted Text Blocks. Imported content for subsites and pages can be re-imported and modified. | ||
| + | |||
| + | == General Process == | ||
| + | The Import process looks like this: | ||
| + | # Import Subsite content into the Subsite Mapping Custom Element | ||
| + | # Process the records in the Subsite Mapping Custom Element [create subsites] | ||
| + | # Import Page content into the Page Mapping Custom Element | ||
| + | # Process the records in the Page Mapping Custom Element [create pages] | ||
| + | # Fix Page links | ||
| + | |||
| + | == Getting Started == | ||
| + | * [[PT Import Content Installation | Installation]] | ||
| + | * [[PT Import Content Customize Subsite Map data | Customize Subsite Map data]] | ||
| + | * [[PT Import Content Customize Page Map data | Customize Page Map data]] | ||
| + | |||
| + | == Components == | ||
| + | * [[PT Import Content ImportController | ImportController]] | ||
| + | === Subsite === | ||
| + | * [[PT Import Content SubsiteController | SubsiteController]] | ||
| + | * [[PT Import Content SubsiteMapDAO | SubsiteMapDAO]] | ||
| + | * [[PT Import Content SubsiteDAO | SubsiteDAO]] | ||
| + | |||
| + | === Pages === | ||
| + | * [[PT Import Content PageController | PageController]] | ||
| + | * [[PT Import Content PageMapDAO | PageMapDAO]] | ||
| + | * [[PT Import Content PageDAO | PageDAO]] | ||
| + | |||
| + | |||
| + | == Troubleshooting == | ||
| + | |||
| + | == [[PT Import Content Known Issues and Bugs | Known Issues/Bugs]] == | ||
| + | |||
| + | == Tasks == | ||
| + | * Delete pages needs CSSecurity integration | ||
| + | * Delete Page and Subsite Mapping content needs CSSecurity integration | ||
| + | * Update Page Mapping - set NeedsUpdate = 1 (to reprocess content) | ||
| + | * Fix Links Method for PageController.cfc | ||
| + | |||
| + | |||
| + | === Reports === | ||
| + | * Pages Mapped | ||
| + | * Subsites Mapped | ||
| + | * Subsites Created | ||
| + | * Subsites Needed to be Created | ||
| + | * Pages Needed to be Updated | ||
Revision as of 16:46, 18 December 2009
Installation Known Issues and Bugs
Contents
[hide]Overview
The PT Import Content project will allow CS Owners to easily import content via the Content Creation API. The basic controls are to import subsites based on a formatted spread sheet and to import page content into Formatted Text Blocks. Imported content for subsites and pages can be re-imported and modified.
General Process
The Import process looks like this:
- Import Subsite content into the Subsite Mapping Custom Element
- Process the records in the Subsite Mapping Custom Element [create subsites]
- Import Page content into the Page Mapping Custom Element
- Process the records in the Page Mapping Custom Element [create pages]
- Fix Page links
Getting Started
Components
Subsite
Pages
Troubleshooting
Known Issues/Bugs
Tasks
- Delete pages needs CSSecurity integration
- Delete Page and Subsite Mapping content needs CSSecurity integration
- Update Page Mapping - set NeedsUpdate = 1 (to reprocess content)
- Fix Links Method for PageController.cfc
Reports
- Pages Mapped
- Subsites Mapped
- Subsites Created
- Subsites Needed to be Created
- Pages Needed to be Updated
