Difference between revisions of "PT Import Content Ext App Configuration"
(Created page with '== Overview == The PT Import Content App uses an XML file to store site specific configurations. If you are installing the PT Import Content application, there is no need to d…') |
(→Configuration Fields) |
||
| Line 42: | Line 42: | ||
force_subsite_name_lcase | force_subsite_name_lcase | ||
force_page_name_lcase | force_page_name_lcase | ||
| + | |||
[[Category:PT Import Content]][[Category:Site Configuration]] | [[Category:PT Import Content]][[Category:Site Configuration]] | ||
Revision as of 15:41, 28 March 2011
Overview
The PT Import Content App uses an XML file to store site specific configurations.
If you are installing the PT Import Content application, there is no need to do anything with this element at this time. The fields will be updated as your proceed through the installation steps.
The fields for the PT Import Content Configuration custom element are defined below.
Setup
Follow the steps to implement the configuration XML file:
- Locate the ptImport.xml in the applications folder: /ADF/apps/pt_import_content/site_files/config/ptImport.xml
- Copy this file into the sites configuration directory (create the directory if it does not exist): /_cs_apps/config/ptImport.xml
- Reset the ADF.
Configuration Fields
pageDataDSN source_dsn generalContentTemplate new_content_container old_content_container content_dashboard_url job_create_url job_detail_url job_cancel_url import_job_view import_job_type_view import_job_item_view import_job_item_table job_error_datasheet_url job_history_url run_per_pass run_pause_mins subsite_mapping_source subsite_mapping_view page_mapping_view content_mapping_dashboard_url content_detail_url content_mapping_source document_mapping_view image_mapping_view tools_action_form site_source_path force_subsite_name_lcase force_page_name_lcase
