Difference between revisions of "PT Article Editor Import Elements"
(Created page with '== Overview == The Article Editor App has several Custom Components defined within CommonSpot. These components are available in the Article Editor's "exported-objects" folder lo…') |
(→Import) |
||
| Line 10: | Line 10: | ||
'''Import Custom Element:''' | '''Import Custom Element:''' | ||
| − | # Article(Article-Custom-Element.zip) | + | # Article (Article-Custom-Element.zip) |
# articleEditor Configuration (articleEditor-Configuration-Custom-Element.zip) | # articleEditor Configuration (articleEditor-Configuration-Custom-Element.zip) | ||
| + | # Events (Events-Custom-Element.zip) | ||
| + | # Event-Mapping (Event-Mapping-Custom-Element.zip) | ||
== Verify Imports == | == Verify Imports == | ||
Latest revision as of 00:44, 15 April 2010
Overview
The Article Editor App has several Custom Components defined within CommonSpot. These components are available in the Article Editor's "exported-objects" folder located at the root of the Profile application directory (e.g. /ADF/apps/pt_article_editor/exported-objects/)
To import these objects, you will need to be an administrator for your site.
Import
Create a "Article Elements" category and import all portions of each component in the order listed.
Import Custom Element:
- Article (Article-Custom-Element.zip)
- articleEditor Configuration (articleEditor-Configuration-Custom-Element.zip)
- Events (Events-Custom-Element.zip)
- Event-Mapping (Event-Mapping-Custom-Element.zip)
Verify Imports
The imported components' render handlers and custom field types must be verified. During the import process, the render handler and custom field types paths may have been changed to reflect the current site's path.
Review and update these paths to reference the ADF path. In most cases, this will just require to be unlocked and a change in the path from the site name to 'ADF'. Check the paths for the custom field types that were imported with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
If the custom elements that are imported contain custom field types that are already in the site, the naming convention for the custom field type will be unique. To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type.
Example: The Photo Category custom element contains two uses of the General Chooser field type, if the General Chooser field type is already installed on the site then the import process will attempt to import another General Chooser but with a new name such as "General Chooser_import_1250003208472." To resolve this issue, open the custom element and assign the field type (General Chooser_import_1250003208472) to the field type with the simple name General Chooser. After reassigning the field type, delete the new imported field from the list of custom field types.
